Podcasts about documenting

On this episode of Face to Face: Shane Belcourt Filmmaker Shane Belcourt's most recent documentary is Ni-Naadamaadiz: Red Power Rising, a documentary about an Indigenous-led occupation in Anicinabe Park over nearly 40 days in 1974. He tells Face to Face it was an electric time in history. • • • APTN National News, our stories told our way. Visit our website for more: https://aptnnews.ca Hear more APTN News podcasts: https://www.aptnnews.ca/podcasts/

The Legacy and Hidden History of the Graces' Style. The full set of fashion plates documenting this radical style revolution was rediscovered at the Morgan Library after being incorrectly cataloged. The true story of this fashion was radical and had been "concealed from the world." The three women, known as the Graces, became world-famous celebrities. Josephine (Rose), who missed Napoleon "terribly" after their divorce, died in 1814. Teresia, a woman "in charge of her own sexuality" with five different fathers to her nine surviving children, married a Belgian prince and died a true princess. She was visited by figures like the Duke of Wellington after Waterloo. Juliet maintained her identity as a "perpetual virgin," serving as the pure white symbol until her death. Despite Napoleon forcing a separation, Teresia and Josephine tried hard to continue seeing each other. 1807 JOSEPHINE

Hello to you listening in Warsaw, Poland!Coming to you from Whidbey Island, Washington this is Stories From Women Who Walk with 60 Seconds (and a bit more) for Motivate Your Monday and your host, Diane Wyzga.I am deeply proud of my Polish heritage and being a lawyer. These times are unprecedented; but especially for judges, the last line of freedom's defense. Attacks on the independence of the judiciary are sweeping our country taking various forms ranging from court capture to direct attacks on judges. The cowards behind the attacks know that the independence of judges - the judicial branch of government - is foundational to democracy.“Judicial independence is fundamental to the rule of law. The rule of law is fundamental to freedom. Freedom is fundamental to the protection of every citizen.” [John Macmenamin - Judge at the Supreme Court of Ireland]Those are not my words. Those are the words of John Macmenamin, a judge at the Supreme Court of Ireland who joined with Polish judges at the “1000 Robes March”, an unprecedented event held in the name of judicial independence.1000 Robes March was the greatest demonstration of judges in contemporary Europe, with more than 30,000 people, including hundreds of judges from 22 European countries marching in solidarity with their Polish colleagues in the fight for judicial independence. The silent march in January 2020 was a reaction to proposed laws that threatened to undermine the judiciary's independence in Poland.  "A Thousand Robes" is a short (12 minute) documentary film directed by Kacper Lisowski. The story is about mutual gratitude, focusing on the positive interactions between judges, lawyers, and the public. It highlights citizens who are moved by the judges' defense of their rights and lawyers who have experienced solidarity from ordinary people and European judges. The film serves as a warning against what dismantling the democratic mechanisms of the state leads to.Documenting this touching episode of the dramatic struggle for the rule of law that still lacks a happy ending in Poland, Kacper Lisowski also talks to the European judges participating in the march of a thousand robes. Particularly poignant is the voice of a Turkish judge who knows from experience what happens when such a struggle is lost.Click HERE to watch A Thousand Robes the film on YouTube.CTA: Maybe like me you will be moved to tears at what We the People can accomplish when we heed a call to action. This is what democracy looks like! Take Hope! Take Heart! Take Courage from all the good work being done by our federal judges who are in solidarity with our Democracy, our Constitution, our rule of law without fear or favor! You're always welcome: "Come for the stories - Stay for the magic!" Speaking of magic, I hope you'll subscribe, share a 5-star rating and nice review on your social media or podcast channel of choice, bring your friends and rellies, and join us! You will have wonderful company as we continue to walk our lives together. Be sure to stop by my Quarter Moon Story Arts website, check out the Services, arrange a no-obligation Discovery Call, and stay current with me as "Wyzga on Words" on Substack.Stories From Women Who Walk Production TeamPodcaster: Diane F Wyzga & Quarter Moon Story ArtsMusic: Mer's Waltz from Crossing the Waters by Steve Schuch & Night Heron MusicALL content and image © 2019 to Present Quarter Moon Story Arts. All rights reserved.  If you found this podcast episode helpful, please consider sharing and attributing it to Diane Wyzga of Stories From Women Who Walk podcast with a link back to the original source.

The practice of celebrating dead ancestors started long before Spanish colonizers came to what is now Mexico, but the Aztec and Mayan custom eventually engulfed the entire country, blending Catholic, Spanish, and Indigenous elements into what is now Dia de los Muertos. The festival even spills into parts of the U.S. Some people with Mexican Indigenous ties are working to cut through the contemporary pop culture trappings of the holiday and reconnect with the deeper, more spiritual origins. We'll also hear about Vision Maker Media's expanded push to train and support young filmmakers to tell stories driven by mission. The Native Youth Media Project partners with tribes, organizations, and individuals to develop storytellers at a time when federal support for such projects has disappeared. GUESTS Janet Martinez (Zapotec), executive director of Communidades Indigenas en Liderazgo (CIELO) Kurly Tlapoyawa (Chicano and Nahua), archaeologist and co-host of the “Tales from Aztlantis” podcast Francene Blythe (Diné, Sisseton Wahpeton and Eastern Band of Cherokee), executive director of Vision Maker Media Anita Huízar-Hernández, associate director of the Hispanic Research Center and publisher and managing editor of the Bilingual Press at Arizona State University

The practice of celebrating dead ancestors started long before Spanish colonizers came to what is now Mexico, but the Aztec and Mayan custom eventually engulfed the entire country, blending Catholic, Spanish, and Indigenous elements into what is now Dia de los Muertos. The festival even spills into parts of the U.S. Some people with Mexican Indigenous ties are working to cut through the contemporary pop culture trappings of the holiday and reconnect with the deeper, more spiritual origins. We'll also hear about Vision Maker Media's expanded push to train and support young filmmakers to tell stories driven by mission. The Native Youth Media Project partners with tribes, organizations, and individuals to develop storytellers at a time when federal support for such projects has disappeared. GUESTS Janet Martinez (Zapotec), executive director of Communidades Indigenas en Liderazgo (CIELO) Kurly Tlapoyawa (Chicano and Nahua), archaeologist and co-host of the “Tales from Aztlantis” podcast Francene Blythe (Diné, Sisseton Wahpeton and Eastern Band of Cherokee), executive director of Vision Maker Media Anita Huízar-Hernández, associate director of the Hispanic Research Center and publisher and managing editor of the Bilingual Press at Arizona State University

Continual Improvement is at the heart of ISO Management, a large part of which is dedicated to ensuring issues don't reoccur. This is more than just putting a plaster on it and calling it a day, it's about finding the root cause. This not only eliminates wasted time, effort and money with firefighting repeated mistakes, but also drives meaningful improvement. Over the years, many techniques have been developed to help with finding cause. In this episode, Ian Battersby explores the need to find the root cause of issues in ISO Management and explains some key techniques for root cause analysis that you can put into practice to help stop recurring issues.   You'll learn ·      What is meant by 'finding cause'? ·      Why do you need to find the cause? ·      Where is finding cause specified in ISO Standards? ·      Finding cause in practice ·      What are the 5 Why's? ·      What is the fish bone / Ishikawa? ·      What is FMEA? ·      What is fault tree analysis? ·      How do these techniques work in practice?   Resources ·      Isologyhub   In this episode, we talk about: [02:05] Episode Summary – Ian dives into finding cause within ISO Management, explaining various techniques to help you prevent recurring issues. [03:15] What is meant by 'Finding cause'? When an output from a process is not what was expected, then it is classed as a non-conformity which will need to be addressed through corrective action. Before you can put that action into place, you need to identify the root cause for the issue. It's about putting right what went wrong. [04:00] Why do you need to find cause? Ian gives an example of a reactive response to resolving an issue, it didn't get to the root of why the mistake happened in the first place.   Finding cause is necessary to stop issues from repeating, rather than simply firefighting issues as they occur. ISO terminology has updated to reflect this over the years. There used to be a term called 'Preventive action', but this has since been changed to 'Corrective action' following on from the 2015 Annex SL update to many ISO Standards. This reflects the new risk-based approach to ISO management. The terms are largely the same in nature, but preventive action was widely misunderstood and so this was renamed and clarified following 2015. [05:55] Where is finding cause specified in ISO Standards? As with many aspects of ISO, the need for finding cause can be found in a few places within a Standard, including: - Clause 6.1.1 Planning: It specifies the need to determine risks and opportunities that need to be addressed. This is because they will affect the desired outcome of your Management System. It's also a good place to start thinking about how to reduce those risks. Evaluating your strengths and weaknesses also gives you the chance to contemplate whether your existing processes are good at delivering what you want. Clause 10 Improvement: The Standard states something to the effect of 'the organisation shall determine and select opportunities for improvement and implement any necessary actions to address those opportunities' These opportunities will focus on improving products and services, which includes correcting, preventing or reducing undesired results. Also included under clause 10 is a subclause that directly addresses non-conformities and corrective action. These specify not only the need to resolve issues as they arise, but to evaluate the need for action to eliminate the root cause. Additional requirements include the need to review these actions and determine if they are actually effective. Ian goes into Clause 10 in more detail in a previous podcast specifically looking at opportunities for improvement. [14:20] Finding cause in practice – Why a methodology is necessary: Ian provides an example where an employee may lack confidence completing a certain activity. Their lack of competence could lead to a process being delivered incorrectly. That adverse quality outcome would then likely end up with the customer who would raise a complaint, in this instance that could be a damaged product. The damaged product is what needs correcting, from your perspective you would be looking at what caused that to prevent recurrence. Without knowing the initial cause, you would need to determine whether it's a production issue or a human error. These types of scenarios can branch out further than the initial quality issue. For example, if that damaged product causes harm, then it turns into a health & safety risk. If products need to be scrapped, then there's an environmental factor. Complaints related to product quality may also not be recorded in a standard non-conformity system, and could easily be missed for a full investigation to find root cause. This is why it's important to have a consistent approach, in both logging issues and evaluating them to determine cause. [18:10] What are the 5 Why's? This is one of the more popular methods that people use to determine cause. It's simply a case of asking why a scenario happened, usually 5 times, though you can ask more or less depending on how long it takes to reach the core issue. It doesn't require much training and all it requires is an open and honest response to the questions. This method can get answers quickly and is often utilised as an early problem solving technique. [19:30] What is the fish bone / Ishikawa? This is a more visual method to find cause. Depicting a fish skeleton that categorises possible causes and groups these accordingly. These causes are then discussed for a few minutes, typically with teams of people in order to gain different perspectives to help pull apart complex problems into their contributing factors. This method is particularly useful in cases where there isn't a single underlying cause. [20:30] What is FMEA? FMEA or Failure Modes and Effects Analysis is a more structured technique and acts like a risk assessment in reverse. It looks at what can go wrong, what the effect of failure is and then how critical that failure is to the outcome of what you're trying to do. It uses risk priorities to decide what's more important. [21:15] What is Fault Tree Analysis? This method utilises a top-down logical approach. It's a diagrammatic representation of what's going wrong. It asks, does this happen? Yes or no or both, and branches down paths that explore the issue. It allows for quantitative measures with a number output that can help determine how likely recurrence will be.   It's a method that is often used in engineering and manufacturing processes. [22:55] Scatter Diagrams:  Scatter diagrams are a good tool to find correlation. They help visualise the relationship between two variables. If you have data rich environments, these can really help you plot out those relationships and make those links that otherwise may have been missed. [23:40] The 5 Why's in more detail:  The 5 Why's is a great starting technique as it requires little training. Ian provides an example of using the 5 Why's, with the scenario of a worker who has injured themselves while cutting some wood. Using the 5 Why's, he asks these questions: ·      Why did the workers hand slip while cutting the wood? – They were holding the material in one had without the use of any clamping device to keep it steady. ·      Why was the material being held by hand instead of using a clamp? Because there was no clamping device available. ·      Why was there no clamping device available on the table? The design of that workstation didn't take into consideration the need for a permanent clamping fixture. ·      Why wasn't that taken into consideration for the workstation? The risk assessment for that workstation was overlooked. From this exercise, you can see how you can get to the root of an issue by simply asking 'Why' a number of times. Again, it can be more or less than 5 times, the name is simply a guideline. [25:40] The Fishbone / Ishikawa method in more detail: Another favoured simple technique for finding cause is the fishbone method. It utilises 6 categories to get to the root of an issue, those being:- ·      Machine: Addressing the equipment or technology that you use to deliver products and services. ·      Method: The way in which you deliver products and services. ·      Material: The raw inputs into your processes. ·      Measurement: The data and metrics that you use to monitor the successful delivery of your products and services. ·      Mother Nature: The environment and conditions in which you're operating.  ·      Man – Although this has now been updated to 'People', addresses the human element of product and service delivery. This is a great method for instances where there may be multiple root issues, so you can categorise and analyse each of them with multiple perspectives involved as this is considered a more collaborative method for root cause. [28:15] Record your findings: We dive more into this in a previous episode, but essentially, it's a requirement of every ISO Standard to address these non-conformities as they occur. Going through the process of root cause and rectifying the issue will need documentation to prove that you are actively addressing these issues, as well as doing as much as you can to prevent recurrence.   There is no defined way to do this in the Standard, so it can be documented via forms, intranets, other digital systems etc. Documenting all the evidence of resolving issues may seem arduous at times, but it will ultimately lead to genuine continual improvement, and will lead to reduced overall error.   If you'd like any assistance with ISO Implementation or support, get in touch with us, we'd be happy to help. We'd love to hear your views and comments about the ISO Show, here's how: ●     Share the ISO Show on Twitter or Linkedin ●     Leave an honest review on iTunes or Soundcloud. Your ratings and reviews really help and we read each one. Subscribe to keep up-to-date with our latest episodes: Stitcher | Spotify | YouTube |iTunes | Soundcloud | Mailing List

This Truth Be Told episode is a powerful exploration of wrongful convictions, highlighting the harrowing journey of those who have been unjustly imprisoned. Through the lens of Jeff Deskovic's story, the conversation delves into the systemic failures of the justice system and the resilience required to overcome such profound adversity. Jeff shares his personal journey of falsely confessing, being wrongfully convicted and later exonerated.  He then expands on his inspirational journey into criminal justice reform. Filmmaker Jia Rizvi captures the raw emotions and critical insights needed to spark meaningful change, making this a must-watch for anyone passionate about justice and reform.  Jia shares the behind-the-scenes work that goes into creating a documentary and artfully and empathetically amplifying Jeff's voice. Learn more about Jia's work and her films here! Support Jeff and his foundation here! Connect with our host, Dave Thompson, CFI! Don't forget to subscribe, rate and share! Truths: Wrongful Convictions: The project highlights the traumatic experience of being wrongfully convicted and the long-lasting impact it has on individuals, emphasizing the need for systemic change in the justice system. Role of Communication: Effective communication is crucial in preventing wrongful convictions, as demonstrated by the filmmakers' efforts to give a voice to those affected and educate the public. Importance of Advocacy: The project underscores the power of advocacy and storytelling in raising awareness and driving legislative changes to prevent future injustices. Challenges of Reentry: Exonerees face significant challenges when reentering society, including lack of support, employment difficulties, and mental health struggles, highlighting the need for comprehensive reentry programs. Impact of Media: Films and documentaries play a vital role in capturing public attention and fostering empathy, which can lead to increased support for reform efforts. Personal Resilience: The resilience and determination of individuals like Jeff, who continue to fight for justice and support others despite their own traumatic experiences, is a powerful testament to human strength. Community and Support: Building a supportive community around exonerees and those advocating for justice is essential for sustaining momentum and achieving meaningful change. Other resources: Home | National Registry of Exonerations Innocence Network Join us at next year's Elite Training Days conference!

How to Build a High-Performing Sales Team in a Founder-Led Business: Insights from Nicholas LoiseFor many small and midsize business owners, sales can be both the engine and the bottleneck of growth. Founder-led sales will only take a company so far before scalability demands process, structure, and leadership. In this episode, host Josh Elledge speaks with Nicholas Loise, Founder of Sales Performance Team, who shares practical strategies for transitioning from founder-driven selling to building a high-performing, self-sustaining sales organization.Building a Scalable Sales SystemNicholas Loise explains that most founders struggle with hiring salespeople because they underestimate how different it is to sell for a small business compared to a large enterprise. Without the backing of a big brand, sales success depends on grit, creativity, and adaptability. He emphasizes that before hiring, founders must document their entire sales process—from prospecting and discovery to objection handling and closing—so new hires have a clear roadmap to follow.Once the playbook is in place, Nicholas recommends hiring two salespeople at once to increase the chances of success, benchmark performance, and encourage healthy collaboration. He also stresses the importance of investing heavily in the first 90 days, creating structured onboarding, shadowing opportunities, and clear milestones to ensure quick ramp-up and retention. Compensation should be simple and transparent, typically a mix of base salary plus commission that motivates results while providing stability during onboarding.Finally, Nicholas discusses how to maintain oversight without micromanaging. Delegating sales effectively requires trust—but also process. Regular reviews, feedback loops, and continuous updates to your playbook keep the system strong. By using objective assessment tools and focusing on cultural fit, founders can build sales teams that scale sustainably and deliver consistent performance long after they've stepped out of the front-line role.About Nicholas LoiseNicholas Loise is the Founder of Sales Performance Team and a seasoned sales strategist who helps founder-led businesses build scalable, high-performing sales teams. With decades of experience in sales leadership, Nicholas specializes in designing sales playbooks, recruiting and onboarding top-performing reps, and aligning compensation structures that drive profitable growth.About Sales Performance TeamSales Performance Team helps $1M–$25M companies transition from founder-led selling to a system-driven sales organization. The firm provides fractional sales leadership, sales team recruitment, onboarding systems, compensation design, and proven frameworks that help founders replace intuition with strategy—and build a sales team that consistently delivers results.Links Mentioned in This EpisodeSales Performance Team WebsiteNicholas Loise LinkedIn ProfileKey Episode HighlightsFounders often struggle to hire sales reps because they underestimate how different small-business selling is from enterprise sales.Documenting your entire sales process—from prospecting to closing—is essential before stepping out of the role.Hiring two salespeople at once improves benchmarking, morale, and retention while reducing hiring risk.Strong onboarding within the first 90 days directly impacts sales performance and long-term success.Keep compensation plans simple, transparent, and performance-driven to attract and retain top...

I can still hear that corporate command, “Better get that in writing.” Learn how to get a better response from your standard communication. #ThePitch #INICIVOX #VirtualMentorship

Summary  In this episode of the Be a Smarter Homeowner Podcast, hosts Elizabeth Dodson and John Bodrozic discuss essential knowledge every homeowner should have regarding their home's utilities. They emphasize the importance of understanding how to manage water, electricity, and gas systems to prevent damage and ensure safety. The conversation covers practical tips on locating shutoff valves, the significance of sump pumps, and the necessity of documenting procedures for emergencies. The hosts aim to empower homeowners with the knowledge to protect their homes and minimize risks effectively. Takeaways  Homeowners should know how to manage their utilities effectively. Understanding where shutoff valves are can prevent significant damage. Documenting utility shutoff procedures can enhance preparedness. Sump pumps are crucial for homes with basements to prevent flooding. Awareness of home systems contributes to overall safety. Gas shutoff valves are essential for preventing neighborhood hazards. Electricity management is key during repairs or emergencies. Homeowners should regularly check and maintain their utility systems. Knowledge of sewer cleanouts can prevent costly backups. Proactive measures can save homeowners from extensive damage. Sound bites  "Be a Smarter Homeowner Podcast" "How do I protect my home?" "Awareness is the key to minimizing damage."   Chapters 00:00 Understanding Home Utilities and Their Importance 03:05 Water Shutoff Valves: The First Line of Defense 05:59 Electricity: Managing Your Home's Power Supply 11:58 Gas Safety: Knowing Your Shutoff Points 17:47 Sump Pumps and Sewer Lines: Preventing Water Damage 30:00 Final Thoughts: Awareness and Preparedness for Homeowners

When you've spent years building trust with a partner who once championed your career, it can be deeply unsettling when they suddenly stop giving you work, exclude you from client calls, or even fail to support your partnership candidacy. I've seen this happen often in BigLaw. It's painful, hard to understand, and often tough to find a way to move forward without that support. In this episode, I explain the structural, economic, and political reasons that drive this kind of behavior, and the concrete steps you can take to protect your career, your client relationships, and your reputation within your BigLaw firm. I also share how to recognize early warning signs, document your value, and rebuild momentum through new mentors, visibility, and business development efforts. At a Glance: 00:00 Introduction and the reality of losing a mentor partner's support 02:12 The first signs of a deliberate cutoff and how to recognize the shift 03:40 Structural reasons behind the change, including billable pressure and firm economics 05:26 How your mentor may fear losing client credit or control as you become more visible 06:45 Why mentors can begin to see protégés as competitors rather than allies 08:24 The emotional impact of losing your mentor, and how to separate feelings from facts 09:54 Protecting your hours and finding alternate work streams 11:03 Documenting every contribution and communicating it effectively 12:52 How to prepare for a difficult conversation with your mentor partner 14:35 Turning insights into a strategy for next steps 15:48 Expanding mentorship, sponsorship, and visibility 16:23 When and how to escalate the issue if needed 19:52 Steps to rebuild relationships and regain career stability 23:25 Why losing a mentor can become a turning point for independence Rate, Review, & Follow on Apple Podcasts & Spotify Do you enjoy listening to Big Law Life?  Please consider rating and reviewing the show! This helps support and reach more people like you who want to grow a career in Big Law.  For Apple Podcasts, click here, scroll to the bottom, tap to rate with five stars, and select “Write a Review.” Then be sure to let me know what you loved most about the episode! Also, if you haven't done so already, follow the podcast here!  For Spotify, tap here on your mobile phone, follow the podcast, listen to the show, then find the rating icon below the description, and tap to rate with five stars. Interested in doing 1-2-1 coaching with Laura Terrell? Or learning more about her work coaching and consulting? Here are ways to reach out to her: www.lauraterrell.com  laura@lauraterrell.com   LinkedIn: https://www.linkedin.com/in/lauralterrell/  Instagram: https://www.instagram.com/lauraterrellcoaching/  Show notes: https://www.lauraterrell.com/podcast  

Uptown Voices: An Uptown Story is a multi-media exhibition in development designed to document Harlem's history through intimate large-format portraits and oral histories of residents who have lived in the community for 30 years or more. The brother and sister team behind the project, photographer Wil Pierce and curator Joyous Pierce, have launched an open call for nominations—inviting New Yorkers to put forward family, friends, or neighbors whose Harlem stories should be preserved.

Rosie Grant is the creator of Ghostly Archive, a project documenting the real-life phenomenon of recipes inscribed on tombstones in cemeteries around the world. After years of seeking out these immortalized dishes, she's released a truly singular cookbook, To Die For: A Cookbook of Gravestone Recipes. Today on the show, we chat about the project, creating the book, and some of Rosie's favorite gravestone recipes. Also on the show, Matt catches up with Vanessa Anderson, known widely online as Grocery Goblin. Vanessa writes a terrific Substack and posts video clips on social media, all in celebration of international grocery stores. Vanessa is based in Los Angeles, home to a great grocery store scene, and we talk about her work and some of her favorite places to shop. Subscribe to This Is TASTE: ⁠⁠Apple Podcasts⁠⁠, ⁠⁠Spotify⁠⁠, ⁠⁠YouTube⁠⁠  Learn more about your ad choices. Visit megaphone.fm/adchoices

In this episode of The Balance, Jessica Vance joins me to discuss her new book, Evidence of Inquiry: Exploring, Questioning, and Documenting with Learning Walls. We explore what it means to “follow your learners” and how inquiry shifts the way teachers engage students around the topics and concepts at the center of the curriculum. Jessica unpacks the purpose and power of learning walls, explaining how they make student thinking visible, create space for collaborative meaning-making, and even serve as professional playgrounds for teachers themselves. Together, we reflect on the mindset, culture, and practical strategies that help both teachers and students embrace uncertainty, curiosity, and deeper learning. Episode Resources Jessica's Instagram: @‌jess_vanceedu Evidence of Inquiry: Exploring, Questioning, and Documenting with Learning Walls Leading with a Lens of Inquiry: Cultivating Conditions for Curiosity and Empowering Agency

Commerce, Conflict, and the High-Risk Sealing Voyage Guest: Eric Jay Dolin Left for Dead is set during the War of 1812, documenting a collision between young America and Britain in the contested Falkland Islands. The narrative begins with the highly lucrative sealing commerce, which involved gathering millions of seal skins and sea otter pelts for sale primarily in China. American sealer Charles Barnard proposed a high-risk voyage aboard the brig Nanina to Murray and Son, aiming to exploit the projected pent-up demand due to reduced competition. Despite the imminent war, they left New York Harbor just as an embargo was placed. The crew included Barnard's elderly, infirm father, Valentine, who was intended to sail the initial cargo back to New York. The presence of four experienced sealing captains among the crew, including diarist Barzillai Pease, created a potential "recipe for disaster."

Fresh off my self-supported AT record, I sit down with 2013 AT self-supported FKT holder Matt Kirk to talk about the weird gravity of post-trail depression, the long arc of the record from Ward Leonard to Stringbean to Tara, and where the line is with tech, tracking, and “help” on a self-supported effort. We dig into calories gone wrong (why 3,500/day failed), Shenandoah as a quiet crux, trail magic ethics, and why simplicity might be the best rule we have left. Matt shares the origin story of SCAR, naming it, and—plot twist—how he met his wife on the AT. I share some nuts and bolts from my run (18 mail drops, ~12 power banks, and way too much battery anxiety), and we both argue for screen-free campfire vibes and keeping the culture alive while the times keep dropping.If you're into FKTs, thru-hiking history, or just need a blueprint for surviving the “now what?” after a big goal, this one's for you.Check out Matt Kirk online:His Blog: https://matthewkirk.blogspot.com/His Youtube: https://www.youtube.com/channel/UCXrGFci8u_goKfnP8PqkaLADonate to the Trevor Project: https://give.thetrevorproject.org/fundraiser/6530749Chapters00:00 Post-Hike Transition and Emotional Challenges02:40 Caloric Miscalculations and Preparation for FKT05:31 Evolution of FKT Records and Technological Advances08:21 The Impact of Previous Record Holders10:48 Guidelines for Self-Supported Hiking13:28 Documenting the Journey: Technology and Tracking16:21 The Balance of Simplicity and Validation in Records19:02 Reflections on the Future of FKT Attempts27:13 Navigating Resupply Challenges32:58 Mental Strategies for Endurance37:13 The Importance of Reflection41:06 Journey into Ultrarunning and FKTs51:09 The Cost of Technology in Hiking54:15 Navigating Technology and Safety on the Trail56:42 The Impact of Technology on Hiking Culture01:00:18 The Balance of Trail Magic and Self-Sufficiency01:05:01 Personal Stories: Meeting on the TrailSubscribe to Substack: http://freeoutside.substack.comSupport this content on patreon: HTTP://patreon.com/freeoutsideBuy my book "Free Outside" on Amazon: https://amzn.to/39LpoSFEmail me to buy a signed copy of my book, "Free Outside" at jeff@freeoutside.comWatch the movie about setting the record on the Colorado Trail: https://tubitv.com/movies/100019916/free-outsideWebsite: www.Freeoutside.comInstagram: thefreeoutsidefacebook: www.facebook.com/freeoutside

The Day After - Episode Recap | Oct 3rdToday's episode featured a powerful sit-down with Andre Anderson and Nabil Al-Kinani (authors of Authors of the Estate), alongside the usual TDA crew. Highlights:Faith & upbringing: Guests reflected on how scripture, family, and estate life shaped resilience and vision.Authors of the Estate project: Documenting unheard stories across Chalk Hill and St. Raphael's - from nerds to road men to aunties and uncles.Reclaiming the narrative: Shifting focus away from the “trap” story to creativity, comics, gaming, and wider cultural contributions.Grassroots publishing: Conversations, WhatsApp messages, and local interviews turned into books hand-delivered into 1,000 homes.Film & legacy: Their project is now a feature film premiering in Leicester Square, cementing estate stories as cinema-worthy history.Eman vs. Nabil - the capitalism clash: A heated “war” broke out between Eman and Nabil on capitalism vs. socialism - with Nabil stressing capitalism's exploitation and Eman pushing back with counter-examples, sparking one of the show's sharpest debates.Critical reflections: Conversations stretched into Nation of Islam vs. mainstream Islam, historical exploitation, and whether revolutions are ever truly allowed to succeed.Future building: Andre introduced tools like the Freedom & Balance card system and plans for a Hood Preservation & Futurist Association - reimagining estates if residents owned the land.

If you have built your BigLaw career around a thriving regulatory or enforcement practice, you know how difficult it can be for you and your practice when that work suddenly isn't there. One month you are buried in nvestigations motivated by government inquiries or merger reviews, and the next your phone goes quiet because enforcement priorities shifted, agency budgets got cut, or a new administration has redirected resources. It is unsettling, especially when your brand, reputation and and client base are tied to that flow of work. In this episode, I walk through the reality of what it can feel like and what to do when your once-busy enforcement and regulatory practice slows. I share how to distinguish between cyclical downturns and structural changes that reshape a practice like this long term, and share some specific examples across areas such as FCPA, antitrust, and privacy to illustrate how BigLaw attorneys can pivot effectively. I also outline practical steps to stay visible with clients as well as inside your firm so that even when the billable work is not there, your value and future opportunities are. At a Glance: 00:00 Introduction need to navigate BigLaw downturns in regulatory and enforcement work 01:20 When busy practices suddenly dry up: regulatory shifts and enforcement changes 02:14 How external forces such as politics, budgets, and agency leadership reshape your practice overnight 03:03 Early warning signs that your work is slowing down in these areas 03:37 The emotional impact: anxiety, uncertainty, and fear of career derailment 04:08 Diagnosing cyclical vs. structural downturns with concrete indicators 05:16 Why this distinction matters for your long-term career strategy 05:39 Examples of temporary pivots that kept practices alive (FCPA, antitrust, GDPR, privacy) 07:04 How lawyers can broaden their practices to adapt to structural changes 08:08 The importance of proactive client communication, including with “good news” updates 09:37 What to do when billable hours stall: seeking work across departments and staying visible 10:41 Positioning yourself as a thought leader through articles, CLEs, and conferences 11:29 Documenting outreach, cross-practice contributions, and client loyalty for firm leadership 12:21 Demonstrating cross-practice value: aligning with busier groups inside your firm 13:30 How client loyalty and referrals strengthen your standing even in slow periods 13:58 Reframing your practice to be less narrowly defined by one enforcement area 14:27 How one partner survived cuts by documenting value and broadening expertise 15:16 Long-game mindset: showing your firm that you are indispensable beyond billable hours Rate, Review, & Follow on Apple Podcasts & Spotify Do you enjoy listening to Big Law Life?  Please consider rating and reviewing the show! This helps support and reach more people like you who want to grow a career in Big Law.  For Apple Podcasts, click here, scroll to the bottom, tap to rate with five stars, and select “Write a Review.” Then be sure to let me know what you loved most about the episode! Also, if you haven't done so already, follow the podcast here!  For Spotify, tap here on your mobile phone, follow the podcast, listen to the show, then find the rating icon below the description, and tap to rate with five stars. Interested in doing 1-2-1 coaching with Laura Terrell? Or learning more about her work coaching and consulting? Here are ways to reach out to her: www.lauraterrell.com  laura@lauraterrell.com   LinkedIn: https://www.linkedin.com/in/lauralterrell/  Instagram: https://www.instagram.com/lauraterrellcoaching/  Show notes: https://www.lauraterrell.com/podcast

On this episode of Japan Station, we're joined by documentary filmmaker Ema Ryan Yamazaki to talk about her latest documentary The Making of a Japanese and her latest short documentary Instrument of a Beating Heart. During the conversation we focus on the making of these films, what makes Japanese elementary schools unique, the role Japanese elementary schools play in shaping Japanese society, and more.

Rebecca Culshaw Smith's Substack, “The Real AIDS Epidemic,” highlights core criticisms of mainstream HIV/AIDS theory, medical testing, pharmaceutical practices, and challenges to scientific orthodoxy. Based on her popular posts, interviews, and thematic content, these are 20 of the most important ideas advanced on her platform: 1. Questioning the existence of HIV as a unique virus, arguing that classic virological isolation (Koch's postulates) has not been fulfilled. 2. Highlighting the non-specificity and cross-reactivity of HIV antibody tests, leading to potential misdiagnosis. 3. Criticism of “viral load” PCR tests for not detecting whole pathogens but only RNA fragments. 4. Noting the shifting criteria for HIV test positivity over time, calling diagnostic standards into question. 5. Documenting long-term “non-progressors” and “elite controllers” who remain healthy without antiretroviral therapy. 6. Raising awareness of AIDS-defining illnesses in HIV-negative individuals and questioning causality. 7. Arguing that hazard from AIDS medications (e.g., AZT, Truvada, Prep) may outweigh their benefits, especially due to their toxicity and inconsistent trial results. 8. Critique of the marketing and deployment of pre-exposure prophylaxis (Prep), calling it a pharmaceutical “scandal” targeting people not at significant risk. 9.Exploring how COVID-19 public health narratives mirror what she views as deception and fear tactics from the AIDS era. 10. Disputing the epidemiological narrative that AIDS is globally caused by a single infectious agent, and highlighting massive regional/demographic inconsistencies. 11. Exposing groupthink, censorship, and reputational shaming used against scientists questioning the HIV/AIDS paradigm. 12. Emphasizing failures of antiretroviral therapy in preventing disease progression for many patients. 13.. Explaining the statistical and mathematical problems in foundational HIV/AIDS research and the “shaky foundation” of guiding studies. 14. Arguing that AIDS-defining diseases may often reflect toxicity, malnutrition, or existing comorbidities, not a distinct viral syndrome. 15. Linking historical and social factors (such as drug use, pharmaceutical incentives) to the creation and persistence of the HIV/AIDS establishment. 16. Alerting readers to issues of false positive antenatal screening and broader concerns about mass diagnostic testing in medicine. 17. Suggesting that “virus-like particles” in the body  are misidentified as pathogens, not proof of HIV's existence. 18. Forecasting that advances in AI and technology may help overturn scientific “consensus” by increasing transparency and debate. 19 Publicly refuting hit pieces and attempts to “cancel” her work as ideological suppression, not science. 20.Advocating for a return to fundamental scientific rigor and genuine skepticism in medical research, especially around virology and public health narratives. These topics synthesize her core objections to HIV/AIDS orthodoxy and frame her Substack as a point of dissent and critique against modern medical paradigms and their social consequences.

A Chinese director has spent over a decade documenting China-Africa stories, using his camera to bridge cultures and foster understanding. He's also dedicated to mentoring the next generation of China-Africa storytellers, further strengthening the partnership.

Artist Kristen Huizar joins What's My Thesis? to reflect on drawing, printmaking, and the act of documenting Los Angeles. Born and raised in Commerce, CA, she traces her path from community college to Cal State Long Beach, where persistence and community shaped her practice. Working with wax pastels on plastic vinyl, hand stitching, and large lino cuts, Huizar explores repetition, process, and the archival impulse. Her drawings function as reportage—capturing overlooked city views, everyday details, and the rapid changes of East L.A. The conversation considers Chicana identity, community studios, and the politics of representation, offering insight into how artists both preserve and reimagine the city.

Karly Heffernan shares her journey from being an elite hockey player for... The post Documenting Decisions: Clarity for the Construction Industry with Karly Heffernan first appeared on Startup Canada.

Join us for one of the most requested guests and Cam's oldest son - Tanner Hanes. Cam and Tanner talk about Tanner's recent elk hunt where he harvested one of the biggest bulls of his lifetime on public land, difficulties of hunting the wilderness, and more!  Follow along: Instagram: https://www.instagram.com/cameronrhanes Twitter: https://twitter.com/cameronhanes Facebook: https://www.facebook.com/camhanes/ Website: https://www.cameronhanes.com Timestamps: 00:00:00  Tanner's Hunting Career: The Army, Work, & Experience from a Friend 00:06:11  Packing Meat out of the Wilderness: Solo vs Group Hunts 00:13:17  Garret Downing: Handling the Mules for the Hunt 00:15:51  Tanner's 7x7 Public Land Bull: The Hunt 00:25:55  Difficult Shots No One Wants to Talk About 00:38:48  Journaling During Hunting & Overcoming Failure 00:44:18  Day 3: Feelings of Jealousy and Defeat 00:49:13  Days 5-7: Hunting Alone, Keep Moving, and Weather in the Mountains 00:54:25  The Last Day: The Bull of Tanner's Lifetime 01:09:18  Hard Work and Luck 01:15:18  Hunting with Cam at 7 Years Old in the Mountains 01:16:47  Support with Hauling the Elk Meat Out & Tanner's Wife's Support 01:22:33  Cam's Wilderness Bull: A Team to Carry Out the Meat 01:31:35  Documenting the Memories 01:37:41  Finding Your Purpose After the Army 01:40:48  Luck is Not Something You Hope for in Hunting, it is Something You Earn 01:42:11  What Prepared Tanner the Most for the Hunt 01:43:25  QA: F#$k, Marry, Kill: Chicken Alfredo, Biscuits & Gravy, & Chicken Pesto 01:44:37  Generational Legacies in Hunting 01:49:36  Outro Thank you to our sponsors: Hoyt:⁠ http://bit.ly/3Zdamyv⁠ use code CAM for 10% off Grizzly Coolers: https://www.grizzlycoolers.com/ use code KEEPHAMMERING for 20% off Montana Knife Company: https://www.montanaknifecompany.com/ Use code CAM for 10% off  LMNT: Visit https://drinklmnt.com/cam for a free sample pack with any purchase MTN OPS Supplements: https://mtnops.com/ Use code KEEPHAMMERING for 20% off and Free Shipping Black Rifle Coffee: https://www.blackriflecoffee.com/ Use code KEEPHAMMERING for 20% your first order

In this episode of the CodeCast Podcast, Terry addresses a common misconception among medical providers: the belief that simply listing a patient's medications or repeatedly noting “continue meds” is enough to support a moderate-level evaluation and management visit, such as CPT codes 99214 or 99204. In reality, this documentation alone does not meet the criteria.= […] The post Are you documenting prescription drug management risk? appeared first on Terry Fletcher Consulting, Inc..

In this episode of the CodeCast Podcast, Terry addresses a common misconception among medical providers: the belief that simply listing a patient's medications or repeatedly noting “continue meds” is enough to support a moderate-level evaluation and management visit, such as CPT codes 99214 or 99204. In reality, this documentation alone does not meet the criteria.= […] The post Are you documenting prescription drug management risk? (Fixed Audio) appeared first on Terry Fletcher Consulting, Inc..

Warning that this epispode of Doin' Time contains audio images of Aboriginal and Torres Strait Islander people who have died, and graphic discussion of deaths in custody.On today's show Marisa speaks with David Mejia-Canales, Senior Lawyer at the Human Rights Law Centre about protest laws.Following that Brett Collins from Justice Action joined the show to speak about youth justice and the work of Justice Action in prisons. The show ends with a conversation with Boe Spearim, First Nations activist and podcaster about the Frontier Wars, police powers and Aboriginal deaths in custody.

Foundations of Amateur Radio The other day I came across an article written by programmer, artist, and game designer "blinry" with the intriguing title: "Fifty Things you can do with a Software Defined Radio". Documenting a weeks' worth of joyous wandering through the radio spectrum it explains in readily accessible terms how they used an RTL-SDR dongle to explore the myriad radio transmissions that surround us all day and every day. As you might know, I've been a radio amateur since 2010 and I must confess, even with all the things I've done and documented here, there's plenty in this adventure guide that I've yet to attempt. For example, when was the last time you decoded the various sub-carriers in an FM broadcast signal, including the pilot tone, the stereo signal, station meta and road traffic information? Have you ever decoded the 433 MHz sensor signals that your neighbours might have installed, weather, security and other gadgets? Or decoded shipping data, transmitted using AIS, or Automatic Identification System, and for context, we're only up to item 12 on the list. One of the biggest takeaways for me was that this is something that is accessible to anyone, and is a family friendly introduction to the world of radio that amateurs already know and love. The article touches on various applications that you might use to explore the highways and byways of the radio spectrum, including SDR++, SDRangel, WSJT-X, QSSTV, and even mentions GNU Radio. With enough detail to whet the appetite, I learned that SDRangel, developed by Edouard F4EXB and 70 other contributors, has all manner of interesting decoders built-in, like ADS-B, Stereo FM, RDS, DAB, AIS, weather balloon telemetry, APRS, even VOR. As it happens, you don't even need to install SDRangel to get going. Head on over to sdrangel.org and click on "websdr" and it'll launch right in your browser. Once you're up and running, you can use your RTL-SDR dongle to start your own small step into the wide world of radio, amateur or not. Sadly the PlutoSDR does not work on the experimental web version, so I had to install SDRangel locally. That said, I did get it to run and connect to my PlutoSDR which worked out of the box. The user tutorial is online and the Quick-Start walks you through the process of getting the software installed and running. One thing that eluded me for way too long is the notion of channel decoders. Essentially you configure the receiver, in my case a PlutoSDR, and start it running. You'll be able to change frequency and see the waterfall display, but nothing else happens, and there's no obvious AM, FM or other mode buttons you'd find on a traditional radio. Instead, you'll need to add a channel decoder, cunningly disguised as a triangle with circles at the corners with a little plus symbol at the top. You'll find it immediately to the left of your device name. When you click it, you're presented with a list of channel decoders, which you can add to the work space. This will do the work of actually decoding the signal that's coming into the software. SDRangel also supports M17, FreeDV, RTTY, FT8 and plenty of other amateur modes, and includes the ability to transmit. Oh, did I mention, it can also connect to remote kiwisdr receivers? I have to say, it's a joy to see software that I've previously looked at and admittedly shied away from, actually doing something with the radio spectrum around me. I will confess that SDRangel has a lot of moving parts and it's like sendmail, user friendly, just picky whom it makes friends with. So, time to dig in, play around and bring it to the next amateur radio field day "Show and Tell" and share with the general public just how interesting the radio spectrum around us can be. I'm going to work my way through the 50 items, just for giggles. What are you waiting for? I'm Onno VK6FLAB

What if your job respected your life as much as you respect your job? Dr. Patricia Grabarek and Dr. Katina Sawyer dive into a radical (but necessary) idea: work should support your life… not consume it.

Francois Daost is a W3C staff member and co-chair of the Web Developer Experience Community Group. We discuss the W3C's role and what it's like to go through the browser standardization process. Related links W3C TC39 Internet Engineering Task Force Web Hypertext Application Technology Working Group (WHATWG) Horizontal Groups Alliance for Open Media What is MPEG-DASH? | HLS vs. DASH Information about W3C and Encrypted Media Extensions (EME) Widevine PlayReady Media Source API Encrypted Media Extensions API requestVideoFrameCallback() Business Benefits of the W3C Patent Policy web.dev Baseline Portable Network Graphics Specification Internet Explorer 6 CSS Vendor Prefix WebRTC Transcript You can help correct transcripts on GitHub. Intro [00:00:00] Jeremy: today I'm talking to Francois Daoust. He's a staff member at the W3C. And we're gonna talk about the W3C and the recommendation process and discuss, Francois's experience with, with how these features end up in our browsers. [00:00:16] Jeremy: So, Francois, welcome [00:00:18] Francois: Thank you Jeremy and uh, many thanks for the invitation. I'm really thrilled to be part of this podcast. What's the W3C? [00:00:26] Jeremy: I think many of our listeners will have heard about the W3C, but they may not actually know what it is. So could you start by explaining what it is? [00:00:37] Francois: Sure. So W3C stands for the Worldwide Web Consortium. It's a standardization organization. I guess that's how people should think about W3C. it was created in 1994. I, by, uh, Tim Berners Lee, who was the inventor of the web. Tim Berners Lee was the, director of W3C for a long, long time. [00:01:00] Francois: He retired not long ago, a few years back. and W3C is, has, uh, a number of, uh. Properties, let's say first the goal is to produce royalty free standards, and that's very important. Uh, we want to make sure that, uh, the standard that get produced can be used and implemented without having to pay, fees to anyone. [00:01:23] Francois: We do web standards. I didn't mention it, but it's from the name. Standards that you find in your web browsers. But not only that, there are a number of other, uh, standards that got developed at W3C including, for example, XML. Data related standards. W3C as an organization is a consortium. [00:01:43] Francois: The, the C stands for consortium. Legally speaking, it's a, it's a 501c3 meaning in, so it's a US based, uh, legal entity not for profit. And the, the little three is important because it means it's public interest. That means we are a consortium, that means we have members, but at the same time, the goal, the mission is to the public. [00:02:05] Francois: So we're not only just, you know, doing what our members want. We are also making sure that what our members want is aligned with what end users in the end, need. and the W3C has a small team. And so I'm part of this, uh, of this team worldwide. Uh, 45 to 55 people, depending on how you count, mostly technical people and some, uh, admin, uh, as well, overseeing the, uh, the work, that we do, uh, at the W3C. Funding through membership fees [00:02:39] Jeremy: So you mentioned there's 45 to 55 people. How is this funded? Is this from governments or commercial companies? [00:02:47] Francois: The main source comes from membership fees. So the W3C has a, so members, uh, roughly 350 members, uh, at the W3C. And, in order to become a member, an organization needs to pay, uh, an annual membership fee. That's pretty common among, uh, standardization, uh, organizations. [00:03:07] Francois: And, we only have, uh, I guess three levels of membership, fees. Uh, well, you may find, uh, additional small levels, but three main ones. the goal is to make sure that, A big player will, not a big player or large company, will not have more rights than, uh, anything, anyone else. So we try to make sure that a member has the, you know, all members have equal, right? [00:03:30] Francois: if it's not perfect, but, uh, uh, that's how things are, are are set. So that's the main source of income for the W3C. And then we try to diversify just a little bit to get, uh, for example, we go to governments. We may go to governments in the u EU. We may, uh, take some, uh, grant for EU research projects that allow us, you know, to, study, explore topics. [00:03:54] Francois: Uh, in the US there, there used to be some, uh, some funding from coming from the government as well. So that, that's, uh, also, uh, a source. But the main one is, uh, membership fees. Relations to TC39, IETF, and WHATWG [00:04:04] Jeremy: And you mentioned that a lot of the W3C'S work is related to web standards. There's other groups like TC 39, which works on the JavaScript spec and the IETF, which I believe worked, with your group on WebRTC, I wonder if you could explain W3C'S connection to other groups like that. [00:04:28] Francois: sure. we try to collaborate with a, a number of, uh, standard other standardization organizations. So in general, everything goes well because you, you have, a clear separation of concerns. So you mentioned TC 39. Indeed. they are the ones who standardize, JavaScript. Proper name of JavaScript is the EcmaScript. [00:04:47] Francois: So that's tc. TC 39 is the technical committee at ecma. and so we have indeed interactions with them because their work directly impact the JavaScript that you're going to find in your, uh, run in your, in your web browser. And we develop a number of JavaScript APIs, uh, actually in W3C. [00:05:05] Francois: So we need to make sure that, the way we develop, uh, you know, these APIs align with the, the language itself. with IETF, the, the, the boundary is, uh, uh, is clear as well. It's a protocol and protocol for our network protocols for our, the IETF and application level. For W3C, that's usually how the distinction is made. [00:05:28] Francois: The boundaries are always a bit fuzzy, but that's how things work. And usually, uh, things work pretty well. Uh, there's also the WHATWG, uh, and the WHATWG is more the, the, the history was more complicated because, uh, t of a fork of the, uh, HTML specification, uh, at the time when it was developed by W3C, a long time ago. [00:05:49] Francois: And there was been some, uh, Well disagreement on the way things should have been done, and the WHATWG took over got created, took, took this the HTML spec and did it a different way. Went in another, another direction, and that other, other direction actually ended up being the direction. [00:06:06] Francois: So, that's a success, uh, from there. And so, W3C no longer works, no longer owns the, uh, HTML spec and the WHATWG has, uh, taken, uh, taken up a number of, uh, of different, core specifications for the web. Uh, doing a lot of work on the, uh, on interopoerability and making sure that, uh, the algorithm specified by the spec, were correct, which, which was something that historically we haven't been very good at at W3C. [00:06:35] Francois: And the way they've been working as a, has a lot of influence on the way we develop now, uh, the APIs, uh, from a W3C perspective. [00:06:44] Jeremy: So, just to make sure I understand correctly, you have TC 39, which is focused on the JavaScript or ECMAScript language itself, and you have APIs that are going to use JavaScript and interact with JavaScript. So you need to coordinate there. The, the have the specification for HTML. then the IATF, they are, I'm not sure if the right term would be, they, they would be one level lower perhaps, than the W3C. [00:07:17] Francois: That's how you, you can formulate it. Yes. The, the one layer, one layer layer in the ISO network in the ISO stack at the network level. How WebRTC spans the IETF and W3C [00:07:30] Jeremy: And so in that case, one place I've heard it mentioned is that webRTC, to, to use it, there is an IETF specification, and then perhaps there's a W3C recommendation and [00:07:43] Francois: Yes. so when we created the webRTC working group, that was in 2011, I think, it was created with a dual head. There was one RTC web, group that got created at IETF and a webRTC group that got created at W3C. And that was done on purpose. Of course, the goal was not to compete on the, on the solution, but actually to, have the two sides of the, uh, solution, be developed in parallel, the API, uh, the application front and the network front. [00:08:15] Francois: And there was a, and there's still a lot of overlap in, uh, participation between both groups, and that's what keep things successful. In the end. It's not, uh, you know, process or organization to organization, uh, relationships, coordination at the organization level. It's really the fact that you have participants that are essentially the same, on both sides of the equation. [00:08:36] Francois: That helps, uh, move things forward. Now, webRTC is, uh, is more complex than just one group at IETF. I mean, web, webRTC is a very complex set of, uh, of technologies, stack of technologies. So when you, when you. Pull a little, uh, protocol from IETFs. Suddenly you have the whole IETF that comes with you with it. [00:08:56] Francois: So you, it's the, you have the feeling that webRTC needs all of the, uh, internet protocols that got, uh, created to work Recommendations [00:09:04] Jeremy: And I think probably a lot of web developers, they may hear words like specification or standard, but I believe the, the official term, at least at the W3C, is this recommendation. And so I wonder if you can explain what that means. [00:09:24] Francois: Well. It means it means standard in the end. and that came from industry. That comes from a time where. As many standardization organizations. W3C was created not to be a standardization organization. It was felt that standard was not the right term because we were not a standardization organization. [00:09:45] Francois: So recommend IETF has the same thing. They call it RFC, request for comment, which, you know, stands for nothing in, and yet it's a standard. So W3C was created with the same kind of, uh thing. We needed some other terminology and we call that recommendation. But in the end, that's standard. It's really, uh, how you should see it. [00:10:08] Francois: And one thing I didn't mention when I, uh, introduced the W3C is there are two types of standards in the end, two main categories. There are, the de jure standards and defacto standards, two families. The de jure standards are the ones that are imposed by some kind of regulation. so it's really usually a standard you see imposed by governments, for example. [00:10:29] Francois: So when you look at your electric plug at home, there's some regulation there that says, this plug needs to have these properties. And that's a standard that gets imposed. It's a de jure standard. and then there are defacto standards which are really, uh, specifications that are out there and people agree to use it to implement it. [00:10:49] Francois: And by virtue of being used and implemented and used by everyone, they become standards. the, W3C really is in the, uh, second part. It's a defacto standard. IETF is the same thing. some of our standards are used in, uh, are referenced in regulations now, but, just a, a minority of them, most of them are defacto standards. [00:11:10] Francois: and that's important because that's in the end, it doesn't matter what the specific specification says, even though it's a bit confusing. What matters is that the, what the specifications says matches what implementations actually implement, and that these implementations are used, and are used interoperably across, you know, across browsers, for example, or across, uh, implementations, across users, across usages. [00:11:36] Francois: So, uh, standardization is a, is a lengthy process. The recommendation is the final stage in that, lengthy process. More and more we don't really reach recommendation anymore. If you look at, uh, at groups, uh, because we have another path, let's say we kind of, uh, we can stop at candidate recommendation, which is in theoretically a step before that. [00:12:02] Francois: But then you, you can stay there and, uh, stay there forever and publish new candidate recommendations. Um, uh, later on. What matters again is that, you know, you get this, virtuous feedback loop, uh, with implementers, and usage. [00:12:18] Jeremy: So if the candidate recommendation ends up being implemented by all the browsers, what's ends up being the distinction between a candidate and one that's a normal recommendation. [00:12:31] Francois: So, today it's mostly a process thing. Some groups actually decide to go to rec Some groups decide to stay at candidate rec and there's no formal difference between the, the two. we've made sure we've adopted, adjusted the process so that the important bits that, applied at the recommendation level now apply at the candidate rec level. Royalty free patent access [00:13:00] Francois: And by important things, I mean the patent commitments typically, uh, the patent policy fully applies at the candidate recommendation level so that you get your, protection, the royalty free patent protection that we, we were aiming at. [00:13:14] Francois: Some people do not care, you know, but most of the world still works with, uh, with patents, uh, for good, uh, or bad reasons. But, uh, uh, that's how things work. So we need to make, we're trying to make sure that we, we secure the right set of, um, of patent commitments from the right set of stakeholders. [00:13:35] Jeremy: Oh, so when someone implements a W3C recommendation or a candidate recommendation, the patent holders related to that recommendation, they basically agree to allow royalty-free use of that patent. [00:13:54] Francois: They do the one that were involved in the working group, of course, I mean, we can't say anything about the companies out there that may have patents and uh, are not part of this standardization process. So there's always, It's a remaining risk. but part of the goal when we create a working group is to make sure that, people understand the scope. [00:14:17] Francois: Lawyers look into it, and the, the legal teams that exist at the all the large companies, basically gave a green light saying, yeah, we, we we're pretty confident that we, we know where the patterns are on this particular, this particular area. And we are fine also, uh, letting go of the, the patterns we own ourselves. Implementations are built in parallel with standardization [00:14:39] Jeremy: And I think you had mentioned. What ends up being the most important is that the browser creators implement these recommendations. So it sounds like maybe the distinction between candidate recommendation and recommendation almost doesn't matter as long as you get the end result you want. [00:15:03] Francois: So, I mean, people will have different opinions, uh, in the, in standardization circles. And I mentioned also W3C is working on other kind of, uh, standards. So, uh, in some other areas, the nuance may be more important when we, but when, when you look at specification, that's target, web browsers. we've switched from a model where, specs were developed first and then implemented to a model where specs and implementing implementations are being, worked in parallel. [00:15:35] Francois: This actually relates to the evolution I was mentioning with the WHATWG taking over the HTML and, uh, focusing on the interoperability issues because the starting point was, yeah, we have an HTML 4.01 spec, uh, but it's not interoperable because it, it's not specified, are number of areas that are gray areas, you can implement them differently. [00:15:59] Francois: And so there are interoperable issues. Back to candidate rec actually, the, the, the, the stage was created, if I remember correctly. uh, if I'm, if I'm not wrong, the stage was created following the, uh, IE problem. In the CSS working group, IE6, uh, shipped with some, version of a CSS that was in the, as specified, you know, the spec was saying, you know, do that for the CSS box model. [00:16:27] Francois: And the IE6 was following that. And then the group decided to change, the box model and suddenly IE6 was no longer compliant. And that created a, a huge mess on the, in the history of, uh, of the web in a way. And so the, we, the, the, the, the candidate recommendation sta uh, stage was introduced following that to try to catch this kind of problems. [00:16:52] Francois: But nowadays, again, we, we switch to another model where it's more live. and so we, you, you'll find a number of specs that are not even at candidate rec level. They are at the, what we call a working draft, and they, they are being implemented, and if all goes well, the standardization process follows the implementation, and then you end up in a situation where you have your candidate rec when the, uh, spec ships. [00:17:18] Francois: a recent example would be a web GPU, for example. It, uh, it has shipped in, uh, in, in Chrome shortly before it transition to a candidate rec. But the, the, the spec was already stable. and now it's shipping uh, in, uh, in different browsers, uh, uh, safari, uh, and uh, and uh, and uh, Firefox. And so that's, uh, and that's a good example of something that follows, uh, things, uh, along pretty well. But then you have other specs such as, uh, in the media space, uh, request video frame back, uh, frame, call back, uh, requestVideoFrameCallback() is a short API that allows you to get, you know, a call back whenever the, the browser renders a video frame, essentially. [00:18:01] Francois: And that spec is implemented across browsers. But from a W3C specific, perspective, it does not even exist. It's not on the standardization track. It's still being incubated in what we call a community group, which is, you know, some something that, uh, usually exists before. we move to the, the standardization process. [00:18:21] Francois: So there, there are examples of things where some things fell through the cracks. All the standardization process, uh, is either too early or too late and things that are in spec are not exactly what what got implemented or implementations are too early in the process. We we're doing a better job, at, Not falling into a trap where someone ships, uh, you know, an implementation and then suddenly everything is frozen. You can no longer, change it because it's too late, it shipped. we've tried, different, path there. Um, mentioned CSS, the, there was this kind of vendor prefixed, uh, properties that used to be, uh, the way, uh, browsers were deploying new features without, you know, taking the final name. [00:19:06] Francois: We are trying also to move away from it because same thing. Then in the end, you end up with, uh, applications that have, uh, to duplicate all the properties, the CSS properties in the style sheets with, uh, the vendor prefixes and nuances in the, in what it does in, in the end. [00:19:23] Jeremy: Yeah, I, I think, is that in CSS where you'll see --mozilla or things like that? Why requestVideoFrameCallback doesn't have a formal specification [00:19:30] Jeremy: The example of the request video frame callback. I, I wonder if you have an opinion or, or, or know why that ended up the way it did, where the browsers all implemented it, even though it was still in the incubation stage. [00:19:49] Francois: On this one, I don't have a particular, uh, insights on whether there was a, you know, a strong reason to implement it,without doing the standardization work. [00:19:58] Francois: I mean, there are, it's not, uh, an IPR (Intellectual Property Rights) issue. It's not, uh, something that, uh, I don't think the, the, the spec triggers, uh, you know, problems that, uh, would be controversial or whatever. [00:20:10] Francois: Uh, so it's just a matter of, uh, there was no one's priority, and in the end, you end up with a, everyone's happy. it's, it has shipped. And so now doing the spec work is a bit,why spend time on something that's already shipped and so on, but the, it may still come back at some point with try to, you know, improve the situation. [00:20:26] Jeremy: Yeah, that's, that's interesting. It's a little counterintuitive because it sounds like you have the, the working group and it, it sounds like perhaps the companies or organizations involved, they maybe agreed on how it should work, and maybe that agreement almost made it so that they felt like they didn't need to move forward with the specification because they came to consensus even before going through that. [00:20:53] Francois: In this particular case, it's probably because it's really, again, it's a small, spec. It's just one function call, you know? I mean, they will definitely want a working group, uh, for larger specifications. by the way, actually now I know re request video frame call back. It's because the, the, the final goal now that it's, uh, shipped, is to merge it into, uh, HTML, uh, the HTML spec. [00:21:17] Francois: So there's a, there's an ongoing issue on the, the WHATWG side to integrate request video frame callback. And it's taking some time but see, it's, it's being, it, it caught up and, uh, someone is doing the, the work to, to do it. I had forgotten about this one. Um, [00:21:33] Jeremy: Tension from specification review (horizontal review) [00:21:33] Francois: so with larger specifications, organizations will want this kind of IPR regime they will want commit commitments from, uh, others, on the scope, on the process, on everything. So they will want, uh, a larger, a, a more formal setting, because that's part of how you ensure that things, uh, will get done properly. [00:21:53] Francois: I didn't mention it, but, uh, something we're really, uh, Pushy on, uh, W3C I mentioned we have principles, we have priorities, and we have, uh, specific several, uh, properties at W3C. And one of them is that we we're very strong on horizontal reviews of our specs. We really want them to be reviewed from an accessibility perspective, from an internationalization perspective, from a privacy and security, uh, perspective, and, and, and a technical architecture perspective as well. [00:22:23] Francois: And that's, these reviews are part of the formal process. So you, all specs need to undergo these reviews. And from time to time, that creates tension. Uh, from time to time. It just works, you know. Goes without problem. a recurring issue is that, privacy and security are hard. I mean, it's not an easy problem, something that can be, uh, solved, uh, easily. [00:22:48] Francois: Uh, so there's a, an ongoing tension and no easy way to resolve it, but there's an ongoing tension between, specifying powerful APIs and preserving privacy without meaning, not exposing too much information to applications in the media space. You can think of the media capabilities, API. So the media space is a complicated space. [00:23:13] Francois: Space because of codecs. codecs are typically not relative free. and so browsers decide which codecs they're going to support, which audio and video codecs they, they're going to support and doing that, that creates additional fragmentation, not in the sense that they're not interoperable, but in the sense that applications need to choose which connect they're going to ship to stream to the end user. [00:23:39] Francois: And, uh, it's all the more complicated that some codecs are going to be hardware supported. So you will have a hardware decoder in your, in your, in your laptop or smartphone. And so that's going to be efficient to decode some, uh, some stream, whereas some code are not, are going to be software, based, supported. [00:23:56] Francois: Uh, and that may consume a lot of CPU and a lot of power and a lot of energy in the end. So you, you want to avoid that if you can, uh, select another thing. Even more complex than, codecs have different profiles, uh, lower end profiles higher end profiles with different capabilities, different features, uh, depending on whether you're going to use this or that color space, for example, this or that resolution, whatever. [00:24:22] Francois: And so you want to surface that to web applications because otherwise, they can't. Select, they can't choose, the right codec and the right, stream that they're going to send to the, uh, client devices. And so they're not going to provide an efficient user experience first, and even a sustainable one in terms of energy because they, they're going to waste energy if they don't send the right stream. [00:24:45] Francois: So you want to surface that to application. That's what the media, media capabilities, APIs, provides. Privacy concerns [00:24:51] Francois: Uh, but at the same time, if you expose that information, you end up with ways to fingerprint the end user's device. And that in turn is often used to track users across, across sites, which is exactly what we don't want to have, uh, for privacy reasons, for obvious privacy reasons. [00:25:09] Francois: So you have to balance that and find ways to, uh, you know, to expose. Capabilities without, without necessarily exposing them too much. Uh, [00:25:21] Jeremy: Can you give an example of how some of those discussions went? Like within the working group? Who are the companies or who are the organizations that are arguing for We shouldn't have this capability because of the privacy concerns, or [00:25:40] Francois: In a way all of the companies, have a vision of, uh, of privacy. I mean, the, you will have a hard time finding, you know, members saying, I don't care about privacy. I just want the feature. Uh, they all have privacy in mind, but they may have a different approach to privacy. [00:25:57] Francois: so if you take, uh, let's say, uh, apple and Google would be the, the, I guess the perfect examples in that, uh, in that space, uh, Google will have a, an approach that is more open-ended thing. The, the user agents has this, uh, should check what the, the, uh, given site is doing. And then if it goes beyond, you know, some kind of threshold, they're going to say, well, okay, well, we'll stop exposing data to that, to that, uh, to that site. [00:26:25] Francois: So that application. So monitor and react in a way. apple has a more, uh, you know, has a stricter view on, uh, on privacy, let's say. And they will say, no, we, the, the, the feature must not exist in the first place. Or, but that's, I mean, I guess, um, it's not always that extreme. And, uh, from time to time it's the opposite. [00:26:45] Francois: You will have, uh, you know, apple arguing in one way, uh, which is more open-ended than the, uh, than, uh, than Google, for example. And they are not the only ones. So in working groups, uh, you will find the, usually the implementers. Uh, so when we talk about APIs that get implemented in browsers, you want the core browsers to be involved. [00:27:04] Francois: Uh, otherwise it's usually not a good sign for, uh, the success of the, uh, of the technology. So in practice, that means Apple, uh, Microsoft, Mozilla which one did I forget? [00:27:15] Jeremy: Google. [00:27:16] Francois: I forgot Google. Of course. Thank you. that's, uh, that the, the core, uh, list of participants you want to have in any, uh, group that develops web standards targeted at web browsers. Who participates in working groups and how much power do they have? [00:27:28] Francois: And then on top of that, you want, organizations and people who are directly going to use it, either because they, well the content providers. So in media, for example, if you look at the media working group, you'll see, uh, so browser vendors, the ones I mentioned, uh, content providers such as the BBC or Netflix. [00:27:46] Francois: Chip set vendors would, uh, would be there as well. Intel, uh, Nvidia again, because you know, there's a hardware decoding in there and encoding. So media is, touches on, on, uh, on hardware, uh, device manufacturer in general. You may, uh, I think, uh, I think Sony is involved in the, in the media working group, for example. [00:28:04] Francois: and these companies are usually less active in the spec development. It depends on the groups, but they're usually less active because the ones developing the specs are usually the browser again, because as I mentioned, we develop the specs in parallel to browsers implementing it. So they have the. [00:28:21] Francois: The feedback on how to formulate the, the algorithms. and so that's this collection of people who are going to discuss first within themselves. W3C pushes for consensual dis decisions. So we hardly take any votes in the working groups, but from time to time, that's not enough. [00:28:41] Francois: And there may be disagreements, but let's say there's agreement in the group, uh, when the spec matches. horizontal review groups will look at the specs. So these are groups I mentioned, accessibility one, uh, privacy, internationalization. And these groups, usually the participants are, it depends. [00:29:00] Francois: It can be anything. It can be, uh, the same companies. It can be, but usually different people from the same companies. But it the, maybe organizations with a that come from very, a very different angle. And that's a good thing because that means the, you know, you enlarge the, the perspectives on your, uh, on the, on the technology. [00:29:19] Francois: and you, that's when you have a discussion between groups, that takes place. And from time to time it goes well from time to time. Again, it can trigger issues that are hard to solve. and the W3C has a, an escalation process in case, uh, you know, in case things degenerate. Uh, starting with, uh, the notion of formal objection. [00:29:42] Jeremy: It makes sense that you would have the, the browser. Vendors and you have all the different companies that would use that browser. All the different horizontal groups like you mentioned, the internationalization, accessibility. I would imagine that you were talking about consensus and there are certain groups or certain companies that maybe have more say or more sway. [00:30:09] Jeremy: For example, if you're a browser, manufacturer, your Google. I'm kind of curious how that works out within the working group. [00:30:15] Francois: Yes, it's, I guess I would be lying if I were saying that, uh, you know, all companies are strictly equal in a, in a, in a group. they are from a process perspective, I mentioned, you know, different membership fees with were design, special specific ethos so that no one could say, I'm, I'm putting in a lot of money, so you, you need to re you need to respect me, uh, and you need to follow what I, what I want to, what I want to do. [00:30:41] Francois: at the same time, if you take a company like, uh, like Google for example, they send, hundreds of engineers to do standardization work. That's absolutely fantastic because that means work progresses and it's, uh, extremely smart people. So that's, uh, that's really a pleasure to work with, uh, with these, uh, people. [00:30:58] Francois: But you need to take a step back and say, well, the problem is. Defacto that gives them more power just by virtue of, uh, injecting more resources into it. So having always someone who can respond to an issue, having always someone, uh, editing a spec defacto that give them more, uh, um, more say on the, on the directions that, get forward. [00:31:22] Francois: And on top of that, of course, they have the, uh, I guess not surprisingly, the, the browser that is, uh, used the most, currently, on the market so there's a little bit of a, the, the, we, we, we, we try very hard to make sure that, uh, things are balanced. it's not a perfect world. [00:31:38] Francois: the the role of the team. I mean, I didn't talk about the role of the team, but part of it is to make sure that. Again, all perspectives are represented and that there's not, such a, such big imbalance that, uh, that something is wrong and that we really need to look into it. so making sure that anyone, if they have something to say, make making sure that they are heard by the rest of the group and not dismissed. [00:32:05] Francois: That usually goes well. There's no problem with that. And again, the escalation process I mentioned here doesn't make any, uh, it doesn't make any difference between, uh, a small player, a large player, a big player, and we have small companies raising formal objections against some of our aspects that happens, uh, all large ones. [00:32:24] Francois: But, uh, that happens too. There's no magical solution, I guess you can tell it by the way. I, uh, I don't know how to formulate the, the process more. It's a human process, and that's very important that it remains a human process as well. [00:32:41] Jeremy: I suppose the role of, of staff and someone in your position, for example, is to try and ensure that these different groups are, are heard and it isn't just one group taking control of it. [00:32:55] Francois: That's part of the role, again, is to make sure that, uh, the, the process is followed. So the, I, I mean, I don't want to give the impression that the process controls everything in the groups. I mean, the, the, the groups are bound by the process, but the process is there to catch problems when they arise. [00:33:14] Francois: most of the time there are no problems. It's just, you know, again, participants talking to each other, talking with the rest of the community. Most of the work happens in public nowadays, in any case. So the groups work in public essentially through asynchronous, uh, discussions on GitHub repositories. [00:33:32] Francois: There are contributions from, you know, non group participants and everything goes well. And so the process doesn't kick in. You just never say, eh, no, you didn't respect the process there. You, you closed the issue. You shouldn't have a, it's pretty rare that you have to do that. Uh, things just proceed naturally because they all, everyone understands where they are, why, what they're doing, and why they're doing it. [00:33:55] Francois: we still have a role, I guess in the, in the sense that from time to time that doesn't work and you have to intervene and you have to make sure that,the, uh, exception is caught and, uh, and processed, uh, in the right way. Discussions are public on github [00:34:10] Jeremy: And you said this process is asynchronous in public, so it sounds like someone, I, I mean, is this in GitHub issues or how, how would somebody go and, and see what the results of [00:34:22] Francois: Yes, there, there are basically a gazillion of, uh, GitHub repositories under the, uh, W3C, uh, organization on GitHub. Most groups are using GitHub. I mean, there's no, it's not mandatory. We don't manage any, uh, any tooling. But the factors that most, we, we've been transitioning to GitHub, uh, for a number of years already. [00:34:45] Francois: Uh, so that's where the work most of the work happens, through issues, through pool requests. Uh, that's where. people can go and raise issues against specifications. Uh, we usually, uh, also some from time to time get feedback from developers and countering, uh, a bug in a particular implementations, which we try to gently redirect to, uh, the actual bug trackers because we're not responsible for the respons implementations of the specs unless the spec is not clear. [00:35:14] Francois: We are responsible for the spec itself, making sure that the spec is clear and that implementers well, understand how they should implement something. Why the W3C doesn't specify a video or audio codec [00:35:25] Jeremy: I can see how people would make that mistake because they, they see it's the feature, but that's not the responsibility of the, the W3C to implement any of the specifications. Something you had mentioned there's the issue of intellectual property rights and how when you have a recommendation, you require the different organizations involved to make their patents available to use freely. [00:35:54] Jeremy: I wonder why there was never any kind of, recommendation for audio or video codecs in browsers since you have certain ones that are considered royalty free. But, I believe that's never been specified. [00:36:11] Francois: At W3C you mean? Yes. we, we've tried, I mean, it's not for lack of trying. Um, uh, we've had a number of discussions with, uh, various stakeholders saying, Hey, we, we really need, an audio or video code for our, for the web. the, uh, png PNG is an example of a, um, an image format which got standardized at W3C and it got standardized at W3C similar reasons. There had to be a royalty free image format for the web, and there was none at the time. of course, nowadays, uh, jpeg, uh, and gif or gif, whatever you call it, are well, you know, no problem with them. But, uh, um, that at the time P PNG was really, uh, meant to address this issue and it worked for PNG for audio and video. [00:37:01] Francois: We haven't managed to secure, commitments by stakeholders. So willingness to do it, so it's not, it's not lack of willingness. We would've loved to, uh, get, uh, a royalty free, uh, audio codec, a royalty free video codec again, audio and video code are extremely complicated because of this. [00:37:20] Francois: not only because of patterns, but also because of the entire business ecosystem that exists around them for good reasons. You, in order for a, a codec to be supported, deployed, effective, it really needs, uh, it needs to mature a lot. It needs to, be, uh, added to at a hardware level, to a number of devices, capturing devices, but also, um, uh, uh, of course players. [00:37:46] Francois: And that takes a hell of a lot of time and that's why you also enter a number of business considerations with business contracts between entities. so I'm personally, on a personal level, I'm, I'm pleased to see, for example, the Alliance for Open Media working on, uh, uh, AV1, uh, which is. At least they, uh, they wanted to be royalty free and they've been adopting actually the W3C patent policy to do this work. [00:38:11] Francois: So, uh, we're pleased to see that, you know, they've been adopting the same process and same thing. AV1 is not yet at the same, support stage, as other, codecs, in the world Yeah, I mean in devices. There's an open question as what, what are we going to do, uh, in the future uh, with that, it's, it's, it's doubtful that, uh, the W3C will be able to work on a, on a royalty free audio, codec or royalty free video codec itself because, uh, probably it's too late now in any case. [00:38:43] Francois: but It's one of these angles in the, in the web platform where we wish we had the, uh, the technology available for, for free. And, uh, it's not exactly, uh, how things work in practice.I mean, the way codecs are developed remains really patent oriented. [00:38:57] Francois: and you will find more codecs being developed. and that's where geopolitics can even enter the, the, uh, the play. Because, uh, if you go to China, you will find new codecs emerging, uh, that get developed within China also, because, the other codecs come mostly from the US so it's a bit of a problem and so on. [00:39:17] Francois: I'm not going to enter details and uh, I would probably say stupid things in any case. Uh, but that, uh, so we continue to see, uh, emerging codecs that are not royalty free, and it's probably going to remain the case for a number of years. unfortunately, unfortunately, from a W3C perspective and my perspective of course. [00:39:38] Jeremy: There's always these new, formats coming out and the, rate at which they get supported in the browser, even on a per browser basis is, is very, there can be a long time between, for example, WebP being released and a browser supporting it. So, seems like maybe we're gonna be in that situation for a while where the codecs will come out and maybe the browsers will support them. Maybe they won't, but the, the timeline is very uncertain. Digital Rights Management (DRM) and Media Source Extensions [00:40:08] Jeremy: Something you had, mentioned, maybe this was in your, email to me earlier, but you had mentioned that some of these specifications, there's, there's business considerations like with, digital rights management and, media source extensions. I wonder if you could talk a little bit about maybe what media source extensions is and encrypted media extensions and, and what the, the considerations or challenges are there. [00:40:33] Francois: I'm going to go very, very quickly over the history of a, video and audio support on the web. Initially it was supported through plugins. you are maybe too young to, remember that. But, uh, we had extensions, added to, uh, a realplayer. [00:40:46] Francois: This kind of things flash as well, uh, supporting, uh, uh, videos, in web pages, but it was not provided by the web browsers themselves. Uh, then HTML5 changed the, the situation. Adding these new tags, audio and video, but that these tags on this, by default, support, uh, you give them a resources, a resource, like an image as it's an audio or a video file. [00:41:10] Francois: They're going to download this, uh, uh, video file or audio file, and they're going to play it. That works well. But as soon as you want to do any kind of real streaming, files are too large and to stream, to, to get, you know, to get just a single fetch on, uh, on them. So you really want to stream them chunk by chunk, and you want to adapt the resolution at which you send the stream based on real time conditions of the user's network. [00:41:37] Francois: If there's plenty of bandwidth you want to send the user, the highest possible resolution. If there's a, some kind of hiccup temporary in the, in the network, you really want to lower the resolution, and that's called adaptive streaming. And to get adaptive streaming on the web, well, there are a number of protocols that exist. [00:41:54] Francois: Same thing. Some many of them are proprietary and actually they remain proprietary, uh, to some extent. and, uh, some of them are over http and they are the ones that are primarily used in, uh, in web contexts. So DASH comes to mind, DASH for Dynamic Adaptive streaming over http. HLS is another one. Uh, initially developed by Apple, I believe, and it's, uh, HTTP live streaming probably. Exactly. And, so there are different protocols that you can, uh, you can use. Uh, so the goal was not to standardize these protocols because again, there were some proprietary aspects to them. And, uh, same thing as with codecs. [00:42:32] Francois: There was no, well, at least people wanted to have the, uh, flexibility to tweak parameters, adaptive streaming parameters the way they wanted for different scenarios. You may want to tweak the parameters differently. So they, they needed to be more flexibility on top of protocols not being truly available for use directly and for implementation directly in browsers. [00:42:53] Francois: It was also about providing applications with, uh, the flexibility they would need to tweak parameters. So media source extensions comes into play for exactly that. Media source extensions is really about you. The application fetches chunks of its audio and video stream the way it wants, and with the parameters it wants, and it adjusts whatever it wants. [00:43:15] Francois: And then it feeds that into the, uh, video or audio tag. and the browser takes care of the rest. So it's really about, doing, you know, the adaptive streaming. let applications do it, and then, uh, let the user agent, uh, the browser takes, take care of the rendering itself. That's media source extensions. [00:43:32] Francois: Initially it was pushed by, uh, Netflix. They were not the only ones of course, but there, there was a, a ma, a major, uh, proponent of this, uh, technical solution, because they wanted, uh, they, uh, they were, expanding all over the world, uh, with, uh, plenty of native, applications on all sorts of, uh, of, uh, devices. [00:43:52] Francois: And they wanted to have a way to stream content on the web as well. both for both, I guess, to expand to, um, a new, um, ecosystem, the web, uh, providing new opportunities, let's say. But at the same time also to have a fallback, in case they, because for native support on different platforms, they sometimes had to enter business agreements with, uh, you know, the hardware manufacturers, the whatever, the, uh, service provider or whatever. [00:44:19] Francois: and so that was a way to have a full back. That kind of work is more open, in case, uh, things take some time and so on. So, and they probably had other reasons. I mean, I'm not, I can't speak on behalf of Netflix, uh, on others, but they were not the only ones of course, uh, supporting this, uh, me, uh, media source extension, uh, uh, specification. [00:44:42] Francois: and that went kind of, well, I think it was creating 2011. I mean, the, the work started in 2011 and the recommendation was published in 2016, which is not too bad from a standardization perspective. It means only five years, you know, it's a very short amount of time. Encrypted Media Extensions [00:44:59] Francois: At the same time, and in parallel and complement to the media source extension specifications, uh, there was work on the encrypted media extensions, and here it was pushed by the same proponent in a way because they wanted to get premium content on the web. [00:45:14] Francois: And by premium content, you think of movies and, uh. These kind of beasts. And the problem with the, I guess the basic issue with, uh, digital asset such as movies, is that they cost hundreds of millions to produce. I mean, some cost less of course. And yet it's super easy to copy them if you have a access to the digital, uh, file. [00:45:35] Francois: You just copy and, uh, and that's it. Piracy uh, is super easy, uh, to achieve. It's illegal of course, but it's super easy to do. And so that's where the different legislations come into play with digital right management. Then the fact is most countries allow system that, can encrypt content and, uh, through what we call DRM systems. [00:45:59] Francois: so content providers, uh, the, the ones that have movies, so the studios here more, more and more, and Netflix is one, uh, one of the studios nowadays. Um, but not only, not only them all major studios will, uh, would, uh, push for, wanted to have something that would allow them to stream encrypted content, encrypted audio and video, uh, mostly video, to, uh, to web applications so that, uh, you. [00:46:25] Francois: Provide the movies, otherwise, they, they are just basically saying, and sorry, but, uh, this premium content will never make it to the web because there's no way we're gonna, uh, send it in clear, to, uh, to the end user. So Encrypting media extensions is, uh, is an API that allows to interface with, uh, what's called the content decryption module, CDM, uh, which itself interacts with, uh, the DR DRM systems that, uh, the browser may, may or may not support. [00:46:52] Francois: And so it provides a way for an application to receive encrypted content, pass it over get the, the, the right keys, the right license keys from a whatever system actually. Pass that logic over to the, and to the user agent, which passes, passes it over to, uh, the CDM system, which is kind of black box in, uh, that does its magic to get the right, uh, decryption key and then the, and to decrypt the content that can be rendered. [00:47:21] Francois: The encrypted media extensions triggered a, a hell of a lot of, uh, controversy. because it's DRM and DRM systems, uh, many people, uh, uh, things should be banned, uh, especially on the web because the, the premise of the web is that the, the user has trusts, a user agent. The, the web browser is called the user agent in all our, all our specifications. [00:47:44] Francois: And that's, uh, that's the trust relationship. And then they interact with a, a content provider. And so whatever they do with the content is their, I guess, actually their problem. And DRM introduces a third party, which is, uh, there's, uh, the, the end user no longer has the control on the content. [00:48:03] Francois: It has to rely on something else that, Restricts what it can achieve with the content. So it's, uh, it's not only a trust relationship with its, uh, user agents, it's also with, uh, with something else, which is the content provider, uh, in the end, the one that has the, uh, the license where provides the license. [00:48:22] Francois: And so that's, that triggers, uh, a hell of a lot of, uh, of discussions in the W3C degenerated, uh, uh, into, uh, formal objections being raised against the specification. and that escalated to, to the, I mean, at all leverage it. It's, it's the, the story in, uh, W3C that, um, really, uh, divided the membership into, opposed camps in a way, if you, that's was not only year, it was not really 50 50 in the sense that not just a huge fights, but the, that's, that triggered a hell of a lot of discussions and a lot of, a lot of, uh, of formal objections at the time. [00:49:00] Francois: Uh, we were still, From a governance perspective, interestingly, um, the W3C used to be a dictatorship. It's not how you should formulate it, of course, and I hope it's not going to be public, this podcast. Uh, but the, uh, it was a benevolent dictatorship. You could see it this way in the sense that, uh, the whole process escalated to one single person was, Tim Burners Lee, who had the final say, on when, when none of the other layers, had managed to catch and to resolve, a conflict. [00:49:32] Francois: Uh, that has hardly ever happened in, uh, the history of the W3C, but that happened to the two for EME, for encrypted media extensions. It had to go to the, uh, director level who, uh, after due consideration, uh, decided to, allow the EME to proceed. and that's why we have a, an EME, uh, uh, standard right now, but still re it remains something on the side. [00:49:56] Francois: EME we're still, uh, it's still in the scope of the media working group, for example. but the scope, if you look at the charter of the working group, we try to scope the, the, the, the, the updates we can make to the specification, uh, to make sure that we don't reopen, reopen, uh, a can of worms, because, well, it's really a, a topic that triggers friction for good and bad reasons again. [00:50:20] Jeremy: And when you talk about the media source extensions, that is the ability to write custom code to stream video in whatever way you want. You mentioned, the MPEG-DASH and http live streaming. So in that case, would that be the developer gets to write that code in JavaScript that's executed by the browser? [00:50:43] Francois: Yep, that's, uh, that would be it. and then typically, I guess the approach nowadays is more and more to develop low level APIs into W3C or web in, in general, I guess. And to let, uh. Libraries emerge that are going to make lives of a, a developer, uh, easier. So for MPEG DASH, we have the DASH.js, which does a fantastic job at, uh, at implementing the complexity of, uh, of adaptive streaming. [00:51:13] Francois: And you just, you just hook it into your, your workflow. And that's, uh, and that's it. Encrypted Media Extensions are closed source [00:51:20] Jeremy: And with the encrypted media extensions I'm trying to picture how those work and how they work differently. [00:51:28] Francois: Well, it's because the, the, the, the key architecture is that the, the stream that you, the stream that you may assemble with a media source extensions, for example. 'cause typically they, they're used in collaboration. When you hook the, hook it into the video tag, you also. Call EME and actually the stream goes to EME. [00:51:49] Francois: And when it goes to EME, actually the user agent hands the encrypted stream. You're still encrypted at this time. Uh, encrypted, uh, stream goes to the CDM content decryption module, and that's a black box well, it has some black, black, uh, black box logic. So it's not, uh, even if you look at the chromium source code, for example, you won't see the implementation of the CDM because it's a, it's a black box, so it's not part of the browser se it's a sand, it's sandboxed, it's execution sandbox. [00:52:17] Francois: That's, uh, the, the EME is kind of unique in, in this way where the, the CDM is not allowed to make network requests, for example, again, for privacy reasons. so anyway, the, the CDM box has the logic to decrypt the content and it hands it over, and then it depends, it depends on the level of protection you. [00:52:37] Francois: You need or that the system supports. It can be against software based protection, in which case actually, a highly motivated, uh, uh, uh, attacker could, uh, actually get access to the decoded stream, or it can be more hardware protected, in which case actually the, it goes to the, uh, to your final screen. [00:52:58] Francois: But it goes, it, it goes through the hardware in a, in a mode that the US supports in a mode that even the user agent doesn't have access to it. So it doesn't, it can't even see the pixels that, uh, gets rendered on the screen. There are, uh, several other, uh, APIs that you could use, for example, to take a screenshot of your, of your application and so on. [00:53:16] Francois: And you cannot apply them to, uh, such content because they're just gonna return a black box. again, because the user agent itself does not see the, uh, the pixels, which is exactly what you want with encrypted content. [00:53:29] Jeremy: And the, the content decryption module, it's, if I understand correctly, it's something that's shipped with the browsers, but you were saying is if you were to look at the public source code of Chromium or of Firefox, you would not see that implementation. Content Decryption Module (Widevine, PlayReady) [00:53:47] Francois: True. I mean, the, the, um, the typical examples are, uh, uh, widevine, so wide Vine. So interestingly, uh, speaking in theory, these, uh, systems could have been provided by anyone in practice. They've been provided by the browser vendors themselves. So Google has Wide Vine. Uh, Microsoft has something called PlayReady. Apple uh, the name, uh, escapes my, uh, sorry. They don't have it on top of my mind. So they, that's basically what they support. So they, they also own that code, but in a way they don't have to. And Firefox actually, uh, they, uh, don't, don't remember which one, they support among these three. but, uh, they, they don't own that code typically. [00:54:29] Francois: They provide a wrapper around, around it. Yeah, that's, that's exactly the, the crux of the, uh, issue that, people have with, uh, with DRMs, right? It's, uh, the fact that, uh, suddenly you have a bit of code running there that is, uh, that, okay, you can send box, but, uh, you cannot inspect and you don't have, uh, access to its, uh, source code. [00:54:52] Jeremy: That's interesting. So the, almost the entire browser is open source, but if you wanna watch a Netflix movie for example, then you, you need to, run this, this CDM, in addition to just the browser code. I, I think, you know, we've kind of covered a lot. Documenting what's available in browsers for developers [00:55:13] Jeremy: I wonder if there's any other examples or anything else you thought would be important to mention in, in the context of the W3C. [00:55:23] Francois: There, there's one thing which, uh, relates to, uh, activities I'm doing also at W3C. Um. Here, we've been talking a lot about, uh, standards and, implementations in browsers, but there's also, uh, adoption of these browser, of these technology standards by developers in general and making sure that developers are aware of what exists, making sure that they understand what exists and one of the, key pain points that people, uh. [00:55:54] Francois: Uh, keep raising on, uh, the web platform is first. Well, the, the, the web platform is unique in the sense that there are different implementations. I mean, if you, [00:56:03] Francois: Uh, anyway, there are different, uh, context, different run times where there, there's just one provided by the company that owns the, uh, the, the, the system. The web platform is implemented by different, uh, organizations. and so you end up the system where no one, there's what's in the specs is not necessarily supported. [00:56:22] Francois: And of course, MDN tries, uh, to document what's what's supported, uh, thoroughly. But for MDN to work, there's a hell of a lot of needs for data that, tracks browser support. And this, uh, this data is typically in a project called the Browser Compat Data, BCD owned by, uh, MDN as well. But, the Open Web Docs collective is a, uh, is, uh, the one, maintaining that, uh, that data under the hoods. [00:56:50] Francois: anyway, all of that to say that, uh, to make sure that, we track things beyond work on technical specifications, because if you look at it from W3C perspective, life ends when the spec reaches standards, uh, you know, candidate rec or rec, you could just say, oh, done with my work. but that's not how things work. [00:57:10] Francois: There's always, you need the feedback loop and, in order to make sure that developers get the information and can provide the, the feedback that standardization can benefit from and browser vendors can benefit from. We've been working on a project called web Features with browser vendors mainly, and, uh, a few of the folks and MDN and can I use and different, uh, different people, to catalog, the web in terms of features that speak to developers and from that catalog. [00:57:40] Francois: So it's a set of, uh, it's a set of, uh, feature IDs with a feature name and feature description that say, you know, this is how developers would, uh, understand, uh, instead of going too fine grained in terms of, uh, there's this one function call that does this because that's where you, the, the kind of support data you may get from browser data and MDN initially, and having some kind of a coarser grained, uh, structure that says these are the, features that make sense. [00:58:09] Francois: They talk to developers. That's what developers talk about, and that's the info. So the, we need to have data on these particular features because that's how developers are going approach the specs. Uh. and from that we've derived the notion of baseline badges that you have, uh, are now, uh, shown on MDN on can I use and integrated in, uh, IDE tool, IDE Tools such as visual, visual studio, and, uh, uh, libraries, uh, linked, some linters have started to, um, to integrate that data. [00:58:41] Francois: Uh, so, the way it works is, uh, we've been mapping these coarser grained features to BCDs finer grained support data, and from there we've been deriving a kind of a, a batch that says, yeah, this, this feature is implemented well, has limited availability because it's only implemented in one or two browsers, for example. [00:59:07] Francois: It's, newly available because. It was implemented. It's been, it's implemented across the main browser vendor, um, across the main browsers that people use. But it's recent, and widely available, which we try to, uh, well, there's been lots of discussion in the, in the group to, uh, come up with a definition which essentially ends up being 30 months after, a feature become, became newly available. [00:59:34] Francois: And that's when, that's the time it takes for the, for the versions of the, the different versions of the browser to propagate. Uh, because you, it's not because there's a new version of a, of a browser that, uh, people just, Ima immediately, uh, get it. So it takes a while, to propagate, uh, across the, uh, the, the user, uh, user base. [00:59:56] Francois: And so the, the goal is to have a, a, a signal that. Developers can rely on saying, okay, well it's widely available so I can really use that feature. And of course, if that doesn't work, then we need to know about it. And so we are also working with, uh, people doing so developer surveys such as state of, uh, CSS, state of HTML, state of JavaScript. [01:00:15] Francois: That's I guess, the main ones. But also we are also running, uh, MDN short surveys with the MDN people to gather feedback on. On the, on these same features, and to feed the loop and to, uh, to complete the loop. and these data is also used by, internally, by browser vendors to inform, prioritization process, their prioritization process, and typically as part of the interop project that they're also running, uh, on the site [01:00:43] Francois: So a, a number of different, I've mentioned, uh, I guess a number of different projects, uh, coming along together. But that's the goal is to create links, across all of these, um, uh, ongoing projects with a view to integrating developers, more, and gathering feedback as early as possible and inform decision. [01:01:04] Francois: We take at the standardization level that can affect the, the lives of the developers and making sure that it's, uh, it affects them in a, in a positive way. [01:01:14] Jeremy: just trying to understand, 'cause you had mentioned that there's the web features and the baseline, and I was, I was trying to picture where developers would actually, um, see these things. And it sounds like from what you're saying is W3C comes up with what stage some of these features are at, and then developers would end up seeing it on MDN or, or some other site. [01:01:37] Francois: So, uh, I'm working on it, but that doesn't mean it's a W3C thing. It's a, it's a, again, it's a, we have different types of group. It's a community group, so it's the Web DX Community group at W3C, which means it's a community owned thing. so that's why I'm mentioning a working with a representative from, and people from MDN people, from open Web docs. [01:02:05] Francois: so that's the first point. The second point is, so it's, indeed this data is now being integrated. If you, and you look, uh, you'll, you'll see it in on top of the MDN pages on most of them. If you look at, uh, any kind of feature, you'll see a, a few logos, uh, a baseline banner. and then can I use, it's the same thing. [01:02:24] Francois: You're going to get a baseline, banner. It's more on, can I use, and it's meant to capture the fact that the feature is widely available or if you may need to pay attention to it. Of course, it's a simplification, and the goal is not to the way it's, the way the messaging is done to developers is meant to capture the fact that, they may want to look, uh, into more than just this, baseline status, because. [01:02:54] Francois: If you take a look at web platform tests, for example, and if you were to base your assessment of whether a feature is supported based on test results, you'll end up saying the web platform has no supported technology because there are absolutely no API that, uh, where browsers pass 100% of the, of the, of the test suite. [01:03:18] Francois: There may be a few of them, I don't know. But, there's a simplification in the, in the process when a feature is, uh, set to be baseline, there may be more things to look at nevertheless, but it's meant to provide a signal that, uh, still developers can rely on their day-to-day, uh, lives. [01:03:36] Francois: if they use the, the feature, let's say, as a reasonably intended and not, uh, using to advance the logic. [01:03:48] Jeremy: I see. Yeah. I'm looking at one of the pages on MDN right now, and I can see at the top there's the, the baseline and it, it mentions that this feature works across many browsers and devices, and then they say how long it's been available. And so that's a way that people at a glance can, can tell, which APIs they can use. [01:04:08] Francois: it also started, uh, out of a desire to summarize this, uh, browser compatibility table that you see at the end of the page of the, the bottom of the page in on MDN. but there are where developers were saying, well, it's, it's fine, but it's, it goes too much into detail. So we don't know in the end, can we, can we use that feature or can we, can we not use that feature? [01:04:28] Francois: So it's meant as a informed summary of, uh, of, of that it relies on the same data again. and more importantly, we're beyond MDN, we're working with tools providers to integrate that as well. So I mentioned the, uh, visual Studio is one of them. So recently they shipped a new version where when you use a feature, you can, you can have some contextual, uh. [01:04:53] Francois: A menu that tells you, yeah, uh, that's fine. You, this CSS property, you can, you can use it, it's widely available or be aware this one is limited Availability only, availability only available in Firefox or, or Chrome or Safari work kit, whatever. [01:05:08] Jeremy: I think that's a good place to wrap it up, if people want to learn more about the work you're doing or learn more about sort of this whole recommendations process, where, where should they head? [01:05:23] Francois: Generally speaking, we're extremely open to, uh, people contributing to the W3C. and where should they go if they, it depends on what they want. So I guess the, the in usually where, how things start for someone getting involved in the W3C is that they have some

Lindsay & Tim take a call from a listener/photographer, his couples' wedding reception is disrupted by a health inspector. They explore the role of photographers during crises, the importance of flexibility, and the lessons learned from unexpected events. Want us to feature your question, photography story, or industry hot take on an episode? Send us a DM, voice note, or video on instagram @TheShootYourShotPodcast. Your privacy is important to us. If you want to remain anonymous just let us know :)   Sign up with Imagen AI to streamline your photo editing and get 1500 edits free! Sign up below for this rad AF offer: https://tinyurl.com/mt46dz6n   Become an IG reel-creating machine with Social Templates! with Promo code: LINDSAY. https://socialtemplates.co/lindsay Chapters 00:00 Introduction and Podcast Overview 02:03 Wedding Mishaps: A Real-Life Story 04:33 Health Inspector Drama at Weddings 09:05 The Role of Photographers in Crisis 13:49 Documenting the Unexpected: A Photographer's Perspective 18:46 Navigating Wedding Day Challenges 23:16 The Importance of Flexibility in Photography 28:01 Lessons Learned from Wedding Experiences 37:42 Conclusion and Call for Listener Stories

What are your options for hosting your Python application or scripts? What are the advantages of a platform as a service, container-based hosts, or setting up a virtual machine? Christopher Trudeau is back on the show this week, bringing another batch of PyCoder's Weekly articles and projects.

When something goes wrong in long-term care, do you know what to do? In this episode, we introduce Documenting Resident Concerns in Long-Term Care, a new resource created to help residents and families respond with confidence. From falls and pressure injuries to conflicts with staff, knowing what questions to ask and what details to document can be the key to real solutions. Lori Smetanka and Jocelyn Bogdan of Consumer Voice share practical strategies for gathering information and advocating effectively. This joint project from the National Consumer Voice for Quality Long-Term Care and the National Center on Elder Abuse (NCEA) offers a clear path to stronger advocacy and better care. Guests: Lori Smetanka, Consumer Voice Executive Director, and Jocelyn Bogdan, Consumer Voice Senior Policy Specialist

In this episode of Perfectly Good Podcast, hosts Jesse and Sylvan welcome filmmaker Bram van Splunteren to discuss his extensive career in music journalism and filmmaking. Bram shares his journey from working as a radio show producer to making music documentaries, with a particular focus on his acclaimed documentary about musician John Hiatt. The conversation covers Bram's early influences, his experiences interviewing iconic musicians like Bob Marley and Led Zeppelin, and his discovery of John Hiatt's music. They delve into the making of the John Hiatt documentary, including memorable moments with Buddy Killen and the Tree Music team, and how the documentary was received in the Netherlands. Bram reflects on John Hiatt's influence and his ongoing connection with his music. This episode offers fascinating insights into the life of a filmmaker deeply connected with the music industry and provides a unique perspective on John Hiatt's contributions to American music. 00:00 Introduction to the Perfectly Good Podcast 00:56 Meet the Guest: A Filmmaker's Journey 03:08 Musical Roots and Early Influences 05:59 Discovering Filmmaking 09:41 Creating Iconic Music Documentaries 14:40 The John Hyatt Documentary 26:35 Memories of John and Musical Encounters 27:22 Exploring the Music Publishing Company 29:37 The Magic of Iconic Songs 32:35 Interview Insights and Improvisations 37:08 John Hyatt's Connection with Dutch Audience 40:15 Challenges in Releasing the Documentary 43:41 Final Thoughts and Future Projects https://vimeo.com/203121417?&login=true Learn more about your ad choices. Visit megaphone.fm/adchoices

Documenting another turbulent week in the American Years of Lead Support us on Patreon: www.patreon.com/trillbillyworkersparty

Three musicians are creating a digital map about the history of clawhammer banjo players of Southwest Virginia. Roxy Todd has their story.

The Youth Matters podcast highlights significant milestones in the lives of second and third generation Arab youth growing up in Australia. These young individuals share their experiences of gaining independence, navigating their first relationships, shaping their identities on social media, and managing the pressures of independence and advocacy. - بودكاست صوت الشباب يوثّق محطات أساسية في حياة الجيلين الثاني والثالث من الشباب العربي الذين نشأوا في أستراليا. يشارك هؤلاء الشباب لحظات تذوّق طعم الحرية، وخوض تجارب علاقاتهم الأولى، وبناء هوياتهم على منصات التواصل الاجتماعي، والتعامل مع ضغوط الاستقلالية.

Transforming Alcohol Recovery with the Sinclair Method: A Conversation with Katie LainIn this episode of the Samantha Parker Show, Samantha sits down with Katie Lain, founder of Thrive Alcohol Recovery, to discuss her decade-long struggle with alcohol and how discovering the neuroscience-based Sinclair Method transformed her life. Katie shares her journey from binge drinking to becoming an advocate for medication-assisted treatment and the Sinclair Method, which uses Naltrexone to help reduce alcohol cravings and promote controlled drinking. The episode covers the brain science behind alcohol addiction, the inefficacy of many traditional abstinence-based treatments, and how Katie turned her recovery into a mission-driven business. They also discuss the importance of finding the right treatment, whether it's AA, the Sinclair Method, or another path, and emphasize the need for individual motivation and gradual lifestyle changes for sustainable recovery.00:00 Introduction to the Samantha Parker Show00:21 Katie Lane's Journey with Alcohol01:03 Discovering the Sinclair Method03:37 How the Sinclair Method Works06:10 Effectiveness and Challenges of the Sinclair Method19:20 The Role of Faith and Purpose in Recovery21:08 Life After Alcohol25:26 Hangover Struggles and Daily Challenges25:46 Inspiration Behind Thrive Alcohol Recovery26:20 Documenting the Journey on YouTube26:47 The Evolution of Thrive Alcohol Recovery28:08 Stigma and Labels in Alcohol Recovery30:28 Exploring Different Recovery Options31:36 The Role of Community and Support34:50 Changing Drinking Trends Among Youth36:50 Rapid Fire Questions and Personal Insights42:17 Encouragement and Resources for RecoveryStep into Your Sober Era! Are you ready to embrace a life of clarity and empowerment? ✨ Check out Sam's Sober Club on Substack for journals, tips, community and more [Subscribe Now ➔] Sam's Sober CLUB | Samantha Parker | Substack Want to Work with The Samantha Parker for Content Management CLICK HERE Follow me on TikTok https://www.tiktok.com/@samanthaparkershow YouTube https://www.youtube.com/@thesamanthaparker Instagram https://www.instagram.com/thesamanthaparker/

Join the Refrigeration Mentor Hub here Learn more about Refrigeration Mentor Customized Technical Training Programs at www.refrigerationmentor.com/courses In this episode, I'm sharing a 10-point preventative maintenance checklist for supermarket refrigeration systems. Having a comprehensive maintenance checklist is so important and will greatly speed up your efficiency on service calls. This list covers everything from visual inspections, to checking compressor health, verifying electrical components, and ensuring proper refrigerant circuits. Having this standard go-to checklist will help technicians elevate their troubleshooting ability, improve the longevity and efficiency of the refrigeration systems you're working on, and enhance your professional reputation.  In this episode, we cover: -Importance of preventative maintenance -Visual inspection essentials -Compressor health check -Electrical components and safety -Refrigerant circuit checks -Condenser and evaporator maintenance -Identifying frosting issues in refrigeration systems -Using trend graphs for maintenance insights -Importance of oil management -Defrost schedule and alarm verification -Documenting and baseline settings Helpful Links & Resources: Episode 332. 7 Transcritical CO2 Refrigeration Service & Maintenance Tips Episode 213. Supermarket Refrigeration Preventative Maintenance with Andrew Freeburg Episode 70. Building Your Refrigeration Maintenance and Service Checklist  

SummaryIn this episode of the Compliance Guide podcast, Sean Weiss speaks with Jonathan Porter, a former prosecutor turned defense attorney, about the complexities of healthcare compliance and the legal landscape surrounding it. They discuss the transition from prosecution to defense, the power dynamics in legal practice, and the challenges faced by healthcare providers in navigating compliance issues. The conversation highlights the importance of robust compliance programs, the intricacies of medical billing, and the role of metadata in legal cases. Jonathan shares insights on best practices for compliance and the increasing scrutiny on kickback investigations, emphasizing the need for healthcare providers to document their processes and decisions effectively.TakeawaysTransitioning from prosecutor to defense attorney involves a significant shift in power dynamics.Prosecutors often have more power and options than defense attorneys.The healthcare compliance landscape is complex and requires thorough understanding.Many younger prosecutors are focused on quick wins rather than collaboration.Healthcare providers face challenges in understanding intricate billing codes and regulations.Robust compliance programs are essential for healthcare organizations.Documenting processes and decisions can protect against legal scrutiny.Kickback investigations are increasing, necessitating careful documentation of relationships with pharmaceutical companies.Metadata plays a crucial role in legal cases, providing insights into provider actions.Open communication and transparency can mitigate risks of legal action.

In this episode of the Western Rookie Podcast, host Dan and guest Tim Kent discuss various aspects of hunting, including the impact of aging on physical capabilities, the importance of nutrition and preparation, and the challenges faced during hunts. They delve into long-term planning for hunting trips, the shift from over-the-counter tags to guided hunts, and the balance between family commitments and hunting aspirations. The conversation emphasizes the value of experiences over trophies and the significance of documenting plans for future hunts. Tim shares insights on navigating state regulations and the adventure of hunting in different states, while also reflecting on the importance of memories made during these experiences. Takeaways: Aging affects physical capabilities in hunting. Nutrition plays a crucial role in hunting performance. Long-term planning is essential for successful hunts. Experiences in the field are more valuable than trophies. Taking time off from hunting can be beneficial for family. Documenting plans helps in achieving hunting goals. Guided hunts can provide better experiences than OTC tags. The challenge of hunting varies by species and terrain. Point creep affects the ability to draw tags. Sharing hunting experiences with others enriches the journey. Learn more about your ad choices. Visit megaphone.fm/adchoices

In this episode of the Western Rookie Podcast, host Dan and guest Tim Kent discuss various aspects of hunting, including the impact of aging on physical capabilities, the importance of nutrition and preparation, and the challenges faced during hunts. They delve into long-term planning for hunting trips, the shift from over-the-counter tags to guided hunts, and the balance between family commitments and hunting aspirations. The conversation emphasizes the value of experiences over trophies and the significance of documenting plans for future hunts. Tim shares insights on navigating state regulations and the adventure of hunting in different states, while also reflecting on the importance of memories made during these experiences.Takeaways:Aging affects physical capabilities in hunting.Nutrition plays a crucial role in hunting performance.Long-term planning is essential for successful hunts.Experiences in the field are more valuable than trophies.Taking time off from hunting can be beneficial for family.Documenting plans helps in achieving hunting goals.Guided hunts can provide better experiences than OTC tags.The challenge of hunting varies by species and terrain.Point creep affects the ability to draw tags.Sharing hunting experiences with others enriches the journey.

In this episode of American Glutton, Ethan Suplee sits down with Ethan Benard, a 26-year-old on a remarkable weight loss journey. From being 200 pounds at age nine to surviving a life-threatening battle with COVID at over 600 pounds, Benard opens up about the turning points that reshaped his perspective on life. He shares the struggles of losing and regaining weight, finding purpose, and building a sustainable path forward.With raw honesty and inspiration, Bernad discusses discipline, setbacks, resilience, and the mindset shift that fuels his transformation. This conversation is heartfelt, motivating, and a must-listen for anyone seeking change.SHOW HIGHLIGHTS00:01 – Introduction01:25 – Childhood weight struggles02:06 – Mental health and neglect02:26 – Hospitalized with COVID05:04 – Near-death experience sparks change10:06 – Life after hospitalization12:34 – Physical pain of extreme weight17:46 – New mindset and motivation19:00 – Losing 100 pounds naturally23:18 – Starting to walk and record progress24:16 – Social media growth and support27:05 – Walking 10,000–20,000 steps at 500 pounds28:44 – Long-term weight and fitness goals33:29 – Doing it without weight loss surgery38:22 – Loose skin and surgery reflections42:39 – Rethinking goal weights49:37 – Body composition and goals53:49 – Skin removal surgery considerations57:21 – Commitment to natural weight loss59:25 – Building a supportive team01:01:52 – Documenting the journey01:03:55 – Closing remarks Hosted on Acast. See acast.com/privacy for more information.

Watching the Emmy award-winning documentary We Will Dance Again was really really difficult. This 2024 documentary captures Hamas terrorists brutally attacking the Nova music festival attendees on October 7th, 2023, and shows the horrifying events that followed, including hostages taking. Documenting a Terrorist Attack by Hamas from Multiple Perspectives is not an easy task. “I think that this is a terror attack that you can see for the first time from both perspectives that captured the same moments at the same time and I think this is the power of this film,” Yariv said. Yariv implored listeners to please remember that most Israelis are for human rights, democratic rule of law, and policies to stop the war between Israel and Palestine. “I think at this point, this war should have ended, the hostages should have been released. I think it's the responsibility of the state and government of Israel to focus on their release, not killing Hamas and Palestinians controlled by Hamas. Israel should have stopped the war. The casualties of war, the innocent casualties of war, are devastating. And there is a point at which a country needs to understand that war cannot solve everything, and violence cannot solve everything,” Yariv said. We discussed what psychological warfare is also at play in this attack and the events following. I noted that both the United States and Israel are under extreme right-wing leadership at this time, and this directly impacts ongoing conflicts and continuing harm. “Do not blame every Israeli for every type of policy that our government is conducting,” Yariv noted. I mirrored the same about the United States: “Don't hate the American people. Most of us are good people, and we don't like Trump, and we're appalled by his destruction of the checks and balances of laws, the applications of all the rights that we fought for.” I also reminded listeners that not everything was black or white in the Israeli and Palestinian conflict, and the history of harm in the region is extensive and complex. “I'm seeing entities of authoritarianism versus people who are pro-democracy and human rights and women's rights and gay rights and indigenous rights and children's rights,” I noted. Yariv and I both agreed that the pain being inflicted upon the Palestinian people was unacceptable and not helping any of these regions to heal. I added that I hoped we were able to find peace without further cooking our planet and destroying our environment, as wars are costly in so many ways. Learn more about your ad choices. Visit megaphone.fm/adchoices

Aspiring podcaster and artist M'Balou Camara interviews me for a special Maryland Art Summit 2025 recording.M'Balou is a former student, current colleague, and emerging podcaster preparing to launch “Heart Reflex,” highlighting voices of the African diaspora in the arts.Our conversation—recorded live at Prince George's Community College—explores our journey from a classroom connection at UMBC to ongoing collaboration, mutual mentorship, and co-leadership in the creative community.I share insights from my nearly 20 years as a podcaster and host of “The Truth in This Art,” focusing on the value of storytelling, reciprocity, and building a living archive for Baltimore's creative voices.We discuss how authentic conversations, trust, and relational support are central to my approach as a host and educator. I break down strategies for fostering access, avoiding gatekeeping, and sustaining creative independence amid funding challenges.Audience questions spark a discussion on practical advice for new podcasters, evolving media formats, and lessons learned from both successes and setbacks.We close with a rapid-fire “reflex round,” reflecting on curiosity, inspiration, and the role of freedom in creative work.Topics Covered:Evolving from instructor-student roles to creative peer collaborationBuilding and sustaining community-rooted podcast archivesThe ethics and art of listening, trust, and relationship-buildingNavigating independence, institutional pressure, and artistic integrityMutual mentorship and non-hierarchical support in the artsPractical strategies for launching and growing a podcastAdapting to changes in media and the podcasting landscapeCentering and uplifting underrepresented stories and artistsReflections on curiosity, inspiration, and freedom through art

Documenting the Search for Truth: Honest Connection, Legendary Voices & UFO Whiteness Explored... In this episode of VISITORS, Kelly sits down with acclaimed documentary filmmaker James Fox, whose work has shaped the public conversation about UFOs and the mysteries of the phenomenon. James dives into his unique process and perspective, the relentless pursuit of credible stories, and his honest connection with UFO whiteness—bringing forward extraordinary testimonies and challenging conventional thinking. They discuss his conversations with pioneers in the field like Stanton Friedman and the rare moment spent with Stephen Hawking.  James also discusses the personal impact of working so closely with witnesses, the responsibility of telling their stories truthfully, and the importance of respectful storytelling with skeptics and believers in mind simultaniously.

EVERYBODY does it now!See Privacy Policy at https://art19.com/privacy and California Privacy Notice at https://art19.com/privacy#do-not-sell-my-info.

Ben Dhiman is an American pro runner for Asics, living in France. He has been one of the strongest long-course athletes in the sport in recent years, this season winning Ventoux by UTMB 89k, and Lavaredo by UTMB 120k - the latter in course record fashion. Later this summer, Ben will be among the favorites at UTMB.   Topics discussed:   How Ben is feeling mid-season a month removed from UTMB The couple disappointing DNFs Ben as succumbed to at UTMB Dealing with the loss of his father in 2024 Ben's winter campaign to run sub-30min in the 10k Documenting his training and racing on Substack His win at Ventoux by UTMB 89k Breaking the course record at Lavaredo Look ahead to UTMB A lot more!   SUBSCRIBE TO BEN'S SUBSTACK   Sponsors:   Use code freetrail10 for 10% off Speedland Footwear Grab a trail running pack from Osprey Use code FREETRAIL25 for 25% off your first order of NEVERSECOND nutrition at never2.com Go to ketone.com/freetrail30 for 30% off a subscription of Ketone IQ   Freetrail Links: Website | Freetrail Pro | Patreon | Instagram | YouTube | Freetrail Experts   Dylan Links: Instagram | Twitter | LinkedIn | Strava