Podcasts about Sha

The show also discussed Olympic champion Sha’Carri Richardson avoiding jail time after reaching a plea agreement in her Florida speeding case. Richardson, who was accused of driving more than 100 mph, was ordered to pay a fine, complete community service, and take a driving course, prompting a conversation about accountability, safety, and learning from mistakes. See omnystudio.com/listener for privacy information.

The Rickey Smiley Morning Show tackled some of the biggest entertainment and culture stories making headlines, starting with news that a new Joe Jackson docuseries is headed to BLK Prime. Developed and narrated by Marlon Jackson, the eight-episode series will explore the late Jackson family patriarch’s rise from Gary, Indiana, to managing one of music’s most successful dynasties while also addressing the long-running debate about his parenting and management style. The show also discussed Olympic champion Sha’Carri Richardson avoiding jail time after reaching a plea agreement in her Florida speeding case. Richardson, who was accused of driving more than 100 mph, was ordered to pay a fine, complete community service, and take a driving course, prompting a conversation about accountability, safety, and learning from mistakes. The entertainment buzz continued with details about The Real Housewives of Atlanta, as Andy Cohen shot down rumors that Shamea Morton was being fired or that NeNe Leakes was returning, signaling that Bravo is standing behind the current cast heading into the next season. The show also weighed in on the controversy surrounding Tuskegee University’s new dress code, which bans items such as bonnets, durags, and bedroom slippers in classrooms and certain campus spaces while requiring students to maintain more professional attire. Supporters say the policy is about workplace readiness and upholding the institution’s historic standards, while critics argue the university should focus more attention on student housing concerns and other campus issues. Elsewhere, the crew debated whether people in relationships can truly have a best friend of the opposite sex, shared personal stories about trust and boundaries, and mixed in their trademark humor, commentary, and listener calls that kept the conversation lively throughout the morning. Website: https://www.urban1podcasts.com/rickey-smiley-morning-show See omnystudio.com/listener for privacy information.

Based on the teaching of Sha'arei Kedusha, Rebbe Chayim Vital.

Most cryptographic findings on your vulnerability report will never be exploited by a real attacker. So why do they keep showing up — and why should you still fix them?In this episode of the Cyber Threat Perspective, Brad Causey and Jordan Natter break down OWASP Top 10 A04: Cryptographic Failures — the entry they openly call their least favorite on the list. They explain why SWEET32, BEAST, and the other scary-sounding named TLS vulnerabilities almost never translate into real-world compromise, why platforms like Security Scorecard and BitSight inflate their severity anyway, and where genuine cryptographic risk actually lives.Jordan also walks through a real penetration test finding: a JSON Web Token signed with HS256, an exposed configuration backup sitting on the web server, and the signing secret that turned a standard user into an administrator.In this episode:- Why A04 dropped on the OWASP Top 10 without becoming less important- The difference between exploitable risk, hygiene risk, and brand reputational risk- An honest take on Security Scorecard and BitSight scores — what they measure, what they miss, and why a perfect score can coexist with a weak password policy and no MFA- The two halves of A04: data in transit (TLS/HTTPS, integrity, tampering) and data at rest (secure storage of credentials, PII, and payment data)- What a JWT actually is, and why pen testers love pulling them apart- Real pen test story: exposed config backup → leaked JWT secret → signature tampering → privilege escalation to admin- Broken server-side signature validation and other improperly implemented cryptography- Why MD5 and SHA-1 still show up for password storage 20 years too late — and what to use instead (Argon2, scrypt, bcrypt)- HSTS, secure renegotiation, and certificate expiration as A04 subcategories- The coffee shop scenario: the full chain of conditions required to exploit SWEET32 — including roughly 250 GB of captured traffic — and why no one has ever documented it happening in the wild- Why a decade-plus-old vulnerability in your environment says more about your vulnerability management program than about your crypto- Quantum computing: how today's theoretical attacks may not stay theoreticalThe takeaway: classify your data, choose modern algorithms, retire deprecated protocols, and keep a functioning vulnerability management program. Not because a threat actor is sitting in your local coffee shop waiting to derive your session key — but because leaving decade-old findings in place is a signal about everything else you might be missing.Next up: OWASP A05, which Brad promises is way cooler than A04.Blog: https://securit360.com/blog/Podcast: https://securit360.buzzsprout.com/YouTube: https://www.youtube.com/@SecurIT360Contact: https://securit360.com/contact/Have a topic you want us to cover? Send it our way.Blog: https://offsec.blog/Youtube: https://www.youtube.com/@cyberthreatpovTwitter: https://x.com/cyberthreatpovFollow Spencer on social ⬇Spencer's Links: https://spenceralessi.comWork with Us: https://securit360.com | Find vulnerabilities that matter, learn about how we do internal pentesting here.

In today's episode, Gastor and Shalewa talk about their world view changing with age, open AI hacking itself, and Sha shares her love for Electric Dreams.PATREON LAUNCH!For all those that have asked how they can help support the pod - it's finally here! Thanks again to all the Troops and Correspondents who rock with us. Check it out - we'll have some exclusive content and fun perks, plus it really does help!⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠patreon.com/WarReportPod⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠Many Thanks to our Patreon Troops & Correspondents for helping us bring this show to life. Shouts to the Correspondents!Tanya WeimanFontayne WoodsMark OrellanaB. EmmerichCharlene BankAskewCharlatan the FraudCynthia PongKen MogulSayDatAgain SayDatAgainLaKai DillStephanie GayleUncleJoe StylenoshCato from StonoJennifer PedersenMarcusSarah PiardAna MathambaJSKnoLooking to further support? Help our data storage/archiving needs here: ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠https://www.amazon.com/hz/wishlist/ls/23X55OW4CFU8Y?ref_=wl_share⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠Instagram:@WarReportPod@SilkyJumbo@GastorAlmonteTwitter:@SilkyJumbo@GastorAlmonteTheme music "Guns Go Cold" provided by Kno of Knomercyproductions Twitter: @Kno Instagram: @KnoMercyProductions

Send us Fan MailVictor, Evelyn, and Mark hang out this week to do a drinking show for the veterans and the To Live and Talk in LA homies SHOWED OUT. The gang talks about meeting celebrity crushes, dying to mobile toilets, cutting your own hair, and play a round of pot luck Am I The Asshole.

In this presentation, Hashem Morvarid turns to an underexplored archive — Shia ḥadīth and devotional literature — to build a typology of mystical experience. Moving through phenomenology, metaphysics, and epistemology, he examines how texts like Nahj al-Balāgha and al-Munājāt al-Shaʿbāniyya describe heart-based perception, and what marks distinguish authentic experience from delusion.

Quantum Blockchain Technologies PLC (AIM:QBT, FRA:BYA1) CEO Francesco Gardin joined Proactive's Stephen Gunnion to discuss the company's ASIC UltraBoost technology, its expected US patent grant and the commercial opportunity ahead. Gardin said the patent process should conclude within four to six weeks of fees being paid, though the company remains cautious until the grant is officially issued. The technology targets the hardware implementation of Bitcoin's SHA-256 algorithm, an area where meaningful advances have been rare, and is estimated to reduce logic gates by 5%-8% while cutting energy consumption by 2%-5%. "According to our estimate, the saving is between 5 and 8% in terms of logic gates. In terms of energy, it's between 2 and 5%," Gardin said, adding that across large-scale mining operations the cumulative impact could be substantial. The company is already working with an ASIC manufacturer and is seeking specialist semiconductor expertise to structure licensing and royalty agreements. With the potential buyers clearly identified as ASIC chip makers, Gardin said the pathway to commercialisation is well defined. Watch the full interview to hear Francesco Gardin discuss the patent timeline, ASIC UltraBoost's potential efficiency improvements and Quantum Blockchain Technologies' commercial strategy. Visit the Proactive YouTube channel for more interviews with listed companies, and don't forget to like this video, subscribe to the channel and enable notifications so you never miss future updates. Read Proactive's Editorial Policy here: https://www.proactiveinvestors.co.uk/pages/editorialPolicy #QuantumBlockchainTechnologies #QuantumBlockchain #FrancescoGardin #Bitcoin #BitcoinMining #ASIC #ASICUltraBoost #Semiconductors #Patent #IntellectualProperty #CryptoMining #BlockchainTechnology #EnergyEfficiency #MiningTechnology #Proactive

The sprint finals delivered on every promise. Noah Lyles ran a world-leading 9.79 and Sha'Carri Richardson put on a show in the women's 100m. The 800m prelims produced some genuine surprises.We discuss:FINALS:- Women's 100m — Sha'Carri Richardson, 10.77: Richardson was in a different gear, pulling away from the field by halfway to win in 10.77 — equaling her season's best and breaking the Icahn Stadium record. Star Athletics teammate Kayla White was second in 10.90, Tamari Davis third in 11.00. Richardson has now won three of the last four U.S. 100m titles.- Men's 100m — Noah Lyles, 9.79: Lyles delivered when it mattered most — his eighth USATF outdoor title and a wind-legal world lead of 9.79, equaling his lifetime best. Ronnie Baker ran a strong season's best of 9.88 for second, Kenny Bednarek third just 0.005 seconds behind Baker, also at 9.88.PRELIMS:- Women's 400m heats: Aaliyah Butler leads all qualifiers winning heat 2 in 50.53, Sanaria Butler won the final heat from lane 1 in 51.10. Alexis Holmes took heat 1 in 51.71. Britton Wilson grabbed the last final spot in 52.12.- Men's 400m heats: Christopher Bailey (45.14) looks like the favorite after a win from an inside lane. The big news — 2024 Olympic champion Quincy Hall fails to make the final, finishing sixth in 46.47. Hall has struggled all season.- Men's 800m heats: Cooper Lutkenhaus and Hobbs Kessler go 1-2 in heat 1 in 1:45.83 and 1:45.93; Wes Ferguson leads all qualifiers with a fierce homestretch move to win in 1:45.17; Atlanta Track Club goes 1-2 in another heat — Sean Dolan (1:46.11) and Camden Marshall (1:46.40); Defending champion Donavan Brazier fails to advance, finishing fourth outside the time qualifiers in 1:46.93.- Women's 800m heats: Roisin Willis takes heat 1 in 1:59.83, overhauling Meghan Hunter in the final 50 meters; A tactical heat 2 produces only two qualifiers — Nia Akins (2:01.78) and Juliette Whittaker (2:02.22) advance. Ajee' Wilson finishes third in 2:02.45 and does not make the final; High school standout Paige Sheppard of Union Catholic (NJ) runs 2:00.99 for fifth in heat 1 — fast enough for the last time qualifier spot, putting a high schooler in the final alongside the pros.

Before the internet could become a place to bank or transact, it needed a way for strangers to know who they were talking to, and whether a message could be trusted. Turing Award winners Ron Rivest, Adi Shamir, and Leonard Adleman helped invent it. In this episode of First Principles, Rivest tells the story of how they developed RSA, the first practical public-key cryptosystem. Their breakthrough made it possible to encrypt information, verify identities, and authenticate messages across an open network without requiring participants to meet or exchange a secret in advance — laying essential groundwork for the secure internet and, decades later, blockchains. Rivest joins Tim Roughgarden, Head of Research at a16z crypto and Professor of Computer Science at Columbia University, and Dan Boneh — Professor of Computer Science at Stanford University, a16z crypto Senior Research Advisor, and the “B” in BLS signatures — for a conversation about the origins and future of modern cryptography. They trace the field from its early days, when most cryptographic research was classified and even the meaning of “security” had not been formally defined, through the publication of the Diffie-Hellman paper and the open problem that ultimately led to RSA. Rivest recounts the night the core idea came together, why the difficulty of factoring made the system plausible, and why no one initially knew whether it would survive sustained attempts to break it. The conversation also explores the other cryptographic primitives that underpin blockchains and the modern internet. Rivest explains why digital signatures interested him even more than encryption, how he designed the MD family of cryptographic hash functions, and why standards such as RSA, DSA, and SHA were shaped as much by politics, patents, and government pressure as by mathematics. Finally, Rivest shares his unusually candid views on quantum computing, post-quantum security, and the deeper theoretical possibility that P could equal NP. Either development could threaten the foundations of modern cryptography — but, as Rivest argues, cryptographers have a responsibility to prepare for even the worst-case scenarios. Highlights 00:00 – Intro: the two problems that could break modern cryptography 01:10 – Why Ron Rivest's work underpins the internet and blockchains 08:10 – Before public-key cryptography, there was no theory of security 11:05 – The open problem that led to RSA 13:55 – The night Ron Rivest discovered the core idea behind RSA 17:55 – Why digital signatures were the real breakthrough 19:14 – The RSA challenge — and a prediction that was off by quadrillions of years 28:33 – How government pressure shaped cryptographic standards 30:36 – Designing the hash functions that made digital signatures practical 33:26 – The Fiat–Shamir transformation, explained 38:04 – Building a cryptography company before the web existed 42:31 – Will quantum computers ever become powerful enough to break RSA? 48:02 – The cryptography securing the internet, elections, and everyday life 50:11 – What surprised Dan: Quantum giveth and quantum taketh away About First Principles First Principles is a special limited series from a16z crypto about the scientific roots of modern computing — especially blockchains — told through rare conversations with the pioneers who helped shape the foundational ideas behind distributed systems, consensus protocols, economics, mechanism design, cryptography, zero knowledge, and more. People often tell the story of the Bitcoin whitepaper as if it appeared out of nowhere. But the ideas behind Bitcoin — and blockchains more broadly — come from decades of computer science, economics, mathematics, and cryptography. First Principles is a guide to that lineage, as told by the people who helped build it. Subscribe to follow along: https://www.youtube.com/playlist?list=PLjQ9HCQMu_8yIg60YAq67HDdvp7E_T5e8 Hear more from: Ron Rivest: https://people.csail.mit.edu/rivest/ Tim Roughgarden: https://twitter.com/Tim_Roughgarden Dan Boneh: https://twitter.com/danboneh Follow a16z crypto: X: https://twitter.com/a16zcrypto LinkedIn: https://www.linkedin.com/showcase/a16zcrypto/posts/ YouTube: https://www.youtube.com/@a16zcrypto Substack: https://a16zcrypto.substack.com/subscribe/ As always, none of the following should be taken as investment, business, legal, or tax advice. Please see a16z.com/disclosures for more important information, including a link to a list of our investments. Hosted by Simplecast, an AdsWizz company. See pcm.adswizz.com for information about our collection and use of personal data for advertising.

One of the tests in bitachon comes when we become convinced that our salvation has to come through a specific person, a specific organization, or a certain circumstance. We know Hashem can help us, but deep down we think there is only one path to accomplishing it. It is up to us to realize that Hashem never needs any specific avenue to bring a yeshuah. It can always come in infinitely more ways than we could ever imagine. I read a story about R' Rabinowitz from Israel whose young daughter was born with a deformity in her leg. After three successful surgeries in Los Angeles, there was only one operation left. The final surgery would allow her to walk normally for the rest of her life. The family naturally assumed that just as the insurance company had paid for the first three surgeries, it would pay for the fourth and final one as well. But then they were told they had reached the coverage limit. The insurance company had already paid over a million shekels and refused to pay any more. The family tried everything they could. They appealed to the Ministry of Health. They contacted different askanim. They hired a lawyer. They met with a medical specialist whose opinion they hoped would help their case. But everything they tried did not work. Even the specialist's report actually worked against them. It appeared that the entire future of their daughter's treatment depended on one thing—convincing the insurance company to change its mind. They did not become discouraged. The family strengthened themselves in bitachon. They learned Sha'ar HaBitachon every day. They accepted upon themselves to become more careful with berachot and answering Amen, and they poured out their hearts to Hashem in tefillah. The rabbi's wife would spend time alone speaking to Hashem in her own words, thanking Him for all the kindnesses He had already shown them and asking Him to continue helping them. Then one of their children said something that completely changed their perspective. "Why do we keep asking Hashem that the insurance company should pay? What difference does it make who pays? Hashem can pay for the surgery even without the insurance company." Those simple words made a tremendous impact on the entire family. So often we become attached to the messenger instead of the Sender. We think the yeshuah has to come in a certain way, and when we see that it is not going to come that way, we begin to feel that hope is lost. But Hashem is never limited by a messenger. If one avenue proves not to work, we must know that Hashem has endless ways—ways that we never even knew existed—to help us. This family continued making normal hishtadlut, but now they did it with the understanding that the source of their salvation was not their hishtadlut and it was not the insurance company. They did what they had to do, and they knew the outcome was in Hashem's Hands. They asked the surgeon for a discount since the insurance wasn't going to cover the surgery, and amazingly, he gave them a fifty-percent discount—something the secretary said she had never seen in forty years. They were then connected with a free-loan fund that agreed to help them. One day, while walking somewhere, the rabbi met a childhood friend who connected him with a wealthy donor in New York who agreed to cover the entire cost of the surgery. Then, just as they landed in Los Angeles, they received a phone call informing them that the Ministry of Health had reversed its decision and approved full funding for the surgery. Hashem gave them multiple solutions all at the same time. Initially, they thought everything depended on the insurance company, but Hashem showed them that He has unlimited ways of helping. He can give a discount on the surgery. He can provide a loan. He can send a wealthy donor. He can cause the insurance company to change its mind. Whenever we find ourselves thinking, "If only this person says yes," "If only I get this deal," or "If only this opportunity works out," we should remember the child's simple words: "What difference does it make who pays?" Our job is to do normal hishtadlut and then understand that Hashem will send the yeshuah in the way that He wants. And He has infinitely more ways to do it than we could ever imagine.

VP of Marketing & Commerce Sha Atakhanov has been driving growth and innovation at homepathic brand Boiron for almost 17 years. From booking some of the first ads on Amazon to being an inaugural brand running shoppable ads on Samsung TVs, , Sha oversees all the channels and media that touch the consumer, and he approaches new opportunities and tech, especially AI, with a simple rule - it has to generate revenue, save time, and save money. And have some fun while you're at it.

What makes a good comic book character? What makes them stand out? What comes first; the character or the story? Those are just some of the questions we answer this week as we delve into one of the most enjoyable sides of comic creation. Also there's some birthday chat, some spider-man chat and plenty of great comics and books to check out, including one by one of comics greats! Great stuff to check out: Spider-Man, Batman, The Punisher, The Fantastic Art of Ron Turner, Comics Assemble, Sha, Pat Mills, Men of the Cloth, Hellbound Media, The Gods and Monsters of Headgrave, Frank Miller: Push the Wall, Retail Park, Underg Planet Atmos: Exordium, Mad Cave Comics, Blood Force

把丹东、集安和珲春三个点连起来，眼前是鸭绿江、图们江，以及一条如今看上去再清楚不过的中朝边界。可把时间拨回康熙、光绪，河流大体未改，人们理解“边界”的方式却已经完全不同。边境从来不只是地图上的一条线。它还管人从哪里来、到哪里去，以及谁有资格把一片土地叫作“我们的”。本期《东亚观察局》，沙青青与清华大学教授宋念申从新书《劃界：在圖們江製造現代東亞（1881–1919）》谈起，追索图们江流域如何在清朝、朝鲜、日本与俄罗斯的角力中变成现代边境。康熙年间的勘界与19世纪末的划界有什么差别？国际法带来的究竟是平等，还是一套由帝国分配资格的规则？间岛、满铁调查和殖民知识又怎样重新定义土地与人口？话题最后落到延边朝鲜族的双重认同，以及历史学面对现实焦虑时，究竟该做什么。- 聊天的人 -宋念申（清华大学人文与社会科学高等研究所教授）沙青青（公众号：13号埋立地、小红书：Sha-13号埋立地）- 时间轴 -03:16 从鸭绿江转向图们江09:00 中朝划界不仅是国界问题，更是一场东亚现代转型12:20 康熙也曾勘界，那条“界”跟今天理解的一样吗19:10 “王朝地理”：山川、礼制与政权合法性如何连在一起22:45 边界既是分隔，也是连接：越垦、边市与灰色地带30:30 帝国主义时代，谁才配做国际法的主体33:45 “间岛出兵”与万宝山事件：殖民扩张前的一次次预演38:55 内藤湖南、宋教仁、申采浩：东亚知识分子如何替国家想象版图44:36 1949年以后，中朝边界为何要放进国际社会主义运动中来理解48:38 延边朝鲜族的身份问题：国籍、族裔和“同胞”之间52:43 “比朝鲜更朝鲜”的延边，与东北抗联的共同革命经验55:55 双重认同并不矛盾：“我是中国人”，同时珍视本民族文化59:00 中华民族共同体不是结果，而是仍在发生的过程61:30 一百多年前的历史惯性，为什么仍牵动今天的东亚- OP -@RayHan- ED -朝鲜族民歌《红太阳照边疆》- Logo -Shane- 收听方式 -推荐您使用小宇宙app、苹果播客、喜马拉雅、网易云音乐、蜻蜓FM等平台订阅收听《东亚观察局》- 剪辑 -沙青青- 出品・制作 -番薯剥壳工作室（Yakimo Studio）

The Daily Dose of Bitachon: Overcoming the Barriers to Tov Hashem Lakol Welcome to our daily dose of Bitachon. Today, we are discussing the impediments and barriers that prevent us from truly understanding the theme of the month of Av: Tov Hashem Lakol —God is good to all. Barrier #2: The Illusion of "Ownership" ( Hergel ) In the introduction to Shaar Habechina (The Gate of Reflection), the Chovos Halevavos explains the second major barrier to our appreciation of God's goodness. When we enter this world, we do not yet possess our full intellect. We grow up surrounded by God's constant benefits. Because we are so accustomed to them, they become regilos (habitual), viyiduos (known), and we view them: כאילו הן עצמיות להם — "As if they are our very essence, inseparable from us." We tell ourselves: "That is just who I am. My house, my hearing, my health—these are not extra gifts; they are my essence." As we grow older and our minds mature, we fail to appreciate these gifts because we are too used to them. We don't pay attention, and we don't say thank you because we view them as a given. We feel entitled. The Prophetic Warning of Hergel (Habit) The Chovos Halevavos brings a proof text from the prophet Hoshea: "And I accustomed Efrayim..." (Hoshea 11:3) While the Radak explains this as God gently training a child to walk step-by-step, followed by the tragedy of: "And they did not know that I healed them," The Chovos Halevavos reads tirgalti through the lens of hergel (habit). God is saying: "I did good for Efrayim, but they became so accustomed and used to it that they stopped recognizing Me." This is directly related to the destruction of the Beis Hamikdash ( churban ). In Parashas Va'eschanan , the Torah warns: "When you beget children and grandchildren, and you have grown old in the land (venoshantem ba'aretz)..." (Devarim 4:25) When you get "old" and settled in the land, everything becomes routine. You lose your freshness, you stop paying attention, and you take the goodness for granted. We don't see God because we are too "used to" our stomachs, our kidneys, and our eyes. The Kuzari's Rule of Appreciation: If you want to appreciate something, imagine life without it Think of a toothache or a bad knee. When it hurts, you would give anything to fix it. But when it works perfectly, do you ever stop to think about it? The Root of Exile: A Lack of Da'as (Contemplation) Yeshayah Hanavi (Isaiah) describes the spiritual decay that led to our exile ( galus ): "Woe to those who rise early in the morning to chase strong drink, who stay up late into the night inflamed by wine. They have lyres, harps, drums, flutes, and wine at their parties..." (Yeshayah 5:11-12) What was their actual sin? The prophet continues: "But they do not look into the deed of Hashem, and the work of His hands they do not see." Because they drowned themselves in physical distractions, they failed to look at creation. The consequence? "Therefore, My nation goes into exile for lack of knowledge (da'as)." Our exile came directly from a failure to contemplate God's creation. Kriyas Shema and the Destruction of Jerusalem In the Gemara ( Shabbos 119a ), Abaye states: "Jerusalem was destroyed only because they neglected the recitation of the morning and evening Kriyat Shema." Why is Kriyat Shema (and its accompanying blessings) the pivot point? Because Kriyas Shema is the designated time to look at God through the lens of creation. Rav Wolbe ( Alei Shur , Vol. 2, p. 59): We must train ourselves to look into Hashem's creations. This is the very purpose of Birchot Hashachar (the morning blessings), Pesukei Dezimra , and the blessings of Kriyat Shema (where we introduce the declaration of God's unity by praising Him as the Creator of light and darkness). The Chofetz Chaim ( Shmiras Halashon , Vol. 2, Ch. 2): It is fitting for a person to contemplate creation at least once a day. Because it is a constant mitzvah, we should set aside a specific time for it—ideally after prayers and before eating, treating it with the same urgency as any daily obligation. Rashi ( Shabbos 119a ): Commenting on the failure to look at creation, Rashi writes that they did not set their hearts "to unify His name over His creations." This is exactly what we do during Kriyas Shema when we declare Hashem Echad (God is One). The Sefer Barak Hashachar : What is the difference between Yabitu (looking) and Ra'u (seeing)? Yabitu means to look carefully. The deeper providence ( hashgacha ) of Hashem requires deep contemplation. Ra'u means to see. God's basic handiwork is obvious to anyone who simply opens their eyes. Reclaiming Our Perspective Why is this the foundation of everything? The Chovos Halevavos teaches that the foundation of our entire relationship with God is Sha'ar Habechina (Reflection). If I do not actively see how much God gives me, how can I feel any obligation to reciprocate? Why should I serve Him? If I take my house, my life, and my health for granted as "mine," then I feel no gratitude. This is why we are commanded to love God: "With all your heart, with all your soul, and with all your possessions (me'odecha)." Why must we love Him with our possessions? Because we identify so strongly with our money and our belongings that they become "us." We take it all for granted. We think, "Of course I have a house, lights, and a car. What, would God leave me without them?" "Celebrate Life!" In Megillas Eichah, it says: "Why should a living man complain? A man of sins?" (Eichah 3:39) The Gemara ( Kiddushin 80b ) explains: What are you complaining about? Adam chai —you are alive! Even with all your sins, God is keeping you alive. Celebrate life! The Schindler's List Analogy (from Rabbi Avigdor Miller zt"l): Imagine a man standing in a concentration camp line. Oscar Schindler comes over and says, "I can get you off this line and save your life. But there are conditions: You will live in a tiny, cramped apartment. Your children will have learning challenges. Your wife will occasionally be difficult." What would that man say? He would grab the pen and sign on the dotted line instantly! He would scream: "Life! I'm alive!" This is how we must look at our lives every single day. I know a man who, due to a severe kidney illness, was unable to relieve himself normally for a long time. When he was finally healed and could say the blessing of Asher Yatzar naturally, he was so overwhelmed with joy that he got into his car and drove eighty miles an hour down the avenue, thrilled to be alive. We should feel that exact thrill every day. Summary of the Hurdles To develop a true Tov Hashem Lakol attitude, we must overcome the major hurdles: Hurdle The Core Issue The Bitachon Remedy Hurdle #1 The desire for more (What we discussed yesterday). Focus on what you have, not what is missing. Hurdle #2 Taking what we have for granted (Viewing God's gifts as our natural essence). Use the "Rabbi Miller lens" to contemplate daily miracles (our eyes, kidneys, and breathing). Part of our spiritual work during these days of Av is to repair the source of our national ruin by looking at the world with fresh eyes, recognizing Hashem's handiwork, and choosing to live with deep, conscious gratitude. Have a wonderful, appreciative day!

Welcome to Daily Bitachon The theme of the month of Av is based on a Pasuk (verse) in Ashrei : "Tov Hashem Lakol" —God is good to everybody. This is a critical concept. The Gemara ( Yoma 9b ) teaches that the primary difference between the first Beis Hamikdash (Temple) and the second Beis Hamikdash came down to Bitachon (trust in God). A lack of Bitachon was a core reason behind the destruction. The Foundation of True Reliance In Chovos HaLevavos ( Sha'ar Bitachon ), the author explains that to truly rely on someone, you must know that they possess ultimate, unceasing generosity and kindness—regardless of whether you are deserving or undeserving. No human fits this description. That quality belongs solely to Hakadosh Baruch Hu , God's generosity is all-inclusive, and His kindness surrounds all. The proof? "Tov Hashem Lakol." Furthermore, in Sha'ar HaBechina , the Chovos HaLevavos emphasizes that God's kindness includes everybody . "Everyone" doesn't mean "most"—it means every single creation. You can take that Pasuk to the bank. Yet, rabim k'ivrim me-hakirun —most people are blind to this reality. Even if they do realize it, mavin godel tovatan , they fail to grasp how immense it is. They don't truly delve into it ( ve'einam maskilim ) for three main reasons. Barrier #1: The Cycle of Desires and Arrogance What is the first major barrier that stops us from appreciating these three words, "God is good to all"? We are entirely consumed by worldly pleasures, personal desires, and a hyper-focus on what we lack. Instead of seeing what we do have, we are totally absorbed in the massive hope of fulfilling what we don't have. The Endless Chase: Whatever a person reaches, they immediately want the next level. The wonderful gifts they already possess become small and limited in their eyes. The Comparison Trap: A person begins to think that anything someone else possesses was somehow taken away from them. The underlying spiritual cause of this is sobering. Tehillim 10:4 states: "Rasha (the wicked one), kegovah apo (because of his arrogance), bal yidrosh (he is not searching for God)... God is not on his mind." Our innate arrogance makes us feel entitled to everything. When we feel entitled to everything, anything we lack feels like a deprivation. We look at others and think, "I was supposed to have that." Meanwhile, the staggering miracles we already possess are brushed aside: A beating heart? Meh. Working knees? Okay. Fully functioning kidneys? So does everybody else. On the black market, the organs inside your body right now would cost a fortune—yet we take them for granted. Rabbi Addis once noted that when you go grocery shopping on an empty stomach, you buy everything in sight because you feel empty inside. You think you need a lot to be happy. But once you eat just a little bit, you are satiated. The problem is we don't even focus on the "little bit" we already have. We adopt the attitude of Esav, who demanded, "Pour it down my throat." We search for treasures on the other side of the world when they are sitting right in our own homes. Two Lessons on Perspective 1. The Treasure Under the Sink There is a famous story about a poor man living in Yerushalayim (Jerusalem) who dreams of a pot of gold buried under a specific bridge in Vienna. He scrapes together his last coins and travels all the way to Vienna. As he paces back and forth by the bridge, a local guard stops him and asks what he's doing. The man confesses his dream. The guard laughs and says, "You Jews and your silly dreams! I had a dream last night that there was a pot of gold buried under the kitchen sink at Alfandari 18 in Yerushalayim. Do you think I'm going to travel all that way?" The man freezes. Alfandari 18 was his own address. He immediately travels back home, digs under his sink, and finds the treasure. The Message: People think they have to go to Vienna to find fulfillment, but the pot of gold is already inside their own home. 2. Rabbi Akiva and the Gift of Straw The Gemara ( Masechet Nedarim 50 ) tells of Rabbi Akiva and his wife, the daughter of Kalba Savua. Her father disowned her and cut off her inheritance for marrying Akiva. They were so poor they slept on a floor covered in straw. Every morning, Rabbi Akiva would gently pick the straw out of her hair and say with hope, "One day, I am going to give you a golden tiara." One day, there is a knock on the door. It is Eliyahu HaNavi (Elijah the Prophet) disguised as a regular beggar. He says, "Do you have any spare straw? My wife just gave birth, and I have absolutely nothing to put her on." They gladly gave him some of their straw. Afterward, Rabbi Akiva turned to his wife and said, "Look at that—that person doesn't even have straw, and we do." The Insight: Eliyahu HaNavi came down from heaven. Why didn't he just give them a gold coin instead of taking their straw? Because Eliyahu HaNavi was giving them something far more valuable than gold: a lesson in attitude. If he had given them gold, they simply would have wanted more gold. By showing them someone who lacked even the bare minimum, he taught them to appreciate the wealth they already had.

The Book of Acts in the Bible reports various activities in the lives of the Emissaries {Apostles} meaning “sent one's” – those sent by Yah and Yahooshua to bring the Good News {Gospel} to others -- primarily Sha'ul {incorrectly Paul}Emissaries exist today just the same but many are not recognized as such. -- The book of Acts is generally attributed to Luke, the writer of the Good News according to Luke – this is Part 7Relationship With Creator is broadcast live Fridays 12Noon – 1PM ET and Music on W4CY Radio (www.w4cy.com) part of Talk 4 Radio (www.talk4radio.com) on the Talk 4 Media Network (www.talk4media.com). Relationship With Creator is viewed on Talk 4 TV (www.talk4tv.com).Relationship With Creator Podcast is also available on Talk 4 Media (www.talk4media.com), Talk 4 Podcasting (www.talk4podcasting.com), iHeartRadio, Amazon Music, Pandora, Spotify, Audible, and over 100 other podcast outlets.Become a supporter of this podcast: https://www.spreaker.com/podcast/relationship-with-creator--3198941/support.

Today we preview the upcoming Monaco Diamond League which goes down on Friday July 10th and will have high quality matchups including Gabby Thomas, Julien Alfred and Adaejah Hodge in the 200m as well as Oblique Seville, Marcell Jacobs and Jordan Anthony in the 100m. We also preview the upcoming Ed Murphy Classic which will have Samuel Ogazi vs Quincy Wilson in the 400m.Finally, we discuss the competition between Melissa Jefferson-Wooden and Sha'carri Richardson, two of the fastest women in the world going head to head throughout 2026.Monaco Entries: https://monaco.diamondleague.com/en/programme-results/Ed Murphy Classic entries: https://edmurpheyclassic.com/athletes ⁠ -------------------------------------------

This show has been flagged as Clean by the host. This series is dedicated to exploring little-known—and occasionally useful—trinkets lurking in the dusty corners of UNIX-like operating systems. In UNIX Curio #8 ( HPR episode 4657 ), I talked about using standard utilities to compare files. Left unmentioned, however, was a method commonly used today—the hash function. As I've stated in previous entries, while I am an engineer, I don't have a background in computer science, so my understanding of the mathematics is limited. But I can give a practical description of what a hash function does. It takes an input, performs a set of calculations on it, and produces an output. As hash functions are practically used, the input is a set of bytes, such as a file or another piece of data like a password. The output is a numerical value in a fixed range—most often, expressed as hexadecimal characters. Because this "hash value" can always be represented in a certain number of bytes, its length as printed is usually a constant number of characters, padded with leading zeros if necessary. This episode will not cover the use of hashes in programming, focusing instead on using them to validate data. A hash function, or more specifically, a cryptographic hash function, has an additional property. It should be very difficult to predict what changes to the input would be required to produce a specific change in the output. An older, related concept is called a "checksum". While these are designed to vary when the input data is damaged or digits are transposed, they do not necessarily have that last property mentioned for cryptographic hashes. You have probably already encountered a checksum, even if you didn't recognize it. On a 16-digit number assigned to a Mastercard or Visa 1 credit or debit card, the first six digits identify the card issuer (such as a bank), the next nine digits are assigned to you by the issuer, and the last digit is a check digit. The check digit is calculated using the values of the previous 15 digits, and it is a simple way to avoid typos in entering a card number. In another example, every Ethernet frame that your devices send or receive includes a checksum 2 to help ensure that the contents weren't scrambled in transit. This is 32 bits long and is called a cyclical redundancy check, commonly referred to as a CRC. A CRC is also used in many other places—for example, the .zip file format includes one for each archive member, and this allows a program extracting files from the archive to identify if any were damaged. Our UNIX Curio for today is another example, the cksum utility 3 . It generates a 32-bit CRC based on the Ethernet algorithm. It operates on either a named file or standard input and outputs the CRC value, the length of the input, and the pathname if a file was given as an argument. Unlike most modern hashing programs, the checksum is printed as a decimal integer and is not padded, so it can be anywhere from one to ten digits long. The length value is the number of bytes in the input (actually specified as the number of octets , as systems could potentially use a byte that isn't eight bits long), also expressed as a decimal integer. There are two major ways that one could use cksum to check the validity of a file. First, if you are transferring a file from one UNIX-like system to another, you could run cksum against it on both systems and check that the CRC and length are the same. The utility can also be given multiple filenames as arguments, which would generate a list that can then be compared. The second way would be for someone publishing a file or set of files to also publish the CRC values, lengths, and names so that people downloading them could verify that they match. However, I don't think the practice of publishing lists like this really started until more recent hash functions like MD5 and SHA-1 came about so it is unlikely that anyone would publish CRC values instead. The advantage of these tools should be pretty obvious in comparison to cmp , one of the utilities discussed in UNIX Curio #8. To verify a file using cmp , you need two files to compare—if you're trying to check a large file you downloaded, you would need to spend the time and bandwidth to download a second copy. And if they didn't match, you would have no idea which of the two, if either, was correct. By contrast, cksum is quicker to run, doesn't require downloading a massive amount of excess data, and if run against the original file, makes clear what the correct value is. This utility is a follow-on from a program called sum , which operated very much the same. I had a bit of trouble tracking down the exact development history, but what seems clear is that two different variants 4 were popular: a BSD version and a System V version. Both output 16-bit checksums, but used different algorithms so they didn't give the same results. Also, the BSD version printed the length of the input data as the number of 1,024-byte blocks, while the System V version instead gave a count of 512-byte blocks. (Some sources claim that System V sum generates a 32-bit checksum 5 , which could possibly be true internal to the algorithm, but I have tested several independent implementations of the utility and all of them output a 16-bit value for both the System V and BSD algorithms.) From what I can tell, the BSD version 6,7 came first; it was in 3BSD but probably appeared even earlier. An identical copy of BSD's sum was included with UNIX/32V 8,9 , which was AT&T's 1979 port of Seventh Edition UNIX to the VAX and became one of the ancestors of System III. The divergence seems to have started with System III, released in 1980; its version of the sum utility 10,11 changed to a new default algorithm, though it could be made to use the BSD algorithm via the -r option. System V looks to have kept the same behavior as System III. It's not clear to me why this algorithm is universally called the "System V algorithm" rather than the "System III algorithm"; perhaps it is because System V saw much more widespread use. Instead of trying to reconcile these differences, the POSIX committee decided to create a new utility with a unique name, use a separate algorithm entirely, and avoid the block-length dispute by printing the length in octets instead of blocks. I should point out that POSIX states that the CRC algorithm for cksum does not strictly meet the mathematical definition of a "checksum". I don't know enough to say exactly why it doesn't qualify or to say whether either of the sum algorithms do. However, in less-formal usage the term "checksum" has gathered the meaning of any value used to represent or validate a set of data, so I am fine with using it no matter the technical details of the algorithm. When two different inputs produce the same checksum or hash value, this is called a "collision". Because the output value has a limited range, there are an infinite number of possible inputs that could produce a collision. From a practical standpoint the possibilities are more limited—the majority of these inputs are larger than the number of atoms in the universe, which can't fit on any machine. Unlike a cryptographic hash algorithm, the CRC is not specifically designed to resist an attacker crafting a malicious input that would cause a collision. However, it should be sufficient to detect accidental damage. Programs implementing more modern cryptographic hash algorithms are superior to the checksum utilities in avoiding collisions (whether malicious or accidental), but there are still three advantages that the older programs have. First, a system running a historical operating system might not have the hash programs available, but is more likely to have cksum or sum already included. Second, the checksum values are much shorter than the hashes output by the newer programs, making them easier for a user to compare by looking at them. This advantage is not as great as it might appear at first, because a common way to check a hash these days is to save a list of hashes and filenames—the hash programs can use that and do the comparison themselves, sparing the user from having to validate it character by character. The third advantage is that cksum prints the input length in bytes. This greatly limits the number of inputs that could be maliciously crafted to create a collision. I did a moderate amount of research on implementations of modern cryptographic hash algorithms and found that some, such as MD5, SHA-1, and SHA-2, do use the length of the input (often termed "message length" in the literature) as part of the material fed in to the algorithm, but none of the hashing utilities present this length to the user as part of its output. There are two possible reasons for this that seem evident to me. First, if one is hashing a password, you would certainly not want to give a clear indication of its length—that would give any attacker a massive head start on guessing the password. However, that doesn't explain why one would avoid printing the input length for a file that is made publicly available. Second, it is convenient in many contexts, such as database entries or in software (such as git ), for the hash to be a fixed length. Including an extra value that can be of variable length would complicate those use cases. However, the length value could simply be dropped and they would be no worse off than they are currently. Historically on UNIX, password hashing was treated differently from checksumming files— the crypt() function 12 was used for passwords while sum and later cksum were used to confirm a file's integrity. So even rather early on, these two use cases employed algorithms with different properties, but I haven't dived into the history deeply enough to know how intentional this was. My discussion in this episode focuses on the file use case, so understand that I'm largely avoiding the topic of password hashing. Digital signatures are yet another use case, one that I'm ignoring entirely. Every few years, some security researcher declares a particular hash algorithm to be "broken" and that everyone should move over to a new one, which generally has a longer hash. While the larger hash space certainly reduces the opportunity for collisions, this disrupts workflows, such as publishing information about software releases by e-mail, which still tends to observe a 78-character limit on each line 13 , making it harder to include a list of hashes with filenames next to them. This is in addition to the work of modifying software and scripts to use the new algorithm and managing how to treat past data. It seems to me that publishing the input length along with the hash would make it far more difficult to craft a malicious input that matches both, but I haven't found discussion of that during my investigation. (See the Appendix for a possible implementation.) Perhaps someone listening can record a response episode for HPR explaining that. References: Payment card number https://en.wikipedia.org/wiki/Payment_card_number Ethernet frame: Frame check sequence https://en.wikipedia.org/wiki/Ethernet_frame#Frame_check_sequence Cksum specification https://pubs.opengroup.org/onlinepubs/009695399/utilities/cksum.html GNU coreutils manual: sum https://www.gnu.org/software/coreutils/manual/html_node/sum-invocation.html FreeBSD 15.0 sum manual page https://man.freebsd.org/cgi/man.cgi?query=sum&sektion=1&manpath=FreeBSD+15.0-RELEASE+and+Ports 3BSD sum manual page https://www.tuhs.org/cgi-bin/utree.pl?file=3BSD/usr/man/man1/sum.1 3BSD sum source https://www.tuhs.org/cgi-bin/utree.pl?file=3BSD/usr/src/cmd/sum.c UNIX/32V sum manual page https://www.tuhs.org/cgi-bin/utree.pl?file=32V/usr/man/man1/sum.1 UNIX/32V sum source https://www.tuhs.org/cgi-bin/utree.pl?file=32V/usr/src/cmd/sum.c System III sum manual page https://www.tuhs.org/cgi-bin/utree.pl?file=SysIII/usr/src/man/man1/sum.1 System III sum source https://www.tuhs.org/cgi-bin/utree.pl?file=SysIII/usr/src/cmd/sum.c Crypt specification https://pubs.opengroup.org/onlinepubs/009695399/functions/crypt.html RFC 2822: Internet Message Format: Line Length Limits https://datatracker.ietf.org/doc/html/rfc2822#section-2.1.1 OpenSSH 10.1 released https://lwn.net/ml/all/dd12623ae86aa5eb@cvs.openbsd.org/ Appendix The MD5 hash algorithm was (and still is) widely used, but many people characterize it as being "broken" and discourage its use. Let us imagine a variant of this, called MD5.L, where the normal MD5 hash is followed by a "." character and the input length expressed as a hexadecimal number. Take, for example, the e-mail message announcing the release of OpenSSH 10.1 14 . At the bottom, it includes an SHA-1 hash and an SHA-2 256-bit hash for the available gzipped tar files. That longer hash is encoded with Base64 because if it were given as a hexadecimal number, it would make the line longer than 78 bytes. The MD5.L hash of the file would be one character shorter than the SHA-1 hash, as shown below. (The extra length of the name makes them both consume the same number of characters. The hashes shown are for the "portable" version of OpenSSH.) Some people claim SHA-1 is also broken, seeking to have people use newer and longer hash functions. For an attacker to compromise MD5.L in this example, they would not only have to create a valid tar file compressed with gzip containing a malicious payload having the right MD5 hash, that file would have to be exactly 1,972,831 bytes long (the decimal equivalent of 1e1a5f). While there are still many possible inputs that could be tried (256 1972831 , to be exact*), this is far fewer than the infinite possibilities for plain MD5, SHA-1, or SHA-2. If for some reason it is super important to have a fixed hash length, let's imagine another variation called MD5+L. In this one, instead of L being the input length, it is the input length modulo one terabyte (2 40 bytes), which can be represented by 10 hexadecimal characters, left-padded with zeros. While this approach substantially increases the number of possible inputs an attacker could try, it is likely that an intended victim would notice that the file they downloaded is larger (or smaller) than expected by that much. The MD5+L hash is longer than a SHA-1 hash, but still shorter than a 256-bit SHA-2 hash. SHA1 (openssh-10.1p1.tar.gz) = 7fd17b99d1beffb47cd380d64079e920bb0bd91f SHA256 (openssh-10.1p1.tar.gz) = ufx6K4JXlGem8vQ+SoHI4d/aYU3bT5slWq/XAgu/B1g= MD5.L (openssh-10.1p1.tar.gz) = 80dd9bb00a86519934710d05903fdf07.1e1a5f MD5+L (openssh-10.1p1.tar.gz) = 80dd9bb00a86519934710d05903fdf07+00001e1a5f Of course, if MD5 is considered to be too weak even with the inclusion of the length, one could produce a ".L" or "+L" version of any hash function. However, longer hashes will end up running into the 78-character limit. *This is a number with 4.75 million digits that the bc utility on my laptop took almost 5 minutes to calculate. Provide feedback on this episode.

Steven Holl and partners Dimitra Tsachrelia Holl, Olaf Schmidt, and Roberto Bannurs join Architectural Record's DESIGN:ED Podcast to discuss their expansion into Asia through their Beijing office, the design process through their small team of twenty-five designers, and Steven reflects on the the past 50 years of SHA

Audio Transcript Elders here and I get the privilege of preaching for you guys this morning. So quick announcement before we get too far. It is a holiday weekend, so we don't have our full kids ministry as usual. So we have, we'll get all the kids in here today. So we got snacks and activities over there kind of where you walk in and then if, if, you know, I got four boys, we only got two here today. So I get it. If they get a little antsy and we need some more room to run, you can go through this back door here, you know, kind of turn back around this way. But we have a meeting room down there where I think the service is projected and just, just some space for the kids to move and you can still follow along with the service. So, yeah, like I said, my name is Rob Fisher, one of the elders here, privileged to. Privilege to preach for you guys today. And so every summer we try to give Aaron, our main teaching pastor, the at least eight weeks off or so out of the pulpit. We think it's important for a couple reasons we want, you know, the Bible says that elders should be, should be able to teach. So we try to get all the elders in here and we also elevate. We elevate preaching, not the preacher. You know, we think it's important not to. We love Aaron. We love the faithful week. He does faithful work. He does week in, week out. But we think it's important to, to be developing other voices and not just be only receiving the word from, from one guy. Now I will say Aaron is preaching his campground this weekend. So they've done a lot of faithful ministry there and we're excited they can do that. So just an overview today we're continuing our series through the book of Exodus. So we're in Exodus chapter 6 today. So we'll start out by reading the text. We'll pray together. Then we're going to work through the text together really line by line. And Lord willing, after we're done working through it, we'll put some main points to it and some themes and we'll see how God is going to use the life and the story of Moses to inform us how we should live in the here and now. Right? So again, we're in Exodus chapter 6 today. We can go ahead and turn there. Continue, continue to the book of Exodus. We're doing this summer. We're going to follow the life of Moses. God has been calling him to be a, to be a part of delivering the Israelites out of Egypt. And we're going to we're going to pick up here in chapter six. So this is the word of the Lord. But the Lord said to Moses, now you shall see what I will do to Pharaoh. For with a strong hand, he will send them out. With a strong hand, he will drive them out of his land. God spoke to Moses and said to him, I am the Lord. I appeared to Abraham, to Isaac and to Jacob as God Almighty. But by my name, the Lord, I did not make myself known to them. I also established my covenant with them, to give them the land of Canaan, the land in which they lived as sojourners. Moreover, I have heard the groaning of the people of Israel whom the Egyptians sold as slaves. And I have remembered my covenant. Say therefore to the people of Israel, I am the Lord. And I will bring you out from under the burdens of the Egyptians. And I will deliver you from slavery to them. I will redeem you with an outstretched arm. With great acts of judgment, I will take you to be my people. And I will be your God. And you shall know that I am the Lord, your God, who has brought you out from under the burdens of the Egyptians. I will bring you into the land that I swore to give to Abraham, to Isaac and to Jacob. I will give it to you for possession. I am the Lord. Moses. Thus. Moses spoke thus to the people of Israel. They did not listen to Moses because of their broken spirit and harsh slavery. So the Lord said to Moses, go in. Tell Pharaoh, king of Egypt, to let the people of Israel go out of his land. Moses said to the Lord, behold, the people of Israel have not listened to me. How then shall Pharaoh listen to me? For I am of uncircumcised lips. The Lord spoke to Moses and Aaron and gave them a charge about the people of Israel and about Pharaoh, king of Egypt. To bring the people of Israel out of the land of Egypt. Now these are the heads of their fathers houses. The sons of Reuben, the firstborn of Israel. Hanak, Palu, Hezron and Carmi. These are the clans of Reuben. The sons of Simeon, Jamil, Jamin, Ohad, Jakin, Zohor and Sha'. Ul. The sons of the Canaanite woman. These are the clans of Simeon. These are the names of the sons of Levi according to their generation. Gershon, Kohath and Merari. The years of the life of Levi being 137 years. The sons of Gershon, Libni and Shimei. By their clans, the sons of Kohath, Amram, Ishar, Hebron and Uziel. The years of the life of Kohath being 133 years. The sons of Merari, Mahil and Mushi. These are the clans of the Levites according to their generations. Amram took as his wife Jochebed, his father's sister, and she bore him Aaron and Moses. The years of the life of Amram being 137 years. The sons of Izar, Korah, Nepheg and Zikri. Don't know about that one. Sons of Uzziel, Mishael, Elsaphan and Sitri. Aaron took as his wife El Shaba, the daughter of Amminadab and the sister of Nahshon. And she bore him Nadab, Abuhu, Eleazar and Ithamar. The sons of Korah, Asir, Elkanah and Abiasaph. These are the clans of the Korahites. Eleazar, Aaron's son, took as his wife one of the daughters of Phutiel, and she bore him Phinehas. These are the heads of the fathers, houses of the Levites by their cleans. And these are the Aaron and Moses, to whom the Lord said, bring out the people of Israel from the land of Egypt by their host. It was they who spoke to Pharaoh, king of Egypt, about bringing out the people of Israel from Egypt. This Moses and this Aaron. And on this day, when the Lord spoke to Moses in the land of Egypt, the Lord said to Moses, I am the Lord. Tell Pharaoh, king of Egypt, all that I say to you. But Moses said to the Lord, behold, I am of uncircumcised lips. How will Pharaoh listen to me? Let's pray. Lord, you're grateful for your word. Grateful that we get to learn from it and study it. We're grateful that your word, it studies and examines us as we study and examine it. Grateful for the life of Moses and the story of Moses. We pray that we would be faithful learners of it. We're grateful that you've sustained this church. And we ask that you would. I ask that you would help me speak your truth. Clearly. We don't come here just out of. Simply out of practice. We want it to be beneficial for the building up of your church, beneficial for the equipping of your saints. And. Yeah, we just pray that it's for your glory and for the. For the good of. For the good of those who know you. And it would be a means of evangelism for those who don't. So it's in Jesus name we pray. Amen. So Exodus 6 is just a. It's just one chapter in the larger Moses narrative, right? So before we can focus on the, on the details of this passage, we have to remember where it sits within the larger story. So if we come to chapter six, without considering the setting of Moses life and his calling and the recent events, we're going to miss a lot of the weight of what God says here. So the Bible, right, is first and foremost a book about God and God's work to bring redemption, restoration to a fallen and rebellious and sinful people. And in this section of Exodus, though, God is in the process of bringing his people out of slavery in Egypt, and he's using Moses as his church chosen instrument. And because of that, we get this kind of like mini biography of Moses. So chapter six should be read as a chapter within a larger story. It is an isolated scene, but we can't. We can't really understand that isolated scene without the broader context, right? So before we work through chapter six, we need to. Just briefly, I want to look back briefly at Moses life and just see what's brought him to this moment. So, so Moses was an Israelite boy. He was born into an Israelite family while the Israelite nation is enslaved in Egypt, right? And when he was born, there's an Egyptian decree that says, you know, all the Israelite boys need to be killed. The Israelite nation is becoming too strong. Moses, however, was miraculously saved by his mother. He's eventually adopted by the Egyptian royal family, and he grows up in the Egyptian royal household. He's 40 years old. He's an adult. And Moses, he's somehow knowing that he's actually an Israelite, and he's seeing the slavery and the oppression of the Israelites, his true people. He stops an Egyptian who was beating an Israelite by murdering the Egyptian, right? And the day after his murder, Moses realizes he's like, I am in trouble. So he flees, he settles in a foreign land. He lives out. And he lives out 40 years, the next 40 years, right, as a shepherd in Midian. So he has a Midian wife, he has a Midian family, he has an occupation, and he's made a life for himself in this. This foreign land. Now, while Moses is being a shepherd, he has an encounter with God. God charges him to be the means by which God takes the nation of Israel out of Egypt. And in that encounter, Moses raises a lot of objections about his own shortcomings for the tasks. We're going to get into more. We're going to get into more of those shortcomings as we continue. But just know that Moses had a lot of questions and concerns about the task that God is giving him. And in response to Moses concerns and questions, God gives Moses powerful signs and miracles to demonstrate his power. And God also gives Moses the help of his brother Aaron to act as Moses spokesman, since Moses is always expressing his concern over his inability to speak well. Right? So that initial exchange between God and Moses is like all of chapter three and half of chapter four. Then at the end of chapter four and through most of chapter five, Moses then is acting on God's command to go back to the people of Israel who are enslaved in Egypt, and then to Pharaoh and to tell them that, you know, God is going to bring them out of Egypt, right? So Moses and Aaron, initially, they go to the elders of Israel. They tell them, God is going to deliver you from Egypt. And obviously this is well received, as we can imagine. And the Bible says the people believed and bowed their heads and they worshiped. But next, in chapter five, the end of chapter five, Moses and Aaron take their message to Pharaoh. And it goes about as well as we can imagine. So we covered last week. It was. It was far from well received by Pharaoh. Pharaoh does not let the Israelites go. And instead of letting them go, he increases their workload. So the Israelite work leaders take their complaints to Pharaoh. Pharaoh receives them without a shred of sympathy. And the Israelite slaves, then they turn their frustration towards Moses and Aaron. And that's seen at the last, at the end of chapter five. Here. This is the last scene that we have before we go into where we're starting today, into chapter six. So I'm going to read you these verses that lead up to where we're going to start from today, so we can get a grasp on the setting here. So Exodus 5, 20, 23 says they met Moses and Aaron. This is the. They say the Israelite foreman who are waiting for them as they came out from Pharaoh. I just can imagine the scene. Moses and Aaron are outside the meeting room. They're just like, oh my gosh, this is not going good, right? And they say to them, the Lord look on you and judge you because you have made a stink in the sight of Pharaoh and his servants. You've put a sword in their hand to kill us. Moses turned to the Lord and said, lord, why have you done this evil to this people? Why did you ever send me? Since I came to Pharaoh to speak your name, he's done evil to this people, and you have not delivered your people at all. So again, the background matters here, because chapter six Begins with Moses discouraged. The people are downcast and Pharaoh is unmoved. So when God replies to Moses, he's replying to, you know, he's replying to his chosen instrument. Moses is still chosen, but the chosen instrument is once again, he's questioning God's plan. He's questioning God's timing, he's questioning his own calling. So we enter chapter six. Keep this God's. Chapter six is God responding to this mood in Moses. And he's answering Moses's frustrations and fears. So in response to Moses complaints, God is gonna, he's gonna reply to Moses questions, not directly, but rather he's gonna call. He's gonna call back to his previously stated purposes. So God is, there's, there's kind of a short answer in verse one, and then there's the long answer in verses two through eight. So verse one says, the Lord said to Moses, now you shall see what I will do to Pharaoh. With a strong hand, he will send them out. With a strong hand, he will drive them out of his land. So the short answer is that God is going to use his strong hand. And this verse, right, the verse is a good reminder to be a good and thorough student of the Bible, right? If we read this over too quickly in this translation of the Bible, it's like it's not clear who the strong hand belongs to, if it's God or Pharaoh. But if you look in the commentaries or the translation, it says the first and second strong hand, it's God. This is all God's work. And this is similar language to the initial conversation between God and Moses at the burning bush about this, how this interaction would go. So like Moses first encounter with God at the burning bush, it lays out how the deliverance process is going to go. And we don't see all the details of the narrative laid out in the in the burning bush conversation, but we see, we can see most of the narrative cover. So Exodus 3, verses 19 and 20. We also, God is using the similar language to convey, to lay out the extraction process of how it's going to go. He says, I know the king of Egypt will not let you go unless compelled by a mighty hand. So I will stretch out my hand, my hand again, and strike Egypt with all the wonders that I will do in it. And after that, he will let you go. So this, this repeated language matters, right? The strong hand, the mighty hand, the outstretched arm, it all points us to the same truth. Israel's deliverance is only going to come by God's power, right? Israel's deliverance is only going to come by God's power. So when we think about verse one, it's just important to see that God is clearly stating that the deliverance of his people will be by his power, his mighty, strong and active outstretched hand. It's important to note that it's not from the willpower of Moses over Pharaoh, and it's not from the generosity of Pharaoh either. Right? The Israelite people can only be on. They're only going to be delivered by the workings of a strong and all powerful God. And the people will be led by Moses, he says, but only because Moses is the man that God chose to be the messenger. So the people would be freed by Pharaoh, but only because of the more powerful and strong mighty hand of God that he showed over the stubbornness of Pharaoh. Right? So God's short answer to Moses is that my promise is not wavered. Moses says, why me? Why is this so hard? Why can't we make any progress, right? God essentially says this. He says, keep watching what I will do. So the current difficulty Moses finds himself in, it's not evidence that God's plan has failed. It's actually evidence that things are going to according to plan. Like Pharaoh will not be easily moved. This was laid out at the burning bush, right? So in God's short answer to Moses in verse one, that's, that's the short answer in verse one. But now let's look at the longer answer, verses two through eight. So as I was reading and I was meditating on this task, being prepared for this, I was just struck again at how God's lengthier reply to Moses groaning again. It's a repetition of something that's already been laid out in the Moses narrative, right? It's been laid out in God's conversation with Moses at the burning bush. So looking at verses four and five, it says, I established my covenant with them to give them the land of Canaan. And I heard people's groanings as slaves. And I remembered my covenant. I remembered my covenant. The same language that Moses uses. So Moses wrote all this when he writes the end of chapter two. At the end of chapter two, just this huge turning point in the narrative, you know, Moses has established himself in the land of Midian. Meanwhile, business as usual, we can say, continues in Egypt. And the rest of the nation of Israel is still under the oppression of Egyptian slavery, right? Chapter 2, verse 23 and 24 says, the people of Israel are crying to God for help to be freed from slavery. And God hears their Cries the key words here. God remembers his covenant with his people. God remembers his covenant with his people. After that, the narrative turns and God calls Moses at the burning bush. Right then, in the burning bush encounter between God and Moses, God twice recalls his covenant to give the land of Canaan to the offspring of Abraham. And that covenant is going to pull us way back to Genesis 12, the Abrahamic covenant in which God promises. Abraham says, your offspring will inhabit the land of canaan. So Genesis 12 is really the basis of the Exodus narrative because it's setting, it's establishing the promise that God's people will have a home where they can live and prosper and worship the true God. Now, keep working forward through verses 6, 7, and 8, God is gonna. He's gonna drive the details of this promised home even further. It's his promise to his people to remember the covenant, right? So verse six says, I, God, I'm going to free you from Egyptian slavery. And we see the imagery of God again here says, I'm reaching out and pulling his people out of slavery with an outstretched arm. In chapter four, God says, I'm going to use a mighty hand. In the beginning of chapter six, he says, I'm going to use a strong hand. And now here in chapter six, verse six, God says, it's worth an outstretched arm with great acts of judgment, right? In verse seven, it says, you will be my people, I will be your God, and you will know that I brought Israel out of slavery. And finally, verse 8 reminds us of the covenant that God made with Abraham. Says God, the promise that God would give the land of Canaan to the Israelites. Okay, so that's our first eight verses of this chapter. And this narrative is going to continue in verse nine. And Moses is going to start taking action on these commands next. But before we get into that, let me just look it back on these eight verses. I want to summarize as best I can here. So verses one through eight, they're. They're God's reply to Moses's grumblings, really, at the end of chapter five. And so if this were like. So I was thinking about this. This is a TV show. It's divided into episodes, right? Chapter 5 ends with. With Moses in the depths. He's standing outside of the meeting place if the Israelite foreman had just brought their failed appeal to Pharaoh. And so, like, right before the credits roll, Moses is just discouraged. He's frustrating. He's wondering why his obedience to God's commands have only made things worse. And I was thinking about this, the Bible doesn't tell us. We don't get any physical demonstrations from Moses in this moment. So I can only imagine it from my own experience. But I'll just say this, if you don't know me, I've worked in construction management for the last. Trying to remember now, 6, 7, 8 years now 9 out of 10 days wear work boots, jeans, a butt down shirt and a hat. When I need to look more presentable, I just don't wear the hat. Okay? Right. But when something goes wrong on a job site, which believe it or not, sometimes happens, right, the person responsible, usually me, you have to figure out what happened, we have to figure out how to fix it. You have to figure out how long it's going to take and then you have to explain it to everybody involved. Right. And then sometimes when multiple things go wrong at once, like my hat comes off, it's a good thing to throw when you're frustrated, right. And your hands go through, your hands go through my hair like this, right. And you're just going, I don't know anything, I don't know anything about anything. Right. But this is like, this is the kind of human frustration that I, that we see Moses in here. Like, we obviously don't know what he was wearing. We don't know if he wears a hat, if he throws it, we don't know if he turned around and kicked the sand or punched the wall. But, but because, but the, his words here, they're a man overwhelmed by a mission that seems to be collapsing in front of him. And we see this frustration mounting in Moses right here. So that, so Moses again, just keep this in mind before this whole conversation happens. Moses is rejected by Pharaoh, he's blamed by the Israelite foreman. And then he's just kind of like, he's like, this is all going backwards. Like nothing is going right here. So his questions at the end of chapter five, they're not like calm theological observations. They're the words of a desperate man. And he's like, he's like, I'm trying to be obedient, but all I'm doing is leading to more suffering here. So that's the first thing to remember in these first eight verses, right. God's answer is replying to a moment of great frustration. Okay, the second thing to remember here is that God never told Moses it was going to be easy. He was like, like at no point was he like, you're just going to waltz in there and it's going to, you know, it's one conversation. It's over, right? It's not how it's laid out. From the burning bush onward God. He's already told Moses that Pharaoh would resist, that the deliverance would require God's mighty hand. So God's reply isn't a change of plan. It's more of a reminder of the plan that he's already revealed. And it's a reminder that Moses, he's like, you should have expected some hardship here, right? And the third thing to remember about these first eight verses, it's God presenting himself as the covenant maker and the covenant keeper. And God is delivering Israel from slavery by delivering Israel from slavery and bringing them one step closer to the land of Canaan. It's more than Moses assignment. It's actually. It's God fulfilling the promise he made to Abraham. So Moses has to trust in this difficult obedience. He says, I have to trust that this is a part of God's larger plan. Okay, okay, we'll keep working through it here. Let's look at verses 9 through 13. I'll read these for us. Just to refresh it here. Moses spoke thus to the people of Israel, but they did not listen to Moses because their broken spirit and harsh slavery. So the Lord said to Moses, go in, tell Pharaoh, king of Egypt, to let the people of Israel go out of his land. But Moses said to the Lord, behold, the people of Israel have not listened to me. How then shall Pharaoh listen to me? For I am of uncircumcised lips. The Lord spoke to Moses and Aaron and gave them a charge about a people of Israel, about the people of Israel, and about Pharaoh, king of Egypt, to bring the people of Israel out of the land of Egypt, Egypt. So. So first of all, here, I think we got to give Moses a little bit of credit here. He has some. We have obedience without grumbling in this case, right? He does what God commands. He's delivering the covenant reminder message to the people. But he hits another setback here. The message falls on deaf ears, right? Verse nine says that they don't. They wouldn't listen because their broken spirit and the harsh slavery. So, like going back to chapter five, Pharaoh's strategy has worked, at least for the moment. And the burden on the Israelites has become so heavy that, like, the mental occupation of survival has crowded out any glimmer of hope. And it's just one of the painful realities of this passage is like, when people are. When you're just crushed by the weight of the present moment, it's hard to see any promise of the future. So the Israelites, I don't think they're rejecting God's promise because it's untrue. I think they're just too burdened to receive it right now. So then moving forward in verses 10 through 13, the focus is going to shift from, from the people's inability to hear God's promise to Moses ongoing struggle to trust God's calling. So, so God tells Moses, he says, go back to Pharaoh and command to let Israel go. But immediately, Moses immediately goes back to his familiar objections. And Moses argues that, he says, if the people of Israel won't listen to me, Pharaoh certainly won't, right? He's like, these are the people. I'm these people who are going to benefit from this, right? Why is Pharaoh gets nothing out of this? Why would he listen? He says, he says, I have uncircumcised lips. And other translations say I have faltering lips, I have poor, poor speech. So in other words, Moses is saying the people who should most want to hear this message are not listening one, and then two. So why should Pharaoh? And lastly, third, I'm still not a good communicator. So God answers, he answers both objections. He gives a charge to Moses and Aaron. And Aaron's present presence is an answer to Moses concerned about speaking, right? Like we go back to chapter to the burning bush encounter. God says, I'll give you Aaron to help you speak, right? So just having Aaron there is an answer to one of the objections. Then the charge itself to Moses and Aaron, it just keeps it mission focused, right? He says, you gotta speak to both Israel and Pharaoh because God me, I am still intending to bring the nation of Israel out of Egypt. So, so neither Pharaoh's resistance, nor Israel's discouragement, nor Moses insecurity can overturn God's command. Okay, so that's, so we're through verse 13 now. Now at this point the narrative is going to pause for a genealogy and like, rather than skipping over it, we need to, we need to, we need to look through this and see how this serves the, the flow of chapter six and how it fits within larger narrative of the Old Testament. This is by no means the, the longest or the most, the most thorough genealogy of the Old Testament. But this one, the purpose of this genealogy, it's going to anchor Moses and Aaron and the family line of Israel. And it reminds us that this rescue mission that we're on here is, is tied to God's long standing covenant promise. So we see the genealogy start with Reuben and Israel, and Israel is another Name for Jacob. And Jacob, right, is the grandson of Abraham, Abraham, Isaac, Jacob. And so we see again that Moses, he's just God's tool to fulfill the covenant between God and Abraham. Okay. And secondly the text self identifies its purpose in verse 26 to 27 says these are the Aaron and Moses to whom the Lord said bring out the people of Israel from the land of Egypt by their host. It was they who spoke to Pharaoh, king of Egypt, about bringing the people of Israel from Egypt. This Moses and this Aaron. So by including this family history, Moses connects the deliverance of Egypt back to Abraham, Isaac and Jacob. He's not just, he's not stepping into this random moment in history. He's being placed place within the covenant story of God that God has been working on for generations. So this genealogy reminds us that God's promise has a history and his faithfulness is not interrupted by Moses weakness or by Pharaoh's resistance. Okay, final section of text here, verse 28:30. It's going to return us back to the main narrative, right? God is again going to direct Moses to speak to Pharaoh. And that's going to set us up for the events in chapter seven, right? There's a slight, there's a slight difference here. It says, tell Pharaoh, King of Egypt, all that I say to you. So we're kind of setting up for what's going to be happening next here. But this genealogy has reminded us that God's covenant purposes are still moving forward. And now the narrative is going to remind us that Moses has to continue forward as God's messenger. Right? But Moses again is going to repeat his old objection. He says, I'm not a strong speaker. How will Pharaoh listen? And the chapter is going to end with this kind of unresolved, unresolved tension in Moses mind. But not, not an unresolved, but nothing unresolved in God's plan. Right? The tension is with Moses. So that's our, that's our, that's our text, that's our passage. So Lord willing, let me just try to wrap this up for us here. It's not, it's not hard to see the repeated patterns here, right? As I, when I start writing a sermon, I have the Bible and I have a blank piece of a yellow legal pad. And I just, I make notes verse by verse, verse by verse. And as I'm doing this, I'm like, Moses complains about inability. God reminds him of God reminds Moses of God's greater purpose. Moses complains again. God reminds Moses again. Moses complains. I mean I Mean, it's like, it's not, it's not a. We don't have to be scholars here to see this repeated pattern, right? But that's like the power of the narrative, though. Like God is giving Moses this clear command. It's grounded in his power, it's grounded in covenant faithfulness. But Moses just keeps going back to his own weakness. Then God keeps pointing Moses, think beyond yourself. He's like, he's pointing Moses away, away from himself. He's pointing Moses back towards God who can accomplish the deliverance, right? And as we think about applying this passage, we have to be careful that we don't turn this into like the hero's journey of Moses and needing to believe in himself, right? The main point is not that Moses finally finds enough courage within himself. And that's the risk. These well known Old Testament narratives like Joseph, Moses, David, Daniel, Jonah, to name a few, that's the risk of these passages. The main point of these is that God is faithful, God is powerful, and God is using weak messengers to carry out his saving work. And that the danger in reading these like famous biblical narratives as if their deepest lesson was merely like, follow the healer's good traits and avoid his bad traits. Like, there's just a we can learn from Moses. But the shortfalling of that is that these characters and Moses, he's not the central figure of the passage, right? The strong arm of God, the mighty hand of God the mighty. The strong hand of God is the force that keeps the story moving forward. So when Moses is just repeatedly questioning his ability to do the work that God has called him to do, in one sense he's right. He's not wrong in his assessment of his own abilities, like Moses did not. He doesn't have the power to change Pharaoh's heart. He doesn't have the power to break the Egyptian oppression. He doesn't have the power to fulfill God's covenant promise. But Moses, still, he just keeps missing the point. It's like God is never asking him to be the deliverer. He's. God is asking him to be the messenger of the deliverer, right? Exodus chapter 3, verses 19 and 20 establish this. They say, I know that the king of Egypt will not let you go unless compelled by a mighty hand. So I will stretch out my hand, this is God speaking, and strike Egypt with all the wonders that I will do in it. And after that he will let you go. So again, God is never asking Moses to be the mighty hand. He's just asking Moses to be the messenger. God is never commanding Moses to fulfill the covenant by his own strength. He's just commanding Moses to be an obedient participant in, in God's plan of keeping the covenant. So guys, if we can, this is like, if we can get this through our brains, we can save ourselves so much worry and hanry and consternation. Like, we are not the Saviors, we are not the Saviors. Moses cannot deliver Israel, deliver Israel by his own strength. And we can't deliver ourselves from the consequences of our own sin. Right? We can't save ourselves. Moses couldn't do it. We can't do it. Salvation belongs to the Lord and our calling is just faithful obedience in that. Now back to thinking about, thinking about this narrative as a whole. Like when we read narratives and especially these biographical narratives, it's easy to be the critic. So I say this next part with some hesitation because I don't, I'm confident I would not have done much better than Moses if I were in this situation. So with that trepidation, I, I, if we can glean one like kind of follow Moses lesson out of this or maybe don't follow Moses lesson. The, the lesson we need to learn is we need to be better at speaking the truth to ourselves, right? Moses has some moments of faithful obedience, but, but he's, more often than not he's, he's just plagued by his own self doubts. So when we think about this in the real world, I think about the phrase, I don't know where I heard it first. It's like you don't rise to the occasion, you drop to the level of your training, right? So I've just gotten done this summer. It's the seventh summer I've coached Demetrius, our oldest in baseball. And the past two summers I've been the first base coach. So I get a little bit of like mid at bat coaching time. And it takes me about half the season to remember that like you're not significantly moving the needle in like player development and talent in the middle of the game, in the middle of the at bat, right? Like you got a player with a bad swing at the beginning of that bat. Nothing you can say is really going to make a significant adjustment in the middle of the at bat. So like in the middle of the, in the middle of the game, in the middle of the moment. Most people, we don't rise to the occasion, we just stoop to the level of the training. Like the game moves so fast, the next moment comes so fast and the next moment is so overwhelming that like you stoop to the level of your training, right? So what we can learn from Moses Bad example here is that we have to be faithful and consistent and diligent in consuming what is right and true and what is from God. And we have to be faithful and consistent and diligent in reminding ourselves that like God is the strong and mighty hand and we are not. Right. And again, in full honesty, I don't think I would stack up much better than Moses. Again, it's easy to be the critic. Our life isn't canonized, Right. The main application is not be better than Moses. The main application is this. Like, we have to be mindful of how highly we view our own abilities and we have to be mindful of how low or not we view God's abilities. Right? We have to be mindful of how highly we view our own abilities. And we have to be mindful of how low or how high we view God's abilities. Right? One of my dear friends and mentors in construction and just life is a man named Travis. He's been doing construction management for over 30 years. He's a wonderful man of God, father of three faithful kids, grandfather, he's in construction terms. He's forgotten more work than I've ever managed and he's forgotten more lessons than I've ever learned yet. Right. If you've been to Lucille Downtown, he managed the renovation. It turned the bank vault into this wonderful event space. He's managed like a 500,000 square foot manufacturing plant. He has the experience and the credentials to be respected. And when I first met Travis, I'd been managing projects for like two years. I was like the most stressed out I had ever been. I had more responsibility than I ever had. Like deadlines in 1, 2, 3, 4 weeks. Coming up, Rachel's eight months pregnant with Chris. I'm like overwhelmed. And I meet Travis. I can remember it's like the Panera in Fitchburg. I'm like, Travis, how do you manage this? And he didn't. I can still remember this conversation. He says he didn't give me any. Do this every day. This is my project management checklist. He goes, you know, Rob, you do everything you can. Sometimes you just have to pray those projects over the finish line. Like that was it. It's like, it's, it's hopefully simple, but. But painfully simple, right? It's like you do all we can, but we have to. We have to. We have to show up, but we have to. We have to show up and do the work that God has called us to. Do diligently. But we have to realize that there are responsibilities and goals that seem impossible for man to shoulder. So we have to have to appeal to the all powerful God for help. So when we think about Moses and our narrative today, like Moses repeated objections, they just reveal we're seeing a man who felt the weight of his own weakness, but he struggled to rest in the strength of God. So church just wrapping this up. As we continue to think about Moses and we continue to think about God using Moses to carry out his work, my prayer is that we would learn to be faithful and obedient voices for God in the world. And not because we're strong enough to accomplish his purposes, but because we serve a God who is. So that's all we got for today. Let me pray for us today and then we'll do Lord supper after that. Lord, what a, What a joy and a burden it is. To be able to. Just take time to go into Moses's life in detail and take time to see, to see his shortcomings and to see, to see your strength and your promises and to see how you're using a flawed and sinful man to fulfill your promises, to fulfill your plan to redeem the world. Like. Pray for us, pray for our church that we would, we would diligently serve, we would diligently show up, we'd be faithful, obedient servants. But we would ultimately remember that it is not, it's not on our own strength. We serve an all powerful God who has a strong hand and a mighty arm. Even thinking of this sermon today, you're using a flawed and sinful man to bring, to deliver a divine and holy word here. So pray these words will not return empty and that they would be faithful for the good of your church, the evangelism of the world, and for the building up of the saints. It's in Christ's name we pray. Amen. The post God Promises Deliverance – Exodus 6: 1-30 appeared first on Red Village Church.

Sha & Jon are back this week and we discussed the following: What's new on streaming and theaters.Jon does a deep dive on Supergirl. A24 collaborates with Google Ai.Disclosure day makes over 200 mil.Werewulf trailer reaction and more! 

Today we preview the 2026 Prefontaine Classic which will showcase some of the most high quality fields we have seen all year. This includes Melissa Jefferson-Wooden taking on Sha'carri Richardson, Shericka Jackson and the Clayton Twins over Women's 100m, Oblique Seville vs Kenny B, Trayvon Bromell and Kanyinsola Ajayi in the Men's 100m, Collen Kebinatshipi vs the Americans in the Men's 400m, Masai Russel vs Tobi Amusan in the Women's 100H, and much much more.-------------------------------------------

A number of sources teach that if a person puts on two garments at the same time, he is likely to forget the Torah he has learned. This is mentioned in the Sha'ar Ha'kavanot, based on the teachings of the Arizal. It is brought also by the Mishna Berura. An example is placing one's Kippa in his hat, and then placing the hat on his head, such that he puts on both head coverings simultaneously. Another example is somebody who is going skiing and puts on two pairs of socks – he must put one sock on the foot at a time, rather than placing one sock inside the other and putting them together on his foot. This can also be relevant to a person wearing a shirt and a sweater; he must put on the shirt and then the sweater, rather than putting the shirt inside the sweater and then putting them on together. This applies also to those who wear two jackets; each must be put on separately. The reason for this Halacha is that according to Kabbalah, a garment is surrounded by an "Or Ha'makif" – a "supernal light." In fact, when we recite each morning the blessing "Malbish Arumim," thanking Hashem for the blessing of clothing, we refer to the special "light" that surrounds the clothes that we wear. This "light" has the effect of bringing a person Kedusha (sanctity) and warding off the Kelipot – the harmful impure forces that threaten him. If a person puts on two garments simultaneously, the inner garment does not receive the "Or Ha'makif." It must first be worn alone so it can receive this "light" before the outer layer covers it.

Tom Hardys rapkarriär, Margret är problemet och havets alla monster. Lyssna på alla avsnitt i Sveriges Radios app. Hela veckans Morgonpasset i P3 hör du i Sveriges Radios app.Sommaren är officiellt över – dags att börja förbereda sig för jul. Margret Atladottir är ÄNTLIGEN tillbaka från semestern och efterlyser sin gua sha. David Druid utser henne till ansiktet utåt för psykisk hälsa. Matilda Rånge från P3 Nyheter om att Vinted anklagas för barnhandel och den nya trenden ”darecation”. Vi ringer upp influencern och Parisbon Sandra Beijer om extremhettan i Paris och det tillfälliga alkoholförbudet. David riktar skarp kritik mot Shakiras VM-öppningsnummer och en ABC-reporter har hamnat i blåsväder efter en Bosnien-kommentar. Vi snackar om alla saker som försvinner och sedan ALDRIG dyker upp igen. Dessutom blir det ett hett snack om kvantfysik, Runar Sögaard har hamnat i klammeri klammera och djurexperten Tom Arnbom gästar studion. Vi snackar om den omtalade silverkindade blåsfisken som skapar kaos i Medelhavet och om alla monster som gömmer sig i Sveriges hav. Margret slår dessutom ett slag för att alla ska ha ärter i frysen. Och ja – Tom Hardy har släppt ett överraskande hiphopalbum.Tidpunkter i avsnittet:11:47 Nyhetsfördjupning: Vinted anklagas för barnhandel21:15 Alkoholförbudet i Paris40:32 Nyhetsfördjupning: Darecation1:07:01 Havets alla monsterKapitellänkarna ovan leder till avsnittet utan musik i Sveriges Radios app.Programledare: David Druid och Margret Atladottir.

Gambling has moved from casinos to our phones. FanDuel, DraftKings, BetMGM, ESPN Bet, Kalshi, and day-trading platforms have made “action” available every minute of the day. When is risk-taking legitimate, and when does it become gambling? Is sports betting different from day trading or prediction markets? What are the dangers of addiction, wasted time, and chasing easy money? with Rabbi Chaim Jachter – Rav of Sha'arei Orah in Teaneck, Dayan on the Elizabeth Beis Din – 25:10 with Rabbi Moshe Rotberg – Rav of Zichron Yechezkel, Toms River NJ, Rov of Hatzalah of Central Jersey, Pyscotherapist - 47:11 with Mr. Yehuda Liff – Therapist at Retorno, Specializing in addiction – 1:09:38 מראי מקומות   

Jon & Sha are back this week and they discussed the following:NYC Knicks winning the Championship and the aftermath.The World Cup so far.Evil Dead almost gets a NC-17 rating.The Box Office this past weekend.Discolusre Day buzz, a live Q&A & more!

Plus, UK Rape Gang Inquiry Shocks World, Horrific Findings Detail Over 250,000 Young White Girls Subjected To Repeated Gang Rape, Trafficking, Pregnancy, Forced Islamic Conversion

Today we recap the 2026 LA Grand Prix including Sha'carri Richardson's 100m opener, as well as Kenny Bendarek, Christian Coleman and Letsile Tebogo in the 100m. We also reflect on the NCAA Championships and the multiple all-time performances we witnessed in Eugene.LA Grand Prix Results: https://results.usatf.org/LAGrandPrix26/?mid=9043&en=18-1-------------------------------------------

durée : 00:58:28 - Avec philosophie - par : Géraldine Muhlmann - La philosophie arabe classique s'est développée autour de grandes questions métaphysiques, logiques et théologiques, en articulant raison et révélation. Parmi ses figures majeures, Avicenne et Averroès ont profondément marqué les débats sur la connaissance, l'être et l'interprétation des textes. - réalisation : Carla Michel, Axel Dubois, Shaïma Giboire, Corinne Amar, Nicolas Berger, Nassim El Kabli, Luna Hadjla - invités : Meryem Sebti Historienne des idées, directrice de recherche au CNRS, Olga Lizzini Professeure des universités, elle enseigne la philosophie arabo-islamique et l'islamologie. Vous aimez ce podcast ? Pour écouter tous les épisodes sans limite, rendez-vous sur Radio France

durée : 00:59:00 - Avec philosophie - par : Géraldine Mosna-Savoye - Dans "La Peste brune", Daniel Guérin livre un témoignage écrit à chaud sur la montée du nazisme au début des années 1930, nourri de deux voyages à travers l'Allemagne. Marquée par ce texte, l'historienne Ludivine Bantigny nous en parle. - réalisation : Nicolas Berger, Manon de La Selle, Shaïma Giboire - invités : Ludivine Bantigny Historienne, spécialiste de l'histoire des mouvements sociaux et des engagements politiques Vous aimez ce podcast ? Pour écouter tous les épisodes sans limite, rendez-vous sur Radio France

Peter digs into Trivolve Tech's forensic management system after it passed 100,000 on-chain transactions on Cardano mainnet. The episode looks at what the milestone actually represents, how the evidence workflow appears to use hashing and zero-knowledge proofs, and why it stands out as a live government-style deployment rather than another proof of concept.Peter also connects the project to Trivolve Tech's broader work in India, including IndianChain and land-record infrastructure tied to millions of farmers and millions of acres. The result is a grounded look at how Cardano is being used for chain-of-custody records, tamper detection, and large-scale public-sector data integrity.Key Takeaways:- Trivolve Tech's forensic management system has surpassed 100,000 on-chain transactions on Cardano mainnet.- The use case focuses on preserving chain-of-custody integrity for police forensic evidence in India.- The workflow described in Catalyst materials combines SHA-256 hashing with zero-knowledge proofs to detect tampering without exposing sensitive evidence data.- Peter links the project to earlier Cardano Foundation work with Dubai Police, suggesting a broader pattern for blockchain-based forensic records.- Trivolve Tech's IndianChain proposal extends the story beyond forensics into government land and agriculture settlement records.- The episode frames this as practical enterprise adoption on Cardano, not a speculative or purely experimental demo.Links & References:- x.com: https://link.learncardano.io/4eWNUc- https://link.learncardano.io/Fkgrh4- Securing Forensic Chain of Custody for Indian State Govt (1million+ cases per year) Using Cardano and Zero-Knowledge Proofs: https://link.learncardano.io/GM6wgh- IndianChain: Indian Government's 10M+ Settlements on Cardano: https://link.learncardano.io/gEWuXU- x.com: https://link.learncardano.io/OpHZnR- Dubai Police will use blockchain to conduct investigations: https://link.learncardano.io/iKza9NWebsite: https://link.learncardano.io/bQ68RcX/Twitter: https://link.learncardano.io/3a1QtvDisclaimer: This content is for educational purposes only. Nothing constitutes financial advice.DISCLAIMER: This content is for informational and educational purposes only and is not financial, investment, or legal advice. I am not affiliated with, nor compensated by, the project discussed—no tokens, payments, or incentives received. I do not hold a stake in the project, including private or future allocations. All views are my own, based on public information. Always do your own research and consult a licensed advisor before investing. Crypto investments carry high risk, and past performance is no guarantee of future results. I am not responsible for any decisions you make based on this content.

Exploring the lives of three Jewish doctors. Living in very different settings, yet linked by a common thread: compassion. They left a lasting mark on medicine and Jewish history and were dedicated to the strong belief that every fragile life matters. In New York, Dr Martin Couney helped save thousands of babies. His sideshow displays were controversial, but at a time when incubator technology was widely doubted, his exhibits brought life-saving technology into the public eye. Dr Mary Gordon was born in Lithuania and her trailblazing career as a pioneering female physician who was deeply connected to Jewish life, allowed her to carry her medical calling into some of the hardest moments of the twentieth century, in Palestine, in detention camps in Cyprus and through world wars. Dr Shlomo Adler's reputation in London as a beloved doctor and trusted medical confidant to Gedolim and Torah leaders as well as to thousands of patients, rested on his complete commitment to care, innovation and halacha. We also hear from his son Dr Yossi Adler - who has continued a 3 generational family legacy - about AI and other issues confronting medicine today   Timestamps: - **0:00:00 – 0:01:13** – Podcast intro, series context (Medicine Part 2), and mention of guests (Rabbi Tatz & Dr. Yossi Adler) - **0:01:13 – 0:02:16** – Introduction of Mary Gordon; granddaughter of Reb Eliezer Gordon; name changes (Miriam → Mary, Sara → Sylvia)   - **0:02:16 – 0:03:49** – Background on the Gordon family, Telshe Yeshiva, and Reb Eliezer Gordon's leadership and social conscience (matzah bakeries)   - **0:03:49 – 0:06:21** – Fire in Telshe (1908), Reb Eliezer Gordon's fundraising trip to England, his death, funeral, and Mary receiving apology from the Chief Rabbi   - **0:06:21 – 0:09:00** – Mary's struggle to enter university, re-doing exams in England, brilliance and speed of study, financial help from Rabbi Moishe Hirsh Siegel, graduation as a physician   - **0:09:00 – 0:10:27** – Status of women doctors in England; WWI, shortage of male doctors; Mary becomes first female medical student allowed to practice in the army   - **0:10:27 – 0:12:57** – Move to South Africa; reuniting with family; pioneering practice in Johannesburg General Hospital; treating rich and poor, all races; miners' strike of 1922   - **0:12:57 – 0:15:30** – Plans to move to Palestine; WWII intervenes; army medical role, rank of captain then lieutenant colonel; final move to Palestine (1946)   - **0:15:30 – 0:18:18** – Postwar DP situation; Anglo-American committee, Truman's proposal for 100,000 DPs; British refusal; Cyprus detention policy and harsh camp conditions   - **0:18:18 – 0:21:06** – Mary chosen by the Jewish Agency to serve in Cyprus; tiny medical team; overwhelming numbers, disease, births; her legendary dedication; quote about measuring temperature vs pain   - **0:21:06 – 0:22:28** – New Year's 1948 story (two big ships arrive, many pregnant women and newborns); Mary persuades nurses to stay; later work in Israel with Yemenite immigrants; return to South Africa, work in Soweto clinics, death and legacy   - **0:22:28 – 0:24:04** – Introduction of Dr. Yossi Adler; recognition that “Dr. Adler” was a global communal institution   - **0:24:04 – 0:26:24** – Growing up in a house that doubled as a practice; constant stream of patients; balancing family meals with emergencies, especially before Hatzalah   - **0:26:24 – 0:28:18** – What made Dr. Adler's practice unique: long-term relationships, personalized care, deep sense of responsibility, readiness to innovate   - **0:28:18 – 0:32:24** – Early roots of his father's connection to Gedolim (Gerrer Rebbe, Imrei Emes); later relationships with Gedolim and Rebbes (Stipler, R' Shach, Satmar, Klausenburger, etc.)   - **0:32:24 – 0:36:24** – Stories illustrating kavod from Rebbes (“Malach Refael goes with Dr. Adler”), and equal importance of all patients; how he handled treating Gedolim without intimidation   - **0:36:24 – 0:40:21** – Lessons Dr. Yossi learned: time use, achrayus (responsibility), integrating halacha and derech eretz into medicine; a few character-defining stories   - **0:40:21 – 0:44:04** – Role of a frum doctor today: giving clear medical facts for Rabbanim, especially in end-of-life, surgery, fasting, and shidduch situations; why doctor ≠ posek   - **0:44:04 – 0:49:05** – Community health issues:   - Vaccine hesitancy and mistrust of authorities     - Halachic support for following broadly accepted medical guidance     - SIDS reduction through “back to sleep” and risk of complacency   - **0:49:05 – 0:53:59** – Discussion on modern weight-loss medications (semaglutide, tirzepatide): when benefits outweigh risks (severe obesity) vs mainly cosmetic use   - **0:53:59 – 0:56:51** – Google and patient information: opportunities and dangers; importance of joint doctor–patient interpretation rather than self-treatment   - **0:56:51 – 0:57:40** – Rabbi Tatz introduction, playful comment about trying to “one up” Rabbi Hirsch with an unknown medical figure   - **0:57:40 – 0:59:37** – Background of Dr. Cooney (Mikhail Kohn): Jewish origins in Prussia, medical studies, interest in premature infants and early incubators   - **0:59:37 – 1:03:10** – Move to America; transformation into “Dr. Cooney”; sideshow incubator exhibits at fairs and Coney Island; hospitals giving up on babies, parents bringing infants in shoeboxes; high survival rates   - **1:03:10 – 1:05:00** – Framing ethical and halachic questions: doing something risky to save life; early incubators as both spectacle and lifesaving tool   - **1:05:00 – 1:08:32** – Classic halachic scenario: terminal/“Ha'ei Sha'ah” patient offered high-risk procedure with chance of cure vs certain shorter-term survival; introduction to “Lo chosheshin lechayei sha'ah” in this context   - **1:08:32 – 1:12:08** – Majority view:     - If chance of success >50%, patient *should* generally accept.     - If

durée : 00:57:30 - Avec philosophie - par : Géraldine Muhlmann - En grand analyste du roman, Roland Barthes, dans ses essais, étudie les mécanismes du récit, la construction des personnages et les effets de sens produits par l'écriture romanesque. Son approche renouvelle la lecture du roman, en s'intéressant au texte plus qu'aux intentions de l'auteur. - réalisation : Carla Michel, Axel Dubois, Shaïma Giboire, Nicolas Berger, Nassim El Kabli, Luna Hadjla - invités : Philippe Forest Romancier et essayiste, Antoine Compagnon Écrivain, enseignant et académicien français Vous aimez ce podcast ? Pour écouter tous les épisodes sans limite, rendez-vous sur Radio France

The Kabbalists taught that when one recites the "Ana Be'cho'ah" prayer, he should arrange the words of the prayer in pairs. Meaning, he should say the first two words, briefly pause, say the next two words, pause, and so on. This is the instruction given by Rav Haim Vital (1543-1620), in Sha'ar Ha'kavanot, based on the teachings of the Arizal. This is brought later by the Ben Ish Hai (Rav Yosef Haim of Baghdad, 1833-1909) and the Kaf Ha'haim (Rav Yaakob Haim Sofer, Baghdad-Jerusalem, 1870-1939). However, Rav Meir Mazuz (1945-2025) ruled that one should not follow this custom, as the reading becomes unintelligible in this manner. By reciting the text of this prayer in pairs of words, one ends up saying, "Ana Be'cho'ah" – "Please, with the strength"; "Gedulat Yeminecha" – "the greatness of Your right"; "Tatir Serura" – "release those who are trapped"; "Kabel Rinat" – "accept the prayer of"; "Amecha Sagebenu" – "Your nation, protect us"; "Taharenu Nora" – "purify us, O Awesome One," and so on. The words are clearly not intended to be broken up in alternating pairs of two, as they have no meaning when recited this way. Rav Mazuz therefore ruled that one should recite the text of the prayer this way: "Ana Be'cho'ah Gedulat Yeminecha" ("Please with the power of the greatness of Your right"), "Tatir Serura" ("release those who are trapped"); "Kabel Rinat Amecha" ("Accept the prayer of Your nation"); "Sagebenu Taharenu Nora" ("protect us, purify us, O Awesome One"). (Incidentally, Rav Mazuz issued a similar ruling regarding the recitation of the famous verse, "Hashem Hoshi'a Ha'Melech Ya'anenu Be'yom Kor'enu." The Kabbalists instructed pausing after the word "Ha'melech," such that one should say: "Hashem Hoshi'a Ha'Melech, Ya'anenu Be'yom Kor'enu." Rav Mazuz noted that this reading sounds as though we ask Hashem to save the King ("Hoshi'a Ha'melech"). The proper way to read this verse, Rav Mazuz ruled, is with the pause after the word "Hoshi'a," such that we say, "Hashem save us; the King shall answer us on the day we call out.") Some Siddurim use a very complex system in punctuating this prayer, adding commas and periods, in an attempt to accommodate both opinions. In any event, Rav Yisrael Bitan writes that as the Arizal, the Ben Ish Hai and the Kaf Ha'haim all say that this prayer should be divided into pairs of words, it is difficult to dismiss this practice. Therefore, this is the preferred way to read Ana Be'cho'ah.

This week on Spitball Media, Jon & Sha are back to talk all things movies!Jon reviews Masters of the Universe after seeing it on the big screen, while Sha finally checks out The Backrooms and shares what the theater experience was like.We're also diving into the latest popcorn buckets, theater collectibles, and the wild world of movie merch.Plus, Disclosure Day hits theaters this weekend, and we host our first ever LIVE Q&A!Grab a drink, join the chat, and hang out with us live every Wednesday on YouTube!If you enjoy horror movies, trailer reactions, and film news, make sure to subscribe and join the Spitball Media community. Join us live every Wednesday Night at 7:30 pm, eastern

durée : 00:57:54 - Avec philosophie - par : Géraldine Muhlmann - S'inspirant de la linguistique, Roland Barthes s'intéresse à la science qui étudie les signes et la manière dont ils produisent du sens dans la société : c'est la sémiologie. Dès lors, si la société est un système de signes, pourquoi restreindre leur analyse aux seuls textes littéraires ? - réalisation : Carla Michel, Axel Dubois, Shaïma Giboire, Nicolas Berger, Nassim El Kabli, Luna Hadjla - invités : Typhaine Samoyault Enseignante universitaire, critique littéraire et romancière, Daniel Bougnoux Professeur à l'université de Grenoble, a établi l'édition critique de la Pléiade Aragon Vous aimez ce podcast ? Pour écouter tous les épisodes sans limite, rendez-vous sur Radio France

After we recite in the morning the section of the Ketoret and the passage of "Abayeh Hava Mesader," we recite a very special prayer – Ana Be'cho'ah. This prayer was composed by one of the great Tanna'im – Rabbi Nehunya Ben Ha'kaneh, whom the Hida (Rav Haim Yosef David Azulai, 1724-1806) describes as one of the earliest Kabbalists, preceding even Rabbi Shimon Bar Yohai. The Ana Be'cho'ah prayer is so significant that the Ben Ish Hai (Rav Yosef Haim of Baghdad, 1833-1909) and many others write that if a person arrives late to Shaharit, and needs to skip the introductory portions of the prayer service, he should not skip Ana Be'cho'ah. This prayer consists of seven lines, each of which with six letters, for a total of 42 letters, and these 42 letters spell the special 42-letter Name of Hashem. This Name is the "elevator," the Name associated with rising to the upper worlds. It is critically important to recite Ana Be'cho'ah as part of our introduction to Shaharit because it elevates us to the heavens so we can present our Tefilot to G-d. By the time we recite the Amida, we want to be standing before the Heavenly Throne, so we can speak directly to the Almighty. The recitation of Ana Be'cho'ah elevates us to the higher spheres so we can speak to Hashem while standing in front of His Throne. It is proper to recite this Tefila slowly and to take note of the first letters of the words. This Name is alluded to also in the first paragraph of Shema, which consists of 42 words (from "Ve'ahabta" through "U'bi'sh'arecha"), corresponding to the 42 letters of this Name. For this reason, some Siddurim feature the letters of this divine Name alongside the words of this paragraph of Shema. Another allusion to this Name is found in Kaddish – specifically, in the phrase "Ve'yishtabah Ve'yitpa'ar Ve'yitromam Ve'yitnaseh Ve'yit'hadar Ve'yit'aleh Ve'yit'halal," which consists of seven words that each contains six letters, for a total of 42. Some have the custom to recite Ana Be'cho'ah each night before going to sleep. The soul departs and rises to the heavens when one sleeps, and so it is appropriate to recite this prayer which, as mentioned, is associated with elevation and ascent. Likewise, it is customary to recite Ana Be'cho'ah at funerals, Heaven forbid, as the coffin is being taken for burial, and the soul is ready to rise to the heavens. In some communities, Ana Be'cho'ah is recited before Lecha Dodi on Friday night, as we elevate ourselves to the higher plane of Shabbat. Likewise, many recite this prayer after counting the Omer, as the Omer counting is intended to elevate us in preparation for Matan Torah on Shabuot. The custom to read Ana Be'cho'ah following the recitation of "Abayeh Hava Mesader" was taught by the Arizal, as brought in Sha'ar Ha'kavanot. This is cited by the Kaf Ha'haim (Rav Yaakob Haim Sofer, Baghdad-Jerusalem, 1870-1939). The Seder Ha'yom (Rav Moshe Ben Machir, Safed, 16 th century), by contrast, writes that it is better to recite Ana Be'cho'ah later, just before Baruch She'amar. He explains that the world was created with the power of this 42-letter Name, and so it is appropriate to allude to this Name just before reciting "Baruch She'amar Ve'haya Ha'olam," when we give praise to Hashem who created the world. However, we follow the Arizal's teaching, that Ana Be'cho'ah should be recited after the section of "Abayeh Hava Mesader." One possible explanation for the Arizal's custom is that the section of "Abayeh Hava Mesader," which lists the various Abodot (services) performed daily in the Bet Ha'mikdash, omits Birkat Kohaim (the priestly blessing), which was recited each day in the Bet Ha'mikdash. In the Bet Ha'mikdash, the Kohanim reciting Birkat Kohanim would use the Shem Ha'meforash – the divine Name that is normally forbidden to utter, and according to some, this was the 42-letter Name. Perhaps, then, we add Ana Be'cho'ah – which is associated with this Name – after the section of "Abayeh Hava Mesader" to allude to the daily recitation of Birkat Kohanim in the Bet Ha'mikdash. The Ana Be'cho'ah prayer concludes with the pronouncement of "Baruch Shem Kebod Malchuto Le'olam Va'ed," giving praise to the exalted Name of G-d, which this prayer expresses.

Today we preview the Oslo Diamond League, including the Men's 200m which will see Letsile Tebogo take on Gout Gout, in what will be his first major meet on the circuit against a truly high quality field. Julien Alfred will also race the 100m, and Karsten Warholm will take on Alison Dos Santos in the 400HThis Sunday, the LA Grand Prix will also go down and Sha'Carri Richardson is expected to make her 100m debut after racing a few 200m in China earlier this year. We will also see Kenny Bednarek, Christian Coleman, Rai Benjamin and Masai Russell competing in LAFinally, we discuss the NCAA Championships going down this weekend with a few notable athletes to keep a look out for.Oslo DL Start Lists: https://oslo.diamondleague.com/en/programme-results/LA Grand Prix meet website: https://www.usatf.org/events/2026/2026-usatf-los-angeles-grand-prix NCAA Champs Live Results: https://flashresults.com/2026_Meets/Outdoor/06-10_NCAA/index.htm ⁠-------------------------------------------

durée : 00:57:46 - Avec philosophie - par : Géraldine Muhlmann - Dans "La Mort de l'auteur" (1967), Roland Barthes critique l'idée d'un auteur maître du sens de son œuvre. Il affirme que l'interprétation d'un texte ne dépend pas des intentions de l'écrivain, mais du fonctionnement du langage et de l'activité du lecteur. - réalisation : Carla Michel, Axel Dubois, Shaïma Giboire, Nicolas Berger, Nassim El Kabli, Luna Hadjla - invités : Eric Marty Écrivain et universitaire, Vincent Kaufmann Professeur émérite de littérature et d'histoire des médias à l'université de St. Gall en Suisse Vous aimez ce podcast ? Pour écouter tous les épisodes sans limite, rendez-vous sur Radio France

Knox Brew Stories is a weekly live radio show and podcast that offers an in-depth look into the beverages, businesses, artists, and inspiring humans who make Knoxville an amazing place to be!In this episode you'll find our regular weekly news about craft beer, as well as:Brew News (6:20)Live Music with Darrow (9:17)Interview with Sha & Ariana of Fleurish (18:17)Live Music with Darrow (48:28)Next Week on Tap (56:19)Live Music with Darrow (57:56)Co-Host & Producer: Ace Preston Co-Host & Producer: Kevin SummittAudio Engineer: Clyde TimbsPodcast Producer: Asher CokerLinks for our featured Guests:https://www.instagram.com/fleurishknoxville/https://www.ijams.org/event-details/special-event-fleurish-2026-a-sustainable-fashion-eventhttps://www.instagram.com/darrow_music/https://distrokid.com/hyperfollow/darrow4/youngBe sure to tune in live every Monday at 6pm EST at http://ChannelZradio.comAnd check out https://www.knoxbrewstories.com/ and https://www.instagram.com/suttreeshighgravity/

durée : 00:58:12 - Avec philosophie - par : Géraldine Muhlmann - "Le Degré zéro de l'écriture", publié en 1953, est un essai majeur de la réflexion littéraire du 20ᵉ siècle. Roland Barthes y analyse les rapports entre langue, style et écriture, montrant que l'écriture est toujours un choix historique et idéologique. Il développe la notion de "degré zéro". - réalisation : Carla Michel, Axel Dubois, Shaïma Giboire, Nicolas Berger, Nassim El Kabli, Luna Hadjla - invités : Mathieu Messager Maître de conférences en langue et littérature française à l'Université de Nantes., Justine Brisson Docteure en littérature française Vous aimez ce podcast ? Pour écouter tous les épisodes sans limite, rendez-vous sur Radio France

Auto-generated transcript: Alhamdulillah Rabbil ‘Aalameen, wa salatu wasalamu ala ash-Sha’ifa al-Anbiya’i wal-Mursaleen, wa hamdu lillahi Rabbil ‘Aalameen. Tasliman kathiran kathira. I am about to share with my brothers and sisters the first hadith in Al-Baqarah, narrated by Umar ibn al-Khattab (RA). He said: “The first thing is…” This is an important thing for us to… Continue reading Attitude decides benefit

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

Working women, "big dogs" who want a soft life. Are UFOs real? Go and forgive your mother, and overcome fear.

Almost 9 years since the big split of the Bitcoin community, it's time to learn more about how the Bitcoin Cash chain developed. Calin Culianu is the creator of Fulcrum, an efficient privacy-preserving SPV client. Steve Thurmond is the most ardent advocate for Cash Stamps: a convenient paper wallet system that's used for gifting. Throughout the episode, more BCH community members will join to have the conversation that you will never hear on any other Bitcoin podcast. Time stamps: 00:01:09 Introducing Calin Culianu & Steve Thurmond 00:02:37 The Evolution of Bitcoin Cash 00:03:59 Who is Behind Bitcoin Cash Now? 00:06:34 Narratives and Misconceptions 00:07:53 Vlad's Perspective on the Fork 00:09:44 Bitcoin's Capture and Speculative Nature 00:11:48 Vlad's Journey with Lightning Network 00:16:07 Blockstream and the "Banker" Conspiracy 00:18:33 The Security Budget Debate 00:22:12 The Problem with IOU Systems like Lightning 00:24:02 Vlad's Disappointment with Onboarding 00:24:58 Ethereum's Rise Amidst Bitcoin's Infighting 00:27:52 The Bankers Won, But Crypto Still Exists 00:32:16 The Future of Bitcoin and Firing Core Devs 00:33:08 The Wall of Consensus in BTC 00:39:19 The Multi-Coin Future 00:42:48 Bitcoin Cash's Development Philosophy 00:49:08 Craig Wright's Controversial Involvement 00:55:16 The Impact of Contentious Forks 00:58:55 The Resilience of Bitcoin Cash 01:02:32 The Value of Open Source Competition 01:08:51 Greg Maxwell's Influence 01:12:00 The Ecash fork 01:25:02 Introducing New BCH Community Members 01:26:38 Building Smart Contracts on Bitcoin Cash 01:34:06 Why UTXO is Better than EVM 01:40:07 Can You Run a BCH Node? 01:41:07 The Flawed "Run a Node" Narrative 01:53:27 The Dangers of RBF and the Importance of 0-Conf 02:05:07 One-Minute Blocks Proposal 02:08:02 Finality and User Experience in Wallets 02:12:13 The "It's Just Money, Bro" Philosophy 02:41:39 What Can You Buy with BCH? 02:48:28 The Permissionless Nature of BCH 02:52:12 The Paradox of Layer Twos 02:57:18 The Stigma of Building on BCH 02:58:21 The Changing Culture of Bitcoin Cash 03:11:35 Ordinals and the "Spam" Debate 03:17:07 Would BCH Still Have a Nice Dev Culture If Michael Saylor Started Buying? 03:28:14 Quantum Computing and Satoshi's Coins 03:42:59 The Tail Emission Debate 03:50:11 The Culture is the Ultimate Defense 03:53:16 The Politicization of Bitcoin Development 03:59:26 Privacy and Fungibility 04:02:21 The Future of Privacy on BCH 04:36:12 Fulcrum: An Electrum Server Implementation 04:38:54 The Litecoin Question 04:49:13 The Difficulty of Recreating Bitcoin's Genesis 04:51:38 The Long-Term Bet on SHA-256 04:54:12 A Break and Introduction to Rosco 05:48:33 CashScript and Smart Contracts on BCH 05:55:22 BCH vs. Ethereum Smart Contracts 06:03:05 The UTXO Stack and Abstraction Layers 06:43:30 The Avalanche Pre-Consensus Question 06:45:51 The "Tax" Fork 07:04:06 The Failed Attack on Bitcoin Cash 07:08:58 The 2018 Inflation Bug Disclosure 07:22:46 The Michael Saylor Phenomenon 07:28:41 The Arrest of Roger Ver 07:39:28 Spending Crypto in the Real World 07:44:22 The End of Crypto-Friendly Spaces in Europe 07:52:05 Prediction Markets and Community Sponsorship 08:08:17 Robin Linus is Jealous of BCH Opcodes 08:09:50 Final Thoughts and Conclusion

durée : 00:59:11 - Avec philosophie - par : Géraldine Muhlmann - Le “Discours de la servitude volontaire” a été écrit autour de 1548 par Étienne La Boétie. Pour Miguel Abensour, cette thèse de La Boétie était une “hypothèse scandaleuse”. Pourquoi s'agit-il d'une hypothèse transgressive en philosophie politique ? - réalisation : Frédéric Worms, Anna Pheulpin, Carla Michel, Riyad Cairat, Antoine Ravon, Shaïma Giboire, Marine Boudalier - invités : Anne Kupiec Professeure de sociologie à l'Université Paris Diderot (Paris 7). Elle a été bibliothécaire à la bibliothèque Cujas et à la Bibliothèque publique d'information (la BPI) à Paris., Michèle Cohen-Halimi Philosophe, professeure de philosophie à l'université Paris 8, David Munnich Spécialiste de philosophie politique Vous aimez ce podcast ? Pour écouter tous les épisodes sans limite, rendez-vous sur Radio France

There is a time-honored tradition to remain awake throughout the night of Shabuot and read the special "Tikkun Lel Shabuot" text that is printed in the Mahzorim. Hacham Ben Sion Abba Shaul (Israel, 1924-1998), in his work Or Le'siyon (vol. 3, 18:11), discusses the importance of this custom and presents numerous laws and guidelines relevant to the proper observance of this special occasion (listen to audio clip for precise citation). First, he mentions that even learned men who prefer studying Gemara must set aside their Talmudic studies in order to read the text of the Tikkun Lel Shabuot. If time remains after they complete the Tikkun, they may then study other material that they find more enjoyable. In Yeshivot, Hacham Ben Sion writes, students should follow the instructions of their Rosh Yeshiva in this regard. He also emphasizes that one should read the Tikkun even if he does not understand some sections of the service. Even if one plans to remain awake throughout the night, he should nevertheless recite the Keri'at Shema Al Ha'mita before Hassot (midnight as defined by Halacha). Already after Hassot, one may recite all the morning Berachot, with the exception of "Al Netilat Yadayim" and Birkot Ha'Torah. One should make a point to use the bathroom at some point before morning in order to be able to recite "Asher Yasar." At the point in the pre-dawn hours when it is uncertain whether Alot Ha'shahar (daybreak, the first appearance of light in the eastern sky) has occurred, one should discontinue his Torah learning. He should instead either immerse in a Mikveh or sing songs of praise until Alot Ha'shahar. After Alot Ha'shahar, one should wash his hands in preparation for prayer, but without reciting a Beracha. He then must recite Birkat HaTorah. Hacham Ben Sion cites in this context a passage in the work Sha'ar Ha'kavanot, which comments that whoever remains awake and diligently involves himself in Torah study throughout this night is guaranteed to survive the entire next year and to avoid all harm. Nevertheless, one should make a point of studying "Li'shmah" – with the proper motivation, out of sincere love for and commitment to Torah learning, and not to receive reward. Hacham Ben Sion also warns that sitting idly or engaging in meaningless chatter is no better than sleeping. It is therefore imperative to ensure to spend the entire night engrossed in Torah learning, and not in any other activities. In particular, one must avoid idle conversation inside the synagogue. Hacham Ben Sion also cites a comment from the Zohar that emphasizes the importance of studying with joy and fervor, in reward for which one is blessed with seventy blessings. The Ben Ish Hai (Rav Yosef Haim of Baghdad, 1833-1909) similarly stressed the importance of studying on this night with great enthusiasm and what he termed "purity of heart." Furthermore, on the festival of Shabuot God decrees how many "Hiddushim" (new insights) each individual will be privileged to develop during the coming year, which is determined based on the level of one's intensive study on Shabuot. Hacham Ben Sion writes that when we speak of Shabuot as "the day of the giving of the Torah," we refer not merely to the historical event of Matan Torah, but rather of the process that is renewed each year on this day. God grants a person on Shabuot the ability to think of new Torah insights, and one must therefore pray on Shabuot for Torah knowledge and the wisdom to understand to the best of his soul's capability, and also try to think of "Hiddushim" during his study on Shabuot. During the day of Shabuot, too, one should try to minimize his sleeping in order to spend as much time as possible involved in Torah learning. Every moment spent learning on Shabuot earns a person reward, and one must not squander this opportunity. In fact, there were great Rabbis who would not sleep at all on Shabuot; after remaining awake throughout the night, they would simply continue learning through the day of Shabuot. The Hid"a (Rav Haim Yosef David Azulai, 1724-1806) likewise advises against indulging in sleep on the day of Shabuot. He also emphasizes that one must ensure not to fall asleep during the prayer service. Finally, one should also devote himself to Torah study with extra vigor and diligence during the "Sheloshet Yemeh Hagbala" – the three days of preparation prior to Shabuot. Just as in the wilderness Beneh Yisrael were instructed to abstain from relations and prepare themselves for three days prior to Matan Torah, so must we increase our efforts to learn Torah and minimize our physical indulgence during these three days. Hacham Ben Sion writes that the level of inspiration one receives from the experience of Shabuot depends on the amount of effort he exerted during the three previous days to prepare for this great experience.

Skipmode walks us through the valley of jeep beats with golden era sureshots, sublime sample reconstructions and a strong salute to Philly with Freeway, 3 Times Dope, Sha'dasious and more. Plus a rare groove jewel from James Mason, fresh soul breaks by Tiwayo and a deep funk salvage op by Edan & Insight. View the full playlist for this show at https://www.wefunkradio.com/show/1294 Enjoying WEFUNK? Listen to all of our mixes at https://www.wefunkradio.com/shows/

In this After Hours bonus episode, Sam is joined by Sha, Ciara and Cole for a chaotic, hilarious, and surprisingly thoughtful conversation you didn't know you needed. From bold personal hot takes to debating what actually counts as a “sheltered life,” nothing is off limits. The crew imagines future YGC guests, guesses what people would assume Sam went to jail for (it gets wild), and settles the ultimate nostalgia battle: Club Penguin vs. Webkinz. They also share their favorite piece of fan mail, drop their number one tip for starting a youth group, confess their weirdest favorite food combos, and dive into their honest thoughts on gentle parenting. It's unfiltered, unpredictable, and packed with laughs from start to finish.See Privacy Policy at https://art19.com/privacy and California Privacy Notice at https://art19.com/privacy#do-not-sell-my-info.