Podcasts about RTC

CRASHOUTS | Taos Soldier does the unthinkable | Balloon Fiesta is back | Bad Bunny's Super Bowl SAP | Did Cardi B cross the line? - RTC.EP124

Doctors Mark Williams and Attorney Sonya Madison begin season six of the RTC.

Conversation starts at 5:45 In this "RTC on the Road" episode (recorded after the Smith's wedding), Marc and Fuller tackle four challenging faith questions: What does trusting God look like in everyday life? How do you keep faith when life falls apart? Have you ever felt like God was silent? And when have you had to forgive someone who didn't deserve it? The conversation gets real quickly as they explore the difference between first-world problems and genuine crisis, the balance between taking action and trusting God's sovereignty, and why basing faith on feelings can be dangerous during difficult seasons. The discussion turns deeply personal when they address forgiveness. Marc shares his honest struggle with forgiving those who have hurt his family through divorce, while Fuller opens up about his own journey forgiving parents who ruled by fear rather than love. They examine the difference between forgiveness and restoration, the role of boundaries in relationships, and how the church should handle abuse and betrayal. This unscripted conversation offers raw, honest perspectives on faith's most challenging questions without easy answers or spiritual platitudes. Learn More about RTC: https://realtalkchristianpodcast.com/ Join the RTC Online Facebook community: https://www.facebook.com/groups/realtalkchristianpodcast

In this episode, we're joined by Dr. Kassam to explore the origins and evolution of Reverse Shoulder Arthroplasty (RSA), from its early rationale in treating RTC arthropathy to the groundbreaking Grammont design. We discuss the core components of RSA, the critical role of center of rotation (COR), glenoid and humeral lateralization, and their impact on biomechanics. We also talk about surgical considerations like scapular notching prevention, baseplate positioning, inlay vs onlay humeral stems, and the significance of neck-shaft angles. Dr. Hafiz Kassam is a board-certified orthopedic surgeon specializing in shoulder reconstruction. He serves as HOI's medical director of shoulder reconstruction. Dr. Kassam has extensive experience in complex shoulder and elbow reconstruction and sports injuries. Dr. Kassam pursued his education and training at world-class institutions in three countries. After completing his undergraduate work and medical training in the United Kingdom, he completed his residency at the University of Toronto, which is one of the largest and most academically productive programs in North America. He then moved to the USA and completed his shoulder and elbow fellowship training at Yale University. He is an expert in minimally invasive techniques in shoulder and elbow joint replacement as well as advanced arthroscopy, traumatic reconstruction and non-operative treatments. He has performed more than 1,000 shoulder replacements and arthroscopic reconstructions in his career so far. Believing in evidence-based choices for his patients and improving outcomes in modern orthopedics, Dr. Kassam is a well-published clinician-scientist. He has authored numerous original scientific research studies, technique guides, and textbook chapters, presenting his work on both the national and international stages. He is the program chair for the Northern California Shoulder and Elbow Course and sits on the Editorial Board for the Journal of Shoulder and Elbow Arthroplasty. Goal of episode: To develop a baseline knowledge of RSA design. In this episode, we provide answers to questions you may have on reserve shoulder arthroplasty, like: What was the original reason for RSA? What are the basic components of an RSA?  What is the importance of COR with regard to RSA? What is glenoid lateralization, and of what importance is it? Does it matter where you get your lateralization from? Is inferior placement of the baseplate on the glenoid a good thing to do? And much more!

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

En este programa hacemos un repaso a algunas noticias de la actualidad commodoriana y a los lanzamientos de las últimas semanas, y vemos la revista Compute!'s Gazette de mayo de 1988. También hablaremos de todo lo que se podrá ver y hacer en el Explora Commodore que celebraremos el próximo sábado 20/9 en el Espai Josep Bota de Barcelona. Todo esto lo veremos con el equipo habitual formado por David Asenjo (https://twitter.com/darro99), Toni Bianchetti (https://twitter.com/seuck), Narciso Quintana "Narcisound" (https://twitter.com/narcisound), Jonatan Jiménez (https://twitter.com/jsabreman) y Paco Herrera (https://twitter.com/pacoblog64). Las noticias comentadas son: - Últimas noticias de la nueva Commodore (video Peri, Compute's sep, GUI64 (Toni): https://youtu.be/uR5oW7YFqfQ?feature=shared ; https://www.youtube.com/watch?v=CrBGqXL5wP4 - Presentación del The A1200 de RetroGames Ltd, asociado al lanzamiento de The Settlers II Gold Edition para Amiga: https://www.youtube.com/watch?v=-Ygh74moytI; https://lookbehindyou.de/en/product/thesettlers2amiga/# - Liberado el codigo original de BASIC 1.1 para MOS 6502: https://hipertextual.com/software/microsoft-libera-6502-basic-codigo-abierto - VIC64-T9K: VIC-II, 6502, 64K de RAM y un puerto UART todo en uno: https://github.com/joachimdraeger/vic64-t9k - Nuevos videos del Mimic Spartan para Commodore 64.: https://www.youtube.com/watch?v=iIOWeAflOUw; https://www.youtube.com/watch?v=X14qr8Ouom8 - Nueva demo para CBM 8296: https://www.youtube.com/watch?v=n87d7j0hfOE - Lanzamiento del C64 mini Black Edition: https://retrogames.biz/products/thec64-mini-black/ - Allister Brimble lanza un album musical para conmemorar los 40 años de Amiga: https://allisterbrimble.bandcamp.com/album/amiga-40 - Problema con aduanas y revistas británicas. - Nuevo vídeo sobre la historia del Drean Commodore 64 en Argentina.: https://www.youtube.com/watch?v=vGX5Iujb-Eo - TRIBUTE, nuevo documental sobre el videojuego español estrenado en Prime: https://www.youtube.com/watch?v=YeHrx9WFuko - Nueva campaña de Kickstarter: Huge Amiga Cheat Codes Book: https://www.kickstarter.com/projects/bendani/huge-amiga-cheat-codes-book-hundreds-of-games-covered - Actualización de GTW64: https://www.gamesthatwerent.com/gtw64 - Herramienta de programación de cartuchos de 2MB para C64 con una Raspberry Pi: https://www.youtube.com/watch?v=As3GDnLnZ3U - Preservado material gráfico del CES 1985 y escaneos canadienses de Commodore: https://drive.google.com/drive/folders/16TPUVmfl2uBhYjdjB_iI_ufHzqgLa4ho?usp=drive_link - Preservado el Amiga Report Magazine: https://bigbookofamigahardware.com/amigareport/?fbclid=IwQ0xDSwMYGPdjbGNrAxgY22V4dG4DYWVtAjExAAEeOHXJZErDhqwOTx3HiGAGCr87TGngNc5st4kc6AGjGNbwlQsQmvoDnaYbC_Y_aem_5SXPBo50rPvDP8NslmEeeg&sfnsn=scwspwa - Video sobre la Commodore 500E con la intervención de Leonard Tramiel: https://www.youtube.com/watch?v=pSnOCFKQ5Os - Actualización del portal de demos c64.ch: https://c64.ch/ - Desarrollo de RTC para VIC-20: https://hackaday.io/project/203682-vic-20-rtc - Desarrollo del chip 6540-010 Character ROM para PET 2001 : http://blog.tynemouthsoftware.co.uk/2025/08/pet-2001-6540-010-character-rom-replacement.html - Actualización del portal de intros intros.c64: https://intros.c64.org/ - Nueva convocatoria de SEUCK COMPO: https://tnd64.unikat.sk/Seuck_Compo_2025_Part2.html - Reemplazo del chip Amber disponible en PCB Way: https://www.pcbway.com/project/shareproject/Commodore_Amiga_Amber_Replacement_Marine_42127eea.html - Apidya Special anunciado para 2026: https://www.indieretronews.com/2025/08/apidya-special-authentic-24-bit-pixel.html Actualizaciones: - RedPill 0.9.56: https://aminet.net/package/dev/misc/REDPILLGameCreator - Versatile Amiga Test Program v.6.59: https://aminet.net/package/util/misc/VATestprogram - SID Known v1.29: https://csdb.dk/release/?id=254223 Los juegos y programas nuevos comentados son: - "H.E.R.O. Is Back (LC-GAMES, C64): https://lowcarb.itch.io/hero-is-back-c64 - Donkey Kong (Varios, Plus/4): https://www.youtube.com/watch?v=ekmc1Px4AMc - Phil's Adventure (Plus/4): https://www.youtube.com/watch?v=81jaVG41ook - Return to Belmar's Castle (Commodore Plus, C64): https://commodore-plus.itch.io/retrurn-to-castle-belmar - City Cat (polytricity, C64): https://polytricity.itch.io/citycat-prowl; https://www.youtube.com/watch?v=vARDDLxQ49Q - Outrun (Amiga edition) (reassembler, Amiga): https://reassembler68k.itch.io/outrun-amiga-edition; https://youtu.be/5PpR-Dm3-nU?si=NOrtZYd8Tsvm4d00 - Musketeer (Psytronik, C64): https://psytronik.itch.io/musketeer - Retroskoi Sharp (sinte para C64) (, C64): https://csdb.dk/release/?id=255391 - Qoud Init Exit IIo (C64): https://retream.itch.io/quod-init-exit-iio - The Gate (allanon71, Amiga): https://allanon71.itch.io/the-gate - Neon Noir (steamknight, Amiga): https://steamknight.itch.io/neonnoir - Desktop Dreams 64 (Back2the8bit, C64): https://back2the8bit.itch.io/desktop-dreams-64 - Svellas (Inofuto, Plus/4): https://plus4world.powweb.com/software/Svellas - US Championship V'ball (jotd666, Amiga): https://jotd666.itch.io/us-championship-vball - Danger Dennis (Justepyx, C64): https://justepyx.itch.io/dangerdennis - Bard's Tale (Csory, Plus/4): https://plus4world.powweb.com/software/Bards_Tale - Carrot Stew (Plus/4): https://plus4world.powweb.com/software/Carrot_Stew - Snake vs Bomb 2 (C64): https://tnd64.unikat.sk/s.html#SnakeVsBomb2 - Dig-Dug revival (LC-Games, C64): https://lowcarb.itch.io/dig-dug-revival-c64 - SoundFX Anywhere (4mat, C64): https://4mat.itch.io/soundfx-anywhere?t=Eipj1Lk92tRYoACMEC4EUQ - Devastator (backtothe8bits, VIC-20): https://backtothe8bits.itch.io/devastator - Space shooter Demo (Amiga): https://www.youtube.com/watch?v=BJZFJWvSuR4 - Scoonex (C64, C16, VIC20, PET): https://www.lemon64.com/forum/viewtopic.php?p=1057815#p1057815 - Beer Rescue (Justepyx, C64): https://justepyx.itch.io/beer-rescue - Black Tower (blueguard, C64): https://www.blueguard.de/Tower/index.htm - Zodiac Deluxe (Legion of doom, Plus/4): https://plus4world.powweb.com/software/Zodiac_Deluxe - Florida Man (NSkimN8r, C64): https://nskimn8r.itch.io/florida-man - Czołgi Party (Protovision, C64): https://csdb.dk/release/?id=254878 - Umi Bombs (KabutoCoder, C64): https://kabutocoder.itch.io/umi-bombs-c64 - Caprica Defense (Peter Otto, C64): https://www.blueguard.de/Caprica/index.htm1 - Speed Maze Rabbit (RetroProgrammation, C64): https://retroprogrammation.itch.io/speed-maze-rabbit - Phantom Leap (actualización) (hoogames2017, Amiga): https://hoogames2017.itch.io/phantom-leap - Dragon Wars (Csory, Plus/4): https://plus4world.powweb.com/software/Dragon_Wars - Dodge These Balls (Amiga): https://entwicklerx.itch.io/dodge-these-balls-amiga - Decade of Ruin (C64): https://alexlogachev.itch.io/decade-of-ruin

 Episode 391. We go belly-to-belly with Frank Perrelli (@fvp_iv • @treigninglab_ok) — NJ State Champion, Cornell NCAA All-American, 2x EIWA Champ, University National Champ, 4x U.S. Senior All-American & U.S. Open runner-up — now leading Treigning Lab Oklahoma, bringing Coach Sam Calavitta's performance system to Stillwater.In this episodeJersey roots ➝ Delbarton ➝ Cornell with Coach Rob Koll & Mike GreyFrom Spartan Combat RTC coach to building Treigning Lab OKScience vs. simplicity in wrestling trainingTesting that matters: VO₂ max (treadmill), RMR, body comp (BIA), HTMA (hair mineral analysis), targeted labsNutrition & weight cuts the right way (food-first, individualized micros, essential amino acids, omegas)What most wrestlers miss in S&C (breathing/diaphragm strength, recovery metrics)Working with elite athletes and prepping for Worlds (RBY, Trent Hidlay)Frank's daily routine (4am, red light, compression, training) & family life in StillwaterChapters 00:00 Cold open & ABR intro03:00 Taylor Ham vs. pork roll (NJ forever)06:40 Delbarton years, Coach Stoll & Guy Russo13:00 Cornell fit, culture, & academics (sink or swim)17:55 Mike Grey's impact & RTC years22:45 Meeting Coach Cal • Treigning Lab philosophy29:00 Testing stack: VO₂/RMR/BIA/HTMA → action plans34:45 The “eyeball test,” late-match fatigue, breathing work37:50 Cutting weight without ruining performance41:55 Cheats, inflammation, and staying dialed42:30 Macros vs. micros (EAAs, krill oil, food-first)50:55 Why Stillwater; building Treigning Lab OK52:00 Worlds prep (RBY, Trent) + Croatia trip57:55 Daily practices & favorite pods (Paul Chek shout)1:01:20 Guilty pleasure TV & sign-offGuest linksFollow Frank IG: @fvp_iv Follow The Treigning Lab Oklahoma IG:  @treigninglab_ok Website Follow & support Airey Bros RadioYouTube:Instagram:Black Sheep Endurance CoachingBuy Me a Coffee

Whether you want to admit it or not, you are in a battle. As Christians, we read that we are wrestle not against flesh above but against evil and spiritual forces beyond our comprehension, but so many Christians act as if nothing is happening around them. In this episode of RTC, you will get to hear the workshop that Marc and Fuller taught at Revive Fest in Leonidas, MI, as we continue our series "RTC on the Road!" Want to learn more about RTC, head over to our website at https://realtalkchristianpodcast.com/. And make sure you join the RTC Facebook community over at https://www.facebook.com/groups/realtalkchristianpodcast.

Scotty827 is back and hanging out with Reddit Talks Clash's own Liam!  As a fan of the RTC podcast (link below), Scotty gets to ask some questions he's wondered about Liam and his Clash Journey, his Titan clan family, and how he leads and organization his 9 (but technically 11 clans)! Plus, our take on the upcoming Legend League rework and since they're serving Pumpkin Spice everything, that means it's time to start planning ahead for Hammer Jam!  All that and everything Clashy! Listen to Liam, Rick, Sam, and Spencer on the Reddit Talks Clash Podcast! Website: Reddit Talks Clash  Podcast: Apple | Spotify   Support a Podcaster with a Creator Code: Coolrick from the RTC Podcast - Creator Code:  coolrick Spence rfrom the RTC Podcast  - Creator Code:  Spencer   Find Scotty and the podcast at: Clashofclanspodcast.com Contact the Show:  clashofclanspodcast@gmail.com or find us in House of EL!  

Christina Kantzavelos is a neurodivergent, and first-generation (third culture) Licensed Clinical Social Worker (LCSW), life coach, writer and chronic illness warrior.  She received both her BA and MSW from the University of California Los Angeles (UCLA) and her MLIS from San Jose State University (SJSU). Charmaine Husum RCAT, RTC, CT, DKATI, ​runs a private Art Therapy and Counselling practice (Centre of the Heart) on the traditional territories of the Blackfoot Confederacy (Siksika, Kainai, Piikani), the Tsuut'ina, the Îyâxe Nakoda Nations, and the Métis people of Calgary Alberta, Canada, seeing clients in person and online both regionally and internationally.  She is also an Artist, Kundalini Yoga teacher and trained in the somatic approach of Integrative Body Psychotherapy and Reiki. In This EpisodeChristina's websitehttps://www.centreoftheheart.com/about.html You can learn more about what I do here:The Trauma Therapist Newsletter: celebrates the people and voices in the mental health profession. And it's free! Check it out here: https://bit.ly/4jGBeSaThe Trauma Therapist Podcast:  I interview thought-leaders in the fields of trauma, mindfulness, addiction and yoga such as Peter Levine, Pat Ogden, Bessel van der Kolk and Bruce Perry. https://bit.ly/3VRNy8zBecome a supporter of this podcast: https://www.spreaker.com/podcast/the-trauma-therapist--5739761/support.

A producer who we've been keeping a steady eye on over the past year is Phoenix native RTC Shogun who not only makes stellar music but is also one of the co-hosts of the incredible producer series The Beatcast with our former guest Ill Al. We were able to get RTC to stop by the show this week to chop it up and have a really cool discussion on short notice! He described what it's been like on his almost 30 year run in music having learned and gravitated to production early on. Following a move to New Orleans RTC was able to return to Phoenix where he and some fellow Phoenix based producers founded Mind Spit Records, helping to build his repertoire in the local scene and beyond. Since that time RTC has continued to evolve in his creative process and he told us about what styles he's been gravitating towards recently. He also touched on his time with The Beatcast and what it has meant to him to be able to have a positive impact on the producer community through the amazing sample challenges and other events. With more new music and other cool content starting to line up we can't wait to see what's next and we thank RTC for stopping by once again!Submit a demo track(s) for release consideration with Proven Knowledge! - https://docs.google.com/forms/d/1l_h_XayHVqWIJHgTYyV5vGgThfRVEiBh8lw9SP8DrQw/viewform?edit_requested=trueConsider becoming a monthly supporter of the show by visiting the link here

What happens when your Christian convictions collide with today's cultural realities? How do you love people while staying true to biblical principles? And what do you do when you're too exhausted from ministry to actually live out your faith? Marc and Fuller tackle some of the hardest questions facing Christians today while driving to a wedding in Peru, Indiana. From the RTC Facebook group, listeners asked about everything from spiritual armor to same-sex weddings to passing faith down to the next generation. You'll hear Marc explain why the "belt of truth" keeps your pants up (literally and spiritually), while Fuller admits he's still working on that whole "gospel of peace" thing. They dive deep into the messy reality of LGBTQ wedding invitations - should you go or not? Marc shares a personal story about drawing loving boundaries, while Fuller wrestles with the ministry implications of saying yes or no. But maybe the most honest moment comes when they open up about their current faith struggles. Marc's trying to figure out how to raise kids who own their faith instead of just inheriting it. Fuller's battling the exhaustion that comes with being an elder - turns out spiritual leadership can actually make your faith harder, not easier. No easy answers here, just two dudes being real about the complicated business of living out biblical convictions in 2025. Join the conversation and see if you relate to their struggles. Recorded on the road - because sometimes the best conversations happen between destinations. ––– Learn more about RTC online at https://realtalkchristianpodcast.com/

Join Marc and Fuller as we start a new series called "RTC On The Road!" In this episode, Marc and Fuller are heading to an RTC listener's wedding and had some real, honest conversations. In this episode, they talk about three different questions, asked by RTC listeners. These questions are: "What's one way to stay spiritually disciplined when traveling or outside of routine?" "What's the difference between conviction and guilt in a Christian life?" "What's one mistake you made in your faith journey that taught you a lot?" You can learn more about our season 7 announcement by reading more below or visiting us online at https://realtalkchristianpodcast.com.   ––– A couple years ago, we changed up Real Talk Christian Podcast: Tighter episodes Less banter (that didn't last too long did it ) Every other week episodes We know that many folks want either (a) more episodes (b) more honest conversations from the heart. Honestly, we can't provide (a), but we are gunna provide (b)!   For the first handle of episodes of season 7, we're trying something different! We are going to be doing "RTC On The Road" where Fuller and I record honest conversations while driving around to different places!   Sure, it may not have the same flavor (and we definitely don't have show notes in front of us), but we're hoping that by us getting back to the roots of "real talk," you'll be able to join us in the honest conversations and honest processing of the Christian faith.

In this episode, Eric and Donaze, alongside special guest DJ Munkey, discuss all the craziness that has gone down this past week, including losing 2 amazing legends in their respective industries, Tessa's potential in WWE, and an exclusive interview with NWA National Promoter, Bryan Idol!Please stay up to date with everything going on in the community. Subscribe to our website at Respectthecombat.com to keep up to date with all the news and latest episodes of RTC that are being released!

This week's EYE ON NPI is tick tock o'clock, it's the Abracon Real-Time Clock with Integrated 32.768 kHz Crystal Oscillator (https://www.digikey.com/en/product-highlight/a/abracon/real-time-clock-with-integrated-32-768-khz-crystal-oscillator). It's a tiny and affordable all-in-one RTC that has everything ya want, and nothin' ya don't. With it's compact package size, it's half the BOM size of what most RTC's need, and has a high quality Abracon crystal (https://www.digikey.com/en/supplier-centers/abracon) already included! We've been using Abracon (https://www.digikey.com/en/supplier-centers/abracon) crystals and oscillators in our designs for decades - for example a 12.288 MHz Crystal (https://www.digikey.com/short/w2qvtnbr) adorns our VS1053 breakout board (https://www.adafruit.com/product/1381). That's not the only thing they're good at, but it's the name recognition they've got as a trusted supplier of quality, affordable crystals and oscillators. So it was not surprising for us to learn that they now have an integrated-crystal real time clock chip for sale. Real time clock chips are specialty low-cost chips that keep track of 'real time' (e.g. the month, day, year, hour, minute, second) so that the rest of the system can go into shutdown mode or lose power, without losing track of time. They also often have alarms so that the system can reboot out of deep sleep to perform some task at an assigned delay or timestamp. As you might expect, the important characteristics to look for in an RTC are accuracy - how close their internal timekeeping is to true time - and power draw - how long they can run off the secondary power source such as a super-cap or coin cell battery (https://www.digikey.com/en/products/detail/panasonic-energy/CR-1025-BN/269738). There's other characteristics that you may care about: the voltage range they can power off of, whether they support a secondary battery backup with auto-switchover, and of course the interface and capabilities like alarms The AB-RTC-XB-32.768KHZ-2-T3 (https://www.digikey.com/short/tp4tjzqz) has many of the things we like to look for in an RTC. First, is a standard I2C interface - most RTCs are, and this makes it easy to add to any microcontroller or microcomputer. Second is a wide operating voltage range for power and logic: 1.2V to 5.5V with both a power and IO power pad! That means it's great even for low voltage cores or 5V Arduino-compatibles, and you can have separate voltages if desired. Alongside those two pins there's also a separate VBat pin for backup battery with auto-switchover. That means when the main power cuts off, say because USB got unplugged, or the main Lipoly battery is drained, we'll switch over to a coin cell or super-cap. Of course, the big feature of this RTC is the built-in crystal. By integrating directly, they're able to have an SMT chip with no external crystal in a 3.2 x 2.5mm package - the same size as most crystals! According to the datasheet, the crystal has a 5 ±23ppm frequency stability at room temp 25℃. That translates to 28 ppm max: 86,400 × (28/1,000,000) = 2.42 seconds gain/loss per day. At the typical 'best case' of 5ppm, its 86,400 × (5/1,000,000) = 0.432 seconds per day. That's in-line with most RTC crystal specifications, although it wouldn't be considered 'high precision' since its not temperature compensated. Temp compensation is much more complex and expected, and most RTCs will get auto-sync from the controller via WiFi/BT/GPS to apply correction every day~month to get them back on track. If you need a compact real time clock with a flexible power supply setup and Abracon-quality crystal, the AB-RTC-XB-32.768KHZ-2-T3 (https://www.digikey.com/short/tp4tjzqz) is an excellent new product offering that's available and in stock at DigiKey right now! Order today and before your morning alarm goes off you'll have this chip in hand and ready to integrate into your next product design.

Last week, we received this question:  "I have a question that has been keeping me awake at night. If god predestines people to hell for his glory, is he still good? I understand that hell exists as the ultimate absence of God and as the final form of giving people over to sin. However I don't understand how god can allow sin to exist, knowing that he is sending his children to hell." In this bonus episode, you'll hear Marc's answer to this question.  Do you have a question that you'd like us to answer? Send us a DM on any of our socials or email us at realtalkchristianpodcast@gmail.com Learn more about RTC at https://realtalkchristianpodcast.com.

In this episode, Eric and Irving, alongside special guest DJ Munkey, discuss all the craziness that has gone down this past week, AJ Styles is returning to TNA, The Tribal Chief has returned, and an exclusive 1-on-1 interview with Adam EatonPlease stay up to date with everything going on in the community. Subscribe to our website at Respectthecombat.com to keep up to date with all the news and latest episodes of RTC that are being released!

Em Angola, ex-dirigente sindical na empresa de Transporte Coletivo Urbano de Luanda critica o cancelamento da greve. Em Moçambique, a desnutrição crónica está a flagelar as crianças da província de Nampula. Especialista aponta as razões. Analisamos ainda como os mais jovens estão a sofrer na pele e na mente, as consequências de manifestações violentas no Quénia.

Guests: Bill Thomas, Executive Director, RTC of Washoe County

Guests: Bill Thomas, Executive Director, RTC of Washoe County

Hear from Sparks firefighters and city council members, RTC, and The Nugget Casino as they get ready for the 25th anniversary of "Star-Spangled Sparks."See omnystudio.com/listener for privacy information.

No shortage of topics in the wrestling world this week!0:00 - Intro & Gable Game8:30 - Carter Starocci Allegations28:05 - Jax Forrest Wrestling in Fargo -> Budapest, Ranking Series32:10 - Tony Ramos Turns Down Northern Colorado Job36:00 - Current Coaching Scene Needs42:30 - Bo Basset Follow-up46:00 - Updated Thoughts on Bo's Destination51:00 - Bo & Iowa a Mutual Split?57:30 - Training at the RTC/250 Mile Radius58:45 - Traeger & Grill TalkBe sure to SUBSCRIBE to the podcast. NEW EPISODES WEEKLY/BIWEEKLY!Support the show & leave a 5-star rating and review on Apple Podcasts, and shop some apparel on BASCHAMANIA.com! For all partnership and sponsorship inquiries, email info@baschamania.com. BASCHAMANIA is a Basch Solutions Production. Learn more about Basch Solutions at BaschSolutions.com.SUBSCRIBE FOR VIDEO ON YOUTUBE!https://www.youtube.com/watch?v=pxf0TDH1TTYTWITTER: http://www.twitter.com/justinjbaschINSTAGRAM: http://www.instagram.com/jbaschBASCHAMANIA: https://www.instagram.com/baschamaniaARGUE WITH THE BRAIN ON TWITTER/X: https://x.com/MatScouts1

A Receita Federal publicou a Portaria RFB nº 549, de 13/06/2025 com o piloto para colaboração da sociedade na efetivação da CBS.

Pre-Assembled Adafruit PiCowbell Adalogger for Pico - MicroSD, RTC & STEMMA QT (0:08) https://www.adafruit.com/product/6355 Adafruit STSPIN220 Stepper Motor Driver Breakout Board (1:25) https://www.adafruit.com/product/6353 Visit the Adafruit shop online - http://www.adafruit.com ----------------------------------------- New nEw NEWs New Products, News, and more: https://www.adafruit.com/newsletter #newnewnew Shop for all of the newest Adafruit products: http://adafru.it/new Visit the Adafruit shop online - http://www.adafruit.com Adafruit on Instagram: https://www.instagram.com/adafruit LIVE CHAT IS HERE! http://adafru.it/discord Subscribe to Adafruit on YouTube: http://adafru.it/subscribe New tutorials on the Adafruit Learning System: http://learn.adafruit.com/ -----------------------------------------

Pre-Assembled Adafruit PiCowbell Adalogger for Pico - MicroSD, RTC & STEMMA QT (0:08) https://www.adafruit.com/product/6355 Adafruit STSPIN220 Stepper Motor Driver Breakout Board (1:25) https://www.adafruit.com/product/6353 Visit the Adafruit shop online - http://www.adafruit.com ----------------------------------------- New nEw NEWs New Products, News, and more: https://www.adafruit.com/newsletter #newnewnew Shop for all of the newest Adafruit products: http://adafru.it/new Visit the Adafruit shop online - http://www.adafruit.com Adafruit on Instagram: https://www.instagram.com/adafruit LIVE CHAT IS HERE! http://adafru.it/discord Subscribe to Adafruit on YouTube: http://adafru.it/subscribe New tutorials on the Adafruit Learning System: http://learn.adafruit.com/ -----------------------------------------

SmackDown (9/21/2000) was an unhinged, sex-fueled fever dream—and we're here to break down every wild second of it.

Send us a textFour former high-ranking Scientology members reveal the complex, troubling story of Marty Rathbun – once David Miscavige's right-hand man who later became one of Scientology's most significant defectors before mysteriously returning to defend the organization.• Marty Rathbun served as Inspector General of RTC and David Miscavige's primary enforcer despite escaping the Sea Org multiple times• Marc Headley recounts being physically assaulted by Rathbun during an interrogation when he refused to confess to something he hadn't done• After his final escape in 2004, Rathbun began speaking out against the church and created a blog that became a rallying point for the "Independent Scientology" movement• The Rathbuns faced extreme harassment from Scientology's "Squirrel Busters" who monitored their home 24/7 with cameras and followed their every move• Marty's wife Monique filed a promising harassment lawsuit against Scientology but inexplicably dismissed it, after which Marty began posting videos attacking former friends• Despite his betrayal, the hosts express compassion for Rathbun, acknowledging his early contributions to exposing Scientology and the complex trauma that likely influenced his actionsIf you or someone you know needs help leaving Scientology, contact The Aftermath Foundation at aftermathfoundation.org. You do not need to share your story publicly to receive assistance.Support the showBFG Store - http://blownforgood-shop.fourthwall.com/Blown For Good on Audible - https://www.amazon.com/Blown-for-Good-Marc-Headley-audiobook/dp/B07GC6ZKGQ/ref=tmm_aud_swatch_0?_encoding=UTF8&qid=&sr=Blown For Good Website: http://blownforgood.com/PODCAST INFO:Podcast website: https://www.buzzsprout.com/2131160 Apple Podcasts: https://podcasts.apple.com/us/podcast/blown-for-good-behind-the-iron-curtain-of-scientology/id1671284503 RSS: https://feeds.buzzsprout.com/2131160.rss YOUTUBE PLAYLISTS: Spy Files Playlist: https://www.youtube.com/playlist?list=PLWtJfniWLwq4cA-e...

WF SmackDown! Is live in Louisville, Kentucky on September 7, 2000!Chris Jericho battles X-Pac to kick off the show. Tazz joins Michael Cole on commentary. WWF Champion The Rock challenges WWF Tag Team Champions to a match later tonight. Rikishi takes on Chris Benoit but Right to Censor get involved. WWF Intercontinental Champion Eddie Guerrero verbally abuses Chyna backstage. The Acolytes and The Dudley Boyz compete in a Bar Room Brawl. Jerry the King Lawler chokes out Tazz with a strap. T&A battle Triple H in a Handicap Match which sees Kurt Angle save Stephanie McMahon-Helmsley from Test. WWF Intercontinental Champion Eddie Guerrero defends against Road Dogg. Afterwards, Guerrero attacks Road Dogg with the belt. Too Cool challenge RTC. The Undertaker takes on Kurt Angle but Chris Benoit gets involved. Triple H makes the save and attacks Angle while Undertaker hits Benoit with a Last Ride. Stephanie McMahon-Helmsley is pissed that The Game attacked Angle. Stone Cold Steve Austin appears from his house and promises to find out who ran him over last November and he will show up to WWF Unforgiven if no one comes clean. The Rock attacks Edge and Christian backstage which leads to WWF Champion The Rock defending the title against WWF Tag Team Champion Christian and Edge's replacement Kane. After the match Kane chokeslams The Rock through the announce table. 

WWF Raw Is War is live in Lexington, Kentucky on September 4, 2000!Test reveals that he called the cops on Triple H on WWF SmackDown! Kane battles Chris Benoit for the #1 Contendership but Benoit nails Kane with a Steel Chair and Rock lands a Rock Bottom to the monster. The Acolytes take on The Dudley Boyz in a Tables Match. WWF Intercontinental Champion Chyna defends against Kurt Angle and Eddie Guerrero. Test battles Triple H. Right to Censor try to recruit Val Venis. WWF Hardcore Champion Steve Blackman defends against Big Boss Man. Road Dogg and Val Venis team up against RTC and after the match, RTC drag Val Venis into a truck. Jerry the King Lawler teams up with Chris Jericho against Tazz and Naked Mideon. And in the main event, WWF Tag Team Champions Edge and Christian defend against The Undertaker and WWF Champion The Rock in which Kane and Chris Benoit get involved.

When we talk about the future of technology, it is easy to focus on the tools, trends, and innovations that dominate headlines. But behind every breakthrough is a human story, and behind every system are individuals navigating an industry that has not always welcomed them equally. That is why I sat down with Sue Harnett, founder and CEO of Rewriting the Code, to learn more about the real work being done to support and elevate women in technology. What followed was a wide-ranging conversation that brings clarity to an often-overlooked challenge and offers insight into what real change looks like. Rewriting the Code is more than a community. It is a global network of over 35,000 women who are united by shared goals and driven by the ambition to create a more inclusive tech industry. Sue shared the origin of the organization, born from her own experiences of feeling out of place in elite academic environments, and how that shaped her commitment to building a culture where young women could grow, thrive, and most importantly, feel like they belong. Today, RTC is impacting lives across the globe with programs that span mentorship, career development, technical education, and real-world support. What stood out was the way RTC moves beyond symbolic gestures and instead provides practical pathways. We explored the launch of targeted initiatives like Rewrite AI and Rewrite Cybersecurity, which aim to prepare women for high-demand areas in the industry. We also discussed the Black Wings program, built specifically for Black women in tech, who represent just two percent of the industry workforce. Through focused community-building and peer support, these programs help dismantle systemic barriers that often go unaddressed. In a time where many companies are retreating from public conversations about diversity due to political pressure, Sue's work feels more relevant than ever. She spoke candidly about the fear she's seeing in boardrooms, the erosion of public DEI commitments, and the quiet but continued support from leaders who still believe in building inclusive workplaces. Her message to companies was simple: inclusion must be intentional, visible, and connected to the lived experience of the people it is meant to support. What this episode reveals is not only the importance of creating opportunities, but also the power of belief. The belief that women belong in every corner of the tech world, and that with the right community, mentorship, and visibility, they can redefine what leadership looks like. So how is your organization showing up for underrepresented talent in tech, and what will it take to turn good intentions into lasting impact?

Two hotels on the Strip, the Luxor and Treasure Island, are getting sued after guests claimed they were "massacred" by bed bugs and left with scars. So, how bad can bed bug bites really get, and is this a frivolous lawsuit? Co-hosts Sarah Lohman and Dayvid Figler are joined by Nevada Current reporter Michael MJ Lyle to talk bed bugs. They also tackle the recent safety upgrades in RTC buses and transit centers, and the doctors from UNLV School of Medicine's inaugural class who are opting to stay in Las Vegas. Learn more about the sponsors of this May 16th episode: Babbel - Get up to 60% off at Babbel.com/CITYCAST Prolonlife.com/city - Use this link for 15% off Get tickets to our live episode recording at the RDA Museum on 5/22 HERE Want to get in touch? Follow us @CityCastVegas on Instagram, or email us at lasvegas@citycast.fm. You can also call or text us at 702-514-0719. For more Las Vegas news, make sure to sign up for our morning newsletter, Hey Las Vegas. Looking to advertise on City Cast Las Vegas? Check out our options for podcast and newsletter ads at citycast.fm/advertise. Learn more about your ad choices. Visit megaphone.fm/adchoices

Inside of our online Facebook group community, we have been getting a lot of questions around the topic of how to study the Bible and understand what you are reading when you are trying to study the Bible. If you are new to the faith or new to truly wanting to study the Bible, it can be a daunting task, and in this episode, we want to come alongside you and help you learn how you can study the Bible for yourself. *Note, this is a classic replay from season 2 of RTC.  Connect with RTC: Website: https://realtalkchristianpodcast.com/ Facebook Group: https://www.facebook.com/groups/realtalkchristianpodcast YouTube: https://www.youtube.com/@realtalkchristianpodcast Instagram: https://www.instagram.com/realtalkchristianpodcast/

Send us a textMike Rinder and Marc Headley dive into the current state of Scientology's Office of Special Affairs (OSA), revealing how the once-powerful intelligence arm is now struggling to keep up with mounting challenges and criticisms.• OSA is Scientology's spy wing, previously known as the Guardian's Office which perpetrated the largest infiltration of the US government in history• Many Guardian's Office members are still working in OSA today despite Scientology's claims they were removed• Key legal figures like Kendrick Moxon (unindicted co-conspirator) still work as OSA's legal counsel• Warren McShane, President of RTC, was previously intelligence head for Guardian's Office New York• OSA currently has too many crises to effectively handle them all – Danny Masterson case, Switzerland legal failures, UK event planning issues• The explosion of ex-members speaking out has increased "10x in six months"• OSA surprisingly paid back Rosemary Chickwack's money without requiring a release or gag order• David Miscavige's paranoia and management style causes high turnover and chaos within OSA• Many OSA failures are directly caused by Miscavige's irrational demands and temper• Former OSA executives note they can't possibly monitor all the SPTV content being createdSupport the showBFG Store - http://blownforgood-shop.fourthwall.com/Blown For Good on Audible - https://www.amazon.com/Blown-for-Good-Marc-Headley-audiobook/dp/B07GC6ZKGQ/ref=tmm_aud_swatch_0?_encoding=UTF8&qid=&sr=Blown For Good Website: http://blownforgood.com/PODCAST INFO:Podcast website: https://www.buzzsprout.com/2131160 Apple Podcasts: https://podcasts.apple.com/us/podcast/blown-for-good-behind-the-iron-curtain-of-scientology/id1671284503 RSS: https://feeds.buzzsprout.com/2131160.rss YOUTUBE PLAYLISTS: Spy Files Playlist: https://www.youtube.com/playlist?list=PLWtJfniWLwq4cA-e...

On episode #138 of the #PackMentality Pop-Ins Podcast, co-host Trent Hidlay sits down with his current Wolfpack RTC head coach Jamill Kelly. Kelly was a teammate (at Oklahoma State) and previously coached under Wolfpack head coach Pat Popolizo, and recently returned to Raleigh to join the RTC. The former Olympic Silver medalist talks about the Pack's recent success at the U.S. Open and Hidlay qualifying for Final X. #packmentality  #wolfpackwrestling  #ncstatewrestling  #wrestlingpodcast SUBSCRIBE TO #PACKMENTALITY POP-INSApple Podcasts | Spreaker | Spotify | RSS

This week's EYE ON NPI is looking at itsy-bitsy-teensy-weensy little rechargeable batteries that can keep your micro-power electronics running for many years without needing any maintenance from your users: it's Panasonic's VL/ML Series Lithium Rechargeable Coin Batteries (https://www.digikey.com/en/product-highlight/p/panasonic/lithium-rechargeable-coin-batteries). These are small, solderable batteries much like the coin cell batteries you're used to replacing in watches, toys, and other gadgets..but this time they can be recharged in-circuit to make maintenance effortless. We've covered lots of batteries and battery holders on EYE ON NPI - from enormous lead acid batteries to tiny coin cells (https://www.digikey.com/en/products/filter/batteries-non-rechargeable-primary/). These are an essential part of the engineer's repertoire as so many products need to work when not plugged into the wall. We use coin cells a lot in our design work: there's nothing as compact and they have great energy density. But they're typically 'primary cells' - not rechargeable. That might be fine if you're using them for something like a remote control (https://support.apple.com/en-us/101261) or a small toy. But they do eventually need to be replaced, which can be a user frustration. For that reason, many products that used to have primary cells like AA's or coin batteries have slowly transitioned to embedding lithium polymer pouches. You can get rechargeable lipoly batteries in 100 mAh or less! (https://www.digikey.com/short/7njnd057) However, there may be some cases where you still want something really really tiny, like say 9mm diameter and under 1mm thick - a size only achievable with a coin cell - but without dealing with removing and replacing a battery every few weeks or months. Especially if we're talking about something that is going to be plugged in once in a while, or where the coin cell is a fall-back. This comes up often with devices that have real time clocks (RTCs) - such as clocks, computers, laptops, tablets, watches, GPS units (https://www.adafruit.com/product/5440), etc. They might have a main battery or power system that can run a microcontroller/CPU and display plus peripherals, but you still want to keep time and maybe an alarm setting when the main power cuts off. Historically, folks have just used coin batteries - ideally replaceable ones - but sometimes not as in the case of the DS1287 (https://theretroweb.com/chip/documentation/ds1287-647b3602989d3299594321.pdf) which had the coin battery sealed inside! If you're designing a product today that needs an RTC battery, we'd say take a good look at the Panasonic's VL/ML Series Lithium Rechargeable Coin Batteries (https://www.digikey.com/en/product-highlight/p/panasonic/lithium-rechargeable-coin-batteries). No holder required: they come with tabs to solder directly onto a PCB in vertical or horizontal orientations. And they come in a variety of sizes from the 20mm / 45mAh to 12mm / 7mAh and even smaller. Note that as expected, you're going to get less capacity than a primary cell, so these are good when you think you'll get recharged every few days or weeks. Don't forget: you will absolutely need a proper lithium charger to recharge these batteries. We've got plenty of charger breakouts you can use, we particularly like the bq25185 (https://www.digikey.com/en/products/detail/adafruit-industries-llc/6091/25805553) which you can easily configure for the 1C current charge rate to match your Panasonic Lithium Rechargeable Coin Batteries (https://www.digikey.com/en/product-highlight/p/panasonic/lithium-rechargeable-coin-batteries) They can all handle 1000+ cycles, we like the bq in particular because it has power-path which will help avoid unnecessary discharging/cycling. Ready for a tiny burst of power to keep your clocks a-tickin'? You can pick up a wide selection of Panasonic's VL/ML Series Lithium Rechargeable Coin Batteries (https://www.digikey.com/en/product-highlight/p/panasonic/lithium-rechargeable-coin-batteries) at DigiKey right now! They're in stock in a range of sizes and configurations for immediate shipment - don't forget that like all Lithium batteries you may need to ship ground, so order now and you'll get those bite-sized batteries shipped within the hour for immediate integration. See it on DigiKey https://www.digikey.com/short/wb83dfff

Fresh off winning the U.S. Open at 70kg, Yianni Diakomihalis returns to Baschamania with a lot to unpack. We dive into his transition to 70kg, what beating James Green meant to him, how a year off changed his approach, and what's fueling him heading toward Final X and the World stage. 01:30 - How This Open Win Compares03:30 - Having a Full Year Off07:00 - The Transition to 70kg10:00 - Cardenas & Bryce Wins11:30 - Takeaways from Finals with Green14:00 - Best of 3 Series at Final X16:45 - Focusing on Green vs World Competition19:00 - Only 26, But Already 2622:30 - Being the Old Guy23:00 - PJ Duke Story24:30 - Inspiration in the Young Guys29:00 - Mindset Focus33:00 - Evolving at This Point in Your Career34:15 - Thoughts on Current State of Team USA39:00 - Impact of Guys Wrestling for Other Countries45:45 - NIL's Impact on RTC's58:00 - Simon Ruiz Story01:00:50 - Fan Q&ATweet us and send us messages with questions and general thoughts! Be sure to SUBSCRIBE to the podcast and go through the archives to hear more great stories.Support the show & leave a 5-star rating and review on Apple Podcasts, and shop some apparel on BASCHAMANIA.com! For all partnership and sponsorship inquiries, email info@baschamania.com.BASCHAMANIA is a Basch Solutions Production. Learn more about Basch Solutions at BaschSolutions.com.SUBSCRIBE ON YOUTUBE! https://www.youtube.com/@JustinBaschCONNECT ON X/TWITTER:TWITTER: http://www.twitter.com/justinjbaschINSTAGRAM: http://www.instagram.com/jbasch

Jason Brink is the CEO and co-founder of Datagram, a decentralized real-time communication (RTC) infrastructure platform that leverages underutilized network resources to provide secure, scalable, and cost-effective communication solutions.  Why you should listen Datagram is a decentralized real-time communication (RTC) infrastructure platform that leverages underutilized resources to provide scalable and cost-effective connectivity solutions. It operates as a DePIN (Decentralized Physical Infrastructure Network) baselayer, utilizing an AI-driven, Hyper-Fabric Network to enable fast and scalable connectivity across various applications, including gaming, AI, and telecom. By unifying idle hardware bandwidth into a global decentralized network, Datagram delivers fast, secure, and scalable connectivity for modern internet applications. ​ One of the key features of Datagram is its AI-driven coordination, which dynamically optimizes traffic, congestion control, and scalability while predicting traffic patterns to balance network loads for peak efficiency. This ensures that the network can adapt to varying demands and maintain optimal performance. Additionally, Datagram offers cross-network interoperability through standardized DePIN cross-network communication, ensuring seamless interoperability, improved efficiency, and optimal resource utilization while scaling effortlessly.  Datagram's decentralized architecture eliminates the need for central servers, reducing the risk of single points of failure and enhancing privacy and security. It provides a multifunctional platform with RTC, CDN, GPU compute, and storage functionalities, supporting mission-critical connectivity across the next generation of digital applications. Use cases include distributing AI/ML workloads, enabling seamless real-time audio and video communication, powering multiplayer gaming with ultra-low latency, and accelerating content delivery through a global node network. Supporting links Stabull Finance Datagram Andy on Twitter  Brave New Coin on Twitter Brave New Coin If you enjoyed the show please subscribe to the Crypto Conversation and give us a 5-star rating and a positive review in whatever podcast app you are using.  

That's right, you can now support RTC by using code "coolrick" or code "spencer" while buying anything in any Supercell Game. This episode we also talk Gold Rush, WWE Event Troops, and if meta shakeups are good for Clash of Clans. Creator Code Links:https://store.supercell.com/en?boost=coolrickhttps://store.supercell.com/en?boost=spencerTimestamps:(00:00) We got Creator Codes!(05:29) Gold Rush Event(08:45) Cheating the Event, Shame!(18:00) WWE Collaboration(25:10) Are the Meta Shakeups Good for Clash?(33:24) Listener Questions(48:36) Shoutouts

In this episode of Without Compromise we sit down with Ryan Chao, President of Rails to Trails Conservancy (RTC), to explore the transformative power of trails, not just as places to recreate, but as vital community infrastructure. With a background in architecture and community development, Ryan shares how his personal journey led him to advocate for a nation connected by trails. From biking and skiing with his family to navigating policy and equity challenges, Ryan offers a compelling look at how trails support health, economic opportunity, and environmental resilience across urban, rural, and suburban communities alike.We also dive into Celebrate Trails Day and RTC's partnership with Athletic Brewing through the Two for the Trails program, Athletic's cornerstone initiative that supports trails across the country and world. Whether you're a lifelong trail user or just starting to explore the outdoors, this conversation will leave you inspired to get involved and advocate for accessible, connected open spaces for all.

This week on Transit Unplugged, Paul visits Las Vegas to talk with M.J. Maynard, CEO of the Regional Transportation Commission of Southern Nevada (RTC). From managing traffic for massive events like the Las Vegas Marathon and Formula 1, to running one of the busiest bus-only transit systems in the U.S., M.J. gives us a behind-the-scenes look at what makes RTC truly unique.Unlike most transit agencies, RTC operates as a centralized hub for mobility—housing the region's public transit provider, the Metropolitan Planning Organization (MPO), traffic management, roadway funding agency, and even bike share operations all under one roof. That structure gives the team unmatched agility when responding to evolving transportation needs, especially in a region that's booming with mega-events and economic growth.Paul and M.J. ride the Deuce on the Strip, visit RTC's award-winning Mobility Training Center, and explore how this consolidated model creates real-time solutions for residents and tourists alike. With a focus on equity, connectivity, and serving both locals and tourists, M.J. shows how Las Vegas moves the masses—and why other regions are taking notes.Transit Unplugged is brought to you by Modaxohttps://www.modaxo.com Host & Producer: Paul Comfort Podcast Editor & Newsletter Guy: Chris O'Keeffe Executive Producer: Julie GatesSpecial thanks to: Tina Olagundoye – Brand Design Tatyana Mechkarova – Social MediaGot a question or comment? Email us at info@transitunplugged.com Subscribe to the Transit Unplugged Newsletter:https://transitunplugged.com/subscribe-to-the-transit-unplugged-newsletter/Disclaimer:The views and opinions expressed in this program are those of the guests, and do not necessarily reflect the views or positions of Modaxo Inc., its affiliates or subsidiaries, or any entities they represent (“Modaxo”). This production belongs to Modaxo and may contain information that may be subject to trademark, copyright, or other intellectual property rights and restrictions. This production provides general information and should not be relied on as legal advice or opinion. Modaxo specifically disclaims all warranties, express or implied, and will not be liable for any losses, claims, or damages arising from the use of this presentation, from any material contained in it, or from any action or decision taken in response to it.

Send us a textWe uncover how Scientology is systematically erasing evidence of David Miscavige's control structure, including the recent removal of "Matters of RTC Concern" from their official websites after decades of existence.• The RTC "triangle" on Scientology org boards has been quietly removed, eliminating visual evidence of how David Miscavige can bypass all command channels• Scientology's pattern of revisionism includes erasing knowledge of FBI raids and high-profile departures within the organization• Int Base manufacturing was relocated to Los Angeles to counter human trafficking allegations after our lawsuit highlighted staff living and working in the same location• Weekly room inspections called "Clean Ship Program" allowed Ethics Officers to search personal belongings under the guise of cleanliness checks• Security at Int Base confiscated personal items, including night vision goggles found by Marc, with guards known to cherry-pick possessions from people who escaped• Scientology manipulates immigration status and work permits to control international Sea Org members, leaving them vulnerable if they attempt to leaveIf you have questions about Scientology secrets you'd like us to explore in future episodes, email claire@blownforgood.com or leave a comment on this video.Support the showBFG Store - http://blownforgood-shop.fourthwall.com/Blown For Good on Audible - https://www.amazon.com/Blown-for-Good-Marc-Headley-audiobook/dp/B07GC6ZKGQ/ref=tmm_aud_swatch_0?_encoding=UTF8&qid=&sr=Blown For Good Website: http://blownforgood.com/PODCAST INFO:Podcast website: https://www.buzzsprout.com/2131160 Apple Podcasts: https://podcasts.apple.com/us/podcast/blown-for-good-behind-the-iron-curtain-of-scientology/id1671284503 RSS: https://feeds.buzzsprout.com/2131160.rss YOUTUBE PLAYLISTS: Spy Files Playlist: https://www.youtube.com/playlist?list=PLWtJfniWLwq4cA-e...

This week on the RTC Weekly Download: Soap Operas from RTC's own "Soaptime" lineup  

We react and discuss what is possible the best Quality of Life update ever to come to Clash of Clans - Removal of Training Time and Hero Recovery Time. Discussion is kind of all over so forgive the non-exhaustive chapter links. This might just be the most positive RTC of all time...Full News and Discussion on RedditTimestamps:(00:00) Intro and Initial Reactions(02:52) The "Why" of it(04:16) Changes to Force Quitting(10:34) Are there Drawbacks? (not really)(13:19) Snapshot Bases(15:39) How Donations Are Changing(19:04) More Snapshot(25:15) Training Potions and Gem Economy(30:09) Audience Questions

The Regional Transportation Commission (RTC) is the agency that handles much of how we get around in Reno. They design and execute road projects, manage our local public transit, and very soon they will be installing bike infrastructure along several major streets downtown to create the Biggest Little Bike Network. Today on the show, we welcome Sara Going, Project Manager at RTC for the Biggest Little Bike Project, to talk about these upcoming street improvements, how they affect local businesses, connecting different neighborhoods, creating safety (and a feeling of safety) for bike riders and all users of the road, what was learned from 2022's micro-mobility pilot project, planned replacement of structurally deficient bridges, and so much more! If you enjoy this episode and would like to support Renoites financially, your generous contribution is incredibly appreciated. You can learn more and sign up to help this ad-free, locally-oriented project continue on into the future. Learn more at http://www.renoites.com Thank you so much for listening! If you have guest suggestions, comments, feedback, or questions for an upcoming mailbag/Q&A episode, send them over to conor@renoites.com or connect with me on social media. Links can be found at http://www.renoites.com 

We used to stock a PiCam Module (https://www.adafruit.com/product/5247) that would plug into a Pi CM4 or CM5 - recently we went to restock it, but the vendor hasn't replied to our emails for many months. So, it could be a good time for us to design something that works similarly but with more capabilities. So we tasked Timon (https://github.com/timonsku) with designing something for us - we just said, "Make the best thing ya can," and he delivered! Check this board out that plugs onto the compute module and provides many great accessories: USB connection for bootloading/USB gadget, USB 3.0 host type A for CM5, micro HDMI, micro SD card for data storage on 'Lite modules, camera connection, and mount, two DSI connectors, fan connect, Stemma QT / Qwiic connection, and RTC battery. There's one shutdown button for CM5 and two GPIO buttons plus one LED. Timon's gonna try to add an EYESPI connector for our next rendering so we can get some I2C/SPI/PWM outputs easily. What do you think? We wanted to keep it compact and not too pricey (aiming for under $30 cost. We'll see if we can get it there) but were able to craft fairly complex projects in a small space. Visit the Adafruit shop online - http://www.adafruit.com ----------------------------------------- LIVE CHAT IS HERE! http://adafru.it/discord Subscribe to Adafruit on YouTube: http://adafru.it/subscribe New tutorials on the Adafruit Learning System: http://learn.adafruit.com/ ----------------------------------------- #raspberrypi #camera #tech

Real Talk Christian Podcast brings you A Christmas Carol: Audio Drama. This audio drama was done by Chris Fuller as a way to help continue to bring stories to life for his kids. He decided that it would be a great Christmas gift to all of those who love this story as much as RTC does. Please enjoy this story of Ebenezer Scrooge, and his Christmas Eve journey from a greedy and selfish, to an all new man, as he discovers what Christmas is about. Merry Christmas from all of us at Real Talk Christian Podcast.

Show Notes:: In this special thanksgiving episode of Real Talk Christian Podcast, Marc Hyde and Chris Fuller reach out to the RTC online community on Facebook to talk about their family traditions. It may give you a few ideas of your own. So as your prepare for this day we give thanks to God, relax and listen in on this special episode. //Other Episode You Might Enjoy// 077: Does God Choose Us or Do We Choose God?: https://realtalkchristianpodcast.com/episodes/077-does-god-choose-us-or-do-we-choose-god/ 069: I Know God Loves Me, but Does God Like Me?: https://realtalkchristianpodcast.com/episodes/069-i-know-god-loves-me-but-does-god-like-me/ 019: When the Church Hurts You: https://realtalkchristianpodcast.com/episodes/019-when-the-church-hurts-you/ 015: Conversation with Paul Lindgreen: https://realtalkchristianpodcast.com/episodes/015-conversation-with-paul-lindgreen/ 001: Does my past effect my future?: https://realtalkchristianpodcast.com/episodes/001-does-my-past-effect-my-future/ // Helpful Links // https://www.youtube.com/@realtalkchristianpodcast The Christian Standard Bible: https://bit.ly/3rulKqi Lifeway Christian Resources: https://bit.ly/3qka4Wv Got Questions?: https://bit.ly/3vSMJfq Dwell Bible App: https://bit.ly/3zUYq8E Cross Formed Kids from Ryan Coatney: https://bit.ly/3h19isZ RTC Quick Links: https://linktr.ee/realtalkchristianpodcast RTC Online: www.realtalkchristianpodcast.com Twin Valley Coffee: https://www.coffeehelpingmissions.com Revive festival : Music Festival | En Gedi Music Fest | Leonidas, MI (myrevivefest.com) Toccoa Coffee:https://toccoacoffee.com RTC Merch-https://rtcpodcast.redbubble.com  

In this episode we discuss: What Layne Norton is missing regarding seed oils What we think of Liver King's steroid use and how this relates to fitness culture and unhealthy body image Ben Bikman's complete misapplication of a study regarding blood sugar and insulin resistance Jay's response to Thomas DeLauer regarding omega-3s and cod liver oil     Check out the Energy Balance Solution program here: https://www.jayfeldmanwellness.com/solution/     Download the Free Energy Balance Food Guide here: https://www.jayfeldmanwellness.com/guide/     Danny's Telegram: https://t.me/dannyroddy   Timestamps: 0:00 – intro 0:28 – Andrew Huberman and Layne Norton on whether seed oils are inherently harmful 4:18 – why Layne Norton's "calories-only" view is flawed, as it ignores how the type of food actually affects our bodies 9:58 – whether animal studies are useful in nutritional research, or if only human randomized control trials (RTC) should be considered 15:57 – problematic assumptions and biases in nutritional research and how they can shape research outcomes 20:59 – why the reported health benefits of polyunsaturated fats in research are misleading and harmful 26:54 – the connection between chronic disease and polyunsaturated fats, and how focusing solely on calories relieves the food industry of responsibility for health outcomes 31:43 – Liver King's self-esteem, body image struggles, steroid use, health risks, and why his apology was commendable 41:36 – why cultural standards for physical appearances are unrealistic, unhealthy, and can lead to conflating steroid-enhanced bodies for genuine health 51:12 – health risks associated with steroid-use and having too much muscle mass 1:00:34 – Thomas Delauer and Derek from moreplatesmoredates discuss omega-3s 1:06:21 – whether the antioxidants in fish oil are worth the damage caused by lipid peroxidation 1:10:54 – whether cod liver oil is any better than fish oil 1:17:11 – how to effectively hydrate your cells and the importance of getting enough salt 1:24:44 – why consuming a lot of plain water without electrolytes actually impairs hydration, contributing to increased swelling, increased stress, and impaired energy production 1:32:38 – the importance of getting adequate potassium in addition to salt intake 1:38:03 – factors that may increase your need for water 1:40:02 – what Ben Bikman misses when it comes to blood glucose and insulin resistance 1:48:15 – the true relationship between insulin and blood sugar regulation 1:54:30 – Ben Bikman misapplies this study: it does not support that carbohydrates cause insulin resistance 2:00:38 – creating content in the health sphere, choosing high quality foods, and the benefits of tracking food (using Cronometer or another similar app)