Podcasts about bfc

Wer wird der Superstar sein, der die 250. Ausgabe der Rückfallzieher mit Glanz und Gloria bescheint? Helene Fischer, ein Wildecker Herz-Bub, King Klopp? Die Planungen für das in kurzer Bälde anstehende Podcast-Jubiläum von Meigl und Guido laufen unter geheimer Geheimhaltung. Wer Details verrät, riskiert Leib und Leben. Kabarett-Legende Meigl, der nach eigener Auskunft ein Künstler ist, der gesellschaftskritisches Gedöns durch Wortwitz, Mimik, Gestik, Mittelscheitel, Cordhose, Old Spice und Musik mit Leutzscher Humor darstellt, ignorierte die Befehle der 25-köpfigen Jubiläums-Planungscrew. Und radelte allen Ernstes mit einem grün-weißen Luftballon mit der Aufschrift „250!“ am Fahrrad-Lenker gen LVZ-Aufnahmestudio. Ein Crew-Mitglied erstach den Ballon auf Guidos Geheiß mit einem Stielkamm der Konsum-Bürstenfabrik Stützengrün im Erzgebirge. Nach harten Worten und Vorwürfen umarmten sich Meigl und Guido, verabreichten sich den vorm Hörspiel üblichen Bruderkuss, öffneten den oberen Knopf ihrer Holzfällerhemden, sortierten die Glieder ihrer mächtigen goldenen Halsketten und legten los. Ja, das 3:1 der Roten Bullen gegen Köln war ganz wunderbar und wurde von Guido mit Reporter-Ikone Wolff Fuss in der legendären Trattoria No.1 seziert. Quintessenz: Wer das 1:3 kassiert, kann das 2:2 nicht mehr machen. Meigl freut sich inbrünstig über die Auferstehung seiner Chemiker (2:0 gegen den BFC) und Mainzer (4:1 in Augsburg): „Das sind Clubs nach meinem Gusto, da wird noch Bier mit Umdrehungen ausgeschenkt, hat die Bratwurst die Länge eines Staffelholzes, zahlen Hunderttausende Mitglieder Beitrag. Bei Chemie und den Nullfünfern wird Tradition mit Leben gefüllt, Güüdddoo!“ Guido steigt mit dieser Hinterlassenschaft des heiligen Thomas Morus in die Bütt: „Tradition, lieber Meigl, ist nicht das Halten der Asche, sondern das Weitergeben der Flamme.“ Und damit sind ausdrücklich keine Feuerwerkskörper gemeint. Außerdem im Bauchladen der Podcast-Giganten: Die schon 26. Konsultation zwischen dem VfL Wolfsburg und RB Leipzig. Meigl tippt wie immer 1:1, Guido, der am Sonntag beim Sport1-Doppelpass sein Innerstes nach Außen kehren wird, tippt 3:1 für RB. Präsentiert werden Meigl und Guido vom sagenumwobenen Hotel & Restaurant Hiemann in der Delitzscher Landstraße 75 in Wiederitzsch. Dieses großartige Kleinod ist seit 30 Jahren Familien geführt, bei Chef Jens Hiemann laufen alle Lebensadern der gastronomischen Vorzeige-Einrichtung zusammen. Vormerken: Am 21. Novembersteigt die Big-Bottle-Party. Meigl und Guido haben schon reserviert. Lob, Lob oder Lob? Bitte an g.schaefer@lvz.de mailen.

On this special London Fashion Week edition of the Glossy Podcast, international reporter Zofia Zwieglinska is joined by editor-in-chief Jill Manoff to break down the shows, shifts and standout moments shaping the season. London has been particularly charged this week, with President Trump's visit, Parliament debating fashion's cultural and economic value, and new BFC head Laura Weir waiving designer fees and boosting international visibility. The London Fashion Week schedule reflects the mix of pressures and possibilities: More fast-fashion names like Zara joined the calendar, bringing visibility but also sustainability concerns. The stalwarts are still showing, including JW Anderson, Simone Rocha and Erdem, which are holding strong among a tough macro environment. And a wave of NEWGEN designers, such as Jenn Lee, The Ouze and Ewusie, are bringing fresh energy. NEWGEN is the British Fashion Council's talent support scheme that gives emerging designers financial backing, mentoring and a platform to show at London Fashion Week. Zofia also shares highlights to come this week in Glossy's coverage, including what is going on at Rixo, Edeline Lee and Patrick McDowell. But at the center of it all is Burberry. Zofia and Jill trace the brand's turbulent recent history — from executive and creative director shifts to pricing resets — and assess Joshua Schulman's “Burberry Forward” strategy (9:00). Luxury analyst Luca Solca from brokerage firm Bernstein joins the episode to weigh in on Burberry's turnaround, stressing the importance of heritage, consistent execution and the brand's ongoing challenge in accessories. We discuss how Burberry's new campaigns — like "Festival Season," featuring Liam Gallagher, and "Back to the City," shot on a red London bus — are reframing the brand. We also talk about how wholesale partners are responding to the brand's Fall 2025 collection and what's next for Burberry, in both the U.K. and the U.S.

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

Avec Justine Parmentier d'Athéna BFC

Prosegue l'analisi degli stranieri che arrivano in Serie A in ottica fantacalcistica. È il turno di Torbjørn Heggem, nuovo difensore del Bologna pronto a prendersi il posto da titolare. Ne parlano Simone Solario e Nicola Bondavalli. Potrero, dove tutto ha inizio. Un podcast sul calcio italiano e internazionale.Su Como TV (https://tv.comofootball.com) nel 2025 potete seguire in diretta e gratuitamente le partite della Saudi Pro League, Saudi King's Cup, Supercoppa d'Arabia, Copa Libertadores, Copa Sudamericana, Recopa, Liga Profesional Argentina, Trofeo de Campeones argentino, Eredivisie, Coppa di Francia, Scottish Premiership, Coppa di Scozia, Scottish League Cup, Scottish Championship, Coppa di Portogallo, Supercoppa di Portogallo, HNL croata e tutti i contenuti di calcio italiano e internazionale on demand.Diventa un supporter di questo podcast: https://www.spreaker.com/podcast/potrero--5761582/support.

Welcome to Forest Fan TV for a live podcast of "Grumpy Old Reds," where Wolfie and the panel tackle all the latest transfer news surrounding Nottingham Forest! The big talking point is the imminent signing of Rennes striker Arnaud Kalimuendo in a potential €30m deal, with reports confirming the 23-year-old is set to join after an impressive 17-goal Ligue 1 season. The panel will debate where he fits into Nuno Espirito Santo's squad—will he lead the line or compete with Chris Wood and Igor Jesus —and who might be dropped or shifted to accommodate his arrival as the Reds prepare for the Premier League and Europa League. The conversation will also look ahead to Brentford, Forest's first Premier League game of the season this weekend at the City Ground, where the panel will assess the team's readiness after a lackluster pre-season. With new signings like Ndoye and potentially Kalimuendo boosting the squad, Wolfie and the crew will discuss tactics, key players to watch, and whether Nuno's less defensive approach can pay off against a tough BFC side. The mood might be grumpy, but the analysis will be sharp as they predict the outcome of this crucial opener.Jump into the live chat and share your thoughts as the podcast unfolds! Where do you think Kalimuendo should play, and who might lose their spot? What's your prediction for the Brentford game—are you optimistic or worried? Don't forget to like, subscribe, and hit the bell to join the banter live #nffc #nottinghamforest #premierleague Learn more about your ad choices. Visit podcastchoices.com/adchoices

Während wir kurioses "Feedback" lesen legen wir uns Otto – Die Riesenspinne versteckt aufs Bein. Ein vogelwilder Auswärtssieg beim BFC! Wiedem auch sei: Alle Spieler sind wichtig und die U19 ist Derbysieger!

Join us in conversation with Black Family Camp founders Frances Saunders and Clare Norris-Bell as we talk about the origin story, the learning, the love, and the transformation of Black Family Camp program.  Registration for the 3rd annual Black Family Camp opens August 1st!Register for BFC 2026 (January 2-4) here! Donate to support Black Family Camp here! Learn more about our amazing partners @ LT Dance Studio hereIf you'd like more information about Camp Stevens visit our website or email executive director Kathy Wilder at kathy@campstevens.org

In this episode of Bitcoin for Corporations, Pierre Rochard is joined by Elías Sacal, CEO of Murano Global Investments (NASDAQ: MRNO), to explore how Bitcoin is disrupting the traditional real estate investment model. They discuss the global shift from debt-based property financing to Bitcoin-backed corporate treasuries, the diminishing store-of-value premium in real estate, and how holding Bitcoin can unlock new capital strategies for developers.Elías also shares how Murano is approaching bitcoin adoption, from both a capital raising and operational standpoint, and what this means for the future of capital allocation in Latin America and beyond.⭐ This episode of the Bitcoin for Corporations Show is sponsored by Ledn, a leading provider of Bitcoin-backed loans.

Today's HeadlinesChina formally bans foreign missionary activityResurrection Sunday means victory in life or death“Spiritual spring” creates Gospel opportunities

With the news of Brooklyn's release of head coach Jessic Silva on their minds, the guests discuss BFC's rough run of play and how they desperately need to figure it out with playoffs right around the corner.

Mit den Superlativen hört es auch nach dem 4:0 gegen den BFC gar nicht mehr auf beim Spitzenreiter 1. FC Lok. Vor über 59 Jahren gab es letztmals einen so hohen Sieg gegen die Berliner. Am 19. März 1966 trug sich unsere Vereinslegende Henning Frenzel doppelt beim 4:0-Heimsieg in die Torschützenliste ein. In dieser Ausgabe kümmern sich die Moderatoren Thomas Franzky und Marko Hofmann ebenfalls um die große blau-gelbe Historie.Erster Gast ist Prof. Dr. Sören Bär. Das ehemalige Aufsichtsratsmitglied stellt am 22. April 2025 ab 18 Uhr in der Volkshochschule Leipzig seinen Film „PRIMA, RENÉ! - Die magische Nacht des 22. April 1987 im Leipziger Zentralstadion“ vor. Dort wird u.a. Ex-Spieler Wolfgang Altmann dabei sein und auch die DVD mit dem Film kann erworben werden. Als zweiter Gast kommt Winterneuzugang Max Klump zu Wort. Der 26-jährige Abwehrmann aus Aschersleben kam über Lok Aschersleben, den 1. FC Magdeburg, den VfL Wolfsburg, den 1. FC Köln, den BFC Dynamo, den FC Wiltz 71 (1. Liga Luxemburg) und den KFC Uerdingen im Januar nach Probstheida. Zweimal wurde er bereits Regionalliga-Meister. Genau zweimal stand er auch schon die gesamten 90 Minuten für den FCL auf dem Feld. Gegentore in diesen Spielen: Null. So gefallen uns Statistiken. Als dritter Gast wird Uwe "Emmi" Emmrich-Kießling von der Laufgruppe des 1. FC Lok begrüßt. Mit dem Silberseelauf am 14. Mai steht ein großes Highlight ins Haus. Start und Ziel ist wieder das Bruno-Plache-Stadion. Schaltet ein und gönnt euch diese wunderbare Sendung!Anregungen, Kritik und (vor allem) Lob zu LokCast könnt ihr gern jederzeit an diese E-Mail-Adresse richten: lokruf-radio@t-online.deSpenden an LokCast und Lokruf: https://www.paypal.com/donate/?hosted_button_id=U7AJWS2H6VTQ6

In dieser besonderen Episode von The Digital Drive begrüßen wir erneut Sylvia Gerl, die Geschäftsführerin der Bundesfachschule für Betriebswirtschaft im Kraftfahrzeuggewerbe (BFC) in Northeim. Nachdem sie uns bereits in einer früheren Folge Einblicke in ihre Arbeit und Visionen für die Kfz-Branche gegeben hat, teilt sie nun ihre persönlichen Erfahrungen aus China. Gemeinsam mit ihren Studierenden hat sie dort wertvolle interkulturelle Eindrücke gesammelt, die sie mit uns teilt. Außerdem gibt sie spannende Einblicke in die aktuellen Entwicklungen und Herausforderungen der BFC.Jetzt reinhören: Erfahrt mehr über die spannende Reise von Sylvia Gerl und die Entwicklung der Automobilbranche in China.

durée : 00:03:22 - Elise Darlay responsable communication et analyste pollens chez Atmo BFC

In episode 5 of the BFC Fashion Forum Podcast, the founder of Positive Retail, Anna Wood and founder of Aro Archive, Ariana Waiata Sheehan discuss the challenges that come with opening a retail space, together they navigate the world of retail and explore the importance of creating a good sense of community in store.Guests: Anna Wood and Ariana Waiata Sheehan.The BFC Fashion Forum Podcast explores topics that are impacting the creative industries. With knowledge sharing at its core, the podcast brings the creative community together and platforms the BFC network. Each episode brings a broad range of voices, sharing personal experiences on how they navigate the industry, while discussing the most pressing issues in fashion today. Hosted on Acast. See acast.com/privacy for more information.

Avec Justine Parmentier d'Athéna BFC

Continuing to dive deeper into the multiple sections of fashion, season 6, episode 4 of the BFC Fashion Forum Podcast brings together #BFCFoundation designer, Kazna Asker, journalist and editor, Mahoro Seward, and model and actor Yasmin El Yassini, to delve into the philosophy of fashion, and exploring how we can find meaning in aesthetics.​​​Guests: Kazna Asker, Mahoro Seward and Yasmin El Yassini.The BFC Fashion Forum Podcast explores topics that are impacting the creative industries. With knowledge sharing at its core, the podcast brings the creative community together and platforms the BFC network. Each episode brings a broad range of voices, sharing personal experiences on how they navigate the industry, while discussing the most pressing issues in fashion today. Hosted on Acast. See acast.com/privacy for more information.

In dieser Episode begrüßen wir Sylvia Gerl, die Geschäftsführerin der Bundesfachschule für Betriebswirtschaft im Kraftfahrzeuggewerbe (BFC) in Northeim. Die BFC eine Fachschule, die sich auf die kaufmännische Qualifizierung im Kfz-Gewerbe spezialisiert hat. Unter der Leitung von Sylvia hat sich die BFC als zentrale Institution für die Ausbildung zukünftiger Führungskräfte im Automobilsektor etabliert. Volker diskutiert die aktuellen Herausforderungen und Chancen in der Aus- und Weiterbildung der Automobilbranche, den Einfluss von Digitalisierung und Elektromobilität sowie die Rolle der BFC als Impulsgeber für die nächste Generation kaufmännischer Führungskräfte. Nebenbei ergründen die beiden, warum Sylvia in etlichen Folgen von "The Digital Drive" Erwähnung gefunden hat, warum sie sich siezen lässt und warum die Seminarräume keine Türklinke haben.  Ein spannender Einblick in eine Institution, die seit Jahrzehnten den Nachwuchs der Branche prägt – mit frischen Ideen, starkem Netzwerk und klarer Vision und in eine sehr besondere Frau. Aber mehr sei nicht verraten ... man muss es einfach hören! www.bfc.de

Today's HeadlinesBangladesh moves closer to Pakistan as Christians face growing threatsPrayer guide aids Christians during RamadanChristian training center in northern China amid communism, Islam, and poverty

Lumière sur un événement qui a lieu partout en BFC, du 1er au 28 février : La JMZH (Journée mondiale des zones humides). Cette journée est en réalité, étendue sur un mois. Un événement qui s'articule autour de randonnées, de projections, d'expositions photos et de moments d'échanges/partages avec les acteurs et actrices qui mènent des actions pour maintenir ces Zones Humides en bonne santé. Bref, au total, ce sont 52 animations organisées par 23 structures, sur tout le territoire ! On reçoit Clément Bastin, chargé de mission du Pôle Milieux Humides de Bourgogne- Franche-Comté, pour nous parler de cette fameuse JMZH.

Experience matters. Everyone always tells new design graduates that it's best to work for someone else while you find your feet. But at what point do you know that you are ready to strike out on your own? While on the surface this conversation with emerging German fashion designer Essie Kramer seems to be about the joys of sourcing old ecclesiastical textiles and turning them into provocative new ensembles, or how digital printing is democratising object-making, I think it's really about confidence and finding your flow. When you know, you know! Essie is one to watch. I'm always excited to meet next gen fashion talent. Featuring young designers has been a pillar of Wardrobe Crisis from the start.I've been lucky enough to be a judge on many new gen competitions over the years, including Redress in Hong Kong, the Circular Design Challenge in India and Australia's National Designer Award. I got to write a bit for Sara Maino's Vogue Italia Talents project, and covered the BFC's New Gen for years.Every series, we've run at least one (sometimes more) Episodes focused on new designers around the world. Got recommendations? Hit us up!And please share these podcasts.Then re-listen to these treasures from our archives:Ep 61 Vogue Talents, featuring HUEMN and Sindiso KhumaloEp 65 with Ruchika from Bodice StudioEp 70 featuring Bethany Williams, Matthew Needham and Patrick McDowellEp 110 with upcyclers Helen Kirkum and Duran LantinkEp 139 with Icelandic knitter Ýr JóhannsdóttirEp 146 with Joao MaraschinEp 204 Michaela StarkHappy listening!Clare x Hosted on Acast. See acast.com/privacy for more information.

Dr. Don Trest exhorts the believers at BFC to example the love and affection for one another as we move into a new year with new possibilities and challenges.bfc4u.org, facebook.com/bfc4u

Today's HeadlinesWatch and wait as Syria and other nations take first steps into its futureBibles for China eyes sinicization trendsMicrofinance model provides an economic and spiritual boost to communities

In episode three of The BFC Fashion Forum Podcast, acclaimed designer Robert Wun, editor Karen Binns, and creative producer Charlotte Clark discuss the creative excellence and global impact of London Fashion Week. Together, they explore the artistry behind the shows, the collaborative spirit that drives the industry, and the city's role as a hub for innovation and talent. From the craft of womenswear to the evolution of event production, this episode celebrates the dynamic energy shaping London's fashion scene. Guests: Robert Wun, Karen Binns, Charlotte Clark. The BFC Fashion Forum Podcast explores topics that are impacting the creative industries. With knowledge sharing at its core, the podcast brings the creative community together and platforms the BFC network. Each episode brings a broad range of voices, sharing personal experiences on how they navigate the industry, while discussing the most pressing issues in fashion today. Hosted on Acast. See acast.com/privacy for more information.

This is BFC's very first holiday song...and we think it's his best one yet! (C)2024 Box Office Poison Records Written, performed, produced by BFC Donkey Hotay Music (BMI) Mastered by Michael Fossenkemper - TurtleTone Studio NYC Art by Angelyce "Chuck" Gonzalez (@vv3spa )

In this episode of The BFC Fashion Forum Podcast, Vanessa Belleau, Jamie Backshall, Helene Selam Kleigh, and Bella Webb discuss the impact of mental wellness on the fashion industry. Featuring insights from a BFC Scholar, the conversation highlights the lack of mental health resources in the industry and explores key areas for improvement.Guests: Vanessa Belleau, Jamie Backshall, Helene Selam Kleigh, Bella Webb.The BFC Fashion Forum Podcast explores topics that are impacting the creative industries. With knowledge sharing at its core, the podcast brings the creative community together and platforms the BFC network. Each episode brings a broad range of voices, sharing personal experiences on how they navigate the industry, while discussing the most pressing issues in fashion today. Hosted on Acast. See acast.com/privacy for more information.

Tom Isted is back in The Ride Companion studio! Tom Isted sits down with Olly and Davi to talk about growing up in Cornwall and transitioning from BMX to MTB. Tom talks about the huge crash during the 'Panning for Gold' edit. He discusses what it takes to actually get an invite to Red Bull Rampage, bike setup for the event and why he chose 26" wheels and why he selected Joel Anderson and Connor Macfarlane for his dig team. Tom also recounts finding and building the BFC canyon with Tyler McCaul and reflects on how his record-breaking Darkfest backflip impacted his career. He reveals what his second run at Red Bull Rampage would have looked like, breaks down the rider protest at Crankworx Rotorua, and offers his perspective on the current state of slopestyle/Crankworx. Tom wraps up by talking about his plans for 2025 and much more... BIG thanks to this episode's sponsors: Want to take your productivity up a couple of notches!? Magic Mind have a limited offer you can use now, that gets you up to 48% off your first subscription or 20% off one time purchases with code RIDE20 at checkout. You can claim it at magicmind.com/ride20 Everybody needs a WORX Hydroshot and other power tools, right? Get 15% off all WORX tools at https://uk.worx.com when you use code THERIDECOMPANION With all these pro rider insights you're going to want to recover like a pro too! Get 20% off with code ‘THERIDECOMPANION' at compex.com/uk/   Support our long term partners: - HUEL: Get 15% OFF with code 'RIDE' at https://huel.com/ - Nissan Vans: https://www.nissan.co.uk/vehicles/new-vehicles/primastar.html - Play Fantasy Downhill at The Race Companion: https://www.theracecompanion.com https://www.instagram.com/theracecompanion - Get 10% off Troy Lee Designs with code 'theridecompanion' at saddleback.avln.me/c/OzduCWvjtcOr - Athletic Greens: Get a FREE 1-year supply of Vitamin D AND 5 FREE travel packs at athleticgreens.com/RIDECOMPANION - Compex: Get 20% off with code ‘THERIDECOMPANION' at compex.com/uk/ - Peak Supps: Get 10% off the TRC bundle and everything on site with code ‘theridecompanion' at  peaksupps.co.uk - Worx: Get 15% off with code ‘THERIDECOMPANION' at worx.com - LAKA: Get 30 days of FREE insurance with code ‘RIDECOMPANION30' at laka.co - HKT Products: Use code ‘PODCAST' for 10% off the entire site. Follow & Engage Olly Wilkins Instagram @odub_23 YouTube @owilkins23 The Ride Companion Instagram @theridecompanion YouTube @TheRideCompanion YouTube clips and BTS channel @moreridecompanion Get official Ride Companion merch, find old episodes and more theridecompanion.co.uk

In this episode, Jabu is joined by leading international sports lawyer, Evert de Bruyn, a key figure behind The Business of Football Conference (BFC), South Africa's first football business summit. Evert discusses the BFC's context within the wider football business ecosystem in South Africa, the brands organising and sponsoring the event and the importance of creating forums for football stakeholders to exchange ideas. He also shares exclusive details about BFC's thematic agenda and line-up of speakers. ---------------

Pastor Bob Wren discusses the book in a review with Carol Mahler, Deanne Kimball, Aubrey Sommer, Camille Williams, and Debra Downs. The ladies of BFC recently completed the book study, and this podcast records their observations.bfc4u.org,facebook.com/bfc4u

In the season opener of The BFC Fashion Forum Podcast, poet and trans visibility activist Kai-Isaiah Jamal, designers Jordan Bowen and Luca Marchetto of JORDANLUCA, cultural historian Fenella Hitchcock, and model, producer and photographer, Zorawar Waraich explore the role of fashion in shaping queer identity and expression in modern Britain. Together, they unpack how what we wear can be harnessed as a powerful medium for self-expression, exploring its connections to sexuality, psychology, and culture within the queer community. From the raw intensity of menswear to decolonisation through fashion, this episode uncovers the power of queer dress.Guests: Kai Isaiah Jamal, JORDANLUCA, Fenella Hitchcock, Zorawar Waraich.The BFC Fashion Forum Podcast explores topics that are impacting the creative industries. With knowledge sharing at its core, the podcast brings the creative community together and platforms the BFC network. Each episode brings a broad range of voices, sharing personal experiences on how they navigate the industry, while discussing the most pressing issues in fashion today. Hosted on Acast. See acast.com/privacy for more information.

The Cat & Cloud podcast is back and we're bringing y'all some big news! If y'all have been following us a while then you've at least heard of the Best Friend's Club and if you haven't, this is the perfect episode for you. This week on the pod, Chris, Jared, and Charles are walking us through the history of the BFC, how it started, how it continues to grow, and finally introducing the Best Friends Blend! To continue expanding the reach of the BFC, we have decided to introduce the Best Friends Blend as our newest espresso offering. This blend will always include one of our BFC coffees, allowing us to vastly increase the amount of BFC coffee sold in our cafes—which means more money goes directly back into the lives of our producers. Give it a try! https://catandcloud.com/products/the-best-friends-blend 00:00 Best Friends Club 01:53 How it Started (unofficial) 06:18 How it Started (official) 11:44 It's About Supporting a Community 15:14 Expanding the Club 17:35 It's About Connection 31:56 Some of the Issues 35:52 The Best Friends Blend Do you have a question you've been dying to ask us? Do you wanna hear us talk about it on the podcast? Visit our website catandcloud.com/podcast, or email us at podcast@catandcloud.com and tell us what it is, and maybe your question will be the one we answer next week! Instagram: https://www.instagram.com/catcloudcoffee/ Cat & Cloud: https://catandcloud.com/ Chris Baca's Personal Blog: https://chrisbaca.com/ We are Cat & Cloud Coffee. Started by three friends trying to pursue their passions with the mission to inspire connection by creating memorable experiences, and we created this podcast to continue forming those connections inside and out of our cafes. The Cat & Cloud podcast was created as a space for two of our founders, Chris Baca and Jared Truby, to share their experiences in the coffee industry and starting a business. Each week the guys sit down to talk about their new challenges as business owners, how they've utilize our mission and values to make decisions, and answer questions from our listening community. If you're looking to expand your coffee knowledge, get some advice for your own small business, or just like the vibes, give us a listen! Enjoy!

Isaac Wait is an old running sole with a wealth of trail running experience ranging from local races in West Virginia to all over the United States, Europe, and Africa. He excels on the big stage of the big races, but he's modest and unassuming about his accomplishments. In this edition, we break down the BFC and its quirky attributes, making it a remarkable experience that more people should try.

Ranko Velimirovic, bivsi kosarkas koji je kroz svoju karijeru nastupao za BKK Radnicki, BFC,Vojvodinu,Beopetrol, novi je gost Jao Mile podcasta.Jao DUĆAN! http://www.jaomile.comRanko je sada u svetu nekretnina a vise informacija mozete naci na sajtu ispod.http://www.citypulse.rs00:00:00 Početak 00:00:40 Podrška 00:00:55 Ranko Velimirovic00:04:10 OI leto00:09:20 Večiti 00:13:00 Jokić /Dončić 00:15:00 Odrastanje 00:21:50 Beograd00:36:25 Piva Ivković 00:40:40 BFC 00:47:00 Vojvodina00:49:00 Beopetrol00:53:00 Rusija 01:04:30 Kipar 01:07:20 Atlas01:12:15 BiH 01:18:00 Pecanje/Mrkonjic01:22:40 Najteži protivnik 01:24:30 Najtalenat 01:27:00 Kraj karijere/Plan za posle01:28:28 Pogled na karijeru01:35:12 Savet mladima 01:36:50 Top 5 01:37:50 TopićThumbnail designer:https://instagram.com/design33_mk?igshid=MzRlODBiNWFlZA==Pratite nas na društvenim mrežama!Instagramhttps://www.instagram.com/jaomile_podcast/Facebook https://www.facebook.com/JAOMILEPODCASTTikTokhttps://www.tiktok.com/@jaomile_podcastTwitter https://twitter.com/mileilicGost: Ranko VelimirovićDatum: 11. Septembar  2024. Autor i domaćin: Mile IlićLokacija: Studio na kraju UniverzumaProdukcija: Infinity Lighthouse#jaomilepodcast #rankovelimirovic #radnicki #djokovic #crvenazvezda #kkpartizan #nikolajovic #nba  #nikolajokic #abaliga #jokic #bogdanovic #euroleague #doncic #nikolatopic

Le Toast ? Mais qu'est-ce ? Le Toast by Beauty Toaster, c'est un format court dans lequel je partage mes découvertes, des infos, des coups de coeur, mais aussi des coups de griffe. Oui, le Toast c'est environ 5 minutes (voire un peu plus...), le temps d'une pause de mascara ou d'un café. Aujourd'hui, Je vous parle de la boucle parfaite. Oui cette boucle de poupée érigée en nouveau standard de beauté capillaire, au risque d'exclure encore et toujours les femmes dont les cheveux ne se prêtent pas à ce genre de définition. Non le cheveu BFC naturel ne doit pas rimer systématiquement avec la boucle parfaite ! Abonnez-vous à Beauty Toaster via le blog, mais également sur les plateformes type Spotify, Deezer, Google Podcast, Podcast addict CastBox, Podbean etc. Surtout, laissez un commentaire et plein d'étoiles sur Spotify et Apple Podcast, si vous avez aimé ce coup de griffe. Vous permettrez ainsi à Beauty Toaster de profiter d'une audience plus large en donnant à d'autres auditeurs la chance de le découvrir. Enfin, parlez-en beaucoup autour de vous. A partager vos découverts avec votre famille, vos ami(e)s, et tous les passionné.es de beauté que vous connaissez, même s'ils vivent loin de vous ;-). Car finalement, Beauty Toaster peut s'écouter partout dans le monde. Merci infiniment pour votre écoute, votre fidélité et votre soutien. Générique : Jazzy Frenchy par Bensound/cchound.com

For episode three, Vogue Business Executive European Editor, Kirsty McGregor is joined by CEO and Co-Founder of Tomorrow, Stefano Martinetto, and Founder and Buying Director of MACHINE-A, Stavros Karelis to discuss the ongoing cultural and socio-economic implications of Brexit on the British fashion industry. Combining their knowledge and experiences from across the industry, Kirsty, Stavros and Stefano highlight the necessity for a collaborative community, alongside organisations like the BFC, to support young and independent designers through times of social and economic uncertainty. About Kirsty McGregor: Kirsty McGregor is executive European editor at Vogue Business. She was previously the editor of UK-based fashion trade magazine Drapers. She joined Drapers in 2014 from a background of social policy journalism.About Stefano Martinetto:Stefano Martinetto is chief executive and co-founder of Tomorrow, a growth and development platform founded in 2008 for fashion brands. Tomorrow are the lead investors in brands such as A-Cold-Wall*, Charles Jeffrey Loverboy, Colville and Martine Rose, as well as retailer MACHINE-A.About Stavros Karelis:Stavros Karelis is founder and buying director of independent concept store MACHINE-A, known supporting young design talents by stocking them alongside established brands. Karelis is also a judge for the BFC's NEWGEN initiative.About the BFC Fashion Forum Podcast:Brought to you by the British Fashion Council, a series of conversations with designers and the broader creative community, all of whom play a vital role in the fashion industry's culture and reputation, promoting British creativity on a global scale. Hosted on Acast. See acast.com/privacy for more information.

Bfc in the city with me to blaze it up with is an extraordinary topic. --- Support this podcast: https://podcasters.spotify.com/pod/show/tagyounotit14/support

In our latest episode we preview the upcoming matchweek by breaking down every fixture and giving our expectations for the weekend. We also spend some time trying to predict which of #LTFC, #NFFC, and #BFC will be relegated and who will remain in the #EPL next season. Tune in!

BFC came through. Would you take a l? Does religion or race divide us more. Just come stimulate your mind with our conversation --- Support this podcast: https://podcasters.spotify.com/pod/show/tagyounotit14/support

Baseball5516, Danger, Hasp, and Secret Salsa talk all things BFC and make our predictions on which paragon originals are coming next!

Folge 9 der Sonderserie PINK NETWORK meets Benzingespräche, mit Co-Host Juliane Schleicher! Zu Gast ist heute Sylvia Gerl von der BFC in Northeim. Sylvia Gerl muss man in der deutschen Autobranche wohl niemandem vorstellen, denn Sie leitet seit 27 Jahren die Kader-Schmeide für den Autohandel schlechthin: die BFC.

On this Flight of The Retail Pilot Ken speaks with LEGEND, Tommy Hilfiger, Principal Designer, Tommy Hilfiger Global.Uplifting and inspiring consumers since 1985, Tommy Hilfiger has pioneered one of the world's most recognized premium lifestyle brands. With Hilfiger's vision and leadership as Principal Designer, his eponymous brand celebrates the essence of classic American style with a modern twist. Tommy Hilfiger offers premium quality and value to consumers worldwide under the TOMMY HILFIGER and TOMMY JEANS lifestyles, with a breadth of collections including men's, women's and kids' sportswear, denim, accessories, and footwear.Hilfiger's career in fashion began when he was a high school student in 1969 — opening his first store, People's Place, in his hometown of Elmira, New York. A decade later, he moved to Manhattan to pursue a career in fashion design, before launching his namesake brand with a single menswear collection. Since then, global retail sales of TOMMY HILFIGER products have grown to reach approximately $9.1 billion in 2022, powered by more than 16,000 associates worldwide — present in 100 countries and more than 2,000 retail stores, including its largest global flagship store at tommy.com.Hilfiger has a longstanding passion for philanthropy and making the world a better place for future generations. Through the global TommyCares organization, the brand supports various international initiatives and charities like Save the Children, the World Wildlife Fund and Fashion Minority Alliance. Hilfiger currently sits on the Board of Next for Autism. Through the Tommy Hilfiger Fashion Frontier Challenge and People's Place Program, the brand is also making strides in its ambitious vision to create fashion that Wastes Nothing and Welcomes All – which actively focuses on topics such as social and environmental sustainability, diversity, and inclusivity in fashion and beyond.Diverse achievements in business and fashion have earned Hilfiger numerous distinguished awards including the CFDA's prestigious Geoffrey Beene Lifetime Achievement Award in 2012, British GQ's Design Legend of the Year in 2020, BFC's Outstanding Achievement Award in 2021 and WWD's John B. Fairchild Honor for Lifetime Achievement in 2022. Hilfiger's life and career have been chronicled in his memoir, American Dreamer, published in November 2016 — reflecting his experiences in the fashion industry from the last 35-plus years. Recounting his early childhood and formative years, it explores the setbacks, triumphs, and sheer determination that drove him to build a multi-billion-dollar global brand.Key takeaways from this interview include:Tommy Hilfiger's Background: Tommy Hilfiger began his journey in retail and design at a young age, starting his own business at 18 years old by opening a retail store -People's Place - selling jeans in 1969. This venture eventually led him to designing and creating products for his stores, culminating in the establishment of his own brand.Innovative Store Concepts: Hilfiger's early stores, particularly People's Place, were not just retail outlets but cultural hubs influenced by music and fashion. They offered a variety of products, hosted band practices, and provided an immersive experience for customers, aligning with the youth culture of the time.Cultural Influences on Brand Identity: Hilfiger aimed to differentiate his brand from traditional preppy styles by infusing it with elements of music, particularly hip-hop, and embracing a more inclusive approach to fashion. This cultural fusion helped establish the personality of the Tommy Hilfiger brand.Disruptive Advertising Strategy: The Hangman ad campaign, conceived by advertising executive George Lois, was a bold and disruptive move that garnered attention for the brand. Despite initial criticism, the controversial campaign succeeded in sparking conversation and establishing Tommy Hilfiger as a distinctive player in the fashion industry.Strategic Partnerships and Growth: Strategic partnerships, such as those with Marjani International and later with Silas Chao and Lauren Stroll, played a crucial role in the brand's growth and expansion. These partnerships facilitated strategic decisions like expanding into Europe and launching successful product lines such as fragrances, contributing to the brand's success and eventual IPO.Archives and Relevance: Both Tommy Hilfiger and Karl Lagerfeld emphasized the importance of going back to fashion archives and making past designs relevant for today's market. This approach ensures a timeless appeal while staying fresh.Strategic Partnerships: The acquisition by Apex and subsequent sale to PVH provided strategic opportunities for Tommy Hilfiger's brand growth. Apex helped in repositioning the company, while PVH's ownership of other brands like Calvin Klein created synergies beneficial for both.Brand Positioning: The positioning of Tommy Hilfiger's brand differs between the US and Europe. Understanding regional customer preferences and pricing strategies is crucial for successful brand positioning.Design Process: Tommy Hilfiger's use of technology, such as 3D design, and the centralization of its design team in Europe contribute to a more efficient and precise design process. This enables faster response to market trends and ensures product quality.Marketing and Brand Communication: The brand utilizes a mix of influencer collaborations, celebrity endorsements, and unique marketing campaigns to amplify its brand message. Embracing digital technologies like augmented reality and exploring AI's potential are also part of the brand's forward-thinking approach to marketing.

Jeff, Virgil and Mark chat with Nelson Page, Executive Director of The Barrymore Film Center in Fort Lee, New Jersey about classic film, 35 and 70mm, indoor and outdoor theater management, the Paramus Drive-In, the repertory programming and mission of the BFC, and Fort Lee's place in American cinema history. Recorded 1/3/24 For more information on The Barrymore Film Center: https://www.barrymorefilmcenter.com https://www.facebook.com/BarrymoreFilmCenter https://www.instagram.com/barrymorefilmcenter For exclusive additional podcasts, videos, sneak peeks, and on-site discounts, visit the Mahoning Drive-In Patreon page at: https://www.patreon.com/mahoningdrivein https://www.mahoningdit.com/ https://www.facebook.com/mahoningdriveintheater/ https://www.instagram.com/mahoningdriveintheater/ https://twitter.com/mahoningdit --- Send in a voice message: https://podcasters.spotify.com/pod/show/mahoningdrivein/message

In this episode of the Landmark Recovery Podcast, we're honored to host Jerry Moe, an influential figure in the field of family recovery. Jerry shares his personal journey and provides an insider's view on the evolution of family recovery programs, including the foundational days of NACOA and the development of the Children's Place. He reflects on his time at BFC and discusses his latest projects, offering valuable perspectives on enhancing family and children's services within the recovery industry. Join us for this enlightening conversation with Jerry, a true advocate for family healing in addiction recovery. Stay connected with Landmark Recovery on Instagram, Facebook, and TikTok for more inspiring stories and expert insights.

Rick DeMint, an NYU Langone employee and part-time MBA student, recently unveiled his exhibition, "Portroids: A 20 Year Retrospective," at Brooklyn Film Camera in Williamsburg. The display featured 212 autographed Polaroid portraits capturing DeMint's favorite celebrities, comedians, and personal connections. Started in 2003 as a way to document his life, the project evolved into a comprehensive showcase of 5,000 photographs spanning two decades. Organized in black and white frames, the exhibition formed a giant Polaroid wall, offering a photo journal of popular culture and a time capsule of the 2000s. Notable figures like MCA, Matthew McConaughey, Chuck D, and Barack Obama, alongside NYU alumni such as Donald Glover, are featured. The show's unique aspect is its encouragement for viewers to photograph the Polaroids, fostering a connection between the audience and the joy DeMint experiences in capturing each subject. Lucas C. Ospina from BFC talks about the Polaroid craze as well. Follow Rick on IG: @portroids Follow Brooklyn Film Camera on IG: @brooklynfilmcamera Follow Harlan on IG: @theofficialharlan Follow Sole Free on IG: @solefreeradio Produced by: @donnadraketv #solefree #sneakers #art #fashion #photo #polaroid #brooklyn #fyp

Baseball5516, Danger, and Secret Salsa are joined by KevKaioken to talk BFC and get to know who Kev is! FOLLOW KEV ON TWITCH! https://www.twitch.tv/kevkaioken Join Predecessor Brotherhood discord! https://discord.gg/predbhd Follow the hosts on Twitch! https://www.twitch.tv/secretsalsa https://www.twitch.tv/baseball5516 Join our Discord! https://discord.gg/5bqyuQNcSx

近两年迪卡侬似乎是一个非常“幸运”的品牌，无论城市里流行了什么新兴的运动（露营、滑雪、钓鱼、滑板、飞盘、骑行等），它都是受益者，很多人会把它视为装备采购的首选地之一。但问题是，迪卡侬已经在中国经营了20年，这家公司的历史更是有47年，它不可能仅依靠社交网络上的热潮做生意。所以在风口来之前，它做了哪些事来生存、发展，这是今天我们基本的好奇。幸运的是，《第一财经》杂志对迪卡侬有长期的追踪报道，这帮助我们在缺乏定期财务数据的情况下，也能对它的经营状况有实在的探讨基础。两则广告：1）8月27日，《第一财经》杂志将在上海BFC外滩金融中心举行读者见面会，杂志的“设计天团”将现场分享商业与设计的话题，报名链接在此（https://mp.weixin.qq.com/s/1y9Emap4U_HbYG9rQxaliw）。2）《第一财经》杂志2023新国货榜样大调查问卷（https://www.wjx.cn/vm/PQ0gAx7.aspx）已经发布，欢迎参与填写。| 资料整理 |常竣斐、陈茗瑄| 主播 |肖文杰、约小亚| 时间轴 |02:59 迪卡侬背后的大靠山08:28 “义乌式创新”和体育民主化12:25 入华初期迪卡侬很保守17:55 加速跑：迪卡侬在华更灵活25:12 应对疫情：风口不是等来的| 延伸阅读 |2022年《第一财经》杂志对迪卡侬的报道https://www.cbnweek.com/#/article_detail/273372018年迪卡侬首次公布中国市场业绩https://www.cbnweek.com/#/article_detail/209622017年《第一财经》杂志对迪卡侬的报道https://www.cbnweek.com/#/article_detail/193532013年《第一财经》杂志对迪卡侬的报道https://www.cbnweek.com/#/article_detail/8470穆里耶家族的管理体系https://www.lemonde.fr/en/summer-reads/article/2022/07/14/family-communism-the-mulliez-family-business-model_5990110_183.htmlIsabelle Gaillard (2022) Decathlon and the 2 Second Tent: From Discount to Innovation (1976–2008), The International Journal of the History of Sport《商业就是这样》鼓起勇气开设听友群啦。欢迎添加节目同名微信，加入听友群，一起讨论有意思的商业现象。微信号：thatisbiz为了营造更好的讨论环境，我们准备了两个小问题，请在添加微信后回答：1，你最喜欢《商业就是这样》的哪期节目？为什么？2，你希望听到《商业就是这样》聊哪个话题？期待与你交流！| 后期制作 |李昱璇、董思哲| 收听方式 |你可以通过小宇宙播客App、苹果播客、Spotify、喜马拉雅、网易云音乐、QQ音乐、荔枝、汽水儿等平台收听节目。| 认识我们 |微信公众号：第一财经YiMagazine联系我们：thatisbiz@yicai.com

Between the late 1970s and the late 1980s, Dynamo Berlin, a club closely associated with the Communist East German Republic's secret police, won the country's title ten consecutive times. The hatred of the team across the country united its fans, but also provided the perhaps most prominent kind of complaint and grumbling that the GDR's citizens had against the regime that ruled them. In 1989, that regime crumbled and fell. And so did Dynamo. Alan McDougall is a historian at the University of Guelph in Canada. He has written The People's Game: Football, State and Society in East Germany, and takes us on the wild ride through a nation that is no more, with a club that polarizes Germany to this day.  Please leave a quick voicemail with any feedback, corrections, suggestions - or just greetings - HERE.HELPFUL LINKS FOR THIS EPISODE:Music:Video Collage of BFC's glory years, with the song “Wann wird Dynamo wieder Meister?” (“When Will Dynamo be Champions Again?”) by 4xDAndreas Auslauf - … Sein (“How it Should be”)Feeling B - Ich Such die DDR (“I'm, searching for the GDR, and no one knows where she is”)Namenlos - Nazis Wieder in Ostberlin ("Nazis Back in East Berlin")Texts, Websites:​​Alan McDougall, The People's Game:Football, State and Society in East Germany“What Happened to the Record East German Champions” (article from Matt Ford @matt_4d from Episode 1 for Deutsche Welle)“Das randalierende Rätsel” (“The rioting enigma”), German TV Documentary from 1992 about BFC's hools in the 1990s“Dynamo Berlin: the soccer club “owned” by the Stasi” (2016 article from David Crossland via CNN)Bonus, about the music: Arun Starkey, “Exploring the Importance of the East German Punk Scene” (2021)Please leave a quick voicemail with any feedback, corrections, suggestions - or just greetings - HERE. Or comment via Twitter, Instagram, Bluesky or Facebook. f you enjoy this podcast and think that what I do fills a gap in soccer coverage that others would be interested in as well, please Recommend The Assistant Professor of Football. Spreading the word, through word of mouth, truly does help. Leave some rating stars at the podcast platform of your choice. There are so many sports podcasts out there, and only ratings make this project visible; only then can people who look for a different kind of take on European soccer actually find me. Artwork for The Assistant Professor of Football is by Saige LindInstrumental music for this podcast, including the introduction track, is by the artist Ketsa and used under a Creative Commons license through Free Music Archive: https://freemusicarchive.org/music/Ketsa/

Join us as we explore the inspiring journey of Coty Ziegler, a New Orleans native and mixed martial artist with 10+ years of boxing experience. As a former BFC lightweight champion, he's now gearing up for his professional debut! Discover the grit, resilience, and determination it takes to pursue your dreams in the world of combat sports. --- Support this podcast: https://podcasters.spotify.com/pod/show/erics-adhd-experience/support

在四合院与小红书博主Holiday进行了一些业务相谈。 如果您对葡萄酒、烈酒、啤酒或其他酒精饮料有兴趣，不妨关注公众号，或联系「杯弓舌瘾小助手」进入团购群。如果您是供应商，也可以向我们推荐合适的产品。 关注「杯弓舌瘾」公众号，或微信搜索bgsyxzs加入听众交流群，欢迎您参与互动。 6月2日-4日，首届外滩精酿啤酒节将在上海BFC外滩金融中心北区广场举办，近30加国内精酿啤酒厂牌和上海本土精酿啤酒代表齐聚一堂。感兴趣的朋友通过杯弓舌瘾或明日酿造的微信公众号购买限量福袋，包含啤酒节周边、现场兑换啤酒的代币以及明日酿造为外滩啤酒节特制的纪念款啤酒，欢迎一起去喝喝！ - 对话成员 - 戴老板（小红书：@Ian的发酵日记） 钱老板（小红书：@钱老板） Holiday（小红书：@Holiday是酒鬼） - 制作团队 - 后期制作 孙称 节目助理 邓逸轩 节目运营 小米粒 logo设计 Jessi、蛋花 - 本节目由 JustPod 出品 ©2023 上海斛律网络科技有限公司 - - 互动方式 - 商务合作：ad@justpod.fm 微博：@杯弓舌瘾TipsyProof @JustPod @播客一下 微信公众号：杯弓舌瘾 / JustPod / 播客一下 小红书：杯弓舌瘾 / JustPod气氛组