Podcasts about Mozilla

In the span of two weeks, OpenAI launched an app platform with 800 million users, released Agent Kit with visual workflows and custom widgets, and dropped Sora—a social video app that instantly became the #1 and #2 app in the App Store. If you've been following our predictions about the next great distribution shift, this is the moment we've been waiting for. The "open" phase has officially begun. In this episode, Brian Balfour (Founder and CEO of Reforge) is joined by Ravi Mehta (former CPO at Tinder, product leader at Meta and TripAdvisor) and Adam Fishman (former Interim VP Product at Mozilla, previously at Patreon and Lyft) to break down what these launches really mean for product leaders. We discuss why this could be the "uh-oh moment" for Google and Apple, how OpenAI is using memory and context to build their moat, and the specific tactical steps you should be taking right now—before your competitors do. We also dive deep on Sora's surprising product design, why it feels more like Snapchat than TikTok, the dopamine mechanics of AI-generated content, and whether Meta is about to "Stories-ify" the whole thing. Get Your Product Team AI-Native This episode is brought to you by Reforge. Reforge provides the tools and training your team needs to become AI-native: Reforge Insights aggregates your scattered customer feedback into actionable intelligence. Reforge Research runs AI interviews and surveys so you can capture new insights at scale. Reforge Build lets you prototype AI features for your existing product in minutes. Reforge Launch gives you the feature management infrastructure you need for AI products. Key Topics: Why ChatGPT's app platform threatens Google Search and the iPhone home screen The distribution shift playbook and what Phase One means for startups vs. incumbents How to get early access and build on OpenAI's platform before it's too late Sora's design choices, creator-product fit, and the unsustainable economics of AI video Why there's no opting out of this wave—and how to catch it This is the strategically most intense environment we've ever seen. Don't miss this one.

Inside Growth 2.0. How AI, GEO & Vibe Coding Are Changing Everything EP322 Profit With A Plan Podcast Release date: October 6, 2025 Guest: Raj Singh, VP of Product at Mozilla Host: Marcia Riner, Business Growth Strategist | Infinite Profit®  

Daniel Stenberg, Swedish Internet protocol expert and founder and lead developer of the Curl project, speaks with SE Radio host Gavin Henry about removing Rust from Curl. They discuss why Hyper was removed from curl, why the last five percent of making it a success was difficult, what the project gained from the 5-year attempt to tackle bringing Rust into a C project, lessons learned for next time, why user support is critical, and the positive long-lasting impact this attempt had. Brought to you by IEEE Computer Society and IEEE Software magazine.

Jim and Leah dive headfirst into a whirlwind chat that covers everything from the fine distinctions between puppets and marionettes to the equally delicate art of building great user experiences. Leah shares her fascinating journey from a Medieval French literature course at Berkeley to leading UX research at companies like Slack, Spotify, Instagram, and Mozilla. Along the way, they tackle why users often don't honestly know what they want, how to avoid building a product no one asked for (looking at you, Juicero), and why good design begins with understanding both people and teams. It's a conversation about people problems disguised as tech problems—with a few detours into bad movie references, car oil changes, and the mythical Trojan horse. Grab your headphones, settle in, and prepare to laugh, learn, and maybe rethink what “user experience” really means.

If you like what you hear, please subscribe, leave us a review and tell a friend!Recent cyber incidents show a surge in attacks targeting both public and private sectors. Threat actors exploited vulnerabilities in software like GeoServer and Pandoc, leading to breaches in U.S. federal agencies and cloud environments. Malware campaigns, such as BadIIS, spread via SEO poisoning, while SonicWall and Boyd Gaming faced rootkits and data breaches, respectively. Security firms like Cloudflare successfully mitigated record-breaking DDoS attacks, and Mozilla introduced safeguards allowing Firefox add-on developers to roll back problematic updates. Law enforcement, including the Secret Service, has intervened to dismantle telecom threats impacting global operations like the UN.

We're back with our twelfth episode of the State of the Thunder! In this episode, we're talking about community initiatives, filling you in on Android development, and finishing our updates on popular Mozilla Connect requests, including true Conversation View! ★ Support this podcast ★

Coming up in this episode * We took a break over the break * Windows 10 pulls a fast one * Firefox brings in another clanker 0:00 Cold Open 2:27 A Distro, a Router and a Choice 25:26 Windows 10 Isn't Dead Yet... 43:45 Browser Watch (feat. Firefox) 1:09:58 Next Time! 1:14:57 Stinger The Video Version! (https://youtu.be/Rsn57QtNsiI) https://youtu.be/Rsn57QtNsiI

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

Topics covered in this episode: * Mozilla's Lifeline is Safe After Judge's Google Antitrust Ruling* * troml - suggests or fills in trove classifiers for your projects* * pqrs: Command line tool for inspecting Parquet files* * Testing for Python 3.14* Extras Joke Watch on YouTube About the show Sponsored by us! Support our work through: Our courses at Talk Python Training The Complete pytest Course Patreon Supporters Connect with the hosts Michael: @mkennedy@fosstodon.org / @mkennedy.codes (bsky) Brian: @brianokken@fosstodon.org / @brianokken.bsky.social Show: @pythonbytes@fosstodon.org / @pythonbytes.fm (bsky) Join us on YouTube at pythonbytes.fm/live to be part of the audience. Usually Monday at 10am PT. Older video versions available there too. Finally, if you want an artisanal, hand-crafted digest of every week of the show notes in email form? Add your name and email to our friends of the show list, we'll never share it. Michael #1: Mozilla's Lifeline is Safe After Judge's Google Antitrust Ruling A judge lets Google keep paying Mozilla to make Google the default search engine but only if those deals aren't exclusive. More than 85% of Mozilla's revenue comes from Google search payments. The ruling forbids Google from making exclusive contracts for Search, Chrome, Google Assistant, or Gemini, and forces data sharing and search syndication so rivals get a fighting chance. Brian #2: troml - suggests or fills in trove classifiers for your projects Adam Hill This is super cool and so welcome. Trove Classifiers are things like Programming Language :: Python :: 3.14 that allow for some fun stuff to show up in PyPI, like the versions you support, etc. Note that just saying you require 3.9+ doesn't tell the user that you've actually tested stuff on 3.14. I like to keep Trove Classifiers around for this reason. Also, License classifier is deprecated, and if you include it, it shows up in two places, in Meta, and in the Classifiers section. Probably good to only have one place. So I'm going to be removing it from classifiers for my projects. One problem, classifier text has to be an exact match to something in the classifier list, so we usually recommend copy/pasting from that list. But no longer! Just use troml! It just fills it in for you (if you run troml suggest --fix). How totally awesome is that! I tried it on pytest-check, and it was mostly right. It suggested me adding 3.15, which I haven't tested yet, so I'm not ready to add that just yet. :) BTW, I talked with Brett Cannon about classifiers back in ‘23 if you want some more in depth info on trove classifiers. Michael #3: pqrs: Command line tool for inspecting Parquet files pqrs is a command line tool for inspecting Parquet files This is a replacement for the parquet-tools utility written in Rust Built using the Rust implementation of Parquet and Arrow pqrs roughly means "parquet-tools in rust" Why Parquet? Size A 200 MB CSV will usually shrink to somewhere between about 20-100 MB as Parquet depending on the data and compression. Loading a Parquet file is typically several times faster than parsing CSV, often 2x-10x faster for a full-file load and much faster when you only read some columns. Speed Full-file load into pandas: Parquet with pyarrow/fastparquet is usually 2x–10x faster than reading CSV with pandas because CSV parsing is CPU intensive (text tokenizing, dtype inference). Example: if read_csv is 10 seconds, read_parquet might be ~1–5 seconds depending on CPU and codec. Column subset: Parquet is much faster if you only need some columns — often 5x–50x faster because it reads only those column chunks. Predicate pushdown & row groups: When using dataset APIs (pyarrow.dataset) you can push filters to skip row groups, reducing I/O dramatically for selective queries. Memory usage: Parquet avoids temporary string buffers and repeated parsing, so peak memory and temporary allocations are often lower. Brian #4: Testing for Python 3.14 Python 3.14 is just around the corner, with a final release scheduled for October. What's new in Python 3.14 Python 3.14 release schedule Adding 3.14 to your CI tests in GitHub Actions Add “3.14” and optionally “3.14t” for freethreaded Add the line allow-prereleases: true I got stuck on this, and asked folks on Mastdon and Bluesky A couple folks suggested the allow-prereleases: true step. Thank you! Ed Rogers also suggested Hugo's article Free-threaded Python on GitHub Actions, which I had read and forgot about. Thanks Ed! And thanks Hugo! Extras Brian: dj-toml-settings : Load Django settings from a TOML file. - Another cool project from Adam Hill LidAngleSensor for Mac - from Sam Henri Gold, with examples of creaky door and theramin Listener Bryan Weber found a Python version via Changelog, pybooklid, from tcsenpai Grab PyBay Michael: Ready prek go! by Hugo van Kemenade Joke: Console Devs Can't Find a Date

State of the Thunder is back after a short hiatus for a new season of answering questions and providing our community with updates on all our products, from mobile and desktop clients to the upcoming Thunderbird Pro! In our first episode of the new season, Alessandro and new cohost Michael Ellis tackle a new batch of your questions with help from members of the Thunderbird team and community. Then they provide updates on the 20-ish top Thunderbird suggestions in Mozilla Connect.  ★ Support this podcast ★

Margo is joined by Cassie McDaniel, Head of Design at Medium, where she leads product design, brand, and research. Cassie has also brought her design expertise to companies like Lattice, Webflow, Glitch, and Mozilla Foundation, and she's passionate about simplifying complex workflows while creating space for more meaningful design. Beyond her professional roles, Cassie is a painter, writer, DIY renovator, and environmental conservation group member—someone who embodies the importance of building a life rich with creativity both in and outside of work. In this conversation, Cassie and Margo explore what it means to be a well-rounded creative leader, how personal passions fuel professional innovation, and why design belongs at the leadership table. Cassie also gives us a peek behind the curtain at Medium's evolving design approach, including how her team thinks about content consumption, new UX navigation, and experiments with AI. Margo and Cassie discuss: The case for doing things outside your job and how hobbies unlock new creative potential How writing serves as “exercise for the brain” and a counterbalance to a busy design career Cassie's approach to mentorship, including hiring, coaching, and guiding designers at all levels A behind-the-scenes look at design at Medium, from flat minimalism to layered storytelling How a family legacy of persistence, from chicken farming to dentistry, shaped Cassie's approach to creativity and leadership Lessons from Cassie's career across Webflow, Glitch, Mozilla, and Medium, and why foundational creative skills translate to digital spaces What makes Medium unique as a platform for authentic stories, connection, and community The value of saying yes to new opportunities, co-designing with communities, and learning from every experience Balancing leadership, writing, and motherhood while still making time for passion projects at home Learn more about Cassie here: Website: cassiemcdaniel.com Medium: cassiebegins.medium.com LinkedIn: linkedin.com/in/cassiemc Instagram: @cassiebegins Connect with Margo: www.windowsillchats.com www.instagram.com/windowsillchats www.patreon.com/inthewindowsill https://www.yourtantaustudio.com/thefoundry   Save the date for Medium Day 2025: https://medium.com/blog/save-the-date-for-medium-day-2025-50b1f15de07d Sign Up for the Sylva Solace Creative Resilience Retreat: https://www.bdi-create.today/sylva-retreat

Android becomes more like iOS, another key dev leaves the Asahi Linux project, Mozilla will probably keep their Google search deal, we troll Félim with some AI bollocks, GNOME can't keep an executive director, Microsoft releases the source for an ancient BASIC implementation, friend of the show Connor is snubbed by an Irish newspaper, a... Read More

Android becomes more like iOS, another key dev leaves the Asahi Linux project, Mozilla will probably keep their Google search deal, we troll Félim with some AI bollocks, GNOME can't keep an executive director, Microsoft releases the source for an ancient BASIC implementation, friend of the show Connor is snubbed by an Irish newspaper, a... Read More

Everyone's talking about GenAI. But adding it to your product isn't just about chasing what's new, it's about making sure it actually makes sense for your users and your long-term strategy.In this episode, Carmen Palmer, CEO of Women In Product talks with Suba Vasudevan, COO, Mozilla.org and SVP, Mozilla Corp take a look at integrating GenAI into your product roadmap without letting hype override clarity or purpose. Whether you're facing internal pressure to “do something AI,” or you're genuinely excited by its potential, this conversation will help you avoid common traps like over-scoping, misaligned use cases, or “GenAI theater”, and instead chart a path that's grounded, scalable, and aligned with your mission.Suba will be a main stage speaker at the 2025 Women In Product Conference.00:00 Introduction to Suba Vasudevan02:08 Early Career Journey and Unique Path04:07 Pivotal Career Moments and Personal Life07:45 Dual Role at Mozilla and Strategic Vision10:49 Incorporating Gen AI into Strategy and Operations19:15 Thought Leadership and Organizational Transformation21:44 Practical Advice for Product Leaders26:44 Challenges and Pitfalls in AI Adoption35:14 Rapid Fire Questions and Personal Insights40:28 Conclusion and Final Thoughts

Raj Singh's career trajectory exemplifies the essence of innovation and adaptability in the tech industry. As the VP of Product at Mozilla, he has successfully transitioned from founding startups to leading product initiatives that leverage artificial intelligence for practical applications. His journey began with the acquisition of his startup, Pulse, which focused on AI-driven meeting summarization, and has continued through notable ventures such as Tempo AI and AllTheCooks. Raj's ability to identify consumer pain points and create solutions that enhance productivity and user experience has been a hallmark of his approach, demonstrating the importance of empathy in product development. Throughout his career, Raj has emphasized the significance of resilience and learning from failure. His experiences in various tech domains, from mobile browsers to community-driven applications, have equipped him with a unique perspective on the challenges and opportunities within the industry. He advocates for a mindset that embraces obstacles as stepping stones to success, encouraging aspiring entrepreneurs to focus on solving real problems for users. This philosophy not only drives his work at Mozilla but also inspires others to pursue their passions with determination and creativity. For those looking to explore innovative solutions in the realm of website design, Raj's latest project, Soloist, offers an exciting opportunity. Soloist is designed to empower users, particularly small business owners and solopreneurs, by simplifying the website creation process through AI-driven tools. To learn more about Soloist and Raj's other initiatives, you can visit his Linktree where you'll find valuable resources and insights into his work and contributions to the tech community. For the accessible version of the podcast, go to our Ziotag gallery.We're happy you're here! Like the pod?Support the podcast and receive discounts from our sponsors: https://yourbrandamplified.codeadx.me/Leave a rating and review on your favorite platformFollow @yourbrandamplified on the socialsTalk to my digital avatar

Ubuntu 25.10 has a release date and Rust Coreutils still looks good. Pop OS 24.04 is finally almost ready, Kazeta brings back the game carts, and Arch Linux is still under attack. Torvalds takes out the Trash, Firefox has announced the end of 32, and KDE is nearing an exciting 6.5. For tips we have wpctl set-default for controlling WirePlumber defaults, Feral's gamemode for optimized game performance, and strings for pulling ASCII strings out of binaries. You can find the show notes at https://bit.ly/4g88VLk and have a great week! Host: Jonathan Bennett Co-Hosts: Jeff Massie and Ken McDonald Download or subscribe to Untitled Linux Show at https://twit.tv/shows/untitled-linux-show Want access to the ad-free video and exclusive features? Become a member of Club TWiT today! https://twit.tv/clubtwit Club TWiT members can discuss this episode and leave feedback in the Club TWiT Discord.

Timestamps: 0:00 i'm a one-tech pony 0:12 Google can keep paying Mozilla and Apple 1:50 Amazon eliminates Prime sharing 2:58 Dolby Vision 2 'Authentic Motion' 4:31 Saily! 5:27 QUICK BITS INTRO 5:34 PS5 getting SSD nerf 6:18 It was an AI garbage bag 6:51 Tesla Master Plan kinda slops 7:27 LEGO Sega Genesis controller NEWS SOURCES: https://lmg.gg/SQLdT Learn more about your ad choices. Visit megaphone.fm/adchoices

Le verdict est tombé à Washington : Google conservera son intégrité. Le juge fédéral Amit Mehta, chargé du procès antitrust historique engagé contre la firme en 2020, a décidé de ne pas imposer le démantèlement du géant technologique. Chrome, Android et le reste de l'écosystème restent entre les mains de la maison mère. Une décision qui soulève autant de soulagement chez les investisseurs que d'interrogations sur la capacité des autorités à réguler les GAFAM.Tout en reconnaissant que Google est en situation de monopole et qu'il a abusé de cette position, le juge a choisi une approche pragmatique. Imposer la cession de produits stratégiques aurait, selon lui, désorganisé profondément le marché numérique, affaibli la qualité des services et créé un risque de chaos technologique. En toile de fond, c'est tout un écosystème — incluant Apple, Samsung ou encore Mozilla — qui dépend des accords commerciaux noués avec Google, notamment pour l'installation par défaut de son moteur de recherche.Mais cette décision n'est pas sans conséquences. Google devra désormais partager certaines données, notamment sur les requêtes de recherche, avec des concurrents comme Bing ou DuckDuckGo. Il lui sera également interdit de signer des contrats d'exclusivité empêchant l'installation d'autres moteurs de recherche sur les appareils et navigateurs.-----------♥️ Vous aimez ce podcast ? Soutenez-le !https://donorbox.org/monde-numerique

Morgan runs a public relations and marketing agency called Firebrand. They raise awareness of technology brands to build awareness, create demand, drive lead generation and close sales. Prior to Firebrand, he was the founder in the US of LEWIS , a global communications firm, which we grew to $35m in revenues and 250+ staff in the US, and $75m with 600 staff globally. He has over 30 years' tech experience, both consumer and B2B. He has advised a range of companies including start-ups such as Amount, Prophecy and Weaviate; non-profits, such as AARP, Mozilla and VSP Vision Care; and public companies, such as BT Group, Equinix, MuleSoft, Splunk and Sky. At LEWIS, he lead the acquisition of three companies - Page One Power which they integrated and rebranded as LEWIS Pulse; the Davies Murphy Group, a 65-person PR and marketing consultancy; and Piston, a 50-person full-service digital advertising agency.

In this episode of The Girl Dad Show, Young Han sits down with Jim Cook, a Silicon Valley veteran with over 30 years of experience scaling startups, including guiding Mozilla from Series A to IPO. Jim is the founder of BenchBoard and the creator of Cook's PlayBooks newsletter, where he coaches leaders and equips them with frameworks to bridge the gap between vision and execution. Jim shares how he's balanced high-stakes executive roles with being present for his family, why sales skills are essential in every career, and how travel helps build empathy in children. He discusses the importance of modeling good behavior, setting boundaries, and staying authentic in both leadership and content creation. Jim also critiques the unhealthy 996 work culture and explains why teaching financial literacy to kids is one of the best investments parents can make. ✨ All episodes of The Girl Dad Show are proudly sponsored by Thesis, helping founders go further, together. Key Takeaways Over 30 years of leadership experience in Silicon Valley, including scaling Mozilla from Series A to IPO. Balancing family and career is crucial during children's formative years. Sales skills are valuable in every profession, not just sales roles. Travel fosters empathy and cultural understanding in children. Modeling behavior is more impactful than simply telling kids what to do. Setting boundaries between work and family leads to healthier relationships. The 996 work culture promotes burnout and imbalance. Financial literacy for kids is a must. Authenticity resonates more with audiences than polished perfection.

video: https://youtu.be/vSfDyg8OxsI Comment on the TWIL Forum (https://thisweekinlinux.com/forum) This week in Linux, we've got a bunch of new releases from the super popular open source office suite LibreOffice to a couple releases from Mozilla and one of the best open source video editors has a new release with Kdenlive. We're also going to take a look back at seven years of Proton as we celebrate the current state of Linux gaming. Plus, CachyOS is currently on the rise as they just took the number one spot on DistroWatch. We'll talk about what that means and what it doesn't. All of this and more on This Week in Linux, the weekly news show that keeps you up to date with what's going on in the Linux and open source world. And we are so close to 100,000 subscribers for the channel. If you haven't subscribed yet, please do. Now, let's jump right into Your Source for Linux GNews. Download as MP3 (https://aphid.fireside.fm/d/1437767933/2389be04-5c79-485e-b1ca-3a5b2cebb006/2a839f6b-6a88-422d-b343-774a9ecd98f5.mp3) Support the Show Become a Patron = tuxdigital.com/membership (https://tuxdigital.com/membership) Store = tuxdigital.com/store (https://tuxdigital.com/store) Chapters: 00:00 Intro 01:06 LibreOffice 25.8 03:45 7 Years of Proton 06:24 CachyOS becomes #1 on DistroWatch 09:34 Sandfly Security, agentless Linux security 12:01 Firefox 142 14:03 Thunderbird 142 17:24 LibreELEC 12.2 18:51 OSMC August 2025 Update 20:49 Kdenlive 25.08 22:49 Humble Bundle Summer Sale 24:06 Arch's AUR Battles DDoS Attacks and Malware 27:08 Outro Links: LibreOffice 25.8 https://blog.documentfoundation.org/blog/2025/08/20/libreoffice-25-8/ https://wiki.documentfoundation.org/ReleaseNotes/25.8 7 Years of Proton https://www.gamingonlinux.com/2025/08/7-years-later-valves-proton-has-been-an-incredible-game-changer-for-linux/ CachyOS becomes #1 on DistroWatch https://distrowatch.com/ https://distrowatch.com/dwres.php?resource=popularity https://cachyos.org/ Sandfly Security, agentless Linux security https://thisweekinlinux.com/sandfly Firefox 142 https://www.firefox.com/en-US/firefox/142.0/releasenotes/ Thunderbird 142 https://blog.thunderbird.net/2025/08/tbpro-august-2025-update/ https://www.thunderbird.net/en-US/thunderbird/142.0/releasenotes/ LibreELEC 12.2 https://libreelec.tv/2025/08/15/libreelec-omega-12-2-0/ OSMC August 2025 Update https://osmc.tv/2025/08/osmcs-august-update-is-here-4/ Kdenlive 25.08 https://kdenlive.org/news/releases/25.08.0/ Humble Bundle Summer Sale https://humblebundleinc.sjv.io/19353m Arch's AUR Battles DDoS Attacks and Malware https://fossforce.com/2025/08/archs-aur-battles-ddos-attacks-and-persistent-malware-all-summer-so-far Support the show https://tuxdigital.com/membership https://store.tuxdigital.com/

Microsoft releases emergency out-of-band (OOB) Windows updates. Trump targets NSA's leading AI and cyber expert in clearance revocations. A breach may have compromised the privacy of Ohio medical marijuana patients. Cybercriminals exploit an AI website builder to rapidly create phishing sites. Warlock ransomware operators target Microsoft's SharePoint ToolShell vulnerability. Google and Mozilla patch Chrome and Firefox. European officials report two cyber incidents targeting water infrastructure. A federal appeals court has upheld fines against T-Mobile and Sprint for illegally selling customer location data. Authorities dismantle DDoS powerhouse Rapper Bot. On our Industry Voices segment, we are joined by Matt Radolec, VP - Incident Response, Cloud Operations, and Sales Engineering at Varonis, speaking about ShinyHunters and the problems with securing Salesforce. Microsoft Copilot gets creative with compliance.  Remember to leave us a 5-star rating and review in your favorite podcast app. Miss an episode? Sign-up for our daily intelligence roundup, Daily Briefing, and you'll never miss a beat. And be sure to follow CyberWire Daily on LinkedIn. CyberWire Guest On our Industry Voices segment, we are joined by Matt Radolec, VP - Incident Response, Cloud Operations, and Sales Engineering at Varonis, who is speaking about ShinyHunters and the problems with securing Salesforce. You can hear more from Matt here. Selected Reading Microsoft releases emergency updates to fix Windows recovery (Bleeping Computer) Trump Revokes Security Clearances of 37 Former and Current Officials (The New York Times) Highly Sensitive Medical Cannabis Patient Data Exposed by Unsecured Database (WIRED) AI Website Builder Lovable Abused for Phishing and Malware Scams (Hackread) Warlock Ransomware Hitting Victims Globally Through SharePoint ToolShell Exploit (InfoSecurity Magazine) High-Severity Vulnerabilities Patched in Chrome, Firefox (SecurityWeek) Russia-linked European attacks renew concerns over water cybersecurity (CSO Online) T-Mobile claimed selling location data without consent is legal, judges disagree (Ars Technica) Officials gain control of Rapper Bot DDoS botnet, charge lead developer and administrator (CyberScoop) Copilot Broke Your Audit Log, but Microsoft Won't Tell You (Pistachio Blog) Audience Survey Complete our annual audience survey before August 31. Want to hear your company in the show? You too can reach the most influential leaders and operators in the industry. Here's our media kit. Contact us at cyberwire@n2k.com to request more info. The CyberWire is a production of N2K Networks, your source for strategic workforce intelligence. © N2K Networks, Inc. Learn more about your ad choices. Visit megaphone.fm/adchoices

Techish is taking a short summer break, but we'll be back in September! In the meantime, we've got a fantastic episode to share from our friends over at the IRL Podcast. You might remember we had IRL host Bridget Todd on Techish recently for our Falling in Love With Your AI episode. So trust us, you're gonna love this one.———————————————————— Decoding the Planet: From Whales to Whistleblowers From season eight of the IRL podcast: AI and Us.AI may be able to talk to animals, but at what cost to the planet. Who is making those decisions, and why it matters. From decoding whale language to protecting our oceans from unchecked offshore drilling, Bridget Todd talks to visionaries seeking to preserve our beautiful, fragile world. Holly Alpine left her job with Microsoft over the company's role in providing fossil fuel companies with AI tools that could accelerate their production of oil and gas. As the AI and climate lead at Hugging Face, a platform for sharing open-source AI models, Sasha Luccioni calls for more transparency from tech companies about how much energy it takes to power AI. Aza Raskin, co-founder and president of the Earth Species Project, explains why using AI to decode animal communication could be the key to protecting our planet.IRL is an original podcast from Mozilla, the non-profit behind Firefox.A Case Study In Corporate Fear"A Case Study in Corporate Fear" deconstructs how fear transforms successful...Listen on: Apple Podcasts SpotifySupport the show————————————————————Join our Patreon for extra-long episodes and ad-free content: https://www.patreon.com/techish Watch us on YouTube: https://www.youtube.com/@techishpod/Advertise on Techish: https://goo.gl/forms/MY0F79gkRG6Jp8dJ2———————————————————— Stay in touch with the hashtag #Techishhttps://www.instagram.com/techishpod/https://www.instagram.com/abadesi/https://www.instagram.com/michaelberhane_/ https://www.instagram.com/hustlecrewlive/https://www.instagram.com/pocintech/Email us at techishpod@gmail.com

Xfce running on Wayland on openSUSE, Canonical laid off the printing guy, Mozilla pisses people off with AI tab groups, and what the post-x86 world will look like for desktop Linux. Plus a handy way to save and run project-specific commands, turning any device into a file server, and a convoluted way to get wind... Read More

Xfce running on Wayland on openSUSE, Canonical laid off the printing guy, Mozilla pisses people off with AI tab groups, and what the post-x86 world will look like for desktop Linux. Plus a handy way to save and run project-specific commands, turning any device into a file server, and a convoluted way to get wind... Read More

Foundations of Amateur Radio Recently I discussed the idea of listening to the radio spectrum across the internet for the purposes of getting signal into your shack when radios, or in my case, antennas are causing you challenges. I continued to explore and discovered a project by Jacobo EA1ITI, called "radioreceiver". Behind that unassuming name lies a tool born in 2014, that allows you to plug an RTL-SDR dongle into your computer, open up your web-browser, and listen to the radio signals that your dongle can receive. In case you're unfamiliar, an RTL-SDR dongle is a small USB device, looks a lot like a USB thumb drive, jump drive, data stick or flash drive, basically a hunk of plastic with a USB connector on it. An RTL-SDR dongle generally also has some form of antenna connector. It's typically sold as a digital radio and digital television receiver, but websites like rtl-sdr.com sell purpose built ones. They can be found starting at about $15. I realise that this is using a local receiver, with a local antenna, but it's inside a web browser, which is half of what I expected. When you hit the play button in the bottom of the screen, you'll be prompted by your web browser to give permission to access your RTL-SDR dongle and the fun starts. You'll see a live waterfall, hear audio, and have the ability to tune to any frequency you can reach. Depending on your dongle, typically somewhere between 500 kHz and 1.76 GHz. The application consists of seven files, a total of 352 kilobytes that you can store on any web server and run, with one caveat, in order for your web browser to talk to your dongle, it needs to be served using HTTPS. Jacobo has set-up radio.ea1iti.es and I've set-up sdr.vk6flab.com, both showing the same tool. You'll find the code on my VK6FLAB GitHub repository, and of course on Jacobo's. There are some things you need to know. You will need to use a web browser that supports WebUSB, currently that's Chrome, Edge, Opera and several others, sorry, Safari and Firefox don't .. perhaps it's time to talk to Apple and Mozilla. All is explained if you click on the little question mark at the bottom of the screen, it will even tell you if the browser you're using to read the help is compatible or not. If you have an Android phone, you can run this tool too, although you will need to find a way to connect your dongle to your phone. I'm currently limited in my ability to test this and you may need to install some drivers on Windows and Linux, but MacOS and presumably Android, works out of the box. The software also supports offline operation, so you can load it as a Progressive Web App, or PWA, and use it in the field away from the internet. Did I mention that all the decoding is happening inside the web browser, so you can see which code is doing what .. and before you ask, yes, it's minimised in the browser, which you can make into human readable code, but when you look at the source, it shows precisely what is happening, all written in Node.js, TypeScript and JavaScript. It supports CW, SSB, AM, Narrow and Wideband FM and decodes stereo, something which none of my amateur radios do. You might be able to tell that I'm excited. It's because this is providing the basic functionality of a radio inside a web browser, and I didn't need to install it to get started. On the Macintosh I tested this on, I literally opened the web page, plugged in a dongle and hit play. Just so we're clear, just because this is using a web page on a web server, you accessing it will only give you access to your radio not mine. This of course opens the doors to all manner of other fun stuff which I'm expecting to play with for the next little while, and yes, this is also Bald Yak adjacent, I'm aware. In the meantime, you can play with this right now, sdr.vk6flab.com is the place to go. Word of warning, it's addictive and easy to forget it's a radio with an antenna plugged into your computer, so take precautions when electrical storms are about. Look forward to hearing what you discover. I'm Onno VK6FLAB

In this conversation, Giorgio Natili discusses the significance of confidential computing in the realm of AI workflows, emphasizing its role in ensuring data sovereignty and security. He explains how confidential computing can reshape AI usage, particularly in sensitive industries like finance and healthcare. The discussion also touches on the challenges organizations face regarding data privacy and the ethical implications of AI. Natili advocates for a balanced approach where AI complements human expertise rather than replacing it, and he highlights the importance of building secure and compliant AI systems. Sound Bites "Data sovereignty is crucial in AI workflows." "AI cannot replace human beings." "The expert in the room is the human being." Episode # 162 Today's Guest: Giorgio Natili, Vice President and Head of Engineering at Opaque Systems Giorgio Natili is a tech leader, author, and advocate for fearless leadership. With over 20 years of experience, he has led teams at companies such as Amazon, Mozilla, and Capital One. LinkedIn: Giorgio Natili  What Listeners Will Learn: Confidential computing enhances the security posture of systems. Data sovereignty is a critical concern for organizations using AI. Confidential computing allows for secure AI workflows without data leakage. The role of trusted execution environments is vital in protecting sensitive data. Organizations often face challenges with compliance and data privacy regulations. AI should complement human expertise, not replace it. Confidential computing can help organizations navigate complex regulatory landscapes. The importance of attestation in ensuring secure AI workflows. AI can be powerful when used ethically and responsibly. Industry applications for confidential computing include finance, healthcare, and legal sectors.

Brian and Eric talk to their TC39 representative colleagues Nic and Ujjwal about TC39 in general, and the most recent meeting. Mentioned Links Agenda with proposal links Mozilla amount element explainer

When AI agents move faster than security teams, the game changes, and the risks multiply. Ron welcomes back Marco “Mystic Marc” Figueroa, Program Manager at Mozilla's 0DIN Program, to continue the conversation and update on 2025's most pressing AI and cybersecurity shifts. From the explosive rise of AI agents and OpenAI's rumored browser to the hidden dangers of MCP implementations and prompt injection exploits like the Gemini attack, Marco shares insights that security pros can't afford to miss. Impactful Moments 00:00 - Introduction 02:00 - Why 2025 is the year of the agent 05:45 - MCP's rapid adoption and security risks 10:00 - The Gemini prompt injection vulnerability 15:00 - How attackers hide malicious AI prompts 18:00 - High success rates in non-technical teams 22:00 - Rise of voice-based AI scams 25:00 - Using jailbreaks to bend AI to your needs 30:00 - Predictions on OpenAI's upcoming browser 33:00 - The profit battle between OpenAI and Microsoft 35:00 - Windsurf's rollercoaster of acquisitions Links: Connect with our guest Marco on LinkedIn: https://www.linkedin.com/in/marco-figueroa-re/ Check out our upcoming events: https://www.hackervalley.com/livestreams Join our creative mastermind and stand out as a cybersecurity professional: https://www.patreon.com/hackervalleystudio Love Hacker Valley Studio? Pick up some swag: https://store.hackervalley.com Continue the conversation by joining our Discord: https://hackervalley.com/discord Become a sponsor of the show to amplify your brand: https://hackervalley.com/work-with-us/

Register for FREE Infosec Webcasts, Anti-casts & Summits – https://poweredbybhis.com00:00:00 - PreShow Banter™ — Stop Asking Wade if he's in Vegas00:02:16 - Perplexity Uses Stealth Crawlers to Evade No-Crawl Directives – 2025-08-0400:11:25 - Story # 1: Insurance won't cover $5M in City of Hamilton claims for cyberattack, citing lack of log-in security00:18:40 - Story # 2: States Enact Safe Harbor Laws that Provide Affirmative Defenses in Data Breach Litigation00:26:45 - Story # 3: Hackers Destroy Aeroflot's IT Infrastructure, Causing Over 42 Flight Cancellations00:34:18 - Story # 4: Attackers exploit link-wrapping services to steal Microsoft 365 logins00:40:09 - Story # 5: Mozilla flags phishing wave aimed at hijacking trusted Firefox add-ons00:42:18 - Wade's plugin recommendation00:44:39 - Story # 6: Perplexity is using stealth, undeclared crawlers to evade website no-crawl directives00:51:11 - Story # 7: After Backlash, ChatGPT Removes Option to Have Private Chats Indexed by Google00:55:21 - AI 202701:01:01 - What's Ralph been up to?

What does it take to transform a mission-driven organization into a high-velocity execution machine? Today, Peter Winick sits down with Suba Vasudevan, COO of Mozilla, to explore how thought leadership drives impact inside and outside the organization. Suba isn't just talking about brand elevation—she's focused on aligning thought leadership with Mozilla's double bottom line: financial success and a healthy internet. You'll hear how she uses thought leadership to drive strategic clarity, cultural alignment, and real-world execution across a global, mission-focused team. Suba unpacks how leaders can build trust, model transparency, and scale their thinking across a workforce by showing up authentically—whether that's in a Slack message or on a podcast. From AI adoption to KPIs, Suba makes it clear: thought leadership isn't optional for modern executives—it's core to leading transformation. She offers a candid look at how leaders should use their voice—not just for visibility, but as a catalyst for cultural change, employee productivity, and long-term innovation. Suba's message is simple and powerful: If you're not investing in thought leadership, you're holding your team back. Three Key Takeaways: • Thought Leadership Is a Leadership Imperative Suba emphasizes that thought leadership isn't optional—it's foundational to effective leadership in today's world. It's how leaders align teams, build trust, and scale their vision across an organization. She views it as table stakes for anyone serious about transformation. • Execution and Culture Must Be Intertwined Driving results at Mozilla means more than setting KPIs. Suba connects culture to execution, highlighting that metrics only matter when they're backed by employee belief, buy-in, and shared values. Thought leadership is her tool to bridge that gap. • AI Is a Culture Shift, Not Just a Tech Shift Suba doesn't just endorse using AI—she models it. By openly using tools like ChatGPT and encouraging her team to do the same, she's shaping a culture of innovation, experimentation, and productivity. Her approach shows how leadership can normalize and accelerate change from the top. If you found Suba Vasudevan's episode valuable—especially her take on aligning leadership, culture, and execution—then you won't want to miss our conversation with Harry Kraemer on Value-Based Thought Leadership. Like Suba, Harry emphasizes the power of authenticity, clarity, and consistency in leadership. He explores how values-driven decision-making builds trust, scales alignment, and creates long-term impact inside complex organizations. While Suba applies these principles to tech and innovation, Harry brings a timeless leadership lens from his experience as a CEO and professor at Kellogg.

In this episode, Raj Singh, multi-time founder and current VP of Product at Mozilla, opens up about the moments that nearly unraveled his career. From getting called into HR over a side hustle to walking away from a startup after being unexpectedly leveled, Raj shares what it's like to navigate the highs and lows of building without losing your identity.He walks us through multiple pivots, including the time he turned down a seven-figure exit and the brutal leadership decision that nearly cost him a co-founder. Raj doesn't just talk strategy, he gets into the emotional rollercoaster of founding: the resentment, the rejections, and the real mental toll of being the one expected to have all the answers.In this conversation, you'll learn:-Why being a “do-it-all” founder doesn't scale-How to manage resentment when you get leveled-What it really takes to make hard calls when no one agrees with youThings to listen for:(00:00) Intro(01:04) Meet Raj and his startup resume(02:02) Growing up in the Bay(04:05) First hustle: installing Ethernet cards(07:54) Early failures and impostor syndrome(09:11) Picking product vs. engineering(10:06) Thanks to our sponsors, Navattic & Appcues(12:49) HR call over a side project(16:23) Fear, risk, and side hustles(24:35) Leaving a startup after a new hire(29:01) Facing public failure as CEO(30:06) Rise of IC tracks and redefining success(34:08) Hardest call of his career(44:41) Power of incentives(47:33) His video game theory of growth(52:06) The real risk: not improving(56:00) There's never a perfect timeThis episode is presented by:Navattic: Interactive Product Demo Software - https://navattic.com/value Appcues: User Engagement for SaaS - https://appcues.com/value Resources:Connect with Raj:LinkedIn: https://www.linkedin.com/in/rajansingh/Linktree: https://linktr.ee/mobilerajX: https://x.com/mobilerajMozilla: https://www.mozilla.org/en-US/Connect with Andrew:LinkedIn: https://www.linkedin.com/in/andrewcapland/ Substack: https://media.deliveringvalue.coHire Andrew as your coach: https://deliveringvalue.co/coaching

Intel pulls the plug on Clear Linux, Mozilla crams more AI into Firefox, ESWIN Computing partners with Ubuntu for a new RISC-V SBC, and finally something worth shoving into the PCIe slot on a Raspberry Pi 5.

Reimagining the Future of Education Through Innovation with Ariam Mogos. Ariam leads the emerging tech portfolio at Stanford's d.school, where she supports students and educators in designing with tools like AI, always with a keen eye on their ethical impact on people and the planet. Her work spans continents, from Africa and Asia to the US and Europe, collaborating with organisations like UNICEF, the World Bank, and the LEGO Foundation. A National Geographic Explorer, Ariam's contributions to digital learning and inclusion have also been recognised by Mozilla and Fast Company

Privacy-friendly ad targeting is getting harder as cookies disappear. Graham Mudd, SVP of Product at Anonym (Mozilla), shares how privacy-preserving technologies can actually improve targeting results. Marketers can leverage first-party data using advanced machine learning techniques to find lookalike audiences without sharing customer data with ad platforms. This approach delivers approximately 30% better efficiency in finding converters compared to broad targeting, while maintaining compliance with evolving privacy regulations across different markets.See Privacy Policy at https://art19.com/privacy and California Privacy Notice at https://art19.com/privacy#do-not-sell-my-info.

Privacy-friendly ad targeting is getting harder as cookies disappear. Graham Mudd, SVP of Product at Anonym (Mozilla), shares how privacy-preserving technologies can actually improve targeting results. Marketers can leverage first-party data using advanced machine learning techniques to find lookalike audiences without sharing customer data with ad platforms. This approach delivers approximately 30% better efficiency in finding converters compared to broad targeting, while maintaining compliance with evolving privacy regulations across different markets.See Privacy Policy at https://art19.com/privacy and California Privacy Notice at https://art19.com/privacy#do-not-sell-my-info.

video: https://youtu.be/GH18mp-2d90 Comment on the TWIL Forum (https://thisweekinlinux.com/forum) This week in Linux is packed! It's an extra long episode. So if you were wanting more and more TWIL, then you're going to get it this week because Steam Summer Sale is here and it is torching bank accounts. Fedora developers are talking about getting rid of 32-bit support and there's a little bit of controversy around that. We're going to break all of that down. Also, Fairphone 6 has been announced and it comes with kernel patches, an upstream Linux kernel on day one. Firefox 140 has arrived as the new ESR, and there's also some exciting news coming in the next release of Firefox as well. And later in the show, KDE's Wayland wave is continuing to grow to about 70% of users these days. Kubuntu drops X11 by default, and KDE is working on a slick first run wizard. All of this and more on This Week in Linux, the weekly news show that keeps you up to date with what's going on in the Linux and Open Source world. Now let's jump right into Your Source for Linux GNews. Download as MP3 (https://aphid.fireside.fm/d/1437767933/2389be04-5c79-485e-b1ca-3a5b2cebb006/9cb2b795-4602-45c2-aae3-941686eed60c.mp3) Support the Show Become a Patron = tuxdigital.com/membership (https://tuxdigital.com/membership) Store = tuxdigital.com/store (https://tuxdigital.com/store) Chapters: 00:00 Intro 01:06 Steam Summer Sale 2025, here's some Steam Deck ready bargains 03:12 Fedora's Controversial 32-Bit Proposal (Could this kill Bazzite?) 09:23 Fairphone 6 Announced: Modular, Repairable, Linux-Ready 14:54 Sandfly Security, agentless Linux security [ad] 16:40 Firefox 140 ESR lands with Tab Unloading & Vertical Pinned Zone 19:41 KDE Korner: Wayland Surges in Usage, Kubuntu Dropping X11, New Initial Setup Wizard 25:27 Flathub Hits 3 Billion Downloads 27:36 Destination Linux podcast for more great content 28:38 2K Classics Humble Bundle with BioShock & Mafia (90% Discount!) 31:24 ONLYOFFICE 9.0 Released: AI Tools, Visio Viewer & Fresh UI! 34:15 Lyon Goes Open Source (France's Third-Largest City) 36:31 Outro Links: Steam Summer Sale 2025, here's some Steam Deck ready bargains https://store.steampowered.com/ (https://store.steampowered.com/) https://www.gamingonlinux.com/2025/06/steam-summer-sale-2025-is-live-heres-some-top-picks-all-under-20/ (https://www.gamingonlinux.com/2025/06/steam-summer-sale-2025-is-live-heres-some-top-picks-all-under-20/) Fedora's Controversial 32-Bit Proposal (Could this kill Bazzite?) https://discussion.fedoraproject.org/t/f44-change-proposal-drop-i686-support-system-wide/156324 (https://discussion.fedoraproject.org/t/f44-change-proposal-drop-i686-support-system-wide/156324) https://www.gamingonlinux.com/2025/06/bazzite-would-shut-down-if-fedora-goes-ahead-with-removing-32-bit/ (https://www.gamingonlinux.com/2025/06/bazzite-would-shut-down-if-fedora-goes-ahead-with-removing-32-bit/) https://www.gamingonlinux.com/2025/06/fedora-linux-devs-discuss-dropping-32-bit-packages-potentially-bad-news-for-steam-gamers/ (https://www.gamingonlinux.com/2025/06/fedora-linux-devs-discuss-dropping-32-bit-packages-potentially-bad-news-for-steam-gamers/) https://www.reddit.com/r/linux/comments/1lj9e00/fedora43changeproposaldropi686support/ (https://www.reddit.com/r/linux/comments/1lj9e00/fedora_43_change_proposal_drop_i686_support/) https://www.reddit.com/r/linuxgaming/comments/1ljo24p/bazzitefoundermightshutdownwholeproject_if/ (https://www.reddit.com/r/linux_gaming/comments/1ljo24p/bazzite_founder_might_shutdown_whole_project_if/) https://www.reddit.com/r/linuxgaming/comments/1lj9oqw/fedoralinuxdevsdiscussdropping32bit_packages/ (https://www.reddit.com/r/linux_gaming/comments/1lj9oqw/fedora_linux_devs_discuss_dropping_32bit_packages/) Fairphone 6 Announced: Modular, Repairable, Linux-Ready https://www.fairphone.com/ (https://www.fairphone.com/) https://www.fairphone.com/en/2025/06/25/switch-to-the-new-fairphone-gen-6/ (https://www.fairphone.com/en/2025/06/25/switch-to-the-new-fairphone-gen-6/) https://murena.com/murena-fairphone-gen-6-is-here-the-most-ethical-smartphone-unveiled/ (https://murena.com/murena-fairphone-gen-6-is-here-the-most-ethical-smartphone-unveiled/) Sandfly Security, agentless Linux security [ad] https://thisweekinlinux.com/sandfly (https://thisweekinlinux.com/sandfly) Firefox 140 ESR lands with Tab Unloading & Vertical Pinned Zone Firefox 140: https://www.mozilla.org/en-US/firefox/140.0/releasenotes/ (https://www.mozilla.org/en-US/firefox/140.0/releasenotes/) https://www.theregister.com/2025/06/24/firefox140esr/ (https://www.theregister.com/2025/06/24/firefox_140_esr/) https://www.omgubuntu.co.uk/2025/06/firefox-140-new-features-update (https://www.omgubuntu.co.uk/2025/06/firefox-140-new-features-update) https://www.phoronix.com/news/Firefox-140 (https://www.phoronix.com/news/Firefox-140) https://9to5linux.com/firefox-140-esr-web-browser-is-now-available-for-download-this-is-whats-new (https://9to5linux.com/firefox-140-esr-web-browser-is-now-available-for-download-this-is-whats-new) Firefox 141 https://9to5linux.com/firefox-141-promises-to-use-less-memory-on-linux-systems-beta-out-now (https://9to5linux.com/firefox-141-promises-to-use-less-memory-on-linux-systems-beta-out-now) https://www.phoronix.com/review/firefox-141-linux-ram (https://www.phoronix.com/review/firefox-141-linux-ram) Mozilla discontinues DeepSpeech https://www.omgubuntu.co.uk/2025/06/mozilla-deepfake-ai-detector-closing-down (https://www.omgubuntu.co.uk/2025/06/mozilla-deepfake-ai-detector-closing-down) https://www.phoronix.com/news/Mozilla-DeepSpeech-Discontinued (https://www.phoronix.com/news/Mozilla-DeepSpeech-Discontinued) https://github.com/mozilla/DeepSpeech (https://github.com/mozilla/DeepSpeech) KDE Korner: Wayland Surges in Usage, Kubuntu Dropping X11, New Initial Setup Wizard https://www.omgubuntu.co.uk/2025/06/kde-initial-setup-tool-kiss-development-progress (https://www.omgubuntu.co.uk/2025/06/kde-initial-setup-tool-kiss-development-progress) https://9to5linux.com/kde-plasma-6-4-1-released-with-various-improvements-and-bug-fixes (https://9to5linux.com/kde-plasma-6-4-1-released-with-various-improvements-and-bug-fixes) https://www.reddit.com/r/linuxgaming/comments/1lipt42/kdeplasmawillcontinuehavinganx11session_as/ (https://www.reddit.com/r/linux_gaming/comments/1lipt42/kde_plasma_will_continue_having_an_x11_session_as/) https://www.gamingonlinux.com/2025/06/kde-plasma-will-continue-having-an-x11-session-as-kubuntu-switches-to-wayland-by-default/ (https://www.gamingonlinux.com/2025/06/kde-plasma-will-continue-having-an-x11-session-as-kubuntu-switches-to-wayland-by-default/) https://www.omgubuntu.co.uk/2025/06/kubuntu-25-10-drops-x11-session (https://www.omgubuntu.co.uk/2025/06/kubuntu-25-10-drops-x11-session) https://lwn.net/Articles/1026552/ (https://lwn.net/Articles/1026552/) https://www.phoronix.com/news/KDE-Wayland-Is-The-Future (https://www.phoronix.com/news/KDE-Wayland-Is-The-Future) Flathub Hits 3 Billion Downloads https://flathub.org/statistics (https://flathub.org/statistics) https://www.reddit.com/r/linux/comments/1lgaz5z/flathubhaspassed3billion_downloads/ (https://www.reddit.com/r/linux/comments/1lgaz5z/flathub_has_passed_3_billion_downloads/) Destination Linux podcast for more great content https://destinationlinux.net/ (https://destinationlinux.net/) Latest Interviews Carl Richell of System76 = https://destinationlinux.net/416 (https://destinationlinux.net/416) Craig Rowland of Sandfly Security = https://destinationlinux.net/409 (https://destinationlinux.net/409) Artyom Zorin of Zorin OS = https://destinationlinux.net/395 (https://destinationlinux.net/395) 2K Classics Humble Bundle with BioShock & Mafia (90% Discount!) https://humblebundleinc.sjv.io/09zAMM (https://humblebundleinc.sjv.io/09zAMM) ONLYOFFICE 9.0 Released: AI Tools, Visio Viewer & Fresh UI! https://www.onlyoffice.com/blog/2025/06/meet-onlyoffice-desktop-editors-v9-0 (https://www.onlyoffice.com/blog/2025/06/meet-onlyoffice-desktop-editors-v9-0) https://www.omgubuntu.co.uk/2025/06/onlyoffice-9-0-desktop-new-features-ai (https://www.omgubuntu.co.uk/2025/06/onlyoffice-9-0-desktop-new-features-ai) Lyon Goes Open Source (France's Third-Largest City) https://www.lyon.fr/actualite/action-municipale/la-ville-de-lyon-renforce-sa-souverainete-numerique (https://www.lyon.fr/actualite/action-municipale/la-ville-de-lyon-renforce-sa-souverainete-numerique) https://www.theregister.com/2025/06/26/lyonleavingmicrosoft/ (https://www.theregister.com/2025/06/26/lyon_leaving_microsoft/) Support the show https://tuxdigital.com/membership (https://tuxdigital.com/membership) https://store.tuxdigital.com/ (https://store.tuxdigital.com/)

Dating apps aren’t broken; they’re working exactly as designed. And for Black women, that’s a problem. In this season premiere of IRL: Online Life is Real Life, host Bridget dives into how dating apps reinforce harmful beauty standards rooted in whiteness, automating what researcher Dr. Apryl Williams calls “sexual racism” into the user experience. This is the first episode in a four-part series from Mozilla and PRX exploring how tech shapes our most personal decisions. Subscribe now to catch every episode: irlpodcast.orgSee omnystudio.com/listener for privacy information.

Patch Tuesday. Mozilla  patches two critical FireFox security flaws. A critical flaw in Salesforce OmniStudio exposes sensitive customer data stored in plain text. The Badbox botnet continues to evolve. AI-powered “ghost students” enrolling in online college courses to steal government funds. Hackers steal nearly 300,000 vehicle crash reports from the Texas Department of Transportation. ConnectWise rotates its digital code signing certificates. The chair of the House Homeland Security Committee announces his upcoming retirement. Our guest is Matt Radolec, VP of Incident Response, Cloud Operations & SE EU from Varonis, wondering if AI may be the Cerberus of our time. Friendly skies…or friendly spies?  Remember to leave us a 5-star rating and review in your favorite podcast app. Miss an episode? Sign-up for our daily intelligence roundup, Daily Briefing, and you'll never miss a beat. And be sure to follow CyberWire Daily on LinkedIn. CyberWire Guest On our Industry Voices segment, we have Matt Radolec, VP of Incident Response, Cloud Operations & SE EU from Varonis, sharing insights on AI: The Cerberus of our time. You can hear Matt's full interview here. The State of Data Security: Quantifying AI's Impact on Data Risk report from Varonis reveals how much sensitive data is exposed and at risk in the AI era. Learn more and get State of Data Security Report. Selected Reading Microsoft warns of 66 flaws to fix for this Patch Tuesday, and two are under active attack (The Register) Microsoft slows Windows 11 24H2 Patch Tuesday due to a 'compatibility issue'  (The Register) ICS Patch Tuesday: Vulnerabilities Addressed by Siemens, Schneider, Aveva, CISA (SecurityWeek) Firefox Patches Multiple Vulnerabilities That Could Lead to Browser Crash (Cyber Security News) Salesforce OmniStudio Vulnerabilities Exposes Sensitive Customer Data in Plain Text (Cyber Security News) CISO who helped unmask Badbox warns: Version 3 is coming (The Register) How Scammers Are Using AI to Steal College Financial Aid  (SecurityWeek) 300K Crash Reports Stolen in Texas DOT Hack (BankInfoSecurity) ConnectWise rotating code signing certificates over security concerns (Bleeping Computer) House Homeland Chairman Mark Green's departure could leave congressional cyber agenda in limbo (CyberScoop) Airlines Don't Want You to Know They Sold Your Flight Data to DHS (404 Media) Want to hear your company in the show? You too can reach the most influential leaders and operators in the industry. Here's our media kit. Contact us at cyberwire@n2k.com to request more info. The CyberWire is a production of N2K Networks, your source for strategic workforce intelligence. © N2K Networks, Inc. Learn more about your ad choices. Visit megaphone.fm/adchoices

There are many misconceptions and overblown promises when it comes to AI. The reality is that Artificial Intelligence is a useful tool that's here to stay. When it's done right, AI seamlessly becomes part of our everyday life systems but when poorly programmed or intentionally misused by human intelligence, it easily becomes the ‘snake oil' of our time. How do we decipher fact from fiction when it comes to AI and how do we protect children from possible long-term adverse impacts?To glean strategies for reducing unknown or harmful influences of AI, Harvesting Happiness Podcast Host Lisa Cypers Kamen speaks with a Senior Fellow at Mozilla, Sayash Kapoor.Sayash draws on his book, AI Snake Oil: What Artificial Intelligence Can Do, What It Can't, and How to Tell the Difference, to guide us in critically evaluating AI claims and understanding its true capabilities and limitations. He offers insights about how to be practically skeptical in an AI-driven world and uncover the truth behind the hype.This episode is proudly sponsored by:Quince—Offers high-quality essentials, home decor, and furnishings at radically low prices.Visit Quince.com/hhtr for free shipping on your order and three hundred and sixty-five-day returns using quince.com/hhtr. Like what you're hearing?WANT MORE SOUND IDEAS FOR DEEPER THINKING? Check out More Mental Fitness by Harvesting Happiness bonus content available exclusively on Substack and Medium.

Mozilla kills Pocket and Fakespot, SteamOS is now available for devices other than the Steam Deck, Nextcloud's Android app was missing key functionality until they made a public stink about it, WSL is now open source, there's a new open source command-line text editor in Windows, and more.   News Investing in what moves the... Read More

There are many misconceptions and overblown promises when it comes to AI. The reality is that Artificial Intelligence is a useful tool that's here to stay. When it's done right, AI seamlessly becomes part of our everyday life systems but when poorly programmed or intentionally misused by human intelligence, it easily becomes the ‘snake oil' of our time. How do we decipher fact from fiction when it comes to AI and how do we protect children from possible long-term adverse impacts?To glean strategies for reducing unknown or harmful influences of AI, Harvesting Happiness Podcast Host Lisa Cypers Kamen speaks with a Senior Fellow at Mozilla, Sayash Kapoor.Sayash draws on his book, AI Snake Oil: What Artificial Intelligence Can Do, What It Can't, and How to Tell the Difference, to guide us in critically evaluating AI claims and understanding its true capabilities and limitations. He offers insights about how to be practically skeptical in an AI-driven world and uncover the truth behind the hype.This episode is proudly sponsored by:Quince—Offers high-quality essentials, home decor, and furnishings at radically low prices.Visit Quince.com/hhtr for free shipping on your order and three hundred and sixty-five-day returns using quince.com/hhtr. Like what you're hearing?WANT MORE SOUND IDEAS FOR DEEPER THINKING? Check out More Mental Fitness by Harvesting Happiness bonus content available exclusively on Substack and Medium.

This week, we discuss OpenAI acquiring io, Salesforce buying Informatica, and the future of AI agents. Plus, Coté shares details about a sensitive procedure and ceiling puzzles. Watch the YouTube Live Recording of Episode (https://www.youtube.com/live/pIp9PXs0SDQ?si=rfo5EdiQCSn_qJo4) 521 (https://www.youtube.com/live/pIp9PXs0SDQ?si=rfo5EdiQCSn_qJo4) Runner-up Titles Don't ride a bike for a week You've got to focus on the important things What's your NPS score? It all comes back to CSV THIS IS MY AI. THERE ARE MANY LIKE IT BUT THIS ONE'S MINE. You need an MCP.Factory Crimp and Hope Rundown Sam & Jony introduce io (https://openai.com/sam-and-jony/) Salesforce to acquire data management company Informatica in $8 billion deal (https://www.cnbc.com/2025/05/27/salesforce-informatica-deal.html) Agentic New capabilities for building agents on the Anthropic API (https://www.anthropic.com/news/agent-capabilities-api?utm_source=aibreakfast.beehiiv.com&utm_medium=newsletter&utm_campaign=openai-developing-a-wearable-device&_bhlid=1206587f1dbd9e1b358248d2b751bb04aca32ebe) Highlights from the Claude 4 system prompt (https://simonwillison.net/2025/May/25/claude-4-system-prompt/) Anthropic brings web search to free Claude users (https://www.engadget.com/ai/anthropic-brings-web-search-to-free-claude-users-224222689.html?guccounter=1&guce_referrer=aHR0cHM6Ly9uZXdzLmdvb2dsZS5jb20v&guce_referrer_sig=AQAAALjAuhaCUa960tMiV3B93BX-_2-Fq04ZYcRiw3-E8JOtY391-_OpEx7nj0HR6NVKVUUhqEZh0Az3M8wmsQhOkhickrd_80juraYFjgYIRNJobHYtZdUe3RvWsrTerX4cpTzkvysIumyb8_R4-e2ZfMMaofZrDNKJsZnLQa_kzZaO) SWE Agents Too Cheap To Meter, The Token Data War, and the rise of Tiny Teams (https://www.latent.space/p/token-data-war?utm_source=post-email-title&publication_id=1084089&post_id=164381135&utm_campaign=email-post-title&isFreemail=true&r=bucq&triedRedirect=true&utm_medium=email) Google CEO Sundar Pichai on the next AI platform shift (https://www.theverge.com/decoder-podcast-with-nilay-patel/673638/google-ceo-sundar-pichai-interview-ai-search-web-future) MCP Registry (https://github.com/modelcontextprotocol/registry) Anil Dash thoughts on MCP Servers (https://bsky.app/profile/anildash.com/post/3lq27z2k6cc2s) If AI Can Play Dungeons & Dragons, It Can Run Your ERP (https://thenewstack.io/if-ai-can-play-dungeons-dragons-it-can-run-your-erp/) MCP is the RSS of AI (https://thenewstack.io/mcp-is-rss-for-ai-more-use-cases-for-model-context-protocol/) Relevant to your Interests Mistral's new Devstral AI model was designed for coding | TechCrunch (https://techcrunch.com/2025/05/21/mistrals-new-devstral-model-was-designed-for-coding/) “Microsoft has simply given us no other option,” Signal says as it blocks Windows Recall (https://arstechnica.com/security/2025/05/signal-resorts-to-weird-trick-to-block-windows-recall-in-desktop-app/) From the ExperiencedDevs community on Reddit: My new hobby: watching AI slowly drive Microsoft employees insane (https://www.reddit.com/r/ExperiencedDevs/comments/1krttqo/my_new_hobby_watching_ai_slowly_drive_microsoft/) KrebsOnSecurity Hit With Near-Record 6.3 Tbps DDoS (https://krebsonsecurity.com/2025/05/krebsonsecurity-hit-with-near-record-6-3-tbps-ddos/) Microsoft Build 2025 Keynote: Everything Revealed, in 14 Minutes (https://www.youtube.com/watch?v=ZGgBuJE0-s4) Once worth over $1B, Microsoft-backed Builder.ai is running out of money (https://techcrunch.com/2025/05/20/once-worth-over-1b-microsoft-backed-builder-ai-is-running-out-of-money/) Meta launches program to encourage startups to use its Llama AI models (https://techcrunch.com/2025/05/21/meta-launches-program-to-encourage-startups-to-use-its-llama-ai-models/?utm_source=aibreakfast.beehiiv.com&utm_medium=newsletter&utm_campaign=openai-developing-a-wearable-device&_bhlid=3602222175ca608068c014ef12dcf2a5d1d6536f) Digg founder Kevin Rose offers to buy Pocket from Mozilla (https://techcrunch.com/2025/05/23/digg-founder-kevin-rose-offers-to-buy-pocket-from-mozilla/) AWS Breaking Changes (https://github.com/SummitRoute/aws_breaking_changes) Cloud computing is too important to be left to the Big Three (https://on.ft.com/43FnwZc) How to Lead an All-Hands After Delivering Bad News (https://hbr.org/2025/05/how-to-lead-an-all-hands-after-delivering-bad-news) Matt Hicks: CentOS move not popular, but better for open source (https://www.techzine.eu/blogs/infrastructure/131813/matt-hicks-centos-move-not-popular-but-better-for-open-source/) How tech workers really feel about work right now (https://www.lennysnewsletter.com/p/how-tech-workers-really-feel-about) Exposed: How ransom gang Lockbit negotiates payments (https://ia.acs.org.au/article/2025/exposed--how-ransom-gang-lockbit-negotiates-payments.html) Behind the Curtain: Top AI CEO foresees white-collar bloodbath (https://www.axios.com/2025/05/28/ai-jobs-white-collar-unemployment-anthropic) U.S. public wants business to move slower on AI: Axios Harris 100 poll (https://www.axios.com/2025/05/27/ai-harris-100-poll-move-slow) Musk's xAI signs Telegram tie-up as billionaire ‘bromance' blooms (https://on.ft.com/45tYlej) In 3.5 years, Notepad.exe has gone from “barely maintained” to “it writes for you” (https://arstechnica.com/gadgets/2025/05/in-3-5-years-notepad-exe-has-gone-from-barely-maintained-to-it-writes-for-you/) After 15 years, WhatsApp is finally ready for the iPad (https://www.theverge.com/news/674596/whatsapp-ipad-app-meta-availability) Nonsense Good Fortune Burger renamed its menu items to sound like office supplies (https://x.com/BrianRoemmele/status/1925648371508810182) Conferences POST/CON 25 (https://postcon.postman.com/2025/), June 3-4, Los Angeles, CA, Brandon representing SDT. Register here for free pass (https://fnf.dev/43irTu1) using code BRANDON (https://fnf.dev/43irTu1) (limited to first 20 People) Contract-Driven Development: Unite Your Teams and Accelerate Delivery (https://postcon.postman.com/2025/session/3022520/contract-driven-development-unite-your-teams-and-accelerate-delivery%20%20%20%20%20%208:33) by Chris Chandler SREDay Cologne, June 12th, 2025 (https://sreday.com/2025-cologne-q2/#tickets) - Coté speaking, discount: CLG10, 10% off. SDT News & Community Join our Slack community (https://softwaredefinedtalk.slack.com/join/shared_invite/zt-1hn55iv5d-UTfN7mVX1D9D5ExRt3ZJYQ#/shared-invite/email) Email the show: questions@softwaredefinedtalk.com (mailto:questions@softwaredefinedtalk.com) Free stickers: Email your address to stickers@softwaredefinedtalk.com (mailto:stickers@softwaredefinedtalk.com) Follow us on social media: Twitter (https://twitter.com/softwaredeftalk), Threads (https://www.threads.net/@softwaredefinedtalk), Mastodon (https://hachyderm.io/@softwaredefinedtalk), LinkedIn (https://www.linkedin.com/company/software-defined-talk/), BlueSky (https://bsky.app/profile/softwaredefinedtalk.com) Watch us on: Twitch (https://www.twitch.tv/sdtpodcast), YouTube (https://www.youtube.com/channel/UCi3OJPV6h9tp-hbsGBLGsDQ/featured), Instagram (https://www.instagram.com/softwaredefinedtalk/), TikTok (https://www.tiktok.com/@softwaredefinedtalk) Book offer: Use code SDT for $20 off "Digital WTF" by Coté (https://leanpub.com/digitalwtf/c/sdt) Sponsor the show (https://www.softwaredefinedtalk.com/ads): ads@softwaredefinedtalk.com (mailto:ads@softwaredefinedtalk.com) Recommendations Brandon: Cable Matters 100-Pack Cat 6 Pass Through RJ45 Connectors (https://www.amazon.com/Cable-Matters-Through-Stranded-Connectors/dp/B07PXMN2VK/?_encoding=UTF8&pd_rd_w=Pk41A&content-id=amzn1.sym.255b3518-6e7f-495c-8611-30a58648072e%3Aamzn1.symc.a68f4ca3-28dc-4388-a2cf-24672c480d8f&pf_rd_p=255b3518-6e7f-495c-8611-30a58648072e&pf_rd_r=B1A17R2AA5KDCVW0K92W&pd_rd_wg=kzlWJ&pd_rd_r=4c4d02be-bbb0-4de7-bc28-242f31111d53&ref_=pd_hp_d_atf_ci_mcx_mr_ca_hp_atf_d&th=1) Matt: Electric Foot Massager (https://www.amazon.com.au/dp/B0C9HJJ7ZR) Coté: Big Mac, inspired by Kenji's home brew (https://youtu.be/52Gf_0odraY?si=74hGU4qqF5gjgZpp).

After more than a month of testimony, the Meta antirust trial is beginning to slow down. The Google search remedies trial, meanwhile, is about to heat up again, with closing arguments coming soon. The Verge's Lauren Feiner has been in the DC courthouse for all of it, and has finally emerged to tell us about what she's seen, and learned, from two all-important monopoly trials. After that, The Verge's Victoria Song tells us about her latest experience with Google's smart glasses prototypes, what Google is doing differently from Meta and Apple, and what she thinks Jony Ive and OpenAI might be building. Finally, we answer a question on the Vergecast Hotline about what to do now that Mozilla is shutting down Pocket. FTC v. Meta: The antitrust battle over WhatsApp and Instagram Did WhatsApp really need Meta? Why the FTC argues Meta is a closer rival to MeWe than TikTok Instagram CEO testifies about competing with TikTok: ‘You're either growing, or you're slowly dying' Android XR is getting stylish partners in Warby Parker, Gentle Monster Xreal teases Project Aura smart glasses for Android XR We tried on Google's prototype AI smart glasses Android XR and Project Moohan hands-on: Gemini is the killer app Mozilla is shutting down Pocket Raindrop.io Instapaper Matter Wallabag Readwise Reader Email us at vergecast@theverge.com or call us at 866-VERGE11, we love hearing from you. Learn more about your ad choices. Visit podcastchoices.com/adchoices

The Wayland-only future is screaming toward us, Mozilla pulls the plug on Pocket, and Steam OS releases Go Country. Microsoft Open Sources WSL; Edit; and more, Gnome needs help with documentation, and Ubuntu goes Chrony. For tips we have zrun for making your own zstd enabled program, more pw-cli howto, y-cruncher for setting number-crunching records, and lsmem and chmem just in case your system has hot-swappable ram. You can see the show notes at https://bit.ly/3H8Ax5P and have fun! Host: Jonathan Bennett Co-Hosts: Rob Campbell, Jeff Massie, and Ken McDonald Download or subscribe to Untitled Linux Show at https://twit.tv/shows/untitled-linux-show Want access to the ad-free video and exclusive features? Become a member of Club TWiT today! https://twit.tv/clubtwit Club TWiT members can discuss this episode and leave feedback in the Club TWiT Discord.

Timestamps: 0:00 honestly i still don't know 0:09 SteamOS update for 3rd party devices! 1:29 OpenAI buys Jony Ive's company 2:46 Veo 3 goes viral, Claude 4 4:07 Scentbird! 5:24 QUICK BITS INTRO 5:31 Xiaomi Xring O1 6:14 Intel Arc B770 lives 7:08 Mozilla kills Pocket, Fakespot 7:48 Wacky Computex stuff! NEWS SOURCES: https://lmg.gg/SSldf Learn more about your ad choices. Visit megaphone.fm/adchoices

The UK's Ministry of Justice suffers a major breach. Mozilla patches two critical JavaScript engine flaws in Firefox. Over 200,000 patients of a Georgia-based health clinic see their sensitive data exposed. Researchers track increased malicious targeting of iOS devices. A popular printer brand serves up malware. PupkinStealer targets Windows systems. An Alabama man gets 14 months in prison for a sim-swap attack on the SEC. Our guest is Ian Tien, CEO at Mattermost, sharing insights on enhancing cybersecurity through effective collaboration. Ethical Hackers win the day at Pwn2Own Berlin.  Remember to leave us a 5-star rating and review in your favorite podcast app. Miss an episode? Sign-up for our daily intelligence roundup, Daily Briefing, and you'll never miss a beat. And be sure to follow CyberWire Daily on LinkedIn. CyberWire Guest On today's Industry Voices segment, we are joined by Ian Tien, CEO at Mattermost at RSAC 2025, who is sharing insights on enhancing cybersecurity through effective collaboration. Check out Ian's blog on “What's Next for Cybersecurity Teams? AI, Automation & Real-Time Workflows.” Listen to Ian's interview here. Selected Reading Hackers steal 'significant amount of personal data' from Ministry of Justice in brazen cyber-attack (Daily Mail Online) M&S and Co-Op: BBC reporter on talking to the hackers (BBC) 210K American clinics‘ patients had their financial data leaked (Cybernews) 480,000 Catholic Health Patients Impacted by Serviceaide Data Leak (SecurityWeek) Over 40,000 iOS Apps Found Exploiting Private Entitlements, Zimperium (Hackread) This printer company served you malware for months and dismissed it as false positives (Neowin) Hack of SEC social media account earns 14-month prison sentence for Alabama man (The Record) Hackers Earn Over $1 Million at Pwn2Own Berlin 2025 (SecurityWeek) Share your feedback. We want to ensure that you are getting the most out of the podcast. Please take a few minutes to share your thoughts with us by completing our brief listener survey as we continually work to improve the show. Want to hear your company in the show? You too can reach the most influential leaders and operators in the industry. Here's our media kit. Contact us at cyberwire@n2k.com to request more info. The CyberWire is a production of N2K Networks, your source for strategic workforce intelligence. © N2K Networks, Inc. Learn more about your ad choices. Visit megaphone.fm/adchoices

It's go time: The biggest Patch Tuesday of 2025 sets the stage for 2025! Microsoft has finally revealed whether it will further extend Windows 10 support past October (it won't). Also, Microsoft designed notifications in Windows 11 to be annoying and pointless, so Paul has some advice. Plus, Proton Drive gets a long awaited albums feature, and more on the way.Windows 11 Recall (preview) and Click to Do (preview) come to stable for the first time Let's give Microsoft a bit of credit for this one non-reported behavior Also: Improvements to Settings, Narrator, Start, Phone Link, Widgets, File Explorer You knew this was coming: Microsoft now testing a "Hey, Copilot" feature It's opt-in and an alternative to holding down Alt + Spacebar for two seconds Microsoft discusses the new Start design and it's not a s#$t show like it was three years ago No builds for the second Friday in a row Improvements to Settings AI agent, intelligent text actions in Click to Do, a few small changes come to 24H2 in Dev and Beta channels Copilot Vision gets Highlights and 2-App Support across all channels Google's big Android reveal includes Material Expressive, big Wear OS update. Android, like Windows 11 (and iOS) is just being updated all the time now Windows 10 Extended support program Will support Microsoft 365 on Windows 10 through October 2028 Those time frames are identical So what about those Surface PCs that can't upgrade to Windows 11? Microsoft has an answer (for all unsupported PCs) and it's not as cynical as you think Microsoft quietly discontinued entry-level 13.8-inch Surface Laptop and 13-inch Surface Pro when it introduced those smaller new models last week Layoffs Microsoft just made $70 billion, so naturally it's laying off employees. How to explain this? The FTC's losing streak against Microsoft continues A proposal for solving the "Mozilla problem" in U.S. v. Google Fortnite could return to the iPhone App Store as soon as today AI OH MY GOD IS THERE NO AI NEWS FOR ONCE. OK, three small items OpenAI brings OneDrive and SharePoint integration with ChatGPT for paid business customers "AI mode" could replace "I'm feeling lucky" on the Google home page Spotify's AI DJ keeps improving Dev Build is next week in Seattle, a few thoughts .NET 10 Preview 4 is out Xbox & Games Today's the day: DOOM: The Dark Ages goes live at 8:00 ET tonight! Xbox Insiders can now play cloud-enabled games with mouse and keyboard Paul reviews the Backbone Pro controller Nintendo revenues slide big ahead of Switch 2 - 15m consoles expected in first year Sony sold 18.5 million PS5s in the most recent fiscal year, down 11 percent YOY Tips & Picks Tip of the week: Windows 11 notifications make iOS look sophisticated App pick of the week: Proton Drive RunAs Radio this week: Active Directory in 2025 with Liz Tesch Brown liquor pick of the week: Limeburners Albany Tawny Cask These show notes have been truncated due to length. For the full show notes, visit https://twit.tv/shows/windows-weekly/episodes/932 Hosts: Leo Laporte, Paul Thurrott, and Richard Campbell Sponsors: 1password.com/windowsweekly threatlocker.com/twit uscloud.com

The remedy phase of one of the antitrust cases against Google wrapped up last week and the judge is expected to issue his decision by August on how the company must address its monopoly in search. One option suggested by the Justice Department: ban Google from paying browsers to make its search engine the default. But Mozilla, the developer of the independent Firefox browser, has opposed this remedy. Marketplace's Meghan McCarty Carino spoke with Laura Chambers, CEO of the Mozilla Corporation, about how the move would be crippling for smaller browsers like theirs.

The remedy phase of one of the antitrust cases against Google wrapped up last week and the judge is expected to issue his decision by August on how the company must address its monopoly in search. One option suggested by the Justice Department: ban Google from paying browsers to make its search engine the default. But Mozilla, the developer of the independent Firefox browser, has opposed this remedy. Marketplace's Meghan McCarty Carino spoke with Laura Chambers, CEO of the Mozilla Corporation, about how the move would be crippling for smaller browsers like theirs.