POPULARITY
6 episodes with iatf
5 episodes with iatf
8 episodes with iatf
4 episodes with iatf
7 episodes with iatf
2 episodes with iatf
14 episodes with iatf
13 episodes with iatf
4 episodes with iatf
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
Neste episódio do Raízes do agro, conversamos com Andressa Biata, produtora rural e embaixadora da Agrishow. Descubra como esta ex-publicitária de Campinas fez uma notável transição para o agronegócio, assumindo os negócios da família na pecuária de Mato Grosso do Sul. Andressa compartilha os desafios de ser uma mulher no agro, a importância da comunicação para o setor e como sua experiência profissional anterior a ajudou a impulsionar o empreendedorismo rural, criando a empresa Rurais, que oferece diversos serviços no campo. Uma conversa essencial sobre resiliência, inovação e o papel transformador das mulheres no agronegócio brasileiro. Este episódio foi gravado na Agrishow, a maior feira do agronegócio da América Latina, diretamente do estande do Grupo Piccin. PARCEIRO DESTE EPISÓDIO Este episódio foi trazido até você pelo Grupo Piccin! O Grupo Piccin, que hoje contempla o foco de trabalho em equipamentos, componentes e inovação, começou com o trabalho de um homem, Santo Piccin. Com a evolução da agricultura, os desafios se tornaram mais complexos, exigindo a utilização de implementos agrícolas mais eficientes. Grupo Piccin: excelente em produzir o melhor para o campo. Site: https://piccin.com.br/Instagram: https://www.instagram.com/grupopiccinFacebook: https://www.facebook.com/grupopiccinLinkedIn: https://www.linkedin.com/company/piccin-máquinas-agrícolas-ltdaYouTube: https://www.youtube.com/channel/UCk4BdnkZnq7gObUiR0XQR7g INTERAJA COM O AGRO RESENHAInstagram: instagram.com/agroresenhaTwitter: x.com/agroresenhaFacebook: facebook.com/agroresenhaYouTube: youtube.com/agroresenhaCanal do Telegram: https://t.me/agroresenhaCanal do WhatsApp: https://bit.ly/zap-arp-01 E-MAILSe você tem alguma sugestão de pauta, reclamação ou dúvida, envie um e-mail para contato@agroresenha.com.br ACOMPANHE A REDE AGROCASTInstagram: instagram.com/redeagrocast/Facebook: facebook.com/redeagrocast/Twitter: x.com/redeagrocast FICHA TÉCNICAApresentação: Paulo OzakiProdução: Agro ResenhaConvidada: Andressa BiataEdição: Senhor A - https://editorsenhor-a.com.brSee omnystudio.com/listener for privacy information.
Neste episódio do Raízes do agro, conversamos com Andressa Biata, produtora rural e embaixadora da Agrishow. Descubra como esta ex-publicitária de Campinas fez uma notável transição para o agronegócio, assumindo os negócios da família na pecuária de Mato Grosso do Sul. Andressa compartilha os desafios de ser uma mulher no agro, a importância da comunicação para o setor e como sua experiência profissional anterior a ajudou a impulsionar o empreendedorismo rural, criando a empresa Rurais, que oferece diversos serviços no campo. Uma conversa essencial sobre resiliência, inovação e o papel transformador das mulheres no agronegócio brasileiro. Este episódio foi gravado na Agrishow, a maior feira do agronegócio da América Latina, diretamente do estande do Grupo Piccin. PARCEIRO DESTE EPISÓDIO Este episódio foi trazido até você pelo Grupo Piccin! O Grupo Piccin, que hoje contempla o foco de trabalho em equipamentos, componentes e inovação, começou com o trabalho de um homem, Santo Piccin. Com a evolução da agricultura, os desafios se tornaram mais complexos, exigindo a utilização de implementos agrícolas mais eficientes. Grupo Piccin: excelente em produzir o melhor para o campo. Site: https://piccin.com.br/Instagram: https://www.instagram.com/grupopiccinFacebook: https://www.facebook.com/grupopiccinLinkedIn: https://www.linkedin.com/company/piccin-máquinas-agrícolas-ltdaYouTube: https://www.youtube.com/channel/UCk4BdnkZnq7gObUiR0XQR7g INTERAJA COM O AGRO RESENHAInstagram: instagram.com/agroresenhaTwitter: x.com/agroresenhaFacebook: facebook.com/agroresenhaYouTube: youtube.com/agroresenhaCanal do Telegram: https://t.me/agroresenhaCanal do WhatsApp: https://bit.ly/zap-arp-01 E-MAILSe você tem alguma sugestão de pauta, reclamação ou dúvida, envie um e-mail para contato@agroresenha.com.br ACOMPANHE A REDE AGROCASTInstagram: instagram.com/redeagrocast/Facebook: facebook.com/redeagrocast/Twitter: x.com/redeagrocast FICHA TÉCNICAApresentação: Paulo OzakiProdução: Agro ResenhaConvidada: Andressa BiataEdição: Senhor A - https://editorsenhor-a.com.brSee omnystudio.com/listener for privacy information.
Hi liebe Hörerin, lieber Hörer :-)DNF oder wegen der Medaille bis ins Ziel schleppen?Was ist sinnvoller? Den Körper unnötig belasten und ggf. aufgrund von Erschöpfung die nächsten Traningstage opfern oder doch lieber, wenn auch mit unbefriedigender Zielzeit und wenig ITRA-Punkten, die Finisher Medaille umhängen können. Was denken "die anderen" wenn man doch so euphorisch war und das Umfeld die Ziele hoch gesteckt hatte. Tja, es läuft nicht immer wie geplant - aber wie geht man mit so einem gebrauchten Renntag um?Hört einfach mal rein und erfahrt, wie es Lukas wirklich erging und wie er mit der Situation umgegangen ist.Wie würdest Du in dieser Situation entscheiden?-------Wir freuen uns jederzeit über Dein Feedback und über Deine Fragen. Also immer her damit. Wenn es Dir gefallen hat, abonniere uns gerne auf Spotify & Co. Das hilft uns sehr.Vielen Dank und viel Spaß!Folgt uns auf Instagram @elevation_podcast.Und hier der Link zum Elevation-Addiction YouTube Kanal: https://youtube.com/@Elevation_AddictionLukas und Oliver
Innsbruck – wo Alpenpanorama und Großstadtflair aufeinandertreffen – wurde am vergangenen Wochenende zum Zentrum der deutschsprachigen Trailrunning-Szene. Beim Innsbruck Alpine Trailrun Festival gingen über 7000 Athlet*innen auf unterschiedlich langen Strecken an ihre Grenzen und machten das Event erneut zu einem der größten Trail-Highlights im Frühjahr.Arne verfolgte das Geschehen ganz genau – allerdings nicht vor Ort, sondern live aus der Münchener Innenstadt via Instagram und Live-Tracking. Klar, dass er eine Meinung zum Wochenende hat – was lief gut, was weniger? Einschätzungen und ehrliche Worte gibt's wie immer in dieser Folge.Und dann ist da noch Lars – der war mittendrin statt nur online dabei und nahm sich die 110 Kilometer mit 5500 Höhenmetern vor. Über 16 Stunden unterwegs, durch Schnee, Sonne und über den Patscherkofel: Was hat er erlebt, was hat funktioniert und was ging daneben? Und wie schnell ist eigentlich zu schnell für ein 110K-Rennen?
Auch die Sprachnachricht #124 ist ein Rennbericht. Dieses Mal vom IATF (Innsbruck Alpine Trailrun Festival). Um genau zu sein von meinen zwei Rennen dort, dem Vertical Short und dem K65. Ich erzähle offenherzig was um mich herum und in mir drin passiert ist. Am Ende verrate ich sogar, welchen Schuh ich gelaufen bin.Viel Freude beim Hören.Chris aka Das ZShownotes* Passender Das Z Letter zur Sprachnachricht* IATF Webseite* On Repeat Empfehlung: DAMNATION A.D. – Wait for a Day * Cover Version von Stephen Brodsky & Adam McGrath* “On Repeat” Spotify Playlist* Gefällt dir das alles hier? Dann spendier mir einen Ko-FiDie Das Z - Sprachnachricht ist die deutschsprachige Audio-Zusammenfassung des Lauf-Blogs & Newsletters Das Z Letter von Chris Z, dem Gründer der Laufsportmarke Willpower und Autor des Buches Runhundred und Hundert-Meilen-Herz. Get full access to Das Z Letter at dasz.substack.com/subscribe
In this episode, we recap The Countess Cup that took place at Choppers Hatchet House this past weekend! We also review the very first knife tournament to take place under the new IATF rules. It was a fantastic weekend filled with good vibes, dollar beers, some dings, and many dongs!Don't forget to donate to our Gal-Lee fund to keep sending women to tournaments throughout the year. Please send any shoutouts, hot takes, comments, and concerns to anaxeleagueoftheirown@gmail.com.
At the heart of The Prophets' vision are “The 24 Essential Supply Chain Processes.” What are they? Find out, and see the future yourself. Click here What does quality really mean in today's automotive world—when the supply chain is shifting, the tech is evolving daily, and the pressure to get it right has never been higher?Scott Trantham is here to answer that. As General Motors' Manager of Supply Quality and Chair of the AIAG Quality Steering Committee, he's helping shape the systems that will define automotive quality—not just today, but for the road ahead.Scott explains how the rise of EVs, autonomy, and complex supply chains puts pressure on traditional systems. Add in growing regulatory pressure and higher consumer expectations, and it's no longer just about making good parts—it's about meeting more demanding standards across a global network.The committee's response? Updating the core tools—SPC, APQP, Control Plan, and more—while aligning with the VDA to create unified global standards.Automation in quality management systems came up as a key point. While standards like IATF 16949 may not require it, Scott outlines clear benefits: better accuracy, visibility, faster problem resolution, and real-time tracking. All strong reasons for suppliers to move away from spreadsheets and manual processes—not because the standard says so, but because it's simply better business.With more than 40 years in the industry, Scott reflects on what keeps him committed: solving problems, launching successful products, and helping shape the future through his work with AIAG.His message to today's quality professionals? Live quality daily, make decisions based on facts and data, and if you get the chance to volunteer on an industry project—take it. You're not just helping your company. You're helping shape the future of the industry.Themes discussed in this episode:How EVs, AVs, and sustainability are changing quality expectations in automotiveWhy updating core tools like APQP and SPC is critical for modern manufacturingThe role of global collaboration in standardizing quality processes across regionsThe need to break down silos between supply chain, IT, and quality teamsHow automation improves quality systems beyond what manual processes can deliverThe challenge of keeping up with evolving ESG and regulatory requirementsThe need to attract and mentor the next generation of quality professionalsWhy mentoring and volunteering are key to sustaining industry-wide quality standardsFeatured on this episode:Name: Scott TranthamTitle: Manager of Supplier Quality and Development at General Motors, and Chair of the AIAG's Quality Steering CommitteeAbout: Scott is the Manager of Global SQ Operations, IT Systems, Training, and Data Analytics at General Motors and has over 40 years of experience in the automotive industry. He also serves on the AIAG Quality Steering Committee and the IAOB Steering Committee, helping shape quality standards across the sector.With expertise in manufacturing, purchasing, supplier quality, and service parts, Scott's strengths range from complex problem solving – delivering solutions that promote industry improvements – to facilitating growth through collaboration and encouraging cross-functional data-driven methodologies to increase efficiencies.Connect:
Die wahrscheinlich bisher kürzeste unserer Folgen reicht gerade noch für einen gemütlichen Zehner... Aber es muss wie auf den Trails gerade schnell gehen, denn es ist Endspurt für Lukas Start beim IATF über 43km.Hauptthema: Fehlanzeige. Wir berichten einfach von unseren aktuellen Erlebnissen was Training, Schuhe und Lukas' Ambitionen in Innsbruck anbelangt. Oliver Haut eine berechnete Zielzeit für Lukas raus und:Wir bedanken uns beim Trailrunning-Geschwätz Podcst, die sich in ihrer Folge 152 herrlich über unseren Lukas unterhalten haben, da er in einer seiner letzten Einheiten ein paar Strava-Segmente, unter anderem von Arne, "zerstört" und sich so die Krönchen geholt hat". Also hört dort unbedingt auch mal rein, wenn ihr es nicht eh schon tut - es lohnt sich.Wir freuen uns jederzeit über Dein Feedback und über Deine Fragen. Also immer her damit. Vielen Dank undviel Spaß!Folgt uns auf Instagram @elevation_podcast.Und hier der Link zum Elevation-Addiction YouTube Kanal: https://youtube.com/@Elevation_AddictionLukas und Oliver
In this episode we discuss the recently announced new IATF App that will be replacing the old Axe Scores app on March 8th. With a controversial fee and a highly passionate community, the announcement sent waves through The Sport of Axe Throwing. Listen in for our takes, opinions, and other ideas on how the IATF could bring in new revenue with a splash! Don't forget to donate to our Gal-Lee fund to keep sending women to tournaments throughout the year. Please send any shoutouts, hot takes, comments, and concerns to anaxeleagueoftheirown@gmail.com.
In der heutigen Folge dreht sich alles um die Golden Trail Series und ein brandneues Highlight, das für Aufsehen sorgt! Der neue Stopp im Pitztal, genauer gesagt in Mandarfen, lässt die Herzen von Lars und Arne höherschlagen. Ein echtes Trailrunning-Spektakel direkt vor der „Haustür“ – wie könnte man da nicht begeistert sein? Ob die beiden im August live vor Ort sein werden, um von diesem einzigartigen Ereignis zu berichten? Die Euphorie ist auf jeden Fall spürbar! Und dann gibt es noch eine echte Sensation: Courtney Dauwalter schreibt Geschichte und bekommt den ersten Vertrag der Superlative im Trailrunning! Ein Fünf-Jahres-Vertrag – so etwas hat es in unserer Sportart bisher noch nie gegeben. Ein Meilenstein, der zeigt, wie sehr der Sport wächst und sich weiterentwickelt. Doch ist das wirklich der große Schritt in eine positive Zukunft? Lars und Arne haben dazu ihre Meinung. Von den Profis zurück zu uns Hobby-Athletinnen und -Athleten: Die letzten Startplätze für die großen Rennen des Jahres werden vergeben – doch wie sieht es eigentlich mit den wichtigen Vorbereitungsrennen aus? Wann sollte man diese einplanen, und vor allem: Wie lang sollten sie sein? Lars und Arne haben wertvolle Tipps parat und verraten, wo ihr euch neben den Klassikern wie IATF, ZUT, UTMB, Lavaredo und Innsbruck noch anmelden solltet, um bestens vorbereitet an den Start zu gehen!
A pecuária feijão com arroz e seus 3 pilares A pecuária feijão com arroz se baseia em 3 pilares: * Biotécnicas reprodutivas e melhoramento genético. * Manejo com técnica e planejamento. * Nutrição estratégica e economicamente viável. O médico veterinário Luiz Henrique Guimarães explicou sobre esse conceito e discorreu sobre o assunto. Aprofundou na reprodução IATV, FIV e clonagem; falou sobre como escolher a suplementação adequada; e respondeu algumas perguntas como: Como programar a retirada dos touros pra fazer IATF? Quanto custa um produto de transferência de embriões? Porque inseminar vacas de leite com angus de corte? Como começar um manejo de pasto em uma fazenda extremamente degradada? Na nutrição de animais confinados é melhor usar sorgo ou milho? Enfim... convidamos você a acompanhar essa prosa que o veterinário Luiz teve com o Francys de Oliveira.
In this episode, we dive into the key updates in the 6th Edition of the IATF Rules with Paul Blattner, Intertek's Global Transportation Manager for Business Assurance. Listen as we unpack the significant changes in the audit cycle, certification structure eligibility, and remote auditing provisions. Learn how these modifications will impact organizational planning and the overall audit process. Follow us on- Intertek's Assurance In Action || Twitter || LinkedIn.
At the heart of The Prophets' vision are “The 24 Essential Supply Chain Processes.” What are they? Find out, and see the future yourself. Click here In this episode of the Auto Supply Chain Prophets podcast, co-hosts Terry Onica and Jan Griffiths welcome Steve Povenz, a recognized leader in automotive quality, to discuss the crucial integration of quality and supply chain functions.Steve believes quality and supply chain are inseparable and fundamental to an organization's success. He points out that many organizations fail because these functions operate in silos, leading to inefficiencies and missed opportunities for improvement. He stresses that quality should be proactive and collaborative, engaging with other departments to understand and mitigate issues before they arise.Steve highlights the importance of regular cross-functional reviews and the use of technology to bridge gaps, streamline processes, and enhance data accuracy. He praises Terry and Cathy Fisher's 24 Essential Supply Chain Processes as a comprehensive roadmap for improving these integrations.Jan and Steve discuss the impact of leadership and culture in fostering collaboration between quality and supply chains. Steve says effective leadership and shared goals lead to successful outcomes regardless of organizational structure. They touch upon the need for evolving standards like IATF 16949 to keep pace with industry changes, particularly the shift from internal combustion engines to electric vehicles. Steve encourages quality professionals to engage with AIAG, participate in summits, and provide feedback to help shape the future of automotive quality standards.The episode concludes with Steve's practical advice for leaders in the automotive supply chain: engage with quality counterparts, involve them in daily operations, and leverage their expertise to solve problems collaboratively. Themes discussed in this episode:The importance of integrating quality and supply chain functions within organizationsThe issue of quality and supply chain functions operating in silos and the negative impact of this separation Leadership's role in fostering collaboration between quality and supply chain functions How technology can automate processes, enhance data collection, and improve overall efficiency within quality and supply chain operationsThe use of performance scorecards, such as those mandated by IATF 16949, to measure and manage quality and delivery performance within the supply chainThe potential benefits of leveraging frameworks like the 24 Essential Supply Chain Processes to align quality and supply chain operationsWhy quality and supply chain functions need to adapt to rapid changes in the automotive industry, particularly with the shift from ICE to BEVHow to achieve continuous improvement through the use of technology, better integration of functions, and proactive identification and resolution of pain points within the supply chainFeatured on this episode: Name: Steve PovenzTitle: Visionary Global Quality Leader, Director of Quality at Shape Corp.About: Steve is a visionary global quality leader with extensive expertise in Quality Management Systems (QMS) and project management. As the Director of Quality at Shape Corp. for 18 years, he has driven significant improvements in customer satisfaction, cost reduction, and quality standards. Steve excels in fostering organizational growth, creating an empowered employee experience, and enhancing stakeholder engagement. His multicultural
Zapraszam Was na rozmowę z Darkiem Antończykiem. Darek jest ekspertem w zakresie wymagań normy ISO 9001. Zarządza międzynarodowym zespołem trenerów, konsultantów i audytorów. Jest trenerem Szkoły Jakości – i właśnie w Szkole Jakości Darek nagrał dla Was fantastyczne szkolenie, w którym w bardzo merytoryczny, przyjemny i przejrzysty sposób zostały przełożone zapisy normy ISO 9001. Bardzo serdecznie polecam Wam to szkolenie i odsyłam na stronę Szkoły Jakości gdzie macie je dostępne od ręki! Razem z Darkiem porozmawiamy sobie o tym dlaczego znajomość wymagań i zapisów ISO 9001 jest ważna. Jak czytać standard ISO 9001 aby dobrze go zrozumieć. Co przyniosa nadchodzące zmiany w ISO 9001. Intro 00:00-2:35 2:37 - Co u Ciebie słuchać aktualnie zawodowo? 3:49 - ISO 9001 jest podstawą w zasadzie wszystkich norm branżowych (IATF, AS…) i z tym standardem pracuje w zasadzie każdy. Dla jakościowca ISO 9001 jest tym, czym konstytucja dla prawnika. Dlaczego znajomość wymagań i zapisów ISO 9001 jest tak ważna? 8:27 - Jeśli mógłbyś wytłumaczyć to w taki prosty sposób (zakładając ze się da) – Jak zbudowana jest norma ISO 9001, jak podejść do tej normy i jak ją czytać aby dobrze ją zrozumieć? 15:37 - W jakim celu aktualizowana jest ta norma? Jakie są powody aktualizacji Twoim zdaniem? I czy są już jakieś przesłanki dotyczące daty publikacji? 38:10 - W środowisku eksperckim pewnie powoli robi się już głośno w związku z nadchodzącą zmianą. Czego Ty jako ekspert oczekujesz od nowej rewizji normy ISO 9001? 44:00 - Czy Twoim zdaniem nowelizacja normy ISO 9001 pociągnie za sobą wprowadzenie zmian w innych normach? Jeśli tak, to jakich? 45:40 - Jak nadchodzące zmiany ISO 9001 wpłyną realnie na Twoją pracę?
Hi, I'm Kathi In dieser Folge ist Kathi zu Gast. Sie finishte ihren ersten Ultra über 100km beim IATF in Innsbruck und wurde im Ziel gefeiert wie eine Siegerin. Die zweifache junge Mutter, die ganz nebenbei bemerkt ein Buch geschrieben hat (Link siehe unten), ist Bloggerin, Laufbotschafterin und Ultramarathoni. Sie war diese Jahr Mitbewohnerin in der IATF-Blogger-Loft und vielleicht habt Ihr ihren emotionalen Zieleinlauf bereits in den sozialen Medien gesehen :-) Kathi berichtet über Ihre Vorbereitung und führt uns sehr lebhaft durch Ihre Rennerlebnisse. Mit welchen unter anderen sehr besonderen Herausforderungen sie zu kämpfen hatte und wie sie sich durchgebissen hat, ist sehr spannend mitzuverfolgen. Viel Spaß bei dieser Longrun-tauglichen Folge. Lasse gerne Abo, like und Kommentare da! Kathi's Buch: Mama lass laufen Kathi auf instagram: @running.kathi Wenn es Dir gefallen hat, abonniere unseren Kanal auf Deiner Lieblings-Plattform. Und wenn möglich - und Du es gut mit uns meinst - bewerte unseren Podcast auf Spotify und Co. Instagram @elevation_podcast. Und hier der Link zum Elevation-Addiction YouTube Kanal: https://youtube.com/@Elevation_Addiction Lukas und Oliver
MORADA NO CAMPO, SEXTA-FEIRA, DIA 17.Divino Onaldo entrevista José Ricardo Fachin, promotor técnico da GlobalGen e coordenador do III Megacurso - Formação de Gerentes e Capatazes em Pecuária de corte; Tema: Apagão de mão de obra ameaça crescimento da IATF no Brasil. ⏰ 12:00h às 13:00h
In this episode we sit down with Kat Riley, Senior Manager of Communications and Operations for the IATF. Learn more about one of the women behind the scenes of our federation including her roller derby days, beginnings of her tenure with the IATF, and love of ice luges! Look out for a big Gal-Lee sponsorship announcement at the end of the episode. Head to our website anaxeleagueoftheirown.com to nominate and donate to our Gal-Lee fund! Be sure to check out our *NEW* merch available!!!! This batch order will close on Monday, May 27th so get those orders in now! We want to hear from you! So if you have any questions feel free to reach out to us on social media or email us at anaxeleagueoftheirown@gmail.com! Enjoy and thank you for your support
Hallo, was geht? Wir waren seit Langem mal wieder gemeinsam an der selben Startline - beim Innsbruck Alpine Trailrun Festival über 65km. Für Lukas wie immer ein A-Rennen, denn er kann sich ohnehin nicht bremsen, für Oliver ein klassisches B-Rennen als erster Wettkampftest. Wir berichten diesmal ohne viel Smalltalk von unserer Vorbereitung, von unseren jeweiligen Zielstellungen und natürlich davon, wie es letzlich am Renntag alles so gelaufen ist. Wie so oft zwei interessant unterschiedliche Berichte :-) Wenn es Dir gefallen hat, abonniere unseren Kanal auf Deiner Lieblings-Plattform. Und wenn möglich - und Du es gut mit uns meinst - bewerte unseren Podcast auf Spotify und Co. Das hilft uns insbesondere in der Anfangsphase sehr. Folgen kannst Du uns zusätzlich auf Instagram @elevation_podcast. Und hier der Link zum Elevation-Addiction YouTube Kanal: https://youtube.com/@Elevation_Addiction Lukas und Oliver
In dieser Folge widmen wir uns dem größten Trailrunning Event im DACH Raum, dem Innsbruck Alpine Trailrunning Festival, vom vergangenen Wochenende. Werfen ein Blick auf die Ergebnisse und die Geschehnisse rund um das Event. Außerdem werfen wir einen Blick voraus auf den Transvulcania und das anstehende Rennen dort mit sehr starken Vertretern aus der Ultra Szene. Die Nominierung des DLV für die anstehende Europameisterschaft im Berg und Traillauf steht auf unserer Agenda und wird von uns kritisch analysiert. Außerdem sprechen wir mit Dani und Tobi über die Golden Trail National Serie. Was gehört alles zu einer Organisation dazu? Wie wird man Veranstaltung der GTNS und was ist die Besonderheit an der Serie? Auch auf die Favoriten werfen wir einen Blick und diskutieren diese. Viel Spaß beim Anhören Lars & Arne
In this episode we discuss the upcoming IATF women's tournament, Countess Cup, why women's tournaments and leagues are important, and a big special announcement with our very first Gal-Lee Sponsorship! We want to hear from you! So if you have any questions feel free to reach out to us on social media or email us at anaxeleagueoftheirown@gmail.com! Enjoy and thank you for your support
In this episode, we review the recently released IATF rule change that will go into effect next month. We also speculate wildly how these rule changes will challenge throwers in new ways. Stay tuned until the end of the episode for a SPECIAL ANNOUNCEMENT! We want to hear from you! So if you have any questions feel free to reach out to us on social media or email us at anaxeleagueoftheirown@gmail.com! Enjoy and thank you for your support
In this episode, we dive deep into the IATF regional competitions that happened all over the world this past weekend. Listen to the good, the bad and the ugly as we discuss our own opinions on this tournament's layout, and things in general that really grinds our gears! We want to hear from you! So if you have any questions feel free to reach out to us on social media or email us at anaxeleagueoftheirown@gmail.com! Enjoy and thank you for your support
Get a drink ready, because this one includes its very own drinking game! In this episode, we interview the notorious Giant Slayer, Kimmy Supnet. One of, if not the best, female in the IATF. Kimmy humbly accepts our love and affection of how amazing she is as we spiral into a drunken sea of advice and compliments! Stay tune for pt.2! We want to hear from you! So if you have any questions feel free to reach out to us on social media or email us at anaxeleagueoftheirown@gmail.com! Enjoy and thank you for your support
At the heart of The Prophets' vision are “The 24 Essential Supply Chain Processes.” What are they? Find out, and see the future yourself. Click here As we enter 2024, the Auto Supply Chain Prophets podcast celebrates another successful year as the go-to source for industry knowledge and content for our dedicated audience. For two seasons and across 47 episodes, our podcast has remained committed to helping automotive manufacturers, suppliers, and industry professionals navigate the complex landscape of the auto supply chain. In this special episode, host and producer Jan Griffiths reflects on the key themes that shaped our 2023. The Auto Supply Chain Prophets explored various aspects of the auto supply chain throughout this journey. We've covered critical topics like global standards, ESG, automation, digitization, and risk management. Our dedication to keeping our audience informed and prepared is evident in the episodes dedicated to future-focused topics like EV adoption and the importance of gamification in supply chain education, putting us at the forefront of industry discussions.As we bid farewell to 2023, the Auto Supply Chain Prophets podcast remains steadfast in its commitment to delivering content that matters and encourages the audience to share their thoughts and suggestions for topics they want to explore in the coming year.Themes discussed in this episode:Podcasting challenges and milestonesThe complexity of the auto supply chain landscapeEmerging trends in the auto supply chainThe critical role of technology in the auto supply chainImplementing automation and digitization Leveraging risk management strategies for supply chain resilienceSimplifying complex standardsMMOG/LE and IATF intersectionImpact of EV adoptionThe future of supply chain educationThe Impact of EQMS (Enterprise Quality Management System)Featured on this episode: Name: Jan GriffithsTitle: President and Founder, Gravitas Detroit About: A veteran executive in the automotive industry, Jan previously served as chief procurement officer for a $3 billion, Tier 1 global automotive supplier. As the president of Gravitas Detroit, Jan provides online courses, speeches, podcasts, and workshops to break the mold of command-and-control leadership to help you unleash the potential of your team and allow authentic leadership to thrive.Connect: LinkedInMentioned in this episode:Episode with Tanya Bolden: How MMOG/LE Is Transforming the Automotive Supply ChainEpisode with Alexis Scipio: ESG in the Automotive Industry: Embracing Sustainability for Global Supply ChainsHosts only episode with Cathy Fisher and Terry Onica: Speeding Past Spreadsheets and Silos: The Intersection of IATF and MMOG/LEAn episode with Mike Payionk:
Ele falou sobre o Planejamento da atividade agropecuária buscando a preparação para situações extremas; explicou o tamanho da solução x tamanho do problema; os Três pilares: Planejamento, organização e gestão; falou da Produção e estocagem de alimentos (forragens, silagem, feno) e estratégias nutricionais que diminuem o consumo de volumoso; e do conceito de fazendas compactas e intensificação além da Reprodução IATF e uso de touro x IATF. Confira essa prosa que foi muito boa!
This week, Jacy, Alex, and Adeline discuss basic game play for IATF, game structure, tournaments, what axes we throw and the highly requested origin story for each of us! Check out our Instagram @anaxeleagueoftheirown81 to see the axe targets, our personal axes and our favorite tournament game: Ass Slappin'. We want to hear from you! So if you have any questions feel free to reach out to us on social media or email us at anaxeleagueoftheirown@gmail.com! Enjoy and thank you for your support
In this episode... China-based British compliance expert, Clive Greenwood, joins Renaud this time to discuss the risks that cheap Li-ion batteries from China flooding the globe pose to consumers. They go on to discuss in detail the health and safety and compliance laws governing batteries (and most products), and forthcoming sustainability laws that will be in place from next year that will affect all importers. It doesn't matter if you're in the EU, USA, or elsewhere; you're running out of time to comply with the laws discussed, and no, those cheap batteries aren't going to be compliant... Show Sections 00:00 - Greetings and introducing Clive. 02:41 - Today's topic: The Risks Posed by Cheap Batteries from China. 06:09 - The battery lifecycle. 11:31 - Some examples of the differences in cost and risk of batteries and EV components from China. 20:19 - Existing and forthcoming standards and regulations affecting batteries. 26:52 - How personal EVs will probably be governed by IATF 16949 in future. 29:10 - New legislation coming in 2024 and 2025 that targets consumer lithium batteries specifically and what this means to importers. 37:19 - From 2025 the liability for fires and other dangers caused by poor-quality batteries is going to be on YOU, the importer, and there's no escape. 41:13 - Selling products with a Li-ion battery? Take these actions to avoid problems... 43:47 - Most issues with batteries are 'near-misses' that importers may never hear about leading to a lack of awareness about the risks with batteries. 45:35 - Chargers and the prevention of battery fires. 47:51 - The ESPR represents a serious challenge for importers with a supply chain in China (and other Asian countries to an extent). 50:19 - Liability for problems won't wait for the importer to put things right, they need to be right the first time around. 52:14 - What changes are happening in other parts of the world regarding health and safety? 57:08 - Wrapping up. Related content... Chinese battery danger Telegraph article Get help from Sofeast to prepare to comply with the EU ESPR What is the EU Ecodesign for Sustainable Products Regulation? The EU Ecodesign Regulation Is Coming, But Are You Prepared? [Podcast part 1] How To Comply With The EU Ecodesign Regulation? [Podcast part 2] E Waste Impact on the Environment (Analysis) Understanding The Environmental Impact of EV Batteries Get in touch with us Connect with us on LinkedIn Send us a tweet @sofeast Prefer Facebook? Check us out on FB Contact us via Sofeast's contact page Subscribe to our YouTube channel Subscribe to the podcast There are more episodes to come, so remember to subscribe! You can do so in your favorite podcast apps here and don't forget to give us a 5-star rating, please: Apple Podcasts Spotify Google Podcasts TuneIn Amazon Podcasts Deezer iHeartRADIO PlayerFM Listen Notes Podcast Addict Podchaser
At the heart of The Prophets' vision are “The 24 Essential Supply Chain Processes.” What are they? Find out, and see the future yourself. Click here MMOGLE and IATF cross reference document In this episode of the Auto Supply Chain Prophets Podcast, The hosts, Cathy Fisher and Terry Onica, along with the Co-host, Jan Griffiths take a broad picture of the automotive sector and its changing standards. Cathy stresses the necessity of clarity in relation to clients, markets, and value for strategic planning to be successful. Terry talks about MMOG/LE training and the need to align MMOG/LE with IATF 16949 standards for a more thorough supply chain management strategy.They discuss the benefits and difficulties presented by the automotive industry's changing landscape. To build a potent fusion of innovation and mass manufacturing skills, they underline the importance of dismantling silos and encouraging collaboration between established OEMs and EV startups. The relevance of sustainability is also discussed, as well as how automotive standards should change to account for emerging technologies and cybersecurity issues. The hosts repeatedly emphasize the importance of a comprehensive approach to supply chain management and the necessity of fusing quality, supply chain, and other elements to ensure long-term success in the rapidly changing auto sector.Join this episode of the Auto Supply Chain Prophets and dive in as they take a macro view of the industry and the standards of the auto industry. Themes discussed in this episode:The Importance of Clarity in Strategic PlanningEvolving Automotive StandardsCollaboration between Legacy Auto and EV StartupsThe Role of Sustainability in the Automotive IndustryChallenges in Supply Chain ManagementFeatured on this episode: Name: Cathy FisherTitle: Founder and President, QuistemAbout: Cathy's firm helps its clients, particularly automotive manufacturers, eliminate customer complaints and increase their profits. She has worked in the automotive supply chain since the 1980s when she started her career with General Motors.Connect: LinkedInName: Terry OnicaTitle: Director, Automotive at QADAbout: For two decades, Terry has been the automotive vertical director of this provider of manufacturing Enterprise Resource Planning software and supply chain solutions. Her career began in supply chain in the late 1980s when she led a team to implement Electronic Data Interchange for all the Ford assembly and component plants.Connect: LinkedInName: Jan GriffithsTitle: President and Founder, Gravitas DetroitAbout: A veteran executive in the automotive industry, Jan previously served as chief procurement officer for a $3 billion, Tier 1 global automotive supplier. As the president of Gravitas Detroit, Jan provides online courses, speeches, podcasts and workshops to break the mold of command and control leadership to help you unleash the potential of your team and allow authentic...
Avi Freedman, CEO at Kentik, joins Corey on Screaming in the Cloud to discuss the fun of solving for observability. Corey and Avi discuss how great simplicity can be deceiving, and Avi points out that with great simplicity comes great complexity. Avi discusses examples of this that he sees in Kentik customer environments, as well as the differences he sees in cloud environments from traditional data center environments. Avi also reveals his predictions for the future and how enterprise M&A will affect the way companies view data centers and VPCs. About AviAvi Freedman is the co-founder and CEO of network observability company Kentik. He has decades of experience as a networking technologist and executive. As a network pioneer in 1992, Freedman started Philadelphia's first ISP, known as netaxs. He went on to run network operations at Akamai for over a decade as VP of network infrastructure and then as chief network scientist. He also ran the network at AboveNet and was the CTO of ServerCentral.Links Referenced: Kentik: https://kentik.com Email: avi@kentik.com Twitter: https://twitter.com/avifreedman LinkedIn: https://www.linkedin.com/in/avifreedman TranscriptAnnouncer: Hello, and welcome to Screaming in the Cloud with your host, Chief Cloud Economist at The Duckbill Group, Corey Quinn. This weekly show features conversations with people doing interesting work in the world of cloud, thoughtful commentary on the state of the technical world, and ridiculous titles for which Corey refuses to apologize. This is Screaming in the Cloud.Corey: Most Companies find out way too late that they've been breached. Thinkst Canary changes this. Deploy Canaries and Canarytokens in minutes and then forget about them. Attackers tip their hand by touching 'em giving you the one alert, when it matters. With 0 admin overhead and almost no false-positives, Canaries are deployed (and loved) on all 7 continents. Check out what people are saying at canary.love today!Corey: Welcome to Screaming in the Cloud, I'm Corey Quinn. This promoted guest episode is brought to us by our friends at Kentik. And into my social grist mill, they have thrown Avi Freedman, their CEO. Avi, thank you for joining me.Avi: Thank you for having me, Corey. I've been a big fan for some time, I have never actually fallen off my seat laughing, but I've come close a couple times on some of your threads.Corey: You must have a great chair.Avi: I should probably upgrade it [laugh].Corey: [laugh]. I have been looking forward to this conversation for a while because you are one of those rare creatures who comes from a similar world to what I did where we were grumpy and old before our time because we worked on physical infrastructure in data centers, we basically wrangled servers into doing the things that we wanted them to do when hardware reliability was an aspiration rather than a reality. And we also moved on from that, in many ways. We are not blind to the modern order of how computers work. But you still run a lot of what you do in data centers, but many of your customers are in cloud. You speak both languages very fluently because of the unifying thread between all of this, which is, of course, the network. How did you wind up in, I guess we'll call it network hell.Avi: [laugh]. I mean, network hell was truly… in the '90s, when the internet was—I mean, the internet is sort of like the human body: the more you study it, the more amazing it is that it ever worked in the first place, not that it breaks sometimes—was the bugs, and trying to put together the technology back then, you know, that we had the life is pretty good nowadays, other than the [laugh] immense complexity that has been unleashed on us by everyone taking the same technology and then writing it in their own software and giving it their own marketing names. And thus, you have multi-cloud networking. So, got into it because it's a problem that needs to be solved, right? There's no ESP that connects the applications together; the network still needs to make it work. And now people own some of it, and then more of it, they don't own, but they're still responsible for it. So, it's a fun problem to solve.Corey: The timing of this episode is apt because I've used Kentik myself for a few things over the years. And to be fair, using it for any of my personal networking problems is a bit like noticing, “Oh, I have a loose thread here on my shirt. Pass me the chainsaw.” It's, my environment is tiny and it's over-scoped. But I just earlier this week wound up having to analyze a day's worth of Flow Logs from one of my clients, and to do this, I had to spin up an EC2 instance with 128 gigs of RAM and then load the Flow Logs for that day into RAM, and then—not kidding—I ran into OOM Killer because I ran out of RAM on this thing.Avi: [laugh].Corey: It is, like, yeah, that's right. The network is chatty, the logs are immense, and it's easy to forget. Because the reason I was doing this was just to figure out what are the things that are talking to each other in this environment to drive up some aspects of data transfer costs. But that is an esoteric use case for this; it's not why most people tend to think about network observability. So, I'm going to ask you the blunt question up front here because it might be a really short episode. Do we have to care about networking in the least now that cloud is the default in most locations? It is just an API call away, isn't it?Avi: With great simplicity comes great complexity. So, to the people running infrastructure, to developers or architects, turning it all on, it looks like just API calls. But did you set the policies right? Can the things talk to each other? Are they talking in patterns that are causing you wild data transfer costs?All these things ultimately come back to some team that actually has to make it go. And can be pretty hard to figure that out, right, because it's not just the VPC Flow Logs. It's, what's the policy? It's, what are they talking to that maybe isn't in that cloud, that's maybe in another cloud? So, how do you bring it all together? Like, you could have—and maybe you should have—used Athena, right? You can put VPC Flow Logs in S3 buckets and use Athena and run SQL queries if all you want is your top talker.Corey: Oh, I did. That's how I started, but Athena is, uh… it has some challenges. Let's just put it that way and leave it there. DuckDB is what I was using and I'm much happier with it for a variety of excellent reasons.Avi: Okay. Well, I'll tease you another time about, you know—I lost this battle at Kentik. We actually don't use swap, but I'm a big fan of having swap and monitoring it so the OOM Killer only does what you want or doesn't fire at all. But that's a separate religious debate.Corey: There's a counterargument of running an in-memory data store. And then oh, we're going to use it as swap though, so it's like, hang on, this just feels like running a normal database with extra steps.Avi: Computers allow you to do amazing things and only occasionally slap you nowadays with it. It's pretty amazing. But back to the question. APIs make it easy to turn on, but not so easy to run. The observability that you get within a given cloud is typically very limited.Google actually has the best. They show some topology and other things. I mean, a lot of what we do involves scraping API calls in the cloud to figure out what does this all mean, then convolving it with the VPC Flow Logs and making it look like a network, and what are the gateways, and what are the rules being applied and what can't talk to itself? If you just look at VPC Flow Logs like it's Syslog, good luck trying to figure out what VPCs are talking to each other. It's exactly the problem that you were describing.So, the ease of turning it on is exactly inversely proportional to the ease of running it. And, you know, as a vendor, we think it's an awesome [laugh] problem, but we feel for our customers. And you know, occasionally it's a pain to get the IAM roles set up to scrape things and help them, but that's you know, that's just part of the job.Corey: It's fascinating to me, just looking from an AWS perspective, just how much work clearly has to be done to translate their Byzantine and very strange networking environment and concepts into things that customers see. Because in many cases, the things that the virtual machines that we've run on top of EC2, let alone anything higher level, is being lied to the entire time about what the actual topology of the environment is. It was most notable, for me at least, at re:Invent 2022, the most recent one, where they announced they have a TCP replacement, scalable, reliable data grammar SRD. It's a new protocol entirely. It's, “Oh, wow, can we use it?” “No.” “Okay.” Like, I get that it's a lot of work, I get you're excited about it. Are you going to talk to us about how it actually works? “Oh, absolutely not.” So… okay, good for you, I guess.Avi: Doesn't Amazon have to write a press release before they build anything, and doesn't the press release have to say, like, why people give a shit, why people care?Corey: Yep. And their story on this was oh, it enables us to be a lot faster at letting EBS volumes talk to some of our beefier instances.Avi: [laugh].Corey: And that's all well and good, don't get me wrong, but it's also, “Yay, it's more reliable,” is a difficult message to send. I mean, it's hard enough when—and it's necessary because you've got to tacitly admit that reliability and performance haven't been all they could be. But when it's no longer an issue for most folks, now you're making them wonder, like, wait, how bad was it? It's just a strange message.Avi: Yeah. One of my projects for this weekend is, I actually got a gaming PC and I'm going to try compression offload to the CUDA cores because right now, we do compress and decompress with Intel cores. And like, if I'm successful there and we can get 30% faster subqueries—which doesn't really matter, you know, on the kind of massive queries we run—and 20% more use out of the computers that we actually run, I'm probably not going to do a press release about it. But good to see the pattern.But you know, what you said is pretty interesting. As people like Kentik, we have to put together, well, on Azure, you can have VPCs that cross regions, right? And in other places, you can't. And in Google, you have performance metrics that come out and you can get it very frequently, and in Amazon and Azure, you can't. Like, how do you take these kinds of telemetry that are all the same stuff underneath, but packaged up differently in different quantos and different things and make it all look the same is actually pretty fun and interesting.And it's pretty—you know, if you give some cloud engineers who focus on the infrastructure layer enough beers or alcohol or just room to talk, you can hear some funny stories. And it all made sense to somebody in the first place, but unpacking it and actually running it as a common infrastructure can be quite fun.Corey: One of the things that I have found notable about your perspective, as particularly, you're running all of the network ingest, to my understanding, in your data center environment. Because we talked about this when you were kind enough to invite me to your company all-hands offsite, presumably I assume when people do that, it's so they can beat me up in the alley, but that only happened twice. I was very pleasantly surprised.Avi: [And you 00:09:23] made fun of us only three times, so you know, you beat us—Corey: Exactly.Avi: —but it was all enjoyed.Corey: But always with love. Now, what I found fascinating was you and I sat down for a while and you talked about your data center architecture. And you asked me—since I don't have anything to sell you—is there an economical way that I could see running your environment on top of AWS? And the answer was sure, if by economical you mean an absolute minimum of six times what you're currently paying a year, sure you can get there. But it just does not make sense for any realistic approach to doing this.And the reason I bring this up is that you're in a data center not because of religious beliefs, “Of, well, this is good enough for my grandpappy, so it's good enough for me.” It's because it solves the problem you have in a way that the cloud providers clearly cannot. But you also are not anti-cloud. So, many folks who are all-in on data centers seem to be doing it out of pure self-interest where, well, if everyone goes all-in on cloud, then we have nothing left to sell them. I've used AWS VPC Flow Logs. They have nothing that could even remotely be termed network observability. Your future is assured as long as people understand what it is that you're providing them and what are you that adds. So yeah, people keep going in a cloud direction, you're happy as houses.Avi: We'll use the best tools for building our infrastructure that we can, right? We use cloud. In fact, we're just buying some reserved instances, which always, you know, I give it the hairy eyeball, but you know, we're probably always going to have our CI/CD bursty stuff in the cloud. We have performance testing regions on all the major clouds so that we can tell people what performance is to and from cloud. Like, that we have to use cloud for.And if there's an always-on model, which starts making sense in the cloud, then I try not to be the first to use anything, but [laugh] we'll be one of the first to use it. But every year, we talk to, you know, the major clouds because we're customers of all them, for as I said, our testing infrastructure if nothing else, and you know, some of them for some other parts, you know, for example, proxying VPC Flow Logs, we run infrastructure on Kubernetes in all—in the three biggest to proxy VPC Flow Logs, you know, and so that's part of our bill. But if something's always on, you know, one of our storage servers, it's a $15,000 machine that, you know, realistically runs five years, but even if you assume it runs three years, we get financing for it, cost a couple $100 a month to host, and that's inclusive of our ops team that runs, sort of, everything, you just do the math. That same machine would be, you know, even not including data transfer would be maybe 3500 a month on cloud. The economics just don't quite make sense.For burst, for things like CI/CD, test, seasonality, I think it's great. And if we have patterns like that, you know, we're the first to use it. So, it's just a question of using what's best. And a lot of our customers are in that realm, too. I would say some of them are a little over-rotated, you know, they've had big mandates to go one way or the other and don't have the right, you know, sort of nuanced view, but I think over time, that's going to fix itself. And yeah, as you were saying, like, the more people use cloud, the better we do, so it's just really a question of what's the best for us at our infrastructure and at any given time.Corey: I think that that is something that is not fully appreciated or well understood is that I work with cloud technologies because for what I do, it makes an awful lot of sense. But I've been lately doing a significant build-out in my home network on the perspective of yeah, this makes sense for what I do. And I now have increased number of workloads that I'm running here and I got to say, it feels a little strange, on some level, not to be paying AWS on something metered by the second whenever I'm running a job here. That always feels a little on the weird side. But I'm not suggesting I filled my house with servers either.Avi: [unintelligible 00:13:18] going to report you to the House on Cloudian Activities Committee [laugh] for—Corey: [laugh].Avi: To straighten you out about your infrastructure use and beliefs. I do have to ask you, and I do have some foreknowledge of this, where is the controller for your network running? Is it running in your house or—Corey: Oh, the WiFi controller lives in Ohio with all the other unpleasant things. I mean, even data transfer between Ohio and Virginia—if you're on AWS—is half-price because data wants to get out of Ohio just as much as the people do. And that's fine, but it can also fail out of band. I can chill that thing for a while and I'm not able to provision new equipment, I can't spin up new SSIDs, but—Avi: Right. It's the same as [kale scale 00:14:00], which is, like, sufficiently indistinguishable from magic, but it's nice there's [head scale 00:14:05] in case something happened to them. But yeah, you know, you just can't set up new stuff without your SSHing old way while it's down. So.Corey: And worst case, it goes away irretrievably, I can spin a new one up, I can pair everything locally, do it by repointing DNS locally, and life will go on. It's one of those areas where, like, I would not have this in Ohio if latency was a concern if it was routing every packet out halfway across the country before it hit the general internet. That would be a challenge for me. But that's not what I'm doing.Avi: Yeah, yeah. No, that makes sense. And I think also—Corey: And I certainly pay AWS by the second for that thing. That's—I have a three-year savings plan for that thing, and if nothing else, it was useful for me just to figure out what the living hell was going on with the savings plan purchase project one year. That was just, it was challenged to get that straightened out in some ways. Turns out that the high watermark of the console is a hundred-and-some-odd-thirty-million dollars you can add to cart and click the buy button. Have fun.Avi: My goodness. Okay, well.Corey: The API goes up to $26.2 billion. Try that in a free tier account, preferably someone else's.Avi: I would love to have such problems. Right now, that is not one of them. We don't spend that much on infrastructure.Corey: Oh, that is more than Amazon's—AWS's at least—quarterly revenue. So, if you wind up doing a $26.2 billion, it's like—it's that old saw. You owe Amazon a million dollars, you have a problem. If you owe Amazon $26 billion, Amazon has a problem. Yeah, that's when Andy Jassy calls you 20 minutes after you make that purchase, and at least to me, he yells at me with a, “Listen here, asshole,” and it sort of devolves from there.Avi: Well, I do live in Seattle, so you know, they send the posse out, I'm pretty sure.Corey: [laugh] I will be keynoting DevOpsDays Seattle on August 1st with a talk that might very well resonate with your perspective, “The Modern Devops: A Million Ways to Die in Production.”Avi: That is very cool. I mean, ultimately, I think that's what cloud comes back to. When cloud was being formed, it's just other people's computers, storage, and network. I don't know if you'd argue that there's a politics, control plane, or a—Corey: Oh, I would say, “Cloud? There's no cloud; just someone else's cost center.”Avi: Exactly. And so, how do you configure it? And back to the question of, should everything be on-prem or does cloud abstract at all, it's all the same stuff that we've been doing for decades and decades, just with other people's software and names, which you help decode. And then it's the question we've always had: what's the best thing to do? Do you like [Wellfleet 00:16:33] or [Protion 00:16:35]? Now, do you like Azure [laugh] or Google or Amazon or somebody else or running your own?Corey: It's almost this generation's equivalent of Vi versus Emacs.Avi: Yes. I guess there could be a crowd equivalent. I use VI, but only because I'm a lisp addict and I don't want to get stuck refining Eliza macros and connecting to the ChatGPT in Emacs. So, you know. Someone just did a Emacs as PID 0. So basically, no init, just, you know, the kernel boots into Emacs, and then someone of course had to do a VI as PID 0. And I have to admit, Emacs would be a lot more useful as a PID 0, even though I use VI.Corey: I would say that—I mean, you wind up in writing in Emacs and writing lisp in it, then I've got to say every third thing you say becomes a parenthetical.Avi: Exactly. Ha.Corey: But I want to say that there's also a definite moving of data going on there that I think is a scale that, for those of us working mostly in home labs and whatnot, can be hard to imagine. And I see that just in terms of the volume of Flow Logs, which to be clear, are smaller than the data transfer they are representing in almost every case.Avi: Almost every.Corey: You see so much of the telemetry that comes out of there and what customers are seeing and what their problems are, in different ways. It's not just Flow Logs, you ingest a whole bunch of different telemetry through a variety of modern and ancient and everything in between variety of protocols to support, you know, the horror that is network equipment interoperability. And just, I can't—I feel like I can't do a terrific job of doing justice to describing just how comprehensive Kentik is, once you get it set up as a product. What is on the wire has always been for me the arbiter of truth because computers will lie to you, but it's very tricky to get them to lie and get the network story to cover for it.Avi: Right. I mean, ultimately, that's one of the sources of truth. There's routing, there's performance testing, there's a whole lot of different things, and as you were saying, in any one of these slices of your, let's just pick the network. There's many different things that all mean the same, but look different that you need to put together. You could—the nerd term would be, you know, normalizing. You need to take all this stuff and normalize it.But traffic, we agree, that's where we started with. We call it the what if what is. What's actually happening on the infrastructure and that's the ancient stuff like IPFIX and NetFlow and sFlow. Some people that would argue that, you know, the [IATF 00:19:04] would say, “Oh, we're still innovating and it's still current,” but you know, it's certainly on-prem only. The major cloud vendors would say, “Oh, well, you can run the router—cloud routers—or you could run cloud versions of the big routers,” but we don't really see that as a super common pattern today.But what's really the difference between NetFlow and the VPC Flow Log? Well, some VPC Flow Logs have permit deny because they're really firewall logs, but ultimately, it's something went from here to there. There might not be a TCP flag, but there might be something else in cloud. And, you know, maybe there's rum data, which is also another kind of traffic. And ultimately, all together, we try to take that and then the business metadata to say, whether it's NetBox in the old world or Kubernetes in the new world, or some other [unintelligible 00:19:49], what application is this? What user is this?So, you can ask questions about why am I blowing up between these cloud regions? What applications are doing it, right? VPC Flow Logs by themselves don't know that, so you need to add that kind of metadata in. And then there's performance testing, which is sort of the what is. Something we do, Thousand Eyes does, some other people do.It's not the actual source of truth, but for example, if you're having a performance problem getting between, you know, us-east and Azure in the east, well, there's three other ways you can get there. If your actual traffic isn't getting there that way, then how do you know which one to use? Well, let's fire up some tests. There's all the metrics on what all of the devices are reporting, just like you get metrics from your machines and from your applications, and then there's stuff even up at the routing layer, which God help you, hopefully you don't need to actually get in and debug, but sometimes you do. And sometimes, you know, your neighbor tells the mailman that that mail is for me and not for you and they believe them and then you have a big problem when your bills don't get paid.The same thing happens in the cloud, the same thing happens on the internet [unintelligible 00:20:52] at the routing. So, the goal is, take all the different sources of it, make it the same within each type, and then pull it all together so you can look at a single place, you can look at a map, you can look at everything, whether it's the cloud, whether it's your own data centers, your own WAN, into the internet and in between in a coherent way that understands your application. So, it's a small task that we've bit off, but you know, we have fun solving it.Corey: Do you find that when you look at customer environments, that they are, and I don't mean to be disparaging here, truly I don't, but if you were to ask me to design something today, I would probably not even be using VPCs if I'm doing this completely greenfield. I would be a lot more cloud-first, et cetera, et cetera. Whereas in many cases, that is not the right path, especially if you know, customers have the temerity to not be founded within the last 18 months before AWS existed in some ways. Do you find that the majority of what they're doing looks like they're treating the cloud like data centers or do you find that they are leveraging cloud in ways that surprise you and would not be possible in traditional data centers? Because I can't shake the feeling that the network has a source of truth for figuring out what's really going on [is very hard to beat 00:22:05].Avi: Yes, for the most part, to both your assertion at the end and sort of the question. So, in terms of the question, for the most part, people think of VPCs as… you know, they could just equivalent be VLANs and [unintelligible 00:22:21], right? I've got policies, and I have these things that are talking to each other, and everything else is not local. And I've got—you know, it's not a perfect mapping to physical interfaces in VLANs but it's the equivalent of that.And that is sort of how people think about it. In the data center, you'd call it micro-segmentation, in the cloud, you call it clouding, but you know, just applying all the same policies and saying this stuff can talk to each other and not. Which is always sort of interesting, if you don't actually know what is talking [laugh] to each other to apply those policies. Which is a lot of what you know, Kentik gets brought in for first. I think where we see the cloud-native thinking, which is overlaid on top of that—you could call it overlay, I guess—which is service mesh.Now, putting aside the question of what's going to be a service mesh, what's going to be a network mesh, where there's something like [unintelligible 00:23:13] sit, the idea that there's a way that you look at traffic above the packets at, you know, layers three to more layer seven, that can do things like load balancing, do things like telemetry, do things like policy enforcement, that is a layer that we see very commonly that a lot of the old school folks have—you know, they want their lsu F5s and they want their F5 script. And they're like, “Why can't I have this in the cloud?”—which I guess you could buy it from F5 if you really want—but that's pretty common. Now, not everything's a sidecar anymore and there's still debates about what's going on there, but that's pretty common, even where the underlying cloud just looks like it could just be a data center.And that seems to be state of the art, I would say, our traditional enterprise customers, for sure. Our web company customers, and you know, service providers use cloud more for their OTT and some other things. As we work with them, they're a little bit more likely to be on-prem, you know, historic. But remember, in the enterprise, there's still a lot of M&A going on, I think that's even going to pick up in the next couple of years and a lot of what they're doing is lift-and-shift of [laugh] actual data centers. And my theory is, it's got to be easier to just make it look like VPCs than completely redo it.Corey: I'd say that there's reasons that things are the way that they are. Like, ignoring that this is the better approach from a technical perspective entirely because that's often not the only answer, it's we have assurances we made as part of audit compliance regimes, of our SOC 2, of how we handle certain things and what those controls are. And yeah, it's not hard for even a junior employee, most of the time, to design a reasonable architecture on a whiteboard. The problem is, how do you take something pre-existing and get it to a state that closely resembles that while not turning it off for a long time?Avi: Right. And I think we're starting to see some things that probably shouldn't exist, like, people trying to do VXLAN as overlays into and between VPCs because that was how their data s—you know, they're more modern on the data center side and trying to do that. But generally, I think people have an understanding they need to be designing architecture for greenfield things that aren't too far bleeding edge, unless it's like a pure developer shop, and also can map to the least common denominator kinds of infrastructure that people have. Now, sometimes that may be serverless, which means, you know, more CDN use and abstracted layers in front, but for, you know, running your own components, we see a lot of differences but also a lot of commonality. It's differences at the micro but commonality the macro. And I don't know what you see in your practice. So.Corey: I will say that what I see in practice is that there's a dichotomy where you have born-in-the-cloud companies where 80% of their spend is on a single workload and you can do a whole bunch of deep optimizations. And then you see the conglomerate approach where it's giant spend, but it's all very diffuse across 1500 different applications. And different philosophies, different processes, different cultures give rise to a lot of these things. I will say that if I had a magic wand, I would—and again, the fact that you sponsor and promote this episode is deeply appreciated. Thank you—Avi: You're welcome.Corey: —but it does not mean that you get to compromise my authenticity and objectivity. You can't buy my opinion, just my attention. But I will say this, that I would love it if my customers used Kentik because it is one of the best things I've ever seen to describe what is talking to what that scale and in volume without going super deep into the weeds. Now, obviously, I'm not allowed to start rolling out random things into customer environments. That's how I get sued to death. But, ugh, I wish it was there.Avi: You probably shouldn't set up IAM rules without asking them, yes. That wouldn't be bad.Corey: There's a reason that the only writable stuff that I have access to is generating reports in Cost Explorer.Avi: [laugh]. Okay.Corey: Everything else is read-only. All we do is to have conversations with folks. It sets context for those conversations. I used to think that we'd be doing this as a software offering. I no longer believe that actually solves the in-depth problems that people have.Avi: Well, I appreciate the praise. I even take some of the backhanded praise slash critique at the beginning because we think a lot about, you know, we did design for these complex and often hybrid infrastructures and it's true, we didn't design it for the two or four router, you know, infrastructure. If we had bootstrapped longer, if we'd done some other things, we might have done it that way. We don't want to be exclusionary. It's just sort of how we focus.But in the kind of customers that you have, these are things that we're thinking about what can we do to make it easier to onboard because people have these massive challenges seeing the traffic and understanding it and the cost and security and the performance, but to do more with the VPC Flow Logs, we need to get some of those metrics. We think about should we make an open-source thing. I don't know how much you've seen the concern that people have universally across cloud providers that they turn on something like Kentik, and they're going to hit their API rate limiter. Which is like, really, you can't build a cache for that at the scale that these guys run at, the large cloud providers. I don't really understand that. But it is what it is.We spent a lot of time thinking about that because of security policy, and getting the kind of metrics that we need. You know, if we open-source some of that, would it make it easier, plug it into people's observability infrastructure, we'd like to get that onboarding time down, even for those more complex infrastructures. But you know, the payoff is there, you know? It only takes a day of elapsed time and one hour or so. It's just you got to get a lot of approvals to get the kind of telemetry that you need to make sense of this in some environments.Corey: Oh, yes. And that's part of the problem, too, is like, you could talk about one of those big environments where you have 1500 apps all talking to each other. You can't make sense of any of it without talking to people and having contacts and occasionally get a little bit of [unintelligible 00:29:07] just what these things are named. But at that point, you're just speculating wildly. And, you know, it's an engineering trap, where I'm just going to guess rather than asking someone who knows the answer because I don't want to look foolish. It's… you just three weeks chasing your own tail. Who's the foolish one?Avi: We're not in a competitive business to yours—Corey: [laugh].Avi: But I do often ask when we're starting off, “So, can you point us at the source of truth that describes what all your applications are?” And usually, they're, like, “[laugh]. No.” But you know, at the same time to make sense of this stuff, you also need that metadata and that's something that we designed to be able to take.Now, Kubernetes has some of that. You may have some of it in ServiceNow, a lot of people use. You may have it in your own text file, CSV somewhere. It may be in NetBox, which we've seen people actually use for the cloud, more on the web company and service provider side, but even some traditional enterprise is starting to use it. So, a lot of what we have to do as a vendor is put all that together because yeah, when you're running across multiple environments and thousands of applications, ultimately scrying at IP addresses and VPC IDs is not going to be sufficient.So, the good news is, almost everybody has those sources and we just tried to drag it out of them and pull it back together. And for now, we refuse to actually try to get into that business because it's not a—seems sort of like, you know, SAP where you're going to be sending consultants forever, and not as interesting as the problems we're trying to solve.Corey: I really want to thank you, not just for supporting the show of course, but also for coming here to suffer my slings and arrows. If people want to learn more, where's the best place for them to find you? And please don't respond with an IP address.Avi: 127.0.0.1. You're welcome at my home at any time.Corey: There's no place like localhost.Avi: There's no place like localhost. Indeed. So, the company is kentik.com, K-E-N-T-I-K. I am avi@kentik.com. I am@avifriedman on Twitter and LinkedIn and some other things. And happy to chat with nerds, infrastructure nerds, cloud nerds, network nerds, software nerds, debate, maybe not VI versus Emacs, but should you swap space or not, and what should your cloud architecture look like?Corey: And we will, of course, put links to that in the [show notes 00:31:20].Avi: Thank you.Corey: Thank you so much for being so generous with your time. I really appreciate it.Avi: Thank you for having this forum. And I will let you know when I am down in San Francisco with some time.Corey: I would be offended if you didn't take the time to at least say hello. Avi Friedman, CEO at Kentik. I'm Cloud Economist Corey Quinn, and this has been a promoted guest episode of Screaming in the Cloud. If you've enjoyed this podcast, please leave a five-star review on your podcast platform of choice, whereas if you've hated this podcast, please leave a all five-star review on your podcast platform of choice, along with an angry comment saying how everything, start to finish, is somehow because of the network.Corey: If your AWS bill keeps rising and your blood pressure is doing the same, then you need The Duckbill Group. We help companies fix their AWS bill by making it smaller and less horrifying. The Duckbill Group works for you, not AWS. We tailor recommendations to your business and we get to the point. Visit duckbillgroup.com to get started.
At the heart of The Prophets' vision are “The 24 Essential Supply Chain Processes.” What are they? Find out, and see the future yourself. Click here Version 6 of MMOG/LE integrates supply chain processes and can reduce a company's inventory by up to 60%. But cost savings isn't the only reason to love this self-assessment.IATF 16949 hasn't been updated since 2016. As the auto industry applies pandemic-era lessons to quality systems, MMOG/LE raises the bar for effective supply chain management and encourages collaboration across all functions in an organization.In this follow-up to How MMOG/LE Is Transforming The Automotive Supply Chain, the Auto Supply Chain Prophets dive into the quality components of MMOG/LE and examine its role alongside existing IATF standards. Themes discussed in this episode: How MMOG/LE v6 addresses quality standards.Supply chain processes suffer from high-level work instructions that lack details.Quality and supply chains need to involve IT for the systems to work together.Many organizations have incongruencies between the cutting-edge technology they're adding to vehicles and the outdated processes used to produce it.The right processes can help startups leapfrog traditional OEMs.What supply chain leaders can do right now to support their future success.Featured on this EpisodeName: Cathy FisherTitle: Founder and President, QuistemAbout: Cathy's firm helps its clients, particularly automotive clients, eliminate customer complaints and increase their profits. She has worked in the automotive supply chain since the 1980s when she started her career with General Motors. Connect: LinkedIn Name: Terry Onica Title: Director, Automotive at QADAbout: For two decades, Terry has been the automotive vertical director of this provider of manufacturing Enterprise Resource Planning (ERP) software and supply chain solutions. Her career began in the supply chain in the late 1980s when she led a team to implement Electronic Data Interchange (EDI) for all the Ford assembly and component plants. Connect: LinkedInEpisode HighlightsTimestamped inflection points from the show[2:01] Answering the naysayers: Terry consistently sees customers reduce inventory by 15-60% after a proper MMOG/LE implementation. She challenges anyone who doubts the assessment's cost-saving powers.[3:59] Automating the response: Lower tiers support electronic data interchange (EDI) so they can react to OEM demands. Terry and Cathy discuss the importance of automation in supply chain communication.[6:23] Explain yourself: Terry says the high-level work instructions she sees from suppliers are often “pathetic.” With QAD, detailed work instructions are included for every process.[12:16] What's new with v6: From environmental, social, and governance...
In this episode Mr Allan Majuru CEO Zimtrade and Ambassador of IATF 2023 shares insights on Zimtrade's initiatives and efforts to grow exports for Zimbabwean businesses and sme's. Mr Allan Majuru is the CEO at Zimtrade, he is also Board Chairperson of Agricultural Marketing Authority of Zimbabwe and Ambassador of Intra Africa Trade Fair (IATF 2023). IATF is an initiative of Afreximbank, in Collaboration with the African Union and the AFCFTA Secretariat, hosted by African governments. Book recommendations: The Monk who sold his ferrari by Robin Sharma The 5am club by Robin Sharma Podcast recommendations: The Smallstarter by John-Paul Iwuoha website link www.shopatzim.co.zw
A inseminação artificial em tempo fixo (IATF) é a uma das principais biotecnologias reprodutivas, que tem como objetivo elevar a eficiência reprodutiva dos rebanhos por meio da indução e sincronização da ovulação das fêmeas através de protocolos hormonais. Os especialistas Ueverson Martins e Patrick Santos estiveram com a gente para um bate papo mais que especial, aprofundando na biotecnologia, mercado, futuro do ramo, além de cursos e estágios que estão oferecendo… Aperte o play e venha aprender muito com estes profissionais que vem crescendo e fazendo um excelente trabalho em prol da genética veterinária! @paatrickgsantos @vetnunes_reproducaoanimal @martinsueverson @brasvene_ #veterinaria #medvet #zootecnia #animal #iatf #semem #reproducao #aspiracao #bovino #boi #vaca #agro #inseminacao #melhoramentogenetico #genetica #reproducao #reproducaoanimal #podcast #podcastbrasil #mevcast #estagio #curso
Dioni Gorla, die Adidas Terrex Athletin ist dreimalige Gewinnerin des Marathon beim IATF, Top 25 beim UMTB OCC, sowie Platz 3 beim Ultra Trail Cape Town. Was einen von Griechenland nach Innsbruck zieht, wie man aus versehen gesponserte Athletin wird und warum Social Media vielleicht nicht so böse ist wie viele sagen, verrät Sie uns in dieser Ausgabe von Run.Cook.Eat.Repeat.
Dioni Gorla, die Adidas Terrex Athletin ist dreimalige Gewinnerin des Marathon beim IATF, Top 25 beim UTMB OCC, sowie Platz 3 beim Ultra Trail Cape Town. Was einen von Griechenland nach Innsbruck zieht, wie man aus versehen gesponserte Athletin wird und warum Social Media vielleicht nicht so böse ist wie viele sagen, verrät Sie uns in dieser Ausgabe von Run.Cook.Eat.Repeat. Drucken Bulgur-Bowl Portionen 1 Zutaten50 g Bulgur100 g Feta0,5 Avocado1 Handvoll Nüsse nach Wahl100 g gekochte Kidneybohnen (der andere Dosenbohnen)50 g gekochte Linsen100 g Brokkoli1 EL Kürbiskernöl2 EL Tahin AnleitungenDen Bulgur nach Packungsanleitung kochenBrokkoli in kleine Röschen schneiden oder reissen und entweder anbraten, blanchieren oder dampfgaren. Je nach Laune und Geschmack.Linsen und Bohnen abgießen und waschen.Nüsse ohne Fett ...Du möchtest deinen Podcast auch kostenlos hosten und damit Geld verdienen? Dann schaue auf www.kostenlos-hosten.de und informiere dich. Dort erhältst du alle Informationen zu unseren kostenlosen Podcast-Hosting-Angeboten. kostenlos-hosten.de ist ein Produkt der Podcastbude.Gern unterstützen wir dich bei deiner Podcast-Produktion.
Góc nhìn về việc xuất khẩu " 999 xe ô tô điện Vinfast " - Phần 1 - Tiêu chuẩn IATF 16949 || John&Partners Trong bối cảnh ô tô nhập khẩu nguyên chiếc từ các nước ASEAN hưởng thuế suất nhập khẩu ưu đãi 0% đang ồ ạt về Việt Nam, gây áp lực nặng nề lên các doanh nghiệp sản xuất, lắp ráp ô tô trong nước, việc VinFast xuất khẩu ô tô sang Mỹ có ý nghĩa vô cùng quan trọng, tạo động lực cho ngành sản xuất ô tô nội địa, góp phần hiện thực hóa chiến lược phát triển ngành công nghiệp ô tô Việt Nam… 1. Ts. Ngô Công Trường - Tiến sĩ Kinh Tế - Đại học Châu Âu - Sáng lập và Giám đốc chuyên môn tại John&Partners - Giám đốc của Hiệp hội Chất lượng Mỹ (ASQ) tại Việt Nam - Nhiều năm kinh nghiệm trong thiết lập, triển khai, đào tạo, tư vấn Tối ưu hóa cấu trúc vận hành doanh nghiệp -- Tìm hiểu thêm về John&Partners tại: - Website: http://john-partners.com - Linkedin: https://www.linkedin.com/company/johnhandpartners - Fanpage: https://www.facebook.com/johnandpartners -- Thông tin liên hệ: - Website: www.john-partners.com - Email: info@john-partners.com - Điện thoại: (84) 077 5955 007 #johnpartners #xuhuong #vinfast
Wishing you a wonderful holiday season!In case you missed it, check out some of our selected episodes from season 1.Episode 21 with Dan Sharkey. You'll know Dan, he's well-known in supply chain circles and he's got his finger on the pulse of today's issues. And he reminds us to and I quote, "contract deliberately"Episode 15 with Katie Pullin, also in the legal profession in the auto supply chain, she talks about the force majeure pandemic, are you abusing the term?Episode 11 with Mike and Rocky, self-confessed quality nerds and data geeks, you'll learn all about automating the quality management system and why the word silo is a four-letter word in their vocabularyEpisode 12 meet the shop floor leaders making it happen at Detroit Manufacturing Systems and how they cultivated and uplifted a strong team that's designed for executionEpisodes 3 & 5 an interview with a well-known supply chain veteran Bill Hurles, Bill is the former executive director of global supply chain for General MotorsEpisode 4 meet Julie Dedene as she reminds us not to forget the grease. She's in the grease business. Learn about the importance of a secondary sourceEpisode 6 with Paul Eichenberg. Paul talks about the unique set of auto supply chain obstacles that the ICE and EV organizations face and the type of auto supply chain leader that the EV industry demandsEpisodes 16 & 17 with Gary Vasliash, you'll know Gary, he's a veteran auto writer in the space. And you'll hear his unique views on the challenges aheadEpisodes 9 & 19 Are you ready to deliver on the promise of delivery? familiar with MMOG/LE, and IATF 6949? listen to Terry and Cathy and download their framework for success. They've done the work for you. At the heart of The Prophets' vision are “The 24 Essential Supply Chain Processes.” What are they? Find out, and see the future yourself. Click here
Danae started her career in metrology in 1986 as a Test Measurement & Diagnostic Equipment (TMDE) Technician in the USMC. Her background includes the alphabet soup of regulated industries to including DOD, FCC, FDA, cGMP, DOE, FAA, SAE, IATF, and NRC. Working in multiple industries and disciplines has given her an opportunity to experience the field of metrology from many perspectives. She is passionate about training up the next generation of metrologists and driven to see metrology advanced as a recognized critical infrastructure to nearly all areas of business. Danae joined Pacific Northwest National Laboratory (PNNL) in the Energy & Environment Nuclear Sciences Division working as a Metrologist for Radiation Measurements and Irradiations (RMI) at the Hanford site in Richland, WA in 2022. She is also currently serving as the National Conference of Standards Laboratories International Vice President, Industrial Metrology Programs and is active in multiple working groups.
The Department of the Interior and Local Government is set to recommend at next week's coming Inter-Agency Task Force o IATF meeting to consider Cebu City Local Government's easing of the face mask rule - Idudulog ng Department of the Interior and Local Government sa pulong ng Inter-Agency Task Force o IATF sa susunod na linggo ang pagluluwag ng Pamahalaang Lungsod ng Cebu sa paggamit ng face mask.
VOTT: Cebu's order on face masks should prompt IATF review | June 13, 2022Subscribe to The Manila Times Channel - https://tmt.ph/YTSubscribe Visit our website at https://www.manilatimes.net Follow us: Facebook - https://tmt.ph/facebook Instagram - https://tmt.ph/instagram Twitter - https://tmt.ph/twitter DailyMotion - https://tmt.ph/dailymotion Subscribe to our Digital Edition - https://tmt.ph/digital Check out our Podcasts: Spotify - https://tmt.ph/spotify Apple Podcasts - https://tmt.ph/applepodcasts Amazon Music - https://tmt.ph/amazonmusic Deezer: https://tmt.ph/deezer Stitcher: https://tmt.ph/stitcherTune In: https://tmt.ph/tuneinSoundcloud: https://tmt.ph/soundcloud #TheManilaTimes#VoiceOfTheTimes Hosted on Acast. See acast.com/privacy for more information.
Subscribe to The Manila Times Channel - https://tmt.ph/YTSubscribe Visit our website at https://www.manilatimes.net Follow us: Facebook - https://tmt.ph/facebook Instagram - https://tmt.ph/instagram Twitter - https://tmt.ph/twitter DailyMotion - https://tmt.ph/dailymotion Subscribe to our Digital Edition - https://tmt.ph/digital Check out our Podcasts: Spotify - https://tmt.ph/spotify Apple Podcasts - https://tmt.ph/applepodcasts Amazon Music - https://tmt.ph/amazonmusic Deezer: https://tmt.ph/deezer Stitcher: https://tmt.ph/stitcherTune In: https://tmt.ph/tuneinSoundcloud: https://tmt.ph/soundcloud #TheManilaTimes Hosted on Acast. See acast.com/privacy for more information.
Subscribe to The Manila Times Channel - https://tmt.ph/YTSubscribe Visit our website at https://www.manilatimes.net Follow us: Facebook - https://tmt.ph/facebook Instagram - https://tmt.ph/instagram Twitter - https://tmt.ph/twitter DailyMotion - https://tmt.ph/dailymotion Subscribe to our Digital Edition - https://tmt.ph/digital Check out our Podcasts: Spotify - https://tmt.ph/spotify Apple Podcasts - https://tmt.ph/applepodcasts Amazon Music - https://tmt.ph/amazonmusic Deezer: https://tmt.ph/deezer Stitcher: https://tmt.ph/stitcherTune In: https://tmt.ph/tuneinSoundcloud: https://tmt.ph/soundcloud #TheManilaTimes Hosted on Acast. See acast.com/privacy for more information.
KUWTT: IATF, high court sued over mandatory jabs | Dec. 8, 2021Subscribe to The Manila Times Channel - https://tmt.ph/YTSubscribeVisit our website at https://www.manilatimes.netFollow us:Facebook - https://tmt.ph/facebookInstagram - https://tmt.ph/instagramTwitter - https://tmt.ph/twitterDailyMotion - https://tmt.ph/dailymotionSubscribe to our Digital Edition - https://tmt.ph/digitalCheck out our Podcasts:Spotify - https://tmt.ph/spotifyApple Podcasts - https://tmt.ph/applepodcastsAmazon Music - https://tmt.ph/amazonmusicDeezer: https://tmt.ph/deezerStitcher: https://tmt.ph/stitcherTune In: https://tmt.ph/tuneinSoundcloud: https://tmt.ph/soundcloud#TheManilaTimes#KeepUpWithTheTimes Hosted on Acast. See acast.com/privacy for more information.
VOTT: Abolishing the IATF is an idea with considerable merit | Mar 25, 2021 Subscribe to The Manila Times Channel - https://tmt.ph/YTSubscribe Visit our website at https://www.manilatimes.net Follow us: Facebook - https://tmt.ph/facebook Instagram - https://tmt.ph/instagram Twitter - https://tmt.ph/twitter DailyMotion - https://tmt.ph/dailymotion Subscribe to our Digital Edition - https://tmt.ph/digital Check out our Podcasts: Spotify - https://tmt.ph/spotify Apple Podcasts - https://tmt.ph/applepodcasts Amazon Music - https://tmt.ph/amazonmusic Deezer: https://tmt.ph/deezer Stitcher: https://tmt.ph/stitcherTune In: https://tmt.ph/tuneinSoundcloud: https://tmt.ph/soundcloud #TheManilaTimes#VoiceOfTheTimes Hosted on Acast. See acast.com/privacy for more information.
VOTT: IATF and MM mayors should resolve policy dispute on reopening of cinemas | Feb 16, 2021#TheManilaTimes#VoiceOfTheTimesSubscribe to The Manila Times Channel - https://tmt.ph/YTSubscribeVisit our website at https://www.manilatimes.netFollow us:Facebook - https://tmt.ph/facebookInstagram - https://tmt.ph/instagramTwitter - https://tmt.ph/twitterDailyMotion - https://tmt.ph/dailymotionSubscribe to our Digital Edition - https://tmt.ph/digitalCheck out our Podcasts:Spotify - https://tmt.ph/spotifyApple Podcasts - https://tmt.ph/applepodcastsAmazon Music - https://tmt.ph/amazonmusicDeezer: https://tmt.ph/deezerStitcher: https://tmt.ph/stitcherTune In: https://tmt.ph/tuneinSoundcloud: https://tmt.ph/soundcloud Hosted on Acast. See acast.com/privacy for more information.
Voice Of The Times | Dec. 22, 2020“Are the DoH and IATF aware that the PCR test creates false positives?”Subscribe to The Manila Times Channel - https://tmt.ph/YTSubscribeVisit our website at https://www.manilatimes.netFollow us:Facebook - https://tmt.ph/facebookInstagram - https://tmt.ph/instagramTwitter - https://tmt.ph/twitterDailyMotion - https://tmt.ph/dailymotionSubscribe to our Digital Edition - https://tmt.ph/digitalCheckout our PodcastsSpotify - https://tmt.ph/spotifyApple Podcasts - https://tmt.ph/applepodcastsAmazon Music - https://tmt.ph/amazonmusic Hosted on Acast. See acast.com/privacy for more information.
“IATF and DoH should defend new face mask/face shield edict”Subscribe to The Manila Times Channel - https://tmt.ph/YTSubscribeVisit our website at https://www.manilatimes.netFollow us:Facebook - https://tmt.ph/facebookInstagram - https://tmt.ph/instagramTwitter - https://tmt.ph/twitterDailyMotion - https://tmt.ph/dailymotionSubscribe to our Digital Edition - https://tmt.ph/digitalCheckout our PodcastsSpotify - https://tmt.ph/spotifyApple Podcasts - https://tmt.ph/applepodcasts Hosted on Acast. See acast.com/privacy for more information.
Neste episódio, Paulo e Ângelo trouxeram mais um mitos e verdades do agronegócio, o décimo episódio desta série que teve início em 2017. Como sempre, a participação dos ouvintes foi chave para que pudéssemos produzir este conteúdo. PARTICIPARAM DESTE EPISÓDIO Alexandre Gomes “Senhor A” – Sete Lagoas/MG Henrique Batistti – Pedra Preta/MT Paulo Segundo – Campo Maior/PI Rogério Matsuda – Lins/SP LINKS CITADOS NO EPISÓDIO ABIC: https://www.abic.com.br Hormônios em vacas: http://www.cbra.org.br/portal/downloads/publicacoes/rbra/v43/n4/P797-802%20-%20RB821%20-%20Camila%20Amaral%20D%20Avila.pdf Morangos: https://summitagro.estadao.com.br/tendencias-e-tecnologia/novos-metodos-garantem-a-producao-de-morangos-sem-agrotoxicos/ Morangos: https://ainfo.cnptia.embrapa.br/digital/bitstream/item/179724/1/Luis-Eduardo-MORANGUEIRO-miolo.pdf Solo argiloso: https://institutoagro.com.br/solo-argiloso/ ACOMPANHE A REDE AGROCAST Instagram: https://www.instagram.com/redeagrocast/ Facebook: https://www.facebook.com/redeagrocast/ Twitter: https://twitter.com/redeagrocast INTERAJA COM O AGRO RESENHA Instagram: www.instagram.com/agroresenha Twitter: www.twitter.com/agroresenha Facebook: www.facebook.com/agroresenha E-MAIL Se você tem alguma sugestão de pauta, reclamação ou dúvida envie um e-mail para contato@agroresenha.com.br APOIE O AGRO RESENHA PicPay: https://picpay.me/agroresenha Padrim: https://www.padrim.com.br/agroresenha PADRINHOS E MADRINHAS DO AGRO RESENHA Paulo Henrique Sá Fortes Mariely Biff Fabio Makoto Okuno Michael Ortigara Goulart Luciano Mendes César Kobayakawa Cleomar Amaral Michely Santana Lucas Fuchs Cesar Augusto da Silva Bessa Paulo Massaharu Ozaki Maria Luisa de Moraes Ozaki Fernando Borges Luiz Fernando Sacchett Dias Geide Antonio Figueiredo Junior Rondiny Carneiro Jaime Sanchez da Cruz Rios Marcos Mamoru Fugio Otto Ozaki André Tavares de Vasconcelos Carla Papai Diego Henrique Uroda Albert Kenji Hirose Valter Galan Daniel Rezende Gobbi Alberto Affonso Marinho Neto Fernando Alonso Bueno Enrique da Silva Gomes Gaspar César Pedroso Pablo Figueiredo Guilherme Távora Paulo Henrique Sá Fortes Caio Zitelli Gabriel Testa Michel Cambri Leonardo Alves César Augusto Figueiredo Wilton Arruda Cinthia Siqueira Raul de Lima Alexandre Sorensen Delci Baleeiro Jr. Fernando Collares Paulo Henrique Wilson Henrique Batistti Marcelo Stabile Alexandre Evaristo Zeni Rodrigues Fábio Francisco de Lima Renata Casassa Cayron Giacomelli Antonio da Luz Rafael Ribeiro Ana Carolina Rossetti Rodrigo Xavier Cássio Reis Natalia Rezende Fernando Rati Tiago Pandolfo Vinícius Rezende Daniel Fontão de Pauli FICHA TÉCNICA Produção: Paulo Ozaki Convidado: Ângelo Ozelame Edição: Senhor A - https://editorsenhor-a.com.br Comunidade Agro de Sucesso: http://www.comunidadeagrodesucesso.com.br/
© 2020-2025 Ivy Podcast Discovery LLC
