Podcasts about capabilities

Introducing EVE This episode kicks off with an introduction to EVE, an AI operator that turns email inboxes into lead generation. Founder Vadim Rogovskiy explains that EVE helps small businesses organize their inboxes to find leads and follow-ups. EVE saves time by drafting personalized emails and flagging upsell or churn signals. He mentions the special pricing: $250 per month for an individual plan and $500 per month for a team plan. EVE offers a seven-day trial, a refund for the first month, and a risk-free first month. Vadim also provides information on how to find more information about EVE online and on LinkedIn. EVE for Independent Consultants The conversation highlights how EVE can be useful for independent consultants who manage their own sales and work. Vadim explains that EVE requires minimal onboarding; users just need to connect their corporate email. EVE integrates with Google and Microsoft for privacy and security, and EVE builds a knowledge graph about the business by analyzing years of email data and internet-based research.  Functionality and Features Vadim describes how EVE classifies contacts and extracts customer profiles from email data and public databases. EVE analyses communication to adopt tone and style, and provides an executive summary of the business to filter and prioritize leads. EVE flags leads that fit the ideal customer profile and provides necessary context for follow-ups and analyzes and prioritizes urgency. EVE can draft emails in the user's style and automate bespoke responses based on previous email history. Automated Re-Engagement of  Cold Leads When asked about re-engaging cold leads that have not responded in months or years, Vadim explains that EVE can suggest templates for re-engaging cold leads. EVE's vision includes automating communications to handle a majority of leads without human intervention. EVE can schedule calls, draft contracts, and answer questions based on the company's knowledge base. EVE's Capabilities in Action. Vadim  shares his screen and logs into EVE using his corporate email.   EVE displays new opportunities and follow-up leads, providing context and recommended actions. EVE shows a full history of communication with leads and allows filtering by various criteria. Timestamps: 00:02:  Overview of EVE 01:28: Use Cases and Onboarding Process   04:28: Detailed Functionality and Features 06:40: Re-Engaging Cold Leads 10:25: Demonstration of EVE's Capabilities 13:49: Pricing and Availability Links: Website: joineve.ai LinkedIn: https://www.linkedin.com/in/vadim-rogovskiy/   Unleashed is produced by Umbrex, which has a mission of connecting independent management consultants with one another, creating opportunities for members to meet, build relationships, and share lessons learned. Learn more at www.umbrex.com.

 David Maxwell discusses South Korea's military spending increase, the largest in over 15 years, which supports the goal of developing independent warfighting capabilities and transitioning operational control (OPCON). He clarifies that the complexity of OPCON transfer is often misunderstood as a sovereignty issue. Maxwell notes that North Korea is thriving due to growing support from China and Russia, making Kim Jong-un less motivated to normalize relations with the United States.

Matt Slick Live (Live Broadcast of 09/30/2025) is a production of the Christian Apologetics Research Ministry (CARM). Matt answers questions on topics such as: The Bible, Apologetics, Theology, World Religions, Atheism, and other issues! You can also email questions to Matt using: info@carm.org, Put "Radio Show Question" in the Subject line! Answers will be discussed in a future show. Topics Include: Matt Recounts his Interaction with those who Evangelized him/Errors of the RCC and the Need to Study God's Word/ Does Scripture Limit the Number of Children we Should Have?/ Is The World Turning Against Israel?/ Adam and Eve and The Tree of Life?/ A Question About the Capabilities of the Upcoming Website/ There Are no Women Authors of Bible Books—What Does This Mean?/ A Question on The Existence of God and One of Matt's Arguments/A Discussion of Logical Approaches to God's Nature/ September 30, 2025

Artificial intelligence (AI) is a transformational technology, but it has limitations in challenging operational settings. Researchers in the AI Division of the Carnegie Mellon University Software Engineering Institute (SEI) work to deliver reliable and secure AI capabilities to warfighters in mission-critical environments. In our latest podcast, Matt Gaston, director of the SEI's AI Division, sits down with Matt Butkovic, technical director of the SEI CERT Division's Cyber Risk and Resilience program, to discuss the SEI's ongoing and future work in AI, including test and evaluation, the importance of gaining hands-on experience with AI systems, and why government needs to continue partnering with industry to spur innovation in national defense. 

Plus, Apple is reportedly nearing production for its latest M5-powered MacBooks. Learn more about your ad choices. Visit podcastchoices.com/adchoices

Identity security is evolving rapidly, and SailPoint is at the forefront of AI-powered identity and access management (IAM). In this session, we dive into SailPoint's key capabilities, automation features, and career opportunities, helping organizations and professionals stay ahead in modern identity security.

Learn how to harness AI as your ultimate business accelerator and create what once seemed impossible in record time What if I told you that "super-agents" could solve your biggest business problems in 20 minutes while you sleep? Look, the AI revolution isn't coming - it's already here, and it's moving faster than most people can even comprehend. In this episode, we dive deep into the reality that everything you've ever imagined AI could do is not only possible right now, but the only limitation is your imagination and willingness to embrace these tools. We're talking about creating functional software prototypes in 20 minutes, generating professional presentations for NASA in hours instead of weeks, and literally having 10 AI "super-agents" work on your problems simultaneously. This isn't about replacing human creativity - it's about amplifying it to levels that would have been science fiction just months ago. Mike Koenigs is the Founder of The Superpower Accelerator and has transformed over 61,000 clients into "Category of One" brands that dominate their markets. This guy just got back from speaking at NASA - not about theory, but actually demonstrating solutions to their 174 biggest documented problems using AI tools most people have never heard of. He's also spoken at the United Nations, leveraging over 30 years of strategic insight to help experts become influential brand leaders. What sets Mike apart isn't just his track record of creating transformational business celebrities - it's his ability to see possibilities where others see obstacles and turn AI into a profit-multiplying superpower without diluting your essence. KEY TAKEAWAYS: AI capabilities are advancing daily - the gap between what was possible six weeks ago versus today shows exponential acceleration. "Super-agents" let you run 10 AI specialists simultaneously on the same problem instead of waiting for one solution. You can create functional software prototypes in 20 minutes without any coding experience or technical background. Master the AI mindset, not specific tools - tools change constantly but strategic thinking principles remain valuable. AI amplifies existing traits - lazy people get lazier while curious people become exponentially more effective. Future advantage belongs to those asking better questions, not those memorizing more answers. Use AI to amplify your thinking, not replace it - letting AI think for you leads to declining performance. Companies must create AI-friendly cultures now or risk losing top talent to competitors who embrace these capabilities. AI Live Event: www.AiAccelerator.com/LIVECharles AI Accelerator Book: www.AiAccelerator.com/CGAiBook Use Coupon Code “BIRD500” for $500 Off (good until Sunday at Midnight) Growing your business is hard, but it doesn't have to be. In this podcast, we will be discussing top level strategies for both growing and expanding your business beyond seven figures. The show will feature a mix of pure content and expert interviews to present key concepts and fundamental topics in a variety of different formats. We believe that this format will enable our listeners to learn the most from the show, implement more in their businesses, and get real value out of the podcast. Enjoy the show. Please remember to rate, review and subscribe to the podcast so you don't miss any future episodes. Your support and reviews are important and help us to grow and improve the show. Follow Charles Gaudet and Predictable Profits on Social Media: Facebook: facebook.com/PredictableProfits Instagram: instagram.com/predictableprofits Twitter: twitter.com/charlesgaudet LinkedIn: linkedin.com/in/charlesgaudet Visit Charles Gaudet's Wesbites:  www.PredictableProfits.com www.predictableprofits.com/community  

Amanda Di Dio, VP of Partnerships and Operations at Optimistic Design, discusses the challenge of balancing user needs with technological constraints in product development. She shares her approach of treating users as active stakeholders, involving them in co-creation and continuous decision-making to shape product visions, prioritize features, and validate solutions.

HEADLINE: Strategic Partnership: Russia Barters Advanced Military Technology, Including Nuclear Submarine Capabilities, for North Korean Munitions GUEST NAME: Professor Bruce Bechtol SUMMARY: Professor Bruce Bechtol details the North Korea-Russia strategic partnership. Russia pays for North Korean munitions with military technology, including nuclear submarine capability, while their special operations forces fought fiercely in Ukraine.1955 KIM IL-SUNG

HEADLINE: Strategic Partnership: Russia Barters Advanced Military Technology, Including Nuclear Submarine Capabilities, for North Korean Munitions GUEST NAME: Professor Bruce Bechtol SUMMARY: Professor Bruce Bechtol details the North Korea-Russia strategic partnership. Russia pays for North Korean munitions with military technology, including nuclear submarine capability, while their special operations forces fought fiercely in Ukraine.

Wendy is a licensed acupuncturist and herbalist in Massachusetts and President of Wellness Allied, an organization advancing science and the integration of ancient wisdom and modern medicine in order to improve prevention, performance and recovery for patients. Wendy is the founder of CBS Acupuncture, now with 8 locations around Boston. She's also a visionary healer. Her mission is to educate others on how ancient wisdom and modern medicine are coming to a better understanding. Dr. Li believes that it will lead to a wider acceptance of integrated approaches to healthcare allowing all people to live longer, and healthier. On this episode we get into Wendy's story, her journey and some of the lesser known uses for acupuncture, like for anxiety, depression, restless leg syndrom and even breast health. CBS acupuncture Home page

HEADLINE: Nvidia's Strategic $5 Billion Investment in Intel Reshapes US Chip Industry GUEST NAME: Chris Riegel SUMMARY: Nvidia, led by Jensen Huang, invests $5 billion in Intel, gaining access to manufacturing capabilities while Intel gets crucial funding. This partnership reduces Nvidia's reliance on TSMC and aligns with President Trump's "national champion strategy." The deal comes amid China's ban on Nvidia chips and China's struggle for technological self-sufficiency. 1933

Tata Consultancy Services (TCS), a global leader in IT services, consulting, and business solutions, operating a Global Delivery Centre in Letterkenny, Ireland, has partnered with Qualcomm to set up the 'TCS Innovation Lab', a space for co-innovation with Qualcomm in Bengaluru, India. TCS and Qualcomm will co-create smart, scalable, and sustainable Edge AI capabilities utilising Qualcomm platforms for industries moving towards a software-driven approach to make their systems more efficient and resilient in the lab. The co-innovation lab will enable the creation of customised low-cost solutions that can be deployed on intelligent devices, on location and in real time to streamline processes at large enterprises. Located in India's start-up and innovation capital, Bengaluru, the lab will be part of the IoT-focused Bringing Life to Things Network lab. The lab, which is equipped with 5G private network infrastructure and other hi-tech network and equipment, will develop capabilities for sectors that need agile IoT solutions, such as security and surveillance, healthcare, smart infrastructure, and manufacturing. With its strategic location and advanced infrastructure, the lab is designed to support the rapid prototyping, experimentation, and large-scale implementation of Edge AI capabilities built on a Software Defined Everything (SDx) approach. Savi Soin, Sr. Vice President & President, Qualcomm India, said, "Our collaboration with TCS marks an important step in bringing practical, real-time Edge AI solutions to industries that are rapidly evolving. The TCS Innovation Lab will serve as a space where advanced AI and connectivity meet real-world challenges. Together, we aim to develop solutions that are cost-effective, efficient, scalable, and tailored to the needs of enterprises looking to modernise and grow in a software-defined world." Enterprises across sectors need to develop and deploy intelligent devices that can autonomously make decisions to run processes efficiently, creating a rise in demand for smart, compact, energy-efficient and high-performance self-healing devices. TCS shall leverage advanced Edge AI and SDx capabilities that are hardware-agnostic, highly configurable, secure, and service-oriented. These will help global enterprises build robust, agile systems that adapt quickly to changes in industry ecosystems and business processes. The proposed solutions shall find applications in medical devices, smart handhelds for controlling industrial processes and machinery, smart infrastructure and advanced safety and surveillance mechanisms. Running TCS' SDx capabilities on Qualcomm Technologies' Edge AI-enabled System-on-Chips will connect the physical and digital worlds more seamlessly. V Rajanna, Business Group Head, Technology, Software and Services, TCS, said, "We are excited to announce the launch of a state-of-the-art co-innovation lab focused on advancing Software Defined Everything (SDx) and Edge AI platforms. This lab will drive the development of next-generation solutions for diverse applications - including intelligent medical devices, smart industrial handhelds, and advanced safety and surveillance systems. TCS remains committed to investing in innovation and harnessing the power of AI to help enterprises unlock greater agility, efficiency, and long-term business value." The latest collaboration between TCS and Qualcomm Technologies, Inc., builds on the large transformational projects carried out by both companies across engineering services, including silicon solution design and IT support. Leveraging this collaboration with Qualcomm Technologies, TCS recently developed a real-time smart visual anomaly detection capability for material inspection for a large automotive manufacturer. The NextGen approach processes live camera feeds to scan for surface defects for industrial, aerial and terrestrial inspections. It identifies even the tiniest imperfections on various surfaces, including steel and painted sur...

Tehillah Niselow is in conversation with Joni Peddie, CEO at Resilient PeopleSee omnystudio.com/listener for privacy information.

I asked my followers what data product I should build next, and they voted: a Pokémon card analytics tool. So, I rolled up my sleeves and built a market analytics platform using Replit and its vibe-coding agent to get from idea to deployable MVP in a few hours! Today's video guides you through the process step by step, so you can build something similar—even if you have 0 technical background.✨ Try vibe-coding yourself with Replit!!! https://replit.com/refer/AveryDatap.s. this is an affiliate link, so I will earn credits if you end up using Replit - but I truly love this tool!Check out my Pokémon card analytics app here and let me know what you think!

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

Andrea Stricker Iran's Nuclear Program Targeted, Verification Crisis Ensues Andrea Stricker discusses Israel and USstrikes on Iran's nuclear facilities like Fordo, Natanz, and Isfahan, destroying centrifuges and weaponization capabilities. The IAEA cannot verify Iran's nuclear material locations after inspectors were expelled. Iran's 60% enriched uranium poses a proliferation risk, leading to anticipated UN sanctions. The strikes prevented JCPOA-allowed centrifuge surges.1045-1100 1870 TEHRAN

CONTINUED Andrea Stricker Iran's Nuclear Program Targeted, Verification Crisis Ensues Andrea Stricker discusses Israel and USstrikes on Iran's nuclear facilities like Fordo, Natanz, and Isfahan, destroying centrifuges and weaponization capabilities. The IAEA cannot verify Iran's nuclear material locations after inspectors were expelled. Iran's 60% enriched uranium poses a proliferation risk, leading to anticipated UN sanctions. The strikes prevented JCPOA-allowed centrifuge surges.1890 TEHRAN

- Roman Yampolsky Interview and DMSO Usage (0:10) - RFK Jr. vs. US Senate (4:57) - Enoch AI Demonstration (13:44) - Enoch's Capabilities and Applications (19:35) - Mission Statement and Future Goals (41:24) - Challenges and Solutions in Health Freedom (1:08:44) - Human Element vs. AI in Medicine (1:09:14) - Legislation and AI in Medicine (1:24:14) - Holistic Medicine and Big Pharma (1:27:10) - Challenges in Medical Freedom (1:35:19) - Historical and Current Medical Practices (1:56:18) - Impact of Electromagnetic Radiation (1:56:37) - Future of Medical Education (2:02:22) - Supporting Holistic Health (2:04:44) - Final Thoughts and Acknowledgments (2:10:57) For more updates, visit: http://www.brighteon.com/channel/hrreport  NaturalNews videos would not be possible without you, as always we remain passionately dedicated to our mission of educating people all over the world on the subject of natural healing remedies and personal liberty (food freedom, medical freedom, the freedom of speech, etc.). Together, we're helping create a better world, with more honest food labeling, reduced chemical contamination, the avoidance of toxic heavy metals and vastly increased scientific transparency. ▶️ Every dollar you spend at the Health Ranger Store goes toward helping us achieve important science and content goals for humanity: https://www.healthrangerstore.com/ ▶️ Sign Up For Our Newsletter: https://www.naturalnews.com/Readerregistration.html ▶️ Brighteon: https://www.brighteon.com/channels/hrreport ▶️ Join Our Social Network: https://brighteon.social/@HealthRanger ▶️ Check In Stock Products at: https://PrepWithMike.com

In this episode of the Dev Pulse, Expand the Stack series, host Zach Stepek broadcasts straight from the show floor at WordCamp US 2025, where he dives into the latest innovations shaking up the WordPress community. Zach catches up with Shilo Eish Yemini and Miriam Schwab from the Elementor team in their unmistakably pink booth […]

Una ricerca condotta sul più grande database mondiale di salute mentale dice senza mezzi termini che affidare uno smartphone e dare accesso ai social network prima dei 13 anni ha delle conseguenze pesantissime sullo sviluppo mentale, con distacco dalla realtà, crollo dell'autostima e incapacità di gestire le emozioni. Di questo passo, avvisano i ricercatori, un terzo dei giovani sarà afflitto da disagi mentali gravi. I rimedi ci sono, e ne vengono proposti quattro tipi. Se vi servono dati per discutere concretamente del problema, questa ricerca condotta du oltre due milioni di individui distribuiti in 163 paesi e su 18 lingue può essere un punto di partenza prezioso.“Protecting the Developing Mind in a Digital Age: A Global Policy Imperative”, ”Tara C. Thiagarajan,Jennifer Jane Newson, Shailender Swaminathan, Journal of Human Development and Capabilities https://doi.org/10.1080/19452829.2025.2518313

Una ricerca condotta sul più grande database mondiale di salute mentale dice senza mezzi termini che affidare uno smartphone e dare accesso ai social network prima dei 13 anni ha delle conseguenze pesantissime sullo sviluppo mentale, con distacco dalla realtà, crollo dell'autostima e incapacità di gestire le emozioni. Di questo passo, avvisano i ricercatori, un terzo dei giovani sarà afflitto da disagi mentali gravi. I rimedi ci sono, e ne vengono proposti quattro tipi. Se vi servono dati per discutere concretamente del problema, questa ricerca condotta su oltre due milioni di individui distribuiti in 163 paesi e su 18 lingue può essere un punto di partenza prezioso.“Protecting the Developing Mind in a Digital Age: A Global Policy Imperative”, ”Tara C. Thiagarajan,Jennifer Jane Newson, Shailender Swaminathan, Journal of Human Development and Capabilities https://doi.org/10.1080/19452829.2025.2518313

Episode Summary: America's ability to secure its interests, whether deterring conflict or fighting and wining, demands a robust Air Force. The current security environment will tolerate nothing less. The service has traditionally measured its prowess via capacity, capabilities, and readiness. The Air Force currently lags in each of these three areas. Want proof? The service's FY 2025 budget request sought to divest 250 aircraft, while only procuring 91. The FY 2026 request seeks to divest 340 aircraft, while only acquiring 76. It is essential that the Trump administration and Congress reverse the service's decline in capacity, capability, and readiness. In this episode, Lt. Gen. David Deptula, USAF (Ret.), JV Venable, and Robert “Otis” Winkler discuss these challenges and outline what needs to be done to reset the Air Force. JV just completed a major report on this topic, and the conversation centers around the top findings. The time for concerted action is now. Credits: Host: Douglas Birkey, Executive Director, The Mitchell Institute for Aerospace Studies Producer: Shane Thin  Executive Producer: Douglas Birkey Guest: Lt. Gen. David Deptula, USAF (Ret.), Dean, The Mitchell Institute for Aerospace Studies Guest: John "JV" Venable, Senior Fellow for Airpower Studies, The Mitchell Institute for Aerospace Studies Guest: Robert "Otis" Winkler, Vice President, Corporate Development and National Security Programs, Kratos Defense and Security Solutions Links: Subscribe to our Youtube Channel: https://bit.ly/3GbA5Of Website: https://mitchellaerospacepower.org/ Twitter: https://twitter.com/MitchellStudies Facebook: https://www.facebook.com/Mitchell.Institute.Aerospace LinkedIn: https://bit.ly/3nzBisb Instagram: https://www.instagram.com/mitchellstudies/ #MitchellStudies #AerospaceAdvantage #China #readiness

Spiros Xanthos is the CEO of Resolve AI which builds agentic AI systems that detect, investigate, and resolve production incidents automatically, letting engineers focus on building instead of firefighting. Their multi-agent platform reduces mean-time-to-resolution by up to 5× and is already running in real-world deployments to boost reliability and productivity.Try AI Box: ⁠⁠https://aibox.aiAI Chat YouTube Channel: https://www.youtube.com/@JaedenSchaferJoin my AI Hustle Community: https://www.skool.com/aihustleLearn about Resolve: https://resolve.ai/Chapters00:00 Introduction to Agentic AI Systems02:30 The Journey to Resolve AI05:17 Capabilities of AI Agents in Production07:59 Ensuring AI Reliability and Reducing Hallucinations10:40 AI in Engineering: Current Use Cases13:37 The Future of AI Agents in Engineering16:13 Getting Started with Resolve AI

Earnest Sweat, a tech innovation expert, was a guest on the latest edition of the REIT Report podcast. In the last of a three-part miniseries, Sweat continued to examine the intersection of AI with the REIT sector, focusing on how REITs can evaluate AI pilots, partnerships, and capabilities. Sweat is a venture capitalist and general partner at Stresswood, an early-stage fund focused on backing exceptional founders building the next wave of enterprise technology. During the interview, Sweat discussed critical questions a REIT leader should ask before launching an AI initiative, as well as how REITs can balance the promise of AI with the reality of implementation, and how REIT leaders should effectively communicate the value and purpose of AI initiatives to their teams. 

Gagan Singh of Elastic discuses how agentic AI systems reduce analyst burnout by automatically triaging security alerts, resulting in measurable ROI for organizationsTopics Include:AI breaks security silos between teams, data, and tools in SOCsAttackers gain system access; SOC teams have only 40 minutes to detect/containAlert overload causes analyst burnout; thousands of low-value alerts overwhelm teams dailyAI inevitable for SOCs to process data, separate false positives from real threatsAgentic systems understand environment, reason through problems, take action without hand-holdingAttack discovery capability reduces hundreds of alerts to 3-4 prioritized threat discoveriesAI provides ROI metrics: processed alerts, filtered noise, hours saved for organizationsRAG (Retrieval Augmented Generation) prevents hallucination by adding enterprise context to LLMsAWS integration uses SageMaker, Bedrock, Anthropic models with Elasticsearch vector database capabilitiesEnd-to-end LLM observability tracks costs, tokens, invocations, errors, and performance bottlenecksJunior analysts detect nation-state attacks; teams shift from reactive to proactive securityFuture requires balancing costs, data richness, sovereignty, model choice, human-machine collaborationParticipants:Gagan Singh – Vice President Product Marketing, ElasticAdditional Links:Elastic – LinkedIn - Website – AWS Marketplace See how Amazon Web Services gives you the freedom to migrate, innovate, and scale your software company at https://aws.amazon.com/isv/

Text-to-video AI is here, but it's far from perfect. Jiebo Luo, Albert Arendt Hopeman professor of Engineering and professor of computer science at the University of Rochester, identifies a solution to one challenge. Jiebo Luo is the Albert Arendt Hopeman Professor of Engineering and Professor of Computer Science at the University of Rochester. He is a Fellow of […]

Ben Criddle talks BYU sports every weekday from 2 to 6 pm.Today's Co-Hosts: Ben Criddle (@criddlebenjamin)Subscribe to the Cougar Sports with Ben Criddle podcast:Apple Podcasts: https://itunes.apple.com/us/podcast/cougar-sports-with-ben-criddle/id99676

Send us a text

Not every high performer wants to lead...here's how to spot true leadership potential! It always comes as a surprise when someone we had earmarked for bigger and better things announces that they have no desire to progress.Our search for talent, and our need to fill the leadership pipeline for our company can deceive us. We occasionally typecast someone who has absolutely no interest in leading.Halo effect often leads us to overestimate someone's ability, and their intuitive sense of their own limitations can freeze them in their own fear of failure.In this episode, I look at why some great employees might not fit our stereotype of ambitious people; I talk about the capabilities that distinguish a rising star from a really good worker; and I give you 8 questions you can ask yourself to work out which is which.We've also created a free downloadable PDF checklist that you can use to assess your rising stars' capabilities, so that you can make better predictions about their future leadership success. ————————Get the insider edge with the No Bullsh!t Leadership Hub on Skool - completely FREE!Join like-minded leaders who love the podcast and dive into exclusive resources, real conversations, and weekly challenges designed to sharpen your leadership game.Don't miss out, join now!————————You can connect with me at:Website: https://www.yourceomentor.comFacebook: https://www.facebook.com/yourceomentorInstagram: https://www.instagram.com/yourceomentorLinkedin: https://www.linkedin.com/in/martin-moore-075b001/Youtube: https://www.youtube.com/@YourCEOMentor————————Our mission here at Your CEO Mentor is to improve the quality of leaders, globally. Hosted on Acast. See acast.com/privacy for more information.

Send us a text

Send us a text

In this episode of the AWS Podcast, we explore the evolving world of contact centers and Amazon Connect. The discussion covers why contact centers remain critical to both business and public sector operations, and how they're transforming from traditional cost centers into valuable sources of business intelligence. Key highlights include Amazon Connect's integration capabilities with AWS services, particularly through AWS Lambda functions, and the recent implementation of generative AI features including contact summarisation, agent evaluations, and Amazon Q in Connect. The conversation emphasizes how modern technology is helping organizations better understand customer needs, improve agent performance, and maintain human empathy in customer service while leveraging automation. The episode also touches on practical aspects of system integration and data management, demonstrating how Amazon Connect helps organizations overcome traditional barriers in contact center operations. https://aws.amazon.com/connect/ https://aws.amazon.com/blogs/contact-center/introducing-the-next-generation-of-amazon-connect/

The FDA Group's Nick Capman sits down with executive consultant Sean Gallimore to break down what makes medtech leaders and teams truly effective. Drawing from decades of experience across medical devices, diagnostics, CROs, and industrial technology, Sean shares his practical framework for leadership—the 4 Cs: Strategic Clarity, Capabilities, Compliance, and Connectedness—and how each one directly impacts growth, culture, and execution.Listeners will learn how to:Pressure-test whether your strategy is actually winnable.Match organizational capabilities to goals (and pivot when they don't).Use KPIs and OKRs to diagnose execution gaps.Build stronger trust and culture through connectedness, from “gemba” walks to multi-channel communication.Sean also shares real-world stories—from transforming an underperforming ultrasound launch to shifting a company's culture from “play not to lose” to “play to win.” Whether you're leading in medtech, life sciences, or beyond, this episode delivers actionable insights you can bring straight back to your team.About the Guest:Sean Gallimore, MBA is an executive consultant with 30 years of leadership across Fortune 500, mid-cap, and private equity–backed companies in medical devices, life sciences, and industrial technology. He has held senior roles at Medtronic, Smith & Nephew, Philips, Parexel, PDI Healthcare, and Dynisco, driving growth through strategy execution, turnarounds, innovation, and building high-performing teams. Today, he advises early-stage medtech companies on scaling operations, commercial strategy, and organizational development.About The FDA Group:The FDA Group helps life science organizations rapidly access the industry's best consultants, contractors, and candidates. Our resources assist in every stage of the product lifecycle, from clinical development to commercialization, with a focus on staff augmentation, auditing, remediation, QMS, and other specialized project work in Quality Assurance, Regulatory Affairs, and Clinical Operations: https://www.thefdagroup.com/

Welcome to episode #997 of Six Pixels of Separation - The ThinkersOne Podcast. What happens when nearly everything a marketer or strategist does today becomes instant, automatic… and nearly free? That's the premise of AI First, the new book from Adam Brotman (my guest this week) and his co-author Andy Sack, which confronts the existential shift that AI is bringing to brand strategy, customer experience and creative work. Adam, the former Chief Digital Officer at Starbucks and co-founder of the strategic consultancy Forum3, brings firsthand experience building digital platforms that changed how global businesses operate. In this episode, we dive into what it really means to become an "AI First” organization, not just layering on tools, but redesigning your business from the ground up. You'll hear why OpenAI's Sam Altman believes 95% of current marketing agency work will be handled by AI, and what that means for leaders, teams and the future of creative differentiation. We explore the difference between being AI-aware and AI-native, how to run internal pilots that create momentum, and what the future holds for customer loyalty and personalization in a post-human-first creative landscape. For anyone wondering what practical transformation looks like in an AI-saturated world and how to build companies that still feel human, this conversation maps the next five years and beyond. Enjoy the conversation… Running time: 52:22. Hello from beautiful Montreal. Listen and subscribe over at Apple Podcasts. Listen and subscribe over at Spotify. Please visit and leave comments on the blog - Six Pixels of Separation. Feel free to connect to me directly on Facebook here: Mitch Joel on Facebook. Check out ThinkersOne. or you can connect on LinkedIn. ...or on X. Here is my conversation with Adam Brotman. AI First. Forum3. Check out his podcast. Follow Adam on LinkedIn. Chapters: (00:00) - The Journey of Digital Transformation. (05:05) - AI First: Understanding the New Paradigm. (10:00) - The Role of AI in Business Strategy. (15:09) - Navigating the Future of Work with AI. (19:50) - The Promise and Challenges of AGI. (31:58) - The Rise of AI and Human Collaboration. (34:07) - Navigating the AI Landscape: Challenges and Opportunities. (37:27) - Intelligence vs. Imitation: Understanding AI's Capabilities. (40:57) - Creativity in the Age of AI: A New Frontier. (43:30) - The Role of Empathy in AI Interactions. (46:41) - Paradigm Shifts: Embracing Change in Technology. (49:01) - Responsible AI: Balancing Innovation and Ethics. (52:44) - The Future of Work: Adapting to AI Transformations.

Debating AI Intelligence and Corporate Utilization on Project Synapse In this episode of Project Synapse, hosts Jim Love, Marcel Gagne, and John Pinard delve into the ongoing debate about AI intelligence and the advancements in AI technology. They discuss the reliability and accuracy of AI models like GPT-5 and Grok, questioning whether these models are truly intelligent or merely sophisticated pattern matchers. The conversation also touches on the future of AI in both corporate settings and personal use, the ethical implications of AI development, and the different AI tools available for varying needs. The hosts explore the potential impact of AI on industries, user experiences, and the dynamics of technological dominance, particularly focusing on the impact of AI-driven changes in corporations like Apple and Google. 00:00 Introduction and AI Debate 00:23 Project Synapse Hosts and Apple Discussion 01:28 Apple's AI and Self-Driving Car Ventures 03:27 Grok's Unhinged Personality and AI Voice Modes 05:11 GPT-5 Rollout and User Reactions 12:08 AI Consistency and User Expectations 14:41 OpenAI's Market Position and User Experience 29:01 Grok's Capabilities and Image Generation 37:40 AI Personalities and Technological Advances 38:50 The Evolution of AI Tools 41:01 Super Intelligence and the Singularity 43:18 Debating AI's Future and Capabilities 46:52 Human vs. AI: Intelligence and Learning 52:59 Transhumanism and AI Integration 01:06:01 Corporate AI vs. Consumer AI 01:13:11 The Future of AI and Global Competition 01:14:29 Conclusion and Final Thoughts

In this episode of The Korea Pro Podcast, Jeongmin, John and Joon Ha examine the decision to postpone key Ulchi Freedom Shield drills to September due to South Korea's summer heatwave. They also discuss USFK commander General Xavier Brunson's recent remarks on the potential for a rushed transfer of operational wartime control (OPCON) and Seoul's ambitious plan to achieve that transition within President Lee Jae-myung's term.  The hosts also break down Lee's newly announced five-year blueprint, outlining 123 national policy tasks built around constitutional reform, balanced economic growth and strengthened diplomatic security. They look at the political and economic stakes of the plan, as well as the nomination of Lee Chan-jin to head the Financial Supervisory Service. About the podcast: The Korea Pro Podcast is a weekly 15-minute conversation hosted by Korea Risk Group Executive Director Jeongmin Kim, Editor John Lee and correspondent Joon Ha Park, diving deep into the most pressing stories shaping South Korea — and dissecting the most complicated ones for professionals monitoring ROK politics, diplomacy, culture, society and technology. Uploaded every Friday. This episode was recorded on Thursday, Aug. 14, 2025. Audio edited by Gaby Magnuson

Egil Østhus on LinkedIn: https://www.linkedin.com/in/egilconr/ Video of Egil talking about Unleash https://www.youtube.com/watch?v=HVBXxFZGVfc Go here to get started with Unleash: https://www.getunleash.io Four Pillars Excerpt from FeatureOps whitepaper and FeatureOps introduction There are four pillars of FeatureOps: The post 305 Feature flags—Fine grain control of Features gives Ops, Business, and Customers new capabilities first appeared on Agile Noir.

Founded by Osama bin Laden in the late 1980s, Al-Qaeda is best known for orchestrating the September 11, 2001 terrorist attacks in the United States, which killed nearly 3,000 people. But what kind of threat does the violent Islamist organisation pose in 2025?In this episode, host Lucas Webber is joined by Edmund Fitton-Brown, a former British diplomat and former Coordinator of the United Nations' Monitoring Team, and an expert on Al-Qaeda. Edmund shares unique insights into Al-Qaeda's current capabilities, the group's strategic recalibration following the October 7th, 2023 Hamas attack, and why he believes a directed Al-Qaeda attack may not be far off.

This episode of the Pipeliners Podcast features a conversation with Suzanne Ogle and Cindy Anderson from the SGA Natural Gas Association. They discuss the association's mission, which is centered on providing training and development to the natural gas industry's workforce. The discussion also touches on the organization's recent rebrand and its role in fostering collaboration and a shared understanding across the entire natural gas value chain. Visit PipelinePodcastNetwork.com for a full episode transcript, as well as detailed show notes with relevant links and insider term definitions.

Brad Lightcap is the Chief Operating Officer of OpenAI. Lightcap joins Big Technology to discuss the launch of GPT-5, how it works, what sets it apart from previous models, and whether it's AGI. We also cover scaling laws, post-training breakthroughs, enterprise adoption, health care applications, pricing strategy, and the company's profitability outlook. Hit play for a front-row seat to OpenAI's thinking on the future of AI. --- Enjoying Big Technology Podcast? Please rate us five stars ⭐⭐⭐⭐⭐ in your podcast app of choice. Want a discount for Big Technology on Substack + Discord? Here's 25% off for the first year: https://www.bigtechnology.com/subscribe?coupon=0843016b Questions? Feedback? Write to: bigtechnologypodcast@gmail.com

What happens when an internal hack turns into a $400 million AI rocket ship? In this episode, Matt Turck sits down with Boris Cherny, the creator of Claude Code at Anthropic, to unpack the wild story behind the fastest-growing AI coding tool on the planet.Boris reveals how Claude Code started as a personal productivity tool, only to become Anthropic's secret weapon — now used by nearly every engineer at the company and rapidly spreading across the industry. You'll hear how Claude Code's “agentic” approach lets AI not just suggest code, but actually plan, edit, debug, and even manage entire projects—sometimes with a whole fleet of subagents working in parallel.We go deep on why Claude Code runs in the terminal (and why that's a feature, not a bug), how its Claude.md memory files let teams build a living, shareable knowledge base, and why safety and human-in-the-loop controls are baked into every action. Boris shares real stories of onboarding times dropping from weeks to days, and how even non-coders are hacking Cloud Code for everything from note-taking to business metrics.AnthropicWebsite - https://www.anthropic.comX/Twitter - https://x.com/AnthropicAIBoris ChernyLinkedIn - https://www.linkedin.com/in/bchernyX/Twitter - https://x.com/bchernyFIRSTMARKWebsite - https://firstmark.comX/Twitter - https://twitter.com/FirstMarkCapMatt Turck (Managing Director)LinkedIn - https://www.linkedin.com/in/turck/X/Twitter - https://twitter.com/mattturck(00:00) Intro (01:15) Did You Expect Claude Code's Success? (04:22) How Claude Code Works and Origins (08:05) Command Line vs IDE: Why Start Claude Code in the Terminal? (11:31) The Evolution of Programming: From Punch Cards to Agents (13:20) Product Follows Model: Simple Interfaces and Fast Evolution (15:17) Who Is Claude Code For? (Engineers, Designers, PMs & More) (17:46) What Can Claude Code Actually Do? (Actions & Capabilities) (21:14) Agentic Actions, Subagents, and Workflows (25:30) Claude Code's Awareness, Memory, and Knowledge Sharing (33:28) Model Context Protocol (MCP) and Customization (35:30) Safety, Human Oversight, and Enterprise Considerations (38:10) UX/UI: Making Claude Code Useful and Enjoyable (40:44) Pricing for Power Users and Subscription Models (43:36) Real-World Use Cases: Debugging, Testing, and More (46:44) How Does Claude Code Transform Onboarding? (49:36) The Future of Coding: Agents, Teams, and Collaboration (54:11) The AI Coding Wars: Competition & Ecosystem (57:27) The Future of Coding as a Profession (58:41) What's Next for Claude Code

In this episode of the Daily Mastermind, George Wright III discusses the critical role of identity in business growth. He introduces the 'identity ladder,' a five-level framework that includes environment, behavior, skills, beliefs, and core identity. By focusing on upgrading these aspects, entrepreneurs can truly scale their businesses. Wright emphasizes that changing one's identity precedes strategy and tactics, urging listeners to adopt a founder's mindset and align their daily habits and beliefs with their business vision. This episode serves as a motivational guide for entrepreneurs to re-evaluate and elevate their identity to achieve greater success.00:51 Welcome to The Daily Mastermind01:19 The Identity Ladder: Five Levels to Success02:14 Level 1: Environment03:23 Level 2: Behavior and Habits04:44 Level 3: Capabilities and Skills06:14 Level 4: Beliefs and Mindset07:26 Level 5: Core Identity08:58 Be, Do, Have: The Right Order for SuccessYou have GREATNESS inside you. I BELIEVE in You. Let's Make Today the Day You Unleash Your Potential!George Wright IIICEO, The Daily Mastermind | Evolution X_________________________________________________________P.S. Whenever you're ready, here are ways I can help you…Get to know me:1. Subscribe to The Daily Mastermind Podcast- daily inspiration, motivation, education2. Follow me on social media Facebook | Instagram | Linkedin | TikTok | Youtube3. Get the Prosperity Pillars Poster I Developed over 20 years from my Mentors.Work with me:My mission is to help you Master Your Mind, Money, & Business, and I firmly believe:It's Never Too Late to Create the Life You Were Meant to Live…a LIFESTYLE of Health, Wealth, and Happiness. Here are ways I've been able to help thousands of people over the past 20 years… 4. FREE DOWNLOAD: Download the FREE 12-Day Authority Formula Email Course.5. JOIN THE EVOLUTION: A Private Members Only Mastermind Group that includes Weekly Group CEO Mentoring, Courses, Resources & Live Events. We will Grow Your Authority.6. GET FEATURED: Grow Your Brand and Authority by getting interviewed and featured alongside celebrities and experts in Valiant CEO Magazine online.7. AUTHORITY LAUNCH: Get a Custom Authority Blueprint that will help you to Quickly Grow Massive Authority and Get Seen by Thousands in Less than One Hour using our Proven Formula.

  According to a new study published in the Journal of Human Development and Capabilities, owning a smartphone before the age of 13 increases the likelihood that they will experience suicidal thoughts. With this troubling statistic, Licensed Professional Counselor, Leigh Richardson, PhD - Brain health Coach and consultant, discusses the details behind these numbers and what parents should know. 

New task force aims to combat construction fraud  $32 million... that's the amount that Utahns has lost to construction fraud since 2022... You hire a contractor to start a project... you pay them... and they walk off the job without finishing it. KSL-TV's Investigative Reporter Matt Gephardt joins the show to discuss his coverage on this issue over the years, and Margaret Woolley Busse from Utah's Department of Commerce on how the state of Utah is looking to curb this rising trend.     Bankruptcy beware: What to know before filing  Rising debt is ballooning out of control as many Americans are trying to keep up with rising prices and economic uncertainty. According to data by the Administrative Office of the U.S. Courts, there has been an increase of 11.5 percent in bankruptcy filings. Utah specifically rose 13.6 percent over the last year. Shane Stewart DMBA Certified Financial Planner joins the show to discuss the ins and outs of what bankruptcy does and doesn't do... and how long this decision can hurt your credit.    What happens when you ask AI to write your obituary  When you face the death of a loved one, you have to deal with all the paperwork that goes along with the death as well as your own grief. What if AI took one of those jobs away? Should it? Greg and Holly go into this new trend of surrendering over writing an obituary to an AI and put it to the test for themselves.    Phone Bans: a back-to-school guide for parents  Back to school is just around the corner, Utah has a new law that has by default... bans phones in schools...  and it's then up to the districts then decide how to implement it in their schools.. Ben Horsley, Granite School District Superintendent, joins the show to discuss the latest on how The Granite School District is implementing phone restrictions and how their past efforts have made a difference in the classroom.     Study: Owning a smart phone before age 13 increases likelihood of suicidal thoughts  According to a new study published in the Journal of Human Development and Capabilities, owning a smartphone before the age of 13 increases the likelihood that they will experience suicidal thoughts. With this troubling statistic, Licensed Professional Counselor, Leigh Richardson, PhD - Brain health Coach and consultant, discusses the details behind these numbers and what parents should know.    A silver lining for marriage and divorce rates?  The traditional image of a family is due for a makeover. Marriage rates are rising slightly, divorce rates are declining, and nearly one-third of young adults are predicted to never marry. Lois Collins, writer for the Deseret News, discusses the new findings.      Best and worst states to have a baby  Having a baby can be rewarding… but also expensive. WalletHub recently published a study on the best and worst states to have children, Greg and Holly look into where Utah placed with WalletHubWriter and Analyst, Chip Lupo.     Should states share their voting data with the DOJ?  Utah was added to a growing list of states getting requests from the DOJ about handing over confidential voter roll data. This move by the DOJ is reported to standardize some state election laws and standards. But should states be required to share this info beyond what is publicly available? Derek Monson, Chief Growth Officer for Sutherland Institute joins the show to discuss.     How teen resources centers are removing barriers for students  As kids are getting ready to go back to school, some struggle to get even basic necessities. That's where teen centers come in. Greg and Holly speak with Jodi Lunt, Director of the Davis Education Foundation about the teen resources centers in the Davis School District.     Utah women arrested, accused of stalking Post Malone  Stalking can be annoying, disruptive, and downright scary - and that's not any different if you're a celebrity.. A Utah woman has been arrested after being accused of stalking Post Malone. Greg and Holly discuss the situation and analyze what can be done if someone is being stalked.     Spooky season in August  We've talked about Christmas in July, but can we talk about spooky season in August? Holly's been re-watching the first season of "Wednesday," as in Wednesday Adams, in preparation for Season #2 that comes out this week. And at least one fast-food restaurant is getting in on the action as we get closer to the premiere and spooky season. Greg and Holly discuss the details and how some retailers are already bringing in spooky season to stores! Holly shares her facts of the day.  

In a world awash with free educational videos and paid programs from platforms such as Udemy and Teachable, Damon Lembi and his team at Learnit are thriving by delivering impressive results. Their secret? Equipping small and mid-sized businesses with the tools to outmaneuver corporate giants, while helping employees build confidence, sharpen skills, and boost job satisfaction. To date, Learnit has served over 14,000 organizations and helped more than 1.8 million professionals master new skills or improve on existing capabilities. This week, Damon delivers a masterclass on the mindset business leaders must embrace to thrive in today's hyper-competitive landscape. It's one of many valuable and actionable business insights we'll hear from Damon. Please take your seats. Class is in session.  [Be sure to pick up a copy of Damon's book, The Learn-It-All Leader: Mindset, Traits and Tools] Monday Morning Radio is hosted by the father-son duo of Dean and Maxwell Rotbart. Photo: Damon Lembi, LearnitPosted: August 4, 2025 Monday Morning Run Time: 48:25 Episode: 14.9 RELATED EPISODES: Teaching a Person to Fish is Okay; Training Others to Teach Fishing is Sublime Can You Prove the Worth of Employee Training, Community Outreach, DEI, and Other So-Called “Soft Skills”? Trainual CEO Chris Ronzio on Bringing Onboarding and Employee Training into the 21st Century

In this episode of the Celebrate Kids podcast, Dr. Kathy delves into the impact of smartphone use on children's mental health, particularly those under the age of 13. Citing a significant study published in the Journal for Human Development and Capabilities, she discusses how early smartphone exposure is linked to suicidal thoughts, emotional regulation issues, and lower self-worth, especially in girls. The study, which analyzed data from nearly 2 million individuals across 163 countries, highlights the detrimental effects of social media, sleep disruptions, cyberbullying, and strained family relationships associated with early smartphone use. Dr. Kathy emphasizes the importance of observing children's behaviors and interests to guide their development, advocating for mindful engagement and opportunities for discovery away from screens.

Send us a textCustomer service in eCommerce comes with unique complexities, especially when managing thousands of product-related inquiries that can make or break a sale. Given the typically lower price points, even premium brands face a dilemma: hiring seasoned agents can be cost-prohibitive, yet relying on less experienced staff may jeopardize customer satisfaction. This is where seamless integration with eCommerce platforms becomes vital—ensuring agents have the right context and tools to respond effectively. Unfortunately, many customer service solutions built for other industries lack this deep integration, leaving eCommerce teams to navigate disjointed systems and compromised service quality.In today's episode, we invited a panel of industry experts for a live discussion on LinkedIn to conduct an independent review of Georgias' capabilities. We covered many grounds including where Georgias might be a fit in the enterprise architecture and where it might be overused. Finally, they analyze many data points to help understand the core strengths and weaknesses of Georgias.Background Soundtrack: Away From You – Mauro SommFor more information on growth strategies for SMBs using ERP and digital transformation, visit our community at wbs.rocks or elevatiq.com. To ensure that you never miss an episode of the WBS podcast, subscribe on your favorite podcasting platform.

- Donation Update and Product Distribution for Texas Flood Victims (0:11) - Impact of Donations and Personal Anecdotes (4:43) - Introduction to Enoch AI and Its Upgrades (14:06) - Enoch's Training Data and Capabilities (28:47) - Alan Dershowitz and the Epstein Files (36:14) - Lee Zeldin and Geoengineering Transparency (38:49) - Doc Pete Chambers and COVID-19 Sabotage (45:27) - Personal Stories and Life Lessons (50:55) - Special Report: Don't Park Yourself on the Train Crossing of Life (57:35) - Final Thoughts and Call to Action (1:16:18) - Diesel Tank Preparedness and Health Insights (1:19:08) - Introduction to Brighton.com and Enoch AI (1:29:03) - Decentralized TV Episode Introduction (1:31:36) - Interview with Alex Collier on Extraterrestrial Experiences (1:34:46) - Discussion on Humanity's Evolution and Consciousness (1:43:37) - Exploration of Ancient Civilizations and Technologies (1:58:13) - Practical Decentralization Strategies (2:01:45) - Conclusion and Call to Action (2:02:02) - US Empire's Decline and Asset Protection (2:03:02) - Decentralized Community and Financial Freedom (2:03:24) - Philosophical Reflections and Show Appreciation (2:03:46) - Promotion of Decentralized TV and New Song (2:52:15) - Faraday Bags and Emergency Preparedness (2:55:56) For more updates, visit: http://www.brighteon.com/channel/hrreport NaturalNews videos would not be possible without you, as always we remain passionately dedicated to our mission of educating people all over the world on the subject of natural healing remedies and personal liberty (food freedom, medical freedom, the freedom of speech, etc.). Together, we're helping create a better world, with more honest food labeling, reduced chemical contamination, the avoidance of toxic heavy metals and vastly increased scientific transparency. ▶️ Every dollar you spend at the Health Ranger Store goes toward helping us achieve important science and content goals for humanity: https://www.healthrangerstore.com/ ▶️ Sign Up For Our Newsletter: https://www.naturalnews.com/Readerregistration.html ▶️ Brighteon: https://www.brighteon.com/channels/hrreport ▶️ Join Our Social Network: https://brighteon.social/@HealthRanger ▶️ Check In Stock Products at: https://PrepWithMike.com