Podcasts about Safari

We get into our Mens Room Question: What was better or worse when you finally gave it a try?

Today, the Safari heads down to Tampa for the 2025 AZA Conference. You'll hear from people with all levels of experience and their thoughts on what they experienced this year, including me and our good buddy Dan Ashe, President and CEO of the AZA! ROSSIFARI LINKS: rossifari.com @rossifari on socials @rossifaripod on TikTok Patreon.com/rossifari to support the pod

Show DescriptionDave and Chris discuss the release of Safari in iOS26, the aesthetics of Liquid Glass in CSS, the importance of material design, and the role of TypeScript in modern web development. The conversation also touches on when to consider rebuilding a tech stack, the significance of user experience, and how to know when to choose a new tech stack. Listen on WebsiteLinks Apple has a private CSS property to add Liquid Glass effects to web content Syntax - Web Development Podcast Theo - t3․gg - YouTube Gina Trapani Foursight Omakub — An Omakase Developer Setup for Ubuntu 24.04+ by DHH

Patreon ⁠⁠⁠⁠⁠⁠⁠⁠https://www.patreon.com/LadsAnonPod⁠⁠⁠⁠⁠⁠⁠⁠⁠ 

Familienreise durch Südafrika mit Kindern: Gemeinsam mit Djoser Family starten wir in Johannesburg, besuchen den beeindruckenden Blyde River Canyon und erleben aufregende Safaris im Kruger Nationalpark. Auf der Suche nach den Big Five berichten wir von einzigartigen Tierbeobachtungen, spannenden Abenteuern und unseren Erfahrungen mit einer Familien-Gruppenreise durch Südafrika.

V Safari Parku Dvůr Králové vyrůstá podivuhodné mládě bércouna Petersova. Zatím nemá jméno, ale jeho rodiči jsou Rabija a Herkules. Ve světových zoologických zahradách byste napočítali necelou stovku těchto vzdálených bratranců slonů nebo damanů. Z toho je zřejmé, že se jedná o vzácný přírůstek, který najdete v jednom z domků městečka Tiébélé.

V Safari Parku Dvůr Králové vyrůstá podivuhodné mládě bércouna Petersova. Zatím nemá jméno, ale jeho rodiči jsou Rabija a Herkules. Ve světových zoologických zahradách byste napočítali necelou stovku těchto vzdálených bratranců slonů nebo damanů. Z toho je zřejmé, že se jedná o vzácný přírůstek, který najdete v jednom z domků městečka Tiébélé.Všechny díly podcastu Safari můžete pohodlně poslouchat v mobilní aplikaci mujRozhlas pro Android a iOS nebo na webu mujRozhlas.cz.

⚡️ Spezial-Folge | Diesmal nehmen wir euch mit auf eine Reise zu ganz besonderen Oktoberfest-Alternativen rund um den Globus. Wir schauen, wo auf der Welt Maßkrüge geschwungen, Dirndl getragen und Blasmusik gespielt wird und das oft mit einer ganz eigenen lokalen Note. Natürlich gibt's auch unsere besten Tipps, wie ihr eine solche Reise mit besonderen Erlebnissen verbinden könnt vom Strand über die Skyline bis zur Safari.Über "Welttournee - Der Reisepodcast"Zwei Jugendfreunde. 30 Urlaubstage. Über 120 Länder. Adrian Klie und Christoph Streicher entdecken die Welt. Nicht als Aussteiger, sondern neben dem Bürojob. Unterhaltsam, ehrlich, mehrfach ausgezeichnet.Alle Links auf einen Blick

Hablemos de la visita del primer ministro de Canadá a México, también de la Bolsa Mexicana que ya es la de mejor desempeño en toda América Latina, Natura vende a su dolor de cabeza, con la pena, mientras que la que fuera la gran acerera de México prepara la venta de sus activos en medio de la quiebra. Además, les gustaría pedir un Uber Safari?[Patrocinado] Conoce más sobre el futuro de los pagos digitales, junto a los expertos de Mastercard que están trazando el camino de la transformación: https://www.bloomberglinea.com/brandedcontent/mexico-y-la-nueva-era-de-los-pagos-digitales-video/

Support The Becket Cook Show on Patreon! NOTE: When you sign up for Patreon, PLEASE do it through a web browser (Safari, Chrome, etc.) and NOT an app on your iPhone. The Apple app charges 30% !!! If you just click on the link above, it should be fine. In today's episode, Rev. Dr. Harold Ristau—parish pastor, former military chaplain, missionary, and seminary professor, now at Luther Classical College—joins Becket Cook to unpack his new book, "Spiritual Warfare and Deliverance: How to Minister to the Demonically Oppressed and Possessed." They tackle why modern skepticism about demons persists, how rationalism distorts a biblical worldview, and why deliverance belongs to the pastoral office. Dr. Ristau explains the difference between oppression and possession, the role of Scripture, fasting, and humility, and why deliverance is more “art + science” than a mechanical formula. You’ll hear practical counsel for house cleansing, using sacred Scripture aloud, and building a post-deliverance life (church, Word, prayer). Dr. Ristau walks through the “RAT principle” (trap, kill, remove the crumbs), cautions against turning psychology into a catch-all, and even weighs in on the “aliens” question through a spiritual lens. If you’re looking for sober theology with concrete tools for real spiritual battles, this conversation is both bracing and deeply pastoral. The Becket Cook Show Ep. 213 Discover more Christian podcasts at lifeaudio.com and inquire about advertising opportunities at lifeaudio.com/contact-us.

Caroline Fleming har fejret sin 50 års fødselsdag. Temaet var safari og cremen af det danske jetset var samlet. Inklusive dronning Mary. Din vært er Ditte Okman og i panelet sidder Nikolaj Vraa, Jakob Steen Olsen og Anne Kirstine Cramon. Programmet er produceret af Sarah Bech. Hvis du vil høre hele udsendelsen, skal du ind på Podimo. Og hvis du endnu ikke er kommet over på Podimo, kan du lige nå få 1 måned for kun 9 kr.: Podimo.dk/dvto See Privacy Policy at https://art19.com/privacy and California Privacy Notice at https://art19.com/privacy#do-not-sell-my-info.

pWotD Episode 3060: Google Chrome Welcome to popular Wiki of the Day, spotlighting Wikipedia's most visited pages, giving you a peek into what the world is curious about today.With 394,834 views on Wednesday, 17 September 2025 our article of the day is Google Chrome.Google Chrome is a web browser developed by Google. It was first released in 2008 for Microsoft Windows, built with free software components from Apple WebKit and Mozilla Firefox. Versions were later released for Linux, macOS, iOS, iPadOS, and also for Android, where it is the default browser. The browser is also the main component of ChromeOS, where it serves as the platform for web applications.Most of Chrome's source code comes from Google's free and open-source software project Chromium, but Chrome is licensed as proprietary freeware. WebKit was the original rendering engine, but Google eventually forked it to create the Blink engine; all Chrome variants except iOS used Blink as of 2017.As of April 2024, StatCounter estimates that Chrome has a 65% worldwide browser market share (after peaking at 72.38% in November 2018) on personal computers (PC), is most used on tablets (having surpassed Safari), and is also dominant on smartphones. With a market share of 65% across all platforms combined, Chrome is the most used web browser in the world today.Google chief executive Eric Schmidt was previously involved in the "browser wars", a part of U. S. corporate history, and opposed the expansion of the company into such a new area. However, Google co-founders Sergey Brin and Larry Page spearheaded a software demonstration that pushed Schmidt into making Chrome a core business priority, which resulted in commercial success. Because of the proliferation of Chrome, Google has expanded the "Chrome" brand name to other products. These include not just ChromeOS but also Chromecast, Chromebook, Chromebit, Chromebox, and Chromebase.This recording reflects the Wikipedia text as of 07:31 UTC on Thursday, 18 September 2025.For the full current version of the article, see Google Chrome on Wikipedia.This podcast uses content from Wikipedia under the Creative Commons Attribution-ShareAlike License.Visit our archives at wikioftheday.com and subscribe to stay updated on new episodes.Follow us on Mastodon at @wikioftheday@masto.ai.Also check out Curmudgeon's Corner, a current events podcast.Until next time, I'm neural Matthew.

Today we're celebrating our 5th birthday — five years, 260 episodes, countless destinations, and some of the most inspiring voices in travel. When I started this show back in 2020, I never could have imagined the incredible community that would form around it, or how many of you would join me each week to dream, to learn, and to reflect on the meaning of travel. So to mark this milestone, I wanted to do something a little different. Instead of a hotelier, a guide, or a travel CEO, I invited three of our most dedicated listeners — Max, Torey, and Nikhil — to join me. Each of them brings their own stories: from safari sunsets and personalized luxury touches, to family adventures and how travel has shaped their careers and worldviews. In today's episode, we'll swap favorite destinations, share insider hotel moments, reflect on lessons travel has taught us about life, and even dive into some Luxury Travel Insider trivia.  Above all, this episode is a celebration of you — the listeners — and of the idea that travel, when done with intention, connects us more deeply to ourselves, to each other, and to humanity. So grab a glass of champagne, settle in, and let's celebrate five incredible years of Luxury Travel Insider.   Looking to book a luxury hotel? Get special perks and support the podcast by booking here: https://www.virtuoso.com/advisor/sarahgroen/travel/luxury-hotels If you want our expert guidance and help planning a luxury trip with experiences you can't find online, tell us more here and we'll reach out: https://bellandblytravel.com/book-a-trip/ Learn more at www.luxtravelinsider.com   Connect with me on Social: Instagram LinkedIn  

Na lang getouwtrek is China het zat. De toezichthouder daar vertrouwt de Amerikaanse technologie van Nvidia echt niet meer, dus geeft alle Chinese bedrijven nu de opdracht om te stoppen met het kopen van hun AI-chips. Alle geplande bestellingen worden geschrapt, en alles dat nog niet geleverd is wordt geannuleerd. Is China dan echt ver genoeg om zonder Amerikaanse chips verder te durven? Of is het gewoon spierballenvertoon? Dat zoeken we deze aflevering uit. Dan hebben we het ook over een ander breekijzer tussen China en de VS. Stukje bij beetje komen we meer te weten over de aanstaande deal rond TikTok. Moederbedrijf ByteDance moet de Amerikaanse activiteiten gaan afstaan, anders gaat de app in de VS op zwart. En er staat een verzameling aan bedrijven klaar om die tak over te nemen. Verder hoor je over ExxonMobil. Dat ziet met een soepeler wordende beurswaakhond z'n kans schoon om activistische aandeelhouders buiten spel te zetten. Je komt ook te weten welk bedrijf eigenlijk eraan dacht om in Amsterdam naar de beurs te komen, maar dat nu opeens een andere bestemming heeft gevonden. En we vertellen je over de nieuwste markt die Uber aanboort. Na taxi's en maaltijdbezorging, zoeken ze het nu in exotischere oorden.See omnystudio.com/listener for privacy information.

Today, the Safari heads to Syracuse, NY, to sit down with Seth and Theo to talk all things red wolves and elephants.  We've got wolf pups, twin baby elephants, conservation stories galore, and so much more! EPISODE LINKS: @syracusezoo on socials rosamondgiffordzoo.org ROSSIFARI LINKS: rossifari.com Patreon.com/rossifari to support the pod @rossifari on the socials @rossifaripod on TikTok 

In this podcast, Thomas Domville walks through Safari's new Tabs layout options in iOS 26, explains the default Compact view, and shows how to switch between Compact, Bottom, and Top tab layouts. The demo is VoiceOver-centric, with practical navigation tips (rotor use, headings, and screen-edge gestures) to make changing this setting quick and repeatable.SummaryWhat changed: Safari now defaults to a Compact UI along the bottom: a single row with More, Tabs, the Address Bar, and a Page Menu. Traditional back/forward controls aren't where long-time users expect.Why it matters: If Compact disrupts your muscle memory (or your VoiceOver workflow), iOS 26 lets you pick an alternate layout—Bottom (classic iOS) or Top (very old Safari style).Key Points & TakeawaysThree layouts available: Compact (default), Bottom (classic), Top (legacy-style).Settings location: You change this in Settings → Apps → Safari → Tabs.VoiceOver navigation pattern: Use headings to jump quickly through long Settings screens; the Apps button sits just left of the Search field at the bottom of Settings.Customization is back: Apple now lets you choose the tab bar placement instead of enforcing a single layout.Step-by-Step GuideFast PathOpen Settings.Go to Apps → Safari.Find the Tabs section.Choose one: Compact, Bottom, or Top.Detailed Instructions with VoiceOverOpen Settings.Four-finger single tap near the bottom to reach the footer controls.Navigate to Apps.You'll encounter the Search field and a Dictate button; Apps is just to the left of Search. Double-tap Apps.Jump by Headings to the letter sections and flick to S; move right to Safari and double-tap.In Safari settings, use Headings to reach Tabs.Swipe right to the layout choices and double-tap your preference:Compact (default)Bottom (classic bottom bar)Top (tab controls at the top) VoiceOver will announce Selected: —you're done.TranscriptDisclaimer: This transcript was generated by AI Note Taker – VoicePen, an AI-powered transcription app. It is not edited or formatted, and it may not accurately capture the speakers' names, voices, or content.Thomas: Hello and welcome. My name is Thomas Domville, also known as AnonyMouse. I have a great battery…

As A&R at Safari Pedals, Abi brings a unique guitar pedal-driven approach to production. From making coffee disappear(she's a professional magician!) to helping artists transform gut feelings into honest, soulful records, she shares her philosophy on trust, vibe, and the magic that happens when you strip away pretense. Whether working remotely or popping up in cities around the world for in-person sessions, Abi is out there building genuine connections and crafting records with the artist at the center of the frame. Plus, we dive into her work hosting The Safari Pedals Show and how guitar pedals became her secret weapon in the studio.For 30% off your first year of DistroKid to share your music with the world click ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠DistroKid.com/vip/lovemusicmore⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠Subscribe to this pod's blog on ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠Substack⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠ to receive deeper dives on the regular

Planning a first safari, or your next one? Wade sits down with Jaco (NUMZAAN Safaris) to lay out a clear, candid guide to South African hunting: safety realities, choosing a reputable outfitter, full-trip budgeting (flights, day fees, trophy fees, shipping), predator calling by day and night, rifle/bullet setups, bringing or renting guns, and how hunting revenue supports entire local communities. Plus: dangerous game honesty (buffalo, leopard, elephant) and a surprising list of best-tasting game.Note: Contains explicit language.Numzaan Safarishttps://www.numzaan.com/https://www.instagram.com/numzaan_safaris01/

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

Frauke kommt aus dem Wanderurlaub in Schweden zurück. Sie hat dort Hitze und Regen getrotzt und vor allem die schöne Natur bewundert. Darum erfüllen wir in dieser Folge einen Hostinnen-Wunsch und feiern die Tiere des Nordens. Und wo wir schon, Stichwort Wandern, bei Freizeitaktivitäten sind: Tauchen ist bei Elchen der Lieblingsfreizeitsport. Rentiere sind die Christine Thürmers unter den nordischen Tieren und fernwandern übers Jahr „ein bisschen“ weiter als Frauke in ihren zwei Wochen Urlaub. Die Jagd vom Vielfraß entspricht einer blutrünstigen Schneeschuhwanderung. Die Schneeeule gewinnt im Weitflug und brüstet sich darüber hinaus mit drei gleichen Vokalen hintereinander im Namen. Und der Lemming… ja also was der so unter der Schneedecke in seinen Nestern treibt, mag als Freizeitaktivität durchgehen, eine olympische Disziplin ist es (noch) nicht. So viel darf verraten werden.Aber hört selbst. Auf geht's zu unserer verschneiten Safari durch Fjäll und Tundra!Und hier noch unser Podcast Tipp für euch:„WirTier“, ist der neue Mensch-Tier-Podcast des Bayerischen Rundfunks: Würdet ihr euer ganzes Leben verändern nach einer Begegnung mit einem Tier? Für den Podcast „WirTier“ haben die Hosts Victoria Marciniak und Julius Bretzel Menschen getroffen, die genau das gemacht haben. Was sie in diesem Moment auf Augenhöhe mit einem Tier begriffen haben und wie das unser Zusammenleben auf diesem Planeten verändern kann, erzählen sie in „WirTier“, dem neuen Mensch-Tier-Podcast des Bayerischen Rundfunks.Und hier geht's zu unserem Podcast-Tipp „WirTier“: https://1.ard.de/wir-tier Weiterführende Links:Karuperlv Valley Project: https://www.karupelv-valley-project.de/deutsch/das-projekt/Anpassung Polarfuchs an Klima Wandel: https://cjes.guilan.ac.ir/article_8218_067ecf55451e8fd9f0f689f4d79af25c.pdfSchneeeule: https://www.cambridge.org/core/journals/bird-conservation-international/article/status-assessment-and-conservation-priorities-for-a-circumpolar-raptor-the-snowy-owl-bubo-scandiacus/8F3760C7DFF40ACE97989236F7CA03F9Eisbären jagen Rentiere: https://link.springer.com/article/10.1007/s00300-021-02954-wVielfraßforschung: https://wildlife.org/worldwide-wolverine-analysis-reveals-research-gaps/Elchinfos: https://www.wwf.de/themen-projekte/bedrohte-tier-und-pflanzenarten/elche Hosted on Acast. See acast.com/privacy for more information.

Segment 1 - Interview with Jeff Pollard Introducing Forrester's AEGIS Framework: Agentic AI Enterprise Guardrails For Information Security For this episode's interview, we're talking to Forrester analyst Jeff Pollard. I'm pulling this segment's description directly from the report's executive summary, which I think says it best: As AI agents and agentic AI are introduced to the enterprise, they present new challenges for CISOs. Traditional cybersecurity architectures were designed for organizations built around people. Agentic AI destroys that notion. In the near future, organizations will build for goal-oriented, ephemeral, scalable, dynamic agents where unpredictable emergent behaviors are incentivized to accomplish objectives. This change won't be as simple or as straightforward as mobile and cloud — and that's bad news for security leaders who in some cases still find themselves challenged by cloud security. Segment 2 - Weekly News Then, in the enterprise security news, there's funding and acquisitions, but we're not going to talk about them AI's gonna call the cops on you and everyone's losing money on it and Anthropic agreed to pay for all the copyright infringement they did when training models and Otter.ai got sued for recording millions of conversations without consent Burger King got embarrassed and their lawyers didn't like it NPM package mayhem certificate authority hijinks AI darwin awards All that and more, on this episode of Enterprise Security Weekly. Segment 3 - Executive Interviews from Black Hat 2025 Interview with Rohit Dhamankar from Fortra Live from Black Hat 2025 in Las Vegas, Matt Alderman sits down with Rohit Dhamankar, VP of Product Strategy at Fortra, to dive deep into the evolving world of offensive security. From red teaming and pen testing to the rise of AI-powered threat simulation and continuous penetration testing, this conversation is a must-watch for CISOs, security architects, and compliance pros navigating today's dynamic threat landscape. Learn why regulatory bodies worldwide are now embedding offensive security requirements into frameworks like PCI DSS 4.0, and how organizations can adopt scalable strategies—even with limited red team resources. Rohit breaks down the nuances of purple teaming, AI-assisted red teaming, and the role of BAS platforms in enhancing defense postures. Whether you're building in-house capabilities or leveraging external partners, this interview reveals key insights on security maturity, strategic outsourcing, and the future of cyber offense and defense convergence. This segment is sponsored by Fortra. Visit https://securityweekly.com/fortrabh to learn more! Interview with Michael Leland from Island At BlackHat 2025 in Las Vegas, Matt Alderman sits down with Michael Leland, VP Field CTO at Island, to tackle one of cybersecurity's most urgent realities: compromised credentials aren't a possibility — they're a guarantee. From deepfakes to phishing and malicious browser plug-ins, attackers aren't “breaking in” anymore… they're logging in. Michael reveals how organizations can protect stolen credentials from being used, why the browser is now the second weakest link in enterprise security, and how Island's enterprise browser can enforce multi-factor authentication at critical moments, block unsanctioned logins in real time, and control risky extensions with live risk scoring of 230,000+ Chrome plug-ins. Key takeaways: Why credential compromise is inevitable — and how to stop credential use How presentation layer DLP prevents data leaks inside and outside apps Real-time blocking of phishing logins and unsanctioned SaaS access Plug-in risk scoring, version pinning, and selective extension control Enabling BYOD securely — even after a catastrophic laptop loss Why many users never go back to Chrome, Edge, or Safari after switching Segment Resources: https://www.island.io/blog/how-the-enterprise-browser-neutralizes-the-risks-of-compromised-credentials This segment is sponsored by Island. Visit https://securityweekly.com/islandbh to learn more! Visit https://www.securityweekly.com/esw for all the latest episodes! Show Notes: https://securityweekly.com/esw-424

Patreon ⁠⁠⁠⁠⁠⁠⁠https://www.patreon.com/LadsAnonPod⁠⁠⁠⁠⁠⁠⁠⁠ 

Segment 1 - Interview with Jeff Pollard Introducing Forrester's AEGIS Framework: Agentic AI Enterprise Guardrails For Information Security For this episode's interview, we're talking to Forrester analyst Jeff Pollard. I'm pulling this segment's description directly from the report's executive summary, which I think says it best: As AI agents and agentic AI are introduced to the enterprise, they present new challenges for CISOs. Traditional cybersecurity architectures were designed for organizations built around people. Agentic AI destroys that notion. In the near future, organizations will build for goal-oriented, ephemeral, scalable, dynamic agents where unpredictable emergent behaviors are incentivized to accomplish objectives. This change won't be as simple or as straightforward as mobile and cloud — and that's bad news for security leaders who in some cases still find themselves challenged by cloud security. Segment 2 - Weekly News Then, in the enterprise security news, there's funding and acquisitions, but we're not going to talk about them AI's gonna call the cops on you and everyone's losing money on it and Anthropic agreed to pay for all the copyright infringement they did when training models and Otter.ai got sued for recording millions of conversations without consent Burger King got embarrassed and their lawyers didn't like it NPM package mayhem certificate authority hijinks AI darwin awards All that and more, on this episode of Enterprise Security Weekly. Segment 3 - Executive Interviews from Black Hat 2025 Interview with Rohit Dhamankar from Fortra Live from Black Hat 2025 in Las Vegas, Matt Alderman sits down with Rohit Dhamankar, VP of Product Strategy at Fortra, to dive deep into the evolving world of offensive security. From red teaming and pen testing to the rise of AI-powered threat simulation and continuous penetration testing, this conversation is a must-watch for CISOs, security architects, and compliance pros navigating today's dynamic threat landscape. Learn why regulatory bodies worldwide are now embedding offensive security requirements into frameworks like PCI DSS 4.0, and how organizations can adopt scalable strategies—even with limited red team resources. Rohit breaks down the nuances of purple teaming, AI-assisted red teaming, and the role of BAS platforms in enhancing defense postures. Whether you're building in-house capabilities or leveraging external partners, this interview reveals key insights on security maturity, strategic outsourcing, and the future of cyber offense and defense convergence. This segment is sponsored by Fortra. Visit https://securityweekly.com/fortrabh to learn more! Interview with Michael Leland from Island At BlackHat 2025 in Las Vegas, Matt Alderman sits down with Michael Leland, VP Field CTO at Island, to tackle one of cybersecurity's most urgent realities: compromised credentials aren't a possibility — they're a guarantee. From deepfakes to phishing and malicious browser plug-ins, attackers aren't “breaking in” anymore… they're logging in. Michael reveals how organizations can protect stolen credentials from being used, why the browser is now the second weakest link in enterprise security, and how Island's enterprise browser can enforce multi-factor authentication at critical moments, block unsanctioned logins in real time, and control risky extensions with live risk scoring of 230,000+ Chrome plug-ins. Key takeaways: Why credential compromise is inevitable — and how to stop credential use How presentation layer DLP prevents data leaks inside and outside apps Real-time blocking of phishing logins and unsanctioned SaaS access Plug-in risk scoring, version pinning, and selective extension control Enabling BYOD securely — even after a catastrophic laptop loss Why many users never go back to Chrome, Edge, or Safari after switching Segment Resources: https://www.island.io/blog/how-the-enterprise-browser-neutralizes-the-risks-of-compromised-credentials This segment is sponsored by Island. Visit https://securityweekly.com/islandbh to learn more! Visit https://www.securityweekly.com/esw for all the latest episodes! Show Notes: https://securityweekly.com/esw-424

Fr. Seán ÓLaoire, born in Ireland, embarked on a journey of profound exploration and service. Armed with a B.Sc. degree in Mathematics from the National University of Ireland, he answered a higher calling, becoming ordained as a Catholic priest in 1972. His path led him to spend 14 transformative years in Kenya, where he immersed himself in diverse cultures and languages.Driven by a deep curiosity for the human spirit, Fr. ÓLaoire pursued advanced studies, earning an M.A. and Ph.D. in Transpersonal Psychology. Today, he channels his insights and expertise as a Licensed Clinical Psychologist in private practice, enriching the lives of those he encounters.A visionary and spiritual guide, Fr. ÓLaoire is the co-founder and Spiritual Director of "Companions on the Journey," a vibrant non-denominational community based in Palo Alto.Through this platform, he fosters unity, compassion, and growth among seekers from all walks of life.Fr. ÓLaoire's literary contributions resonate globally, transcending borders and languages. His thought-provoking works, including "Spirits in Spacesuits" and "Souls on Safari," delve into the depths of human existence, offering profound insights and perspectives. His latest endeavor, "Setting God Free: Moving Beyond the Caricature We've Created in Our Own Image," challenges conventional beliefs and invites readers to embark on a liberating journey of self-discovery and spiritual liberation.With each publication, Fr. ÓLaoire continues to inspire and empower individuals worldwide, bridging the gap between spirituality and psychology. His legacy is one of enlightenment, compassion, and a relentless pursuit of truth.Become a supporter of this podcast: https://www.spreaker.com/podcast/next-level-soul-podcast-with-alex-ferrari--4858435/support.

Segment 1 - Interview with Jeff Pollard Introducing Forrester's AEGIS Framework: Agentic AI Enterprise Guardrails For Information Security For this episode's interview, we're talking to Forrester analyst Jeff Pollard. I'm pulling this segment's description directly from the report's executive summary, which I think says it best: As AI agents and agentic AI are introduced to the enterprise, they present new challenges for CISOs. Traditional cybersecurity architectures were designed for organizations built around people. Agentic AI destroys that notion. In the near future, organizations will build for goal-oriented, ephemeral, scalable, dynamic agents where unpredictable emergent behaviors are incentivized to accomplish objectives. This change won't be as simple or as straightforward as mobile and cloud — and that's bad news for security leaders who in some cases still find themselves challenged by cloud security. Segment 2 - Weekly News Then, in the enterprise security news, there's funding and acquisitions, but we're not going to talk about them AI's gonna call the cops on you and everyone's losing money on it and Anthropic agreed to pay for all the copyright infringement they did when training models and Otter.ai got sued for recording millions of conversations without consent Burger King got embarrassed and their lawyers didn't like it NPM package mayhem certificate authority hijinks AI darwin awards All that and more, on this episode of Enterprise Security Weekly. Segment 3 - Executive Interviews from Black Hat 2025 Interview with Rohit Dhamankar from Fortra Live from Black Hat 2025 in Las Vegas, Matt Alderman sits down with Rohit Dhamankar, VP of Product Strategy at Fortra, to dive deep into the evolving world of offensive security. From red teaming and pen testing to the rise of AI-powered threat simulation and continuous penetration testing, this conversation is a must-watch for CISOs, security architects, and compliance pros navigating today's dynamic threat landscape. Learn why regulatory bodies worldwide are now embedding offensive security requirements into frameworks like PCI DSS 4.0, and how organizations can adopt scalable strategies—even with limited red team resources. Rohit breaks down the nuances of purple teaming, AI-assisted red teaming, and the role of BAS platforms in enhancing defense postures. Whether you're building in-house capabilities or leveraging external partners, this interview reveals key insights on security maturity, strategic outsourcing, and the future of cyber offense and defense convergence. This segment is sponsored by Fortra. Visit https://securityweekly.com/fortrabh to learn more! Interview with Michael Leland from Island At BlackHat 2025 in Las Vegas, Matt Alderman sits down with Michael Leland, VP Field CTO at Island, to tackle one of cybersecurity's most urgent realities: compromised credentials aren't a possibility — they're a guarantee. From deepfakes to phishing and malicious browser plug-ins, attackers aren't “breaking in” anymore… they're logging in. Michael reveals how organizations can protect stolen credentials from being used, why the browser is now the second weakest link in enterprise security, and how Island's enterprise browser can enforce multi-factor authentication at critical moments, block unsanctioned logins in real time, and control risky extensions with live risk scoring of 230,000+ Chrome plug-ins. Key takeaways: Why credential compromise is inevitable — and how to stop credential use How presentation layer DLP prevents data leaks inside and outside apps Real-time blocking of phishing logins and unsanctioned SaaS access Plug-in risk scoring, version pinning, and selective extension control Enabling BYOD securely — even after a catastrophic laptop loss Why many users never go back to Chrome, Edge, or Safari after switching Segment Resources: https://www.island.io/blog/how-the-enterprise-browser-neutralizes-the-risks-of-compromised-credentials This segment is sponsored by Island. Visit https://securityweekly.com/islandbh to learn more! Show Notes: https://securityweekly.com/esw-424

A veces comer en sí no es solo un gusto para el paladar, es una auténtica experiencia. Sobre todo si se trata de disfrutar en lo que son considerados auténticos restaurantes temáticos. En este “A Fuego Lento” hacemos un recorrido por los restaurantes temáticos más sorprendentes de Aragón. Desde la explosión de sabor mexicano en Huesca, hasta una selva, un safari o una cárcel al más puro Al Capone en Zaragoza. Y, por supuesto, una parada en el lejano oeste de Teruel. Un viaje gastronómico distinto, lleno de experiencias y mucho sabor.

Christian ; Follower of GOD Servant of CHRIST         Decorated Combat VeteranCorporate; U.S. Marine Corps Urban Warfare Instrictor;        S.R.T. Commander Active Shooter Response Team  Law Enforcement Los Angeles Police (L.A.P.D.) Police Officer / Fugitive Recovery F.B.I. Instructor N.R.A Instructor  Competition Shooter; Multi Time State Rifle Pistol Champion  Hunting; Life Long Hunter Proffessional Hunter and Guide  Private Security Contractor; Several Agencies,  Current.  GOD Provides / JESUS SavesBecome a supporter of this podcast: https://www.spreaker.com/podcast/gunfighter-life-survival-guns-tactical-hunting--4187306/support.Have a Blessed Day 

Hello and welcome to a brand-new season of Travel Stories with Moush! It's such a joy to kick off Season 5 and before anything else, I want to thank each and every one of you. Your support has helped this podcast grow, win accolades and climb the charts time and again. Please keep supporting and subscribing coz it's the only way we can keep bringing you these incredible stories from around the world.In this episode of the podcast, we set sail with Dani Wilson Naqvi - luxury family travel curator and award-winning travel designer, as she takes us across some of the world's most extraordinary places.Episode Highlights:• Raja Ampat, Indonesia - Dani shares her once-in-a-lifetime sailing adventure through this “Lost Paradise”.• Rwanda & Africa - A deeply moving experience trekking with gorillas in Rwanda and learning lessons of peace and resilience from its people.• Okavango Delta and Botswana – She recalls safaris in these places where her children's classrooms became the wild outdoors.• Bhutan - A destination she treasures for its philosophy of simplicity.• Sri Lanka - Why she believes this island is one of the world's most underrated gems.• Cape Town & South Africa – Great for remote living and a haven for foodies.• Norwegian fjords – Discovering Restaurant Iris – a hidden gem.              https://www.restaurantiris.no/• Lake Como – Luxury meets unforgettable experiences at Passalacqua.              https://www.passalacqua.it/en/• Costa Rica – Discover the Blue Zones.• Brazil -Journey across the Amazon.Connect with Dani at:https://www.instagram.com/daniwilsonnaqvi/Thank you all for tuning in today!If you enjoyed this episode, please hit that subscribe button here, or on your favorite podcast platform.I'd love to hear from you! What destinations or guests should we feature next? Drop a comment, leave a rating, or write a review - it truly makes a difference.Stay connected with me on Instagram @moushtravels to find out who's joining me next week. You can also explore all past episodes and destinations mentioned by our guests on www.moushtravels.com or in the episode show notes.Thanks for listening! Until next time, safe travels and keep adventuring. "Want a spotlight on our show? Visit https://admanager.fm/client/podcasts/moushtravels and align your brand with our audience."Connect with me on the following:Instagram @moushtravelsFacebook @travelstorieswithmoushLinkedIn @Moushumi BhuyanYou Tube @travelstorieswithmoush

Support The Becket Cook Show on Patreon! NOTE: When you sign up for Patreon, PLEASE do it through a web browser (Safari, Chrome, etc.) and NOT an app on your iPhone. The Apple app charges 30% !!! If you just click on the link above, it should be fine. In today's episode with Becket Cook, Matias Wilson shares a powerful story of transformation—from childhood wounds and confusion, to searching for love and identity in all the wrong places, and ultimately finding true peace in Christ. He opens up about abuse, insecurity, resentment, and years of pursuing fulfillment through same-sex relationships, only to encounter God’s relentless pursuit and grace. This testimony is raw, honest, and deeply hopeful. If you’ve wrestled with identity, shame, or longing for belonging, Matias’ story will remind you that God sees, loves, and redeems. The Becket Cook Show Ep. 212 Discover more Christian podcasts at lifeaudio.com and inquire about advertising opportunities at lifeaudio.com/contact-us.

Full disclosure - there is nothing short about this edition of the shortcast. Rusty is in the middle of nowhere (actually near Mildura) for the Sunraysia Safari. Just before competitors set off for 1200ks of cross country he caught up with Rob & Dean Herridge under Maximum Motorsport E-Z Up. What brings them back to this gruelling event and the ‘David n Goliath’ fight they wage in their Subaru’s including a new WRX. It’s a cool story of Father and Son rallying together in truly unique countryside on the edge of the desert. Then Tony Quinn joins us and we know how much you love a TQ catch-up. He’s come straight from Tailem Bend where his grandson Ryder turned heads with an epic drive in GT4. Tony talks about trying to win Sunraysia again in a Dakar spec V8 powered Navara. And he’s still keeping an eye on The Bend this weekend as his Triple 8 team tries to win the first of the Supercars enduros this season. Rally fans, Supercars supporters, GT enthusiasts. There’s something for all of you in the ep. Enjoy. Head to Rusty's Facebook, Twitter or Instagram and give us your feedback and let us know who you want to hear from on Rusty's Garage.See omnystudio.com/listener for privacy information.

Volvemos de vacaciones con una tertulia cargada: arrancamos ligeros y entramos a fondo en la “ilustración oscura”, el tecno-feudalismo y la visión de poder de Peter Thiel y el círculo neorreaccionario, y cómo ese imaginario se cuela en debates políticos de alto nivel.Comentamos la cena en la Casa Blanca con los grandes CEOs: el momento “gracias, gracias…” de Tim Cook, las risas de Zuckerberg y el festival de promesas de inversión, y lo que eso dice de la relación poder-tech hoy.Pasamos a “Little Tech vs Big Tech”: el supuesto manifiesto pro-pequeños, el proteccionismo “a lo chino” y cómo la consolidación está dejando hueco solo para unos pocos.Caso del día: Browser Company (Arc). ¿Tiene sentido que Atlassian se lleve un navegador por ~600M con casi cero revenue? Le damos contexto histórico y de negocio.Zoom al antitrust: qué dice realmente la sentencia sobre Google, nada de romper Chrome/Android, pero adiós a exclusividades de búsqueda (como con Safari), comité técnico y compartir ciertos datos con competidores y por qué llega justo cuando el paradigma del search se mueve hacia modelos tipo OpenAI con Microsoft.Cerramos con GPT-5: más preciso y con menos alucinaciones… a costa de latencias que en API se sienten duras frente a la experiencia en Chat. Qué significa esto para producto y para workflows reales.

Neste episódio falamos do veredito da Google nos EUA, dos despedimentos na Salesforce, Safari 26 e muito mais…

Today, the Safari heads out to Escondido, CA, to the world famous San Diego Zoo Safari Park. I sit down with Marco, one of the two ambassadors of the San Diego Zoo Wildlife Alliance. We talk about his unique path to his career, how a background in training led to an office job that usually keeps him out of the office, why birds are his first love, and so much more! EPISODE LINKS: @zoologymarco on socials @sandiegozoo on socials @sdzsafaripark on socials sandiegozoowildlifealliance.org ROSSIFARI LINKS: @rossifari on socials @rossifaripod on TikTok Rossifari.com patreon.com/rossifari to support the pod

Understanding podcast downloads and metrics, including what is the podcast market size? Insights from the Podcast Landscape 2025 report (part 1), claiming your podcast in Apple Podcasts when you don't have access to your original email, sharing your podcast in Spotify just got easier, and stats mean and median download numbers Audience feedback drives the show. We'd love for you to contact us and keep the conversation going! Email thefeed@libsyn.com, call 412-573-1934 or leave us a message on Speakpipe! We'd love to hear from you!

Understanding podcast downloads and metrics, including what is the podcast market size? Insights from the Podcast Landscape 2025 report (part 1), claiming your podcast in Apple Podcasts when you don't have access to your original email, sharing your podcast in Spotify just got easier, and stats mean and median download numbers Audience feedback drives the show. We'd love for you to contact us and keep the conversation going! Email thefeed@libsyn.com, call 412-573-1934 or leave us a message on Speakpipe! We'd love to hear from you!

Patreon ⁠⁠⁠⁠⁠⁠https://www.patreon.com/LadsAnonPod⁠⁠⁠⁠⁠⁠⁠ 

Richard Stevens, CEO of Zyft, has spent his first six months steering the AI-powered shopping assistant through a period of explosive growth. With over 650,000 downloads, 100,000+ daily searches, and $7.5 million in fresh funding, Zyft is reshaping how Australians shop, and how retailers compete.Today, we're discussing:Zyft's origins and growth: from Damien Waller's vision in 2019 to 650,000 downloads and $7.5M raised in 2025.How the app works: Chrome and Safari extensions, mobile apps, barcode scanning, and live retailer feeds.The consumer mindset: why cost-of-living pressures have made shoppers more price-conscious and open to AI tools.Retailer opportunities: using Zyft's data and transparency to boost discoverability, credibility, and conversion.The future of shopping: what AI-powered price comparison means for retailers heading into Black Friday, Cyber Monday, and beyond.Connect with Richard StevensExplore ZyftSMS us to request a guest!Support the showWant to level up your ecommerce game? Come hang out in the Add To Cart Community. We're talking deep dives, smart events, and real-world inspo for operators who are in it for the long haul. Connect with Nathan BushContact Add To CartJoin the Community

Summary In this episode, Tony and Don discuss Don's recent month-long travel adventure that included a safari in Africa, a cruise on the Sun Princess, and a river cruise in Europe. They explore the unique experiences of each trip, including wildlife encounters, culinary highlights, and the differences between ocean and river cruising. Don shares his insights on the costs, the people he met, and the unforgettable moments that made this journey special.    

Animal Kingdom in one day with kids. Exact plan with rope drop strategy, Lightning Lane Multipass picks, must see shows, best character meets, can't miss food, hidden trails, and how to handle evenings. It's not just a zoo and not just a place for thrill rides. We show how to balance Flight of Passage or Kilimanjaro Safari at rope drop with a chill, animal forward day that still hits the headliners. 01:00 Skip park or half day debate with kids 02:30 Rope drop philosophy with Multipass basics and pricing 03:30 Flight of Passage vs Safari at rope drop, how to pair with Multipass 05:30 First three Multipass picks that work all day 07:30 Characters you should prioritize and where to find them 09:00 Trails, photo spots, and “side quests” around Tree of Life 11:00 3 2 1 family plan: 3 rides, 2 characters or shows, 1 meal 13:00 Use Tusker House to meet Mickey and friends fast 15:00 Quick eats that hit, what to skip for food 18:00 Kali River Rapids: when to ride and when to skip 20:00 Park hours, Pandora at night, and evening hop strategy 22:00 Half day vs full day and cutting table service if time is tight   Plan your next trip with me (free): https://www.adventuresofadisneydad.com/get-a-quote

The latest In Touch With iOS. In Episode 385, Dave Ginsburg, Kelly Guimont, Jill McKinley, Ben Roethig, and Marty Jencius preview the September 9th Apple Event. They cover iOS 26 Beta 9 and visionOS updates, iPhone 17 rumors, Apple Watch Series 11 upgrades, and Apple Wallet's enhanced travel features. The panel also dives into AirPods Pro 3, HomePod, Apple TV speculation, Astropad's anti-reflective protector, and Apple's evolving AI strategy. A lively mix of insight, rumors, and humor for Apple fans. The show notes are at InTouchwithiOS.com  Direct Link to Audio  Links to our Show Give us a review on Apple Podcasts! CLICK HERE we would really appreciate it! Click this link Buy me a Coffee to support the show we would really appreciate it. intouchwithios.com/coffee  Another way to support the show is to become a Patreon member patreon.com/intouchwithios Website: In Touch With iOS YouTube Channel In Touch with iOS Magazine on Flipboard Facebook Page BlueSky Mastodon X Instagram Threads Summary In Episode 385 of In Touch With iOS, host Dave Ginsburg is joined by panelists Kelly Guimont, Jill McKinley, Ben Roethig, and Marty Jencius for an in-depth discussion on everything Apple ahead of the much-anticipated September 9th Apple Event. The panel kicks off with reactions to the iOS 26 Beta 9 and visionOS Beta 9 releases, highlighting improvements like 3D charting support for developers, enhanced accessibility ratings in the App Store, and visual refinements such as the updated liquid glass interface. While some bugs remain, overall performance feels crisper and more polished. Looking ahead to the event, the conversation centers on the iPhone 17 lineup — including rumors of a lighter iPhone 17 Air, spatial photography integration for Vision Pro, and whether the upgrades justify an annual refresh. Opinions are divided: some are eager to upgrade, while others remain skeptical about how compelling the changes will be. The panel also dives into expected updates for the Apple Watch Series 11 and Apple Watch Ultra 3, including a possible return of blood oxygen monitoring and other health features. Other Apple ecosystem topics include: Apple Wallet enhancements — digital boarding passes with live activities, airport maps, luggage tracking, and U.S. passport support. AirPods Pro 3 rumors — improved noise cancellation, redesigned stems, and heart rate monitoring integration. HomePod and AirTag updates — hopes for better battery life and a more seamless user experience. Apple TV speculation — possible Wi-Fi 7 support and potential gaming opportunities. In a lighter segment, the group discusses Astropad's new anti-reflective “Fresh Coat” screen protector, designed to reduce glare by 75% on the upcoming iPhone 17 Pro models. They also dive into Opera's revamped tab management on iOS, debating its potential to rival Safari and Chrome. Finally, the episode touches on Apple's AI ambitions, exploring reports of a planned answer engine integrated with Siri, leveraging deals with OpenAI, Perplexity, or even Google Gemini. While Apple's AI strategy sparks mixed opinions, the panel agrees that user privacy and energy efficiency will likely remain top priorities. This episode serves as the perfect primer before Apple's big event, balancing news, rumors, personal insights, and witty banter to prepare listeners for what's next in the Apple ecosystem. Topics and Links In Touch With Vision Pro this week.  visionOS 26 Beta 9 Release Notes | Apple Developer Documentation Beta this week. iOS26 Beta 9 was released this week.  Apple releases iOS 26 beta 9 for iPhone Apple releases beta 9 for iPadOS 26, tvOS 26, watchOS 26, more [U] iOS 26: Import and Export Markdown Files in Apple Notes Apple Wallet has three new features for boarding passes in iOS 26 - 9to5Mac In Touch With Mac this week macOS Tahoe 26 beta 9 now available Predictions for the Apple Event September 9th Beyond iPhone 17: Apple Rumored to Launch 10 Other Products in 2025 - MacRumors AirPods Pro 3 coming next week: Here's every rumored feature - 9to5Mac Five new Apple products are the biggest September 9 launch ‘maybes' - 9to5Mac iPhone 17 event promises to go beyond the usual yearly updates for each product - 9to5Mac AirPods Max get an elegant solution to their biggest design flaw - 9to5Mac - Marty's AirPodMax charger Other Topics Astropad's 'Fresh Coat' Screen Protector Cuts iPhone Reflections by 75% Without Color Loss/ Apple Patents Next-Generation Taptic Engine Apple's Shock-Resistant Haptic Engine Patent Signals Durability Leap for Future Devices Apple Plans AI-Powered Web Search Tool for Siri to Rival OpenAI, Perplexity   News New Opera Browser Features Aim to End Safari Tab Management Woes - MacRumors Ecobee's Smart Security System Now Works With Home App and Siri  flair.co Specific page for the vents: Smart Home HVAC Solutions for Central Heating and Cooling – Flair Flair + ecobee: Smart HVAC Control Made Simple Instagram Finally Comes to iPad Netflix Moments Feature Gets Major Update for Scene Sharing on iOS Announcements Macstock 9 has wrapped for 2025. Attendees will receive a link for the session recordings when  they're ready in 30-45 days. If you missed Macstock we missed you! Why not purchase a digital pass to relive all the amazing presentations? Click the link below to purchase the digital pass. Macstock X has already been announced July 10,11,12, 2026 hopeful you all can join us.  Macstock IX Digital Pass Our Host Dave Ginsburg is an IT professional supporting Mac, iOS and Windows users and shares his wealth of knowledge of iPhone, iPad, Apple Watch, Apple TV and related technologies. Visit the YouTube channel https://youtube.com/intouchwithios follow him on Mastodon @daveg65, , BlueSky @daveg65  and the show @intouchwithios   Our Regular Contributors Jeff Gamet is a podcaster, technology blogger, artist, and author. Previously, he was The Mac Observer's managing editor, and Smile's TextExpander Evangelist. You can find him on Mastadon @jgamet Pixelfed @jgamet@pixelfed.social and Bluesky @jgamet.bsky.social‬ Podcasts The Context Machine Podcast  Retro Rewatch Retro Rewatch His YouTube channel https://youtube.com/jgamet Marty Jencius, Ph.D., is a professor of counselor education at Kent State University, where he researches, writes, and trains about using technology in teaching and mental health practice. His podcasts include Vision Pro Files, The Tech Savvy Professor and Circular Firing Squad Podcast. Find him at jencius@mastodon.social  https://thepodtalk.net  Eric Bolden is into macOS, plants, sci-fi, food, and is a rural internet supporter. You can connect with him by email at eabolden@mac.com, on Mastodon at @eabolden@techhub.social, on his blog, Trending At Work, and as co-host on The Vision ProFiles podcast.   Jill McKinley works in enterprise software, server administration, and IT A lifelong tech enthusiast, she started her career with Windows but is now an avid Apple fan. Beyond technology, she shares her insights on nature, faith, and personal growth through her podcasts—Buzz Blossom & Squeak, Start with Small Steps, and The Bible in Small Steps. Watch her content on YouTube at @startwithsmallsteps and follow her on X @schmern. Chuck Joiner is the host of MacVoices and hosts video podcasts with influential members of the Apple community. Make sure to visit macvoices.com and subscribe to his podcast. You can follow him on Twitter @chuckjoiner and join his MacVoices Facebook group. Ben Roethig Former Associate Editor of GeekBeat.TV and host of the Tech Hangout and Deconstruct with Patrice  Mac user since the mid 90s. Tech support specialist. X @benroethig and all other social media @benroethig.   Website: https://roethigtech.com/

Send us a text!Watch this episode on YouTubeThis week: We have a price on the Vision Air, a Lego iMac G3 that needs your support, Tim Cook can sleep well at night again, a gorgeous dual Studio Display setup — and OUR PREDICTIONS for the ‘Awe Dropping' event! Place your own votes here.This episode supported by:Listeners like you. Your support helps us fund CultCast Off-Topic, a new weekly podcast of bonus content available for everyone; and helps us secure the future of the podcast. You also get access to The CultClub Discord, where you can chat with us all week long, give us show topics, and even end up on the show. Support The CultCast at support.thecultcast.com — or unsubscribe at unfork.thecultcast.comCultCloth will keep your iPhone, MacBook, display, guitars, glasses and lenses sparkling clean! For a limited time use code CULTCAST at checkout to score a two free CarryCloths with any order $20+ at CultCloth.coInsta360 GO Ultra is the tiny, hands-free 53g camera that redefines how you capture your life. To bag a bag of free Sticky Tabs with your Insta360 GO Ultra purchase, head to store.insta360.com and use the promo code cultcast, available for the first 30 purchases only.This week's stories:Vision Air could cost half what Vision Pro doesApple is reportedly working on a Vision Air that will be half as expensive and almost half the weight of the Vision Pro.Vote to make this Lego iMac G3 a realityVote for the Lego iMac G3 design and help transform this nostalgic Apple computer into a real-life Lego product.Apple's lucrative Google search deal is safeGoogle can continue its search deal to pay Apple billions of dollars a year for a prime spot as Safari's default search engine.Top 12 drool-worthy dual Studio Display setupsWhat's better than a sleek Apple Studio Display? Two of them! Lust over the best dual Studio Display setups.The CultCast ‘Awe Dropping' PredictionsIt is time to lay down our predictions for the biggest Apple announcement of the year. Previously, Lewis won at WWDC, but Leander and Griffin have the opportunity to kick him off his throne.Submit your predictions here!

Christine just turned 40 and they guys are careful not to overwhelm her in her elderly state. Jay fantasizes about hypothetically murdering her on a vacation safari in Africa. | Did you know that John Heder is a Mormon and did not write Napoleon Dynamite? | Bobby plays the Mega Millions and if he wins, he plans to run away with is new A.I. girlfriend. Go to punchup.live/bigjayoakerson and punchup.live/robertkelly for all tour dates and info! *To hear the full show to go www.siriusxm.com/bonfire to learn more! FOLLOW THE CREW ON SOCIAL MEDIA: @thebonfiresxm @louisjohnson @christinemevans @bigjayoakerson @robertkellylive @louwitzkee @jjbwolf Subscribe to SiriusXM Podcasts+ to listen to new episodes of The Bonfire ad-free and a whole week early.  Start a free trial now on Apple Podcasts or by visiting siriusxm.com/podcastsplus.

A.M. Edition for Sept. 3. After a 2024 ruling that Google operated a search monopoly, a U.S. district judge rejected a forced spinoff of Chrome and allowed the company to continue paying Apple to be the default search provider on Safari. Plus, GOP lawmakers release more than 30,000 pages of documents related to convicted sex offender Jeffrey Epstein. And in a lavish military parade in Tiananmen Square, Xi Jinping flaunts China's growing military power and deepening ties to Washington's adversaries. Azhar Sukri hosts. Sign up for the WSJ's free What's News newsletter. Learn more about your ad choices. Visit megaphone.fm/adchoices

This week, Spike, Paul Zuckerman, and Jonny Lieberman recap their wild time at Pebble Beach, share stories of Monterey Car Week arrests, and test drive some incredible vehicles. Zuckerman is approached by an alleged "Lady of the Night", while Jonny takes a $1.25 million Safari car offroading. ______________________________________________

We're back in studio! What a summer. We catch up on everything we missed: Laura's safari recap (close encounters with wildlife and a guide named Cloud), Taylor Swift and Travis Kelce's engagement and all the speculation around it (the ring, the Ralph Lauren looks, and the American Eagle campaign), Serena Williams' new GLP-1 partnership and the body image conversation it sparked, plus Cracker Barrel's attempted rebrand that did not go as planned. The best (and worst) of the internet — and our lives — all in one episode.You can watch the full episode on ⁠⁠YouTube here⁠⁠.Make sure to check out ⁠⁠Laura's Don't Tell Comedy Special ⁠⁠and leave a comment telling her hair looks great.Follow us on Instagram ⁠⁠@laurasogar⁠⁠ and ⁠⁠@mae_planert⁠⁠ and follow the pod ⁠⁠@doomscrolldiariespod

Marty speaks about today's VisionOS 26 developer beta 9 explaining what is new for users and developers.visionOS 26 Beta 9 Release Noteshttps://developer.apple.com/documentation/visionos-release-notes/visionos-26-release-notes What AVP users will noticeApp Store now shows an Accessibility section on app pages (like a quick “nutrition label” before you download).Share a window from People View: tap Nearby to share with folks around you—or invite FaceTime callers.Mac Virtual Display looks cleaner—sharper edges in passthrough around your Mac/keyboard.Safari: the Clear button is back in the History sidebar. (Heads-up: immersive video can still trap the UI—force-quit if it happens.)Search crash fix rolled out via OTA; EyeSight reliably shows content again.AirDrop videos now open in Files; Messages gets a handful of small polish fixes.Known issue: Spotlight may show blank app icons in Siri Suggestions.Dev bits On-device AI hooks: apps can tap Apple's model directly; faster first responses = snappier features without the cloud.3D charts land in Swift Charts → expect true 3D data views in visionOS apps.Security tightening: default TLS 1.2+ for new builds; very old servers may break. Logs redact more by default.What I've read:- No Jupiter Environment- Still persistence issues for some users- Still widget anchoring problems for some usersEmail: ThePodTalkNetwork@gmail.comWebsite: ThePodTalk.Net

Today, the Safari heads back to Mendon, MA, to hang out with Betsey Brewer to catch up on the latest news about Earth, Ltd.! In the process, we also discuss a new and exciting experience that will be coming to the zoo, mention some friends of the podcast, talk about rhinos, and you get not one, not two, but THREE Rossifari Poop Stories! EPISODE LINKS: southwickszoo.com @southwickszooofficial@earthltdROSSIFARI LINKS: Rossifari.com Patreon.com/rossifari @rossifari on socials @rossifaripod on TikTok 

This is a paid advertisement by BetterHelp. ⁠https://www.betterhelp.com/lads⁠

Safari hunting, conservation, and family hunting traditions from squirrels to elk are key topics of this wonderful interview with Dallas Safari Club CEO Rob McCanna. We recorded this live at the recent inaugural summer DSC convention, and it was one of the most enjoyable conversations I've ever had with a top-end industry leader. Rob is a down-to-earth guy that hunts hard and appreciates time afield as much or more than most—and is dedicating years to preserving, protecting, and promoting our way of life. ENJOY!    FRIENDS, PLEASE SUPPORT THE PODCAST!  Join the Backcountry Hunting Podcast tribe and get access to all our bonus material on www.patreon.com/backcountry   Check out our new "recommended outfitters" hunt booking agency! We're super excited about this venture that allows us to share our favorite destinations around the world with our loyal listeners. We'll also be doing hosted hunts each year, which will be available first to our loyal listeners on Patreon.  We have a new advertising partner! Check out Swift Bullets, known and trusted as the best of the best by most African Dangerous Game specialists.  It's Porter's Firearms' 30-year anniversary this month! They're offering some incredible deals specifically to podcast listeners. Call Shane Porter at 870-701-0504 for details.    VISIT ALL OUR SPONSORS HERE:  www.timneytriggers.com www.browning.com www.leupold.com www.siembidacustomknives.com www.onxmaps.com www.silencercentral.com https://www.portersfirearms.com/ https://javelinbipod.com www.swiftbullets.com

Support The Becket Cook Show on Patreon! NOTE: When you sign up for Patreon, PLEASE do it through a web browser (Safari, Chrome, etc.) and NOT an app on your iPhone. The Apple app charges 30% !!! If you just click on the link above, it should be fine. In this episode, Becket Cook chats with Dr. Thaddeus Williams, professor at Talbot School of Theology (Biola University) and author of "Confronting Injustice Without Compromising Truth," to unpack his recent World Magazine article, "An Anti-Gospel Take on Greed." They dive deep into the growing influence of socialism in Christian circles, the biblical response to economic justice, and why Marxist assumptions about wealth, greed, and justice fall short of the gospel. Dr. Williams shares personal stories, historical insights, and a theological framework for understanding economics through a biblical lens. Shed & Beam Podcast: https://www.youtube.com/@drthaddeuswilliams The Becket Cook Show Ep. 211 Discover more Christian podcasts at lifeaudio.com and inquire about advertising opportunities at lifeaudio.com/contact-us.