Podcasts about AV1

I det 414:e avsnittet av Skolspanarna är det Hans och Patrik som samtalar – och det blir ett rejält svep genom digitaliseringens landskap. De börjar med nyheter från Google Workspace, där NotebookLM nu låter både lärare och elever skapa flashcards, quiz och rapporter. Men det är inte bara verktygen som diskuteras – även frustrationen över AI-genererade texter med märklig formatering får sin plats. De tipsar om Ollama, en tjänst för att köra språkmodeller lokalt, och Privnote, ett smart sätt att skicka självdöende meddelanden. Samtidigt väcks frågan: Ska staten ha rätt att scanna alla bilder vi skickar? Diskussionen kopplas till läckage från kommuner och miljödata – och vad som händer när insamlad information inte skyddas tillräckligt. Samtalet får en röd tråd genom tidigare avsnitt om digitalisering – från TPACK och SAMR till Blooms taxonomi. Vad innebär digitalisering egentligen idag? Och hur påverkar sociala medier, mobilförbud och läsförståelse vår syn på undervisning? De går igenom forskning om en-till-en-datorer, distansundervisning, AV1-robotar och adaptiva läromedel. Verktyg som Imvi Labs diskuteras utifrån egna erfarenheter, och möjligheterna med AI i undervisningen får stort utrymme – från rättstavning och uppläst text till avancerad diagnostik. Framtidens nyckelkompetenser lyfts: att ställa rätt frågor och att kunna bedöma om svaret är korrekt. AI förändrar både undervisning och lärarroll – kanske är vi snart där att varje elev har en digital tvilling som följer deras utveckling i realtid? Det mesta är sig likt även denna gång – samtalet kretsar kring skola, digitalisering och lite annat.

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

Dans cet épisode du CKB Show, on fait le point sur l'arrivée surprise d'Android 16 avec toutes ses nouvelles fonctionnalités pour votre smartphone . On analyse aussi le nouveau logo de Google, symbole d'un virage stratégique vers l'intelligence artificielle et Gemini. On se demande également quel est l'avenir de Google Chrome et Google Search face à ces changements. Accrochez-vous pour une discussion tech passionnante !00:00: Introduction et présentation des sujets de l'épisode (Android 16 et le nouveau logo de Google)01:00: Partage sur l'utilisation de l'Intelligence Artificielle au quotidien01:50: Salutations aux auditeurs, remerciements aux Patriotes et présentation de la chronique audio "Actualité Tech"03:40: Annonce de l'arrivée surprise d'Android 16 et changement de stratégie de Google pour un déploiement plus rapide05:40: Calendrier de déploiement d'Android 16 (Developer Preview, Beta, versions stables)07:30: Compatibilité d'Android 16 (Pixel, Samsung, Motorola, Xiaomi, OnePlus, Oppo, etc.)09:00: Discussion sur le rythme des mises à jour et la stabilité10:40: Introduction aux nouvelles fonctionnalités d'Android 1611:30: Affichage adaptatif des applications sur grands écrans et pliables13:30: Possibilité de minimiser les fenêtres dans la barre des tâches (sur tablettes)14:00: Améliorations audio et Bluetooth (Bluetooth Low Energy, contrôle du volume, réglage indépendant par oreille, changement de micro)16:30: Partage audio via Oracast (connecter plusieurs casques)18:00: Prise en charge du codec AV1 (amélioration qualité vidéo)19:30: Introduction des mises à jour en direct (Live Activities) dans les notifications20:30: Notification de changement de fuseau horaire21:00: Refonte de l'interface utilisateur (Application Téléphone, Menu Paramètres)22:00: Séparation des centres de notification et des paramètres rapides23:00: Mode compact pour les notifications sur l'écran de verrouillage24:30: Réintégration et repensée des boutons de navigation26:00: Amélioration de la fréquence de rafraîchissement adaptative27:00: Personnalisation du double appui sur le bouton d'alimentation28:00: Mode nuit automatique plus intelligent et étendu aux applications tierces29:30: Réorganisation et simplification de la gestion des paramètres rapides30:00: Écran dédié pour les tuiles WiFi et Bluetooth32:30: Nouvelles API multimédia et sélecteur d'images intégré33:30: Raccourcis d'application sous forme de "bulles" sur grands écrans34:30: Multitâche : Écran partagé avec ratios flexibles35:30: Améliorations de la gestion de la batterie (limite de charge, recalibrage, suivi d'état)37:00: Enregistrement d'écran externe (HDMI)37:30: Potentiel d'utiliser le smartphone Android 16 comme unité centrale (comparaison Dex)38:00: Transition vers le nouveau logo de Google38:40: Description et symbolisme du nouveau logo (dégradé, "AI first", lien avec Gemini)40:30: Raisons stratégiques du changement de logo (vente forcée de Chrome, déclin de Google Search)42:00: Le déclin de Google Search face aux IA conversationnelles et nouvelles plateformes43:30: Gemini comme nouveau point central de Google (intégration, modèles IA, potentiel de remplacement de Google)46:00: L'avenir du smartphone, interface vocale et Gemini Live47:30: Le modèle financier de Google et l'hypothèse d'un virage vers le payant (modèle 80/20)50:00: Interrogations sur la nécessité future de Google Search et Google Chrome51:00: Exemple de Gemini Live pour les personnes malvoyantes52:00: Le "cimetière d'applications" de Google comme signe d'innovation et de tests54:00: Remerciements et appels à l'action (soutien, partage, abonnement, commentaires)55:30: Introduction aux Coups de cœur55:45: Coup de cœur d'Adrien : Série Netflix Astérix et Obélix : Le Combat des Chefs57:50: Coup de cœur d'Adrien : Perplexity dans WhatsApp59:00: Coup de cœur de Nicolas : Curio Shuffle (découverte de sites web)60:30: Conclusion et au revoir

Will $500 Switch 2 prices help Steam Deck adoption? Wizards of the Coast DMCA'd a Baldur's Gate 3 Stardew mod, AV1 still kind of sucks, Ricochet set a new record, and everything you need to know about tactical downhill skiing.

This week, we highlight DIRECTV's expanding RSN bundling options, which cover 18 MLB, 16 NBA, and 10 NHL franchises and the addition of Max Basic with Ads to its MyEntertainment Genre Pack. We also highlight the MLB TV streaming outage on opening day, JioHotstar's announcement that JioHotstar now has over 100 million subscribers, and Netflix's news that it is now streaming HDR10+ content for AV1-enabled devices. Finally, we detail the launch of EdgeCast Cloud Services from Parler Cloud Technologies and Bitmovin's news of reaching free cash flow in 2024, with 2025 revenue expected to be in the $30M+ range.Podcast produced by Security Halt Media

Welcome back! This week we have Paulo Iscold back on to talk about Acrowrx updates, as well as the Acrowrx contest coming up. We further drive into Acrowrx to talk about the seemingly unlimited uses for it. This was a really fun episode! Please head to www.acrowrx and sign up for a membership! The contest goes from 3/15-3/23 and basically, you can fly as many times as you want to get your best flight and have it judged for the contest. Head to www.acrowrx.com and sign up! Thank you to LIFT Aviation! Head to www.liftaviationusa.com and use the promo code FLYCOOLSHIT at checkout for 25% off most items. AV1 helmets are restocked! Use the promo code AV1restock at checkout for 100 bucks off an AV1 helmet! Thank you to Fly Good Merch! Head to www.flygoodmerch.com and use the promo code AKRO at checkout for 10% off the entire website.

This week, Mark Donnigan and I recap news from IBC about using cloud-based compute services for video workflows, encoding optimization, AV1/codec adoption, live encoding use cases, and AI's potential impact on encoding platforms. We also give updates on the Venu/Fubo lawsuit, price increases for NBA League Pass, the upgraded Roku Ultra device, Google rebranding their FAST channels, and some viewership numbers from Peacock. Finally, we discuss some interesting statements from Netflix regarding their ad tier, the NFL games on Christmas and how they view one-off sporting events versus full seasons.Companies mentioned include Akamai, Amagi, AOM, ATEME, AWS, Bitmovin, Brightcove, CDN77, Disney+ Hotstar, Dolby, Edgio, Harmonic, iSIZE, Neilsen, Netflix, NETINT, NVIDIA, THEO Technologies, Visionular, WaveOne, YouTube.Thanks to this week's podcast sponsors: Integrated Digital Solutions and Netskrt Systems.Podcast produced by Security Halt Media

「DMM TV、国内大手配信事業者で初めてAV1コーデックに対応。作品の画質はそのまま通信量は約50％オフ」　合同会社DMM.comが運営する「DMM TV」は、国内の大手配信事業者として初めて次世代動画圧縮コーデック技術「AV1」を採用し、2024年7月よりAV1コーデックを用いた動画配信を本格的に開始することを発表した。

✅ Confira o ONLYOFFICE DocSpace 2.5: https://www.onlyoffice.com/docspace.aspx ✅ Todas as novidades do ONLYOFFICE DocSpace 2.5: https://diolinux.com.br/tecnologia/novidades-do-onlyoffice-docspace-25.html

AV1 encoding on Linux with a shouty little Arc, Nvidia gets in sync with Wayland, EndeavourOS loses

Dive into our APRIL 2024 Microsoft Teams Show! Host Rob Scott teams up with special guest Tom Arbuthnot from Empowering.Cloud to unpack recent updates and announcements. Joined by a panel of seasoned Teams experts, find out what's new in the Teams ecosystem.In this update, we talk through the most popular Teams news headlines with this month's special guests:Graham Walsh, Product Specialist at NeatKevin Kieller, Co-Founder and Lead Analyst, enableUCJosh Blalock, Chief Video Evangelist at JabraBIG NEWS: Microsoft to Decouple Teams from Office – A Global Game-Changer!Teams Phone's New HorizonsThe upcoming Queues app in Teams Premium (Summer 2024) Reliability redefined with a Teams Phone service level agreement promising 99.999% uptime Strategic Survivable Branch Appliance Enhancements Teams Phone Mobile's new operator rosterTeams Phone Devices Enhanced Teams Phone devices UI for streamlined call handling directly from your phone's home screen. Multi-task like a pro with improved multi-call handling. Sophisticated contact management for swift communication. Remote admin controls via TAC for bulk configuration and contact managementMeetings and Rooms RevolutionJosh Blalock announces Microsoft Device Ecosystem Platform (MDEP) launches with Jabra and Yealink. AV1 enhancement for screen sharing in Teams — expect lower bandwidth usage and smoother frame rates. IntelliFrame's automatic camera switching and multiple camera view for a richer remote experience. Upcoming intelligent speaker recognition and transcript attribution for a more inclusive meeting atmosphere. Simplified join options with ultrasound proximity, QR code, and meeting ID features. Copilot's Intelligent EvolutionCopilot compose enhancements bring smarter interactions to Teams chat. Intelligent call and meeting recaps in Teams Premium and Teams Mobile. Teams Events Comms svNext - April 23Microsoft 365 Community Conference - April 30 - May 1 -2Teams Fireside chat - May 9 Commsverse - June 26-27

Enterprise Connect har varit igång borta i Florida och Microsoft passade självklart på att släppa en massa nyheter. Teamspodden passar på att sammanfatta några av dem i detta avsnittet.   Nu gör vi landet redo för Teams Premium! - Exobe Enhancing Screen Sharing with AV1 in Microsoft Teams - Microsoft Community Hub Introducing the Queues app: Enabling customer engagement in Microsoft Teams - Microsoft Community Hub Teams Rooms and Devices: Enterprise Connect 2024 - Microsoft Community Hub Enhance collaboration with Microsoft Teams Premium - Microsoft Community Hub What's New in Microsoft Teams | Enterprise Connect 2024 Edition - Microsoft Community Hub Microsoft Teams: Building a Foundation for the Future - Microsoft Community Hub

The crew covers the newest Framework laptop, the Raspberry Pi IPO, and Intel's Thread Director work in the kernel. There's coverage on Vulkan Video and AV1, the Wayland and KDE drama, and even news about Rust in Thunderbird. We have tips for grabbing a serial device right away, GNU screen for saving machines from spotty SSH connections, and a tip on what to do if your remote desktop is just a black screen. The show notes are at https://bit.ly/3SsbTyZ and enjoy! Host: Jonathan Bennett Co-Host: Jeff Massie Guest: David Ruggles Want access to the video version and exclusive features? Become a member of Club TWiT today! https://twit.tv/clubtwit Club TWiT members can discuss this episode and leave feedback in the Club TWiT Discord.

Valve nukes two fan projects, AV1 comes to Twitch, AMD launches the Ryzen 8000G, Unity bans VLC, and a HoloISO powered Steam Deck competitor.

Pre-show: Marco has discovered knobbed microwaves John’s toaster journey

Ryan is back! At least, this week. As a guest. But he's BACK, darn it. We talked about stuff. M3. Qualcomm.  ARM.  So much financial. More topics in the time stamps below. Timestamps:00:00 Cold Open00:45 Intro04:39 Food with Josh07:51 Qualcomm X Elite Windows benchmarks24:32 Apple M3 discussion36:23 Intel financials42:57 AMD financials47:48 Qualcomm had financials, too48:57 AV1 is everywhere50:27 Ryan is lit51:45 Security Corner59:14 Gaming Quick Hits1:03:30 What 5 years at Intel did to Ryan1:04:41 Back to Gaming1:08:41 Picks of the Week1:16:47 Outro ★ Support this podcast on Patreon ★

This is a recap of the top 10 posts on Hacker News on October 31st, 2023.This podcast was generated by wondercraft.ai(00:38): German court prohibits LinkedIn from ignoring "Do Not Track" signalsOriginal post: https://news.ycombinator.com/item?id=38081633&utm_source=wondercraft_ai(02:28): Phind Model beats GPT-4 at coding, with GPT-3.5 speed and 16k contextOriginal post: https://news.ycombinator.com/item?id=38088538&utm_source=wondercraft_ai(04:06): Firefox got faster for real users in 2023Original post: https://news.ycombinator.com/item?id=38087573&utm_source=wondercraft_ai(06:06): I've overlayed stays on a light pollution satellite mapOriginal post: https://news.ycombinator.com/item?id=38083484&utm_source=wondercraft_ai(07:54): macOS Sonoma Boot FailuresOriginal post: https://news.ycombinator.com/item?id=38089342&utm_source=wondercraft_ai(09:42): Home schooling's rise from fringe to fastest-growing form of educationOriginal post: https://news.ycombinator.com/item?id=38085417&utm_source=wondercraft_ai(11:15): AV1 video codec gains broader hardware supportOriginal post: https://news.ycombinator.com/item?id=38083588&utm_source=wondercraft_ai(12:49): Jury Finds Realtors Conspired, Awards Nearly $1.8B in DamagesOriginal post: https://news.ycombinator.com/item?id=38089356&utm_source=wondercraft_ai(14:35): Norwegian ban on Meta behavioral advertising extended to entire EUOriginal post: https://news.ycombinator.com/item?id=38092612&utm_source=wondercraft_ai(16:09): California employers must reimburse remote workers for all necessary expensesOriginal post: https://news.ycombinator.com/item?id=38085289&utm_source=wondercraft_aiThis is a third-party project, independent from HN and YC. Text and audio generated using AI, by wondercraft.ai. Create your own studio quality podcast with text as the only input in seconds at app.wondercraft.ai. Issues or feedback? We'd love to hear from you: team@wondercraft.ai

This week I recap the opening weekend of the NFL season reviewing the streaming services across YouTube (NFL Sunday Ticket), ESPN (Monday Night Football), Amazon, (Thursday Night Football), and Peacock (Sunday Night Football). I document why YouTube came out on top, the problems Amazon and Peacock had, and the complete outages that took place on Xfinity and Shaw.I also discuss the patent suit that Sling TV and DISH Technologies filed against fuboTV alleging infringement on eight patents related to multi-bitrate streaming, with the oldest patent dating back to Move Networks technology. And I briefly cover news from Apple that the new A17 Pro chip will support AV1 video via a dedicated AV1 decoder in the new iPhone 15 Pro and iPhone 15 Pro Max.

Marc Schwieterman from daily.co joins us to talk about the in and outs of building a video SDK and what capabilities are for iOS.Guest Marc Schwieterman marcschwieterman.com  Github @marcisme Twitter @mschwieterman Mastodon @marc@xoxo.zone Daily Related Episodes Spatial Experiences of the Wild with Adrian Eves It Depends with Brandon Williams Empower Station with Matt Braun Connecting Wirelessly with Gui Rambo Related Links  Daily Daily Client SDK for Python — daily-python documentation How and why Daily is using Rust for our WebRTC API platform Introducing Daily Adaptive HEVC for iOS native video Video SDK Features: Build Video Calls into any UI or App - Daily The Swift Package for the Daily Client on iOS daily-ios-starter-kit WWDC  Create a more responsive camera experience Discover Continuity Camera for tvOS Support external cameras in your iPadOS app What's new in voice processing iPhone 15 Pro has an AV1 decoder but no encoder Add support for visionOS targets · Issue #642 · rust-lang/compiler-team Support Apple tvOS in libstd by thomcc · Pull Request #103503 · rust-lang/rust Social MediaEmailleo@brightdigit.comGitHub - @brightdigitTwitter BrightDigit - @brightdigitLeo - @leogdionLinkedInBrightDigitLeoInstagram - @brightdigitPatreon - empowerappshowCreditsMusic from https://filmmusic.io"Blippy Trance" by Kevin MacLeod (https://incompetech.com)License: CC BY (http://creativecommons.org/licenses/by/4.0/) (00:00) - What is Daily (03:16) - Building an iOS SDK for Video (16:19) - Swift UI (28:12) - WWDC 2023 (33:06) - AV Foundation and Networking (41:18) - Future Plans and AI ★ Support this podcast on Patreon ★

A Path Through the Storm   When storms loom, media outlets often show footage of people placing plywood on homes and businesses and hunkering down. Caregiving is its own storm. Although sometimes receiving advance notice, caregiving can often descend like a tornado—and last a lifetime. If cameras followed caregivers, many daily activities might resemble the frantic bustle of those boarding homes and businesses. Imagine trying to build a five-year plan while simultaneously working to survive a hurricane. Incredulously, many caregivers regularly attempt such a feat. While the aftermath of hurricanes usually brings clearer skies that allow rebuilding, the lengthy caregiving storm usually ends at a cemetery—and the path to rebuilding appears shrouded in confusion, despair, and even desolation. Yet a path through and following the storm does exist. It's called endurance. The challenges of caregiving can forge a resilience and resolve that spills into every area of life. Many faced with hardships lament, “How do I get out of this?” Caregivers (and others) can instead change that question to “What can I become through this?” Entire marketing ads promote tempting versions of success that sadly ring hollow as the years pass. Endurance remains its own success while standing the test of time.           " . . . knowing that suffering produces endurance, and endurance produces character, and character produces hope . . ." —Romans 5:3–4 esv   [AV1]

Des smartphones, une tablette, de l'intelligence artificielle à tous les niveaux, c'est le menu de la Google I/O qu'on va picorer aujourd'hui. Dans le flash info, on revient aussi sur les pubs qui apparaissent dans Windows 11, et sur Spotify qui a supprimé des tas de chansons générées par l'intelligence artificielle.Avec le Pixel Fold, Google se lance sur le marché des smartphones pliantsPixel Tablet : Google remet le couvert sur les tablettesPixel 7a : Google muscle son entrée de gammeLa recherche de Google expérimente l'intelligence artificielle générativeDes itinéraires immersifs à venir dans Google MapsAndroid détectera automatiquement les AirTags indésirables dès cet étéMicrosoft envisage de mettre des publicités dans les paramètres système de Windows 11Spotify supprime des « dizaines de milliers » de morceaux générés par l'IAEn deuxième partie d'émission, Pierre fait le point sur le codec vidéo AV1 qui est en passe de s'imposer sur toutes les plateformes et chez tous les constructeurs… sauf chez Apple. Pourquoi ? Comment ? Vous saurez tout ou presque ce matin !Apple ne gère toujours pas le codec AV1 et c'est un gros problème en 2023Bonne écoute ! On se retrouve dès demain pour un nouvel épisode de Sortie de veille.___Vous aimez ce podcast ? Mettez-lui ⭐️⭐️⭐️⭐️⭐️ !Pour écouter l'intégralité du podcast, devenez membre du Club iGen (http://clubigen.fr) et bénéficiez d'un site web dédié et d'articles exclusifs, sans publicité dans nos applications ! Soutenez votre site préféré et bénéficiez d'une version sans pub ! https://plus.acast.com/s/sortie-de-veille-un-podcast-de-macgeneration. Hébergé par Acast. Visitez acast.com/privacy pour plus d'informations.

Coming up in this episode 1. Leo shows his moxy 2. Ubuntu falls flat 3. Watch the browsers 4. A Look back on our season 5. and Leo moves his files See this episode on Youtube (https://youtu.be/Vbofi3pndm4) https://youtu.be/Vbofi3pndm4 319 Audio Timestamps 0:00 Cold Open 2:03 Proxy Moxie 16:42 Ansible In Your Pantsible 22:56 Ubuntu Falls Flat 41:57 Browser Watch! 1:03:55 Feedback 1:13:49 Season 3 Recap 1:26:17 Community Focus: Geerling Guy 1:28:13 App Focus: TermSCP & Filezilla 1:37:25 Next Time: Raspberry Pi OS 1:39:25 Stinger Banter Proxmox (https://www.proxmox.com/en/proxmox-ve) Ansible (https://www.ansible.com) Announcements Give us a sub on YouTube (https://linuxuserspace.show/youtube) and TILvids (https://tilvids.com/a/linuxuserspace). You can watch us live on Twitch (https://linuxuserspace.show/twitch) the day after an episode drops. If you like what we're doing here, make sure to send us a buck over at https://patreon.com/linuxuserspace Flattening out Ubuntu Ubuntu and the official flavors decide not to include Flatpak by default (https://discourse.ubuntu.com/t/ubuntu-flavor-packaging-defaults/34061?u=d0od) More Announcements Want to have a topic covered or have some feedback? - send us an email, contact@linuxuserspace.show Browser Watch Total Cookie Protection (https://blog.mozilla.org/en/mozilla/firefox-androids-new-privacy-feature-total-cookie-protection-stops-companies-from-keeping-tabs-on-your-moves/) Firefox Extension (https://blog.mozilla.org/en/mozilla/email-protection-just-got-easier-in-firefox/) Firefox will get support for animated AV1 images and in a surprise move (https://9to5linux.com/firefox-113-promises-support-for-animated-av1-images-official-debian-package-and-more) an official debian/ubuntu package in .deb format. Edge is testing (https://www.bleepingcomputer.com/news/microsoft/microsoft-is-testing-a-built-in-crypto-wallet-in-microsoft-edge/) a Crypto Wallet. Edge added DALL-E right into the browser (https://www.bleepingcomputer.com/news/microsoft/microsoft-edge-can-now-generate-images-with-ai/)! Brave adds a VPN option (https://brave.com/desktop-vpn/). Brave removes (https://brave.com/privacy-updates/24-google-sign-in-permission/) legacy Google sign-in Cookies. Chrome/Chromium will unload background tabs (https://arstechnica.com/gadgets/2023/02/chrome-110-will-automatically-discard-background-tabs-heres-how-to-stop-it/) to save memory. Falkon is finally getting hardware acceleration (https://www.omglinux.com/falkon-browser-hardware-acceleration/)! Gnome Web has a few tricks coming (https://www.reddit.com/r/gnome/comments/11pav5t/comment/jbww3sb/) in version 44, as well. Feedback Senor Araton On compiling the Gentoo Kernel Installed a distribution-binary-kernel to get a running system. Leo wants to compile all the things. John A. On Linux Books ownCloud (https://www.oreilly.com/library/view/running-linux-5th/0596007604/) Bradly on the Ubuntu ShipIt Program Tried to convert as many as possible. Bonus Bradly Also - Leo, make the switch to Proxmox. Dan is right. R.L. on -O3 Just FYI, the compiler option is -O3 (dash oh three), not -03 (dash zero 3) The O obviously stands for Optimize

Lisa works on the Dev Craft team at Instagram that embarked on a journey to bring Kotlin to the Instagram for Android code base a little over three years ago. Now, nearly half of the large codebase is migrated and over 80% of newly committed code is in Kotlin. Tune in to hear what the unique challenges of bringing a new language to an existing app are and what it means for build speed, IDE experiences and developer happiness. Got feedback? Send it to us on Twitter (https://twitter.com/metatechpod), Instagram (https://instagram.com/metatechpod) and don't forget to follow our host @passy (https://twitter.com/passy and https://mastodon.social/@passy). Fancy working with us? Check out https://www.metacareers.com/. Links Meta Engineering Blog: How Meta brought AV1 to Reels - https://engineering.fb.com/2023/02/21/video-engineering/av1-codec-facebook-instagram-reels/  Source-only ABIs for Java - https://engineering.fb.com/2017/11/09/android/rethinking-android-app-compilation-with-buck/ Timestamps Intro 0:06 Intro Lisa 1:27 Dev Craft at Instagram 3:03 Building DevX Partnerships 3:56 The History of Kotlin at Instagram 6:22 Declarative UI 18:29 Build Speed Challenges 20:25 Source-Only ABIs 23:19 IDE Performance 26:19 Kotlin at IG in 2023 27:15 Outro 32:02 Bloopers 33:07

“Often, CEOs get fixated on their competition. I think it's a really big mistake because you just end up impersonating them. Just look after your customers and give them a great product and service, such that you don't even have to be concerned about your competition.” In this Best of Series episode, we hear from Accidental CEO of AV1, Keith Wootton, on finding inspiration, daily disruption, and crafting a magnetic culture.

    Microsoft: 1:15 - Hololens government project not happening - Microsoft 365 and One Drive being combined - More people don't want Microsoft to purchase Activision   General Tech: 17:00 - New AMD processors - Intel 13900KS - John Deere wants you to think they care. They don't. - OBS adds AV1 encoding   Google: 36:53 - Pixel 7 camera glass shattering   General Tech: 41:17 - Samsung Galaxy S23 event announced - New Sony Walkman - Roku will be making their own TVs   Gaming: 59:44 - Asus gaming Chromebook - Avatar Generations - TNMT: Shredder's Revenge - Microsoft Developer Direct Livestream - Indie Game Spotlight of the Week: Super Giant Games, Hades 2     https://www.patreon.com/callingallplatforms    T-Shirts!   Contact: podcast@callingallplatforms.com Social: Facebook Twitter YouTube   Apple Podcasts Google Podcasts Spotify Android

Edubuntu is back! Handbrake gets super AV1 powers, System76 is giving away a Thelio Mira Workstation, hacking Xfinity with Linux, and data recovery with xfs_undelete.

Get a $100 60-day credit on your new account at: http://linode.com/wan Timestamps (Courtesy of NoKi1119) Note: Timing may be off due to sponsor change 0:00 Chapters 2:09 Intro 2:38 Topic #1 - Updates on the eufy situation 3:46 Rob's video, notifications, port-forwarding & 30-day deletion 5:14 Data notification, Linus on heat pumps & Luke corrections 8:24 Users information, GDPR, event logs & EULA 12:24 taping over lights 14:09 How would you provide "free" local storage? 14:56 eufy's quote, Luke's hot take 16:12 Linus on hand-picking data & "local-only" 20:06 Topic #2 - OpenAI's ChatGPT text & code generator 25:02 ChatGPT, security filters, Luke's ballad on butts 31:32 Linus unable to log into beta, discusses prompt 34:36 Linus's prompt on Luke's butt 35:54 Luke uses his character & prompts stories via chatbot 37:04 Discussing Advent of Code, automated prompts 40:42 OpenAI prompted a warning to Linus 42:28 Learning programming via chatbot, API docs reference 44:54 Broken GPU scenario, generating an LTT video script 48:38 Chatbot's advice on feeding kids vegetables 50:56 Chatbot's spicy dbrand Tweet, Luke on jobs future 56:12 Chatbot explaining world problems Kanye West's style 57:22 Sponsors 1:04:06 Linus tries the chatbot for Extra again 1:05:28 Compiler error in generated code, API issues 1:07:24 LTTStore limited amount of black shaft screwdrivers 1:09:22 Topic #3 - LTT Labs beta site demo 1:12:52 Preview of comparing two product reviews 1:14:14 LMG still hiring 1:14:55 Topic #4 - Apple's SOS saves a stranded Snowmobiler 1:16:28 Apple shuts off AirDrop in China after 10 minutes 1:18:08 ChatGPT makes Discord bot for responses, poor Jake 1:18:48 Topic #5 - The Last Seven Days in Twitter #3 1:19:26 Elon on Apple not advertising & "free speech suppression" 1:20:02 Hunter Biden story suppression 1:20:18 Elon on an "alternate phone," Linus calls everyone out 1:20:48 No longer enforcing COVID misinformation policy 1:21:08 Elon resolves misunderstanding with Tim Cook 1:23:22 Why not make a fork? Discussing Logitech G Cloud 1:25:58 Twitter engagement, trending & business aspect 1:31:10 Linus calls out FP user on "children consent" 1:31:56 Topic #6 - DnD will now call races "species" 1:33:18 Merch Messages #1 1:33:29 Encouragement for those entering the developer space 1:49:38 Do over-regulations stifle innovation? 1:51:18 With similar AI threads, would it be unique? 1:54:12 Topic #7 - Scalpers unable to sell RTX 4080 or return it 1:54:40 Hardware Unboxed's video on a "new" RTX 3060 8GB 1:56:14 Comparing relative performance, low-end alternatives 1:59:38 Merch Messages #2 1:59:46 How would Luke spend LMG's money? 2:02:46 Topic #8 - Luke on Intel's Arc 2:07:33 Would people overlook AMD's flaws after Arc's introduction? 2:09:38 Luke discusses AV1 for streamers, AV1 advantages 2:11:28 Would Linus put an RDNA3 GPU in his personal rig? 2:12:24 Luke is not sure what to do with his money 2:13:17 Topic #9 - Hacksmith's "fire-cooled" PC collab 2:13:55 Showcasing Mini-Saber 2:16:17 Reselling PTM7950 idea, conflict of interest & assets 2:20:22 Validating data, transparency, trust & spoofing 2:23:38 Merch Messages #3 2:23:46 Thoughts on the removal of product pages 2:24:56 Using DXVK, Valve's Proton 2:27:01 What's next on a future home tour? 2:27:46 Selling branded merch to fund open source projects? 2:30:03 Outro

Diese Folge ist wie ein Flummi, der mit voller Wucht in den Raum geworfen wird. Wir springen in den Themen und reden u.a. über die Weltlage, relative Entfernungen, simultane Übersetzung, digital klonen lassen, wirre Geschäftsideen, aktuelle VR Technik, ungeschnitten nur auf Twitch und den Hausbau in Amerika. Eure Fragen oder Themen unter dem Hashtag #die2onair Links zu den Themen der Folge: ► Spirited https://www.imdb.com/title/tt10999120/ ► AV1 auf Twitch https://www.twitch.tv/videos/637388605 ► Guitar Teacher REACTS: Billy Strings "Dust In A Baggie" LIVE @ The Opry https://youtu.be/dfPgSYtMe34 ► Building an invisible 4K TV https://youtu.be/2fX1qYMcfgs Die2 auf Twitter https://twitter.com/die2onair

Try FreshBooks free, for 30 days, no credit card required at https://www.freshbooks.com/wan Deploy a cloud server in seconds with Hetzner at https://www.hetzner.com/cloud?pk_source=youtube&pk_content=yt-cloud-2022 Get Exclusive NordSecurity deals here ➼ https://nordsecurity.com/wan All products are risk-free with Nord's 30-day money-back guarantee! Timestamps (Courtesy of NoKi1119) Note: Timing may be off due to sponsor change 0:00 Chapters 1:06 Intro 1:36 Topic #1 - NVIDIA unlaunches RTX "4080 12GB" 2:30 NVIDIA's misleading cards naming 7:18 History of shameful corporal behavior 10:06 NVIDIA's "apology" showcases store queues 11:38 LTT's video on ARC for AV1, ideas & GPUs discussion 14:52 Topic #2 - Google AI struggles with FP's Privacy Policy 19:22 YouTube's Creator Summit, issues with AI 23:32 Topic #3 - Netflix launches ad-based subscription 26:16 Rate of ads per hour, interrupting movies 28:56 Discussing ad blocking & downgrading 33:42 LTTStore new merch 34:36 LTTStore beanie colors 35:53 LTTStore backpack updates 37:24 Merch Messages #1 37:30 Noctua's paste guard 38:36 Tech tips for toddlers & babies, discussing Yeezy's 46:00 Linus's thoughts on EV bikes 49:26 Topic #4 - Sony is against Microsoft-Blizzard acquisitions 51:28 Counter-arguments, Microsoft's article 55:42 Luke on another Blizzard lawsuit 59:24 Sponsors 1:02:00 Failing to call Colton Potter 1:03:12 Topic #5 - Meta's Quest Pro VR headset 1:05:48 Discussing price & specs 1:08:33 Moore's law, generational leaps 1:12:06 AI erases NHL players 1:14:46 Discussing Meta 3, Meta 2 Amazon reviews 1:17:19 Colton Potter announces LTX 2023 dates 1:19:55 Topic #6 - Discussing Mark Bench 1:20:32 Weird data on LTT's RTX 4090 video 1:22:46 Topic #7 - Microsoft Surface Pro 8 & X 1:23:01 Discussing pricing & specs, all-Intel 1:23:44 Microsoft Surface Studio 2 Plus 1:24:04 Merch Messages #2 1:24:13 Did Linus try playing pickleball? 1:25:25 Tips for transitioning into adult independence 1:26:02 Whale investors 1:32:08 Experiencing issues after PC building 1:34:08 Would LOUQE go out of business? 1:38:58 Software development & testing 1:41:45 SoundCore Sleep A10 1:42:01 Why not use OpenBenchmarking? 1:43:54 Convincing a boss to invest, LMG content exclusivity 1:50:14 FP Poll: to use exclusives occasionally? 1:53:54 Outro

このエピソードを聞いてしまったら最後、あなたはRTX 4090/80を欲しくなってしまうでしょう。そのくらいインパクトが大きい6つの技術を西川善司さんが超わかりやすく解説します。 ▽トピック オープニング / アバター / Nvidia エンコーダー / デュアル AV1 エンコーダー / シェーダー実行リオーダリング (SER) ▽関連リンク @backspacefm / Twitter シンBSマガジン YouTube版 #465 『アバター：ジェームズ・キャメロン 3Dリマスター』9.23（金・祝）より3D大スクリーンで2週間限定公開 GeForce RTX 40 シリーズ GPU の紹介 - NVIDIA ▽レギュラースポンサー この番組はフェンリル株式会社の提供でお届けしております。 backspace専用マストドンインスタンス、通称グルドンはさくらインターネットのサポートを受けて運用しています。 backspace.fmでは我々の活動を応援してくれるスポンサーを募集しています。興味がある方はぜひこちらにて連絡ください！drikin+backspacefm@gmail.com この番組は Riverside.fm を使ってリモート収録しています。 Riverside.fmはビデオ通話をしながら高音質ファイルを同時に収録することができる、ポッドキャストなどのリモート収録に特化したサービスです。興味がある方はぜひこちらをチェックしてみてください。https://bit.ly/RiversideFM_Backspace

Join The Full Nerd gang as they talk about the latest PC hardware topics. In this episode the gang is joined by the Stream Professor himself EposVox to cover what happened to PCWorld's YouTube channel (spoilers: it was deleted), in-depth AV1 testing on an Intel Arc A380, and of course we answer your questions live! AV1 encoding deep-dive: https://www.youtube.com/watch?v=ctbTTRoqZsM Buy The Full Nerd merch: https://crowdmade.com/collections/pcworld Join the PC related discussions and ask us questions on Discord: https://discord.gg/SGPRSy7 Follow the crew on Twitter: @GordonUng @BradChacos @MorphingBall @KeithPlaysPC @AdamPMurray Follow PCWorld for all things PC! ------------------------------­---- SUBSCRIBE: http://www.youtube.com/subscription_center?add_user=PCWorldVideos TWITCH: https://www.twitch.tv/PCWorldUS TWITTER: https://www.twitter.com/pcworld

Get a $100 60-day credit on your new account at: http://linode.com/wan Get three months of Gusto FREE at: https://gusto.com/wan Get Exclusive NordSecurity deals here: https://nordsecurity.com/wan All products are risk-free with Nord's 30-day money-back guarantee! Timestamps: (Courtesy of NoKi1119 - NOTE: Timestamps may be off due to change in sponsors) 0:00 Chapters 1:16 Intro 1:44 Topic #1 - Even MORE trouble for Intel's ARC 2:18 Third parties are leaving ARC behind 4:14 Intel struggles with RMA, NCIX stories 6:21 ONE halts production, board partners not interested 10:18 Wafer production, AV1 encoder 15:02 Merch Messages #1, LTT backpack launched! 16:22 LTTStore products that would work with backpack 22:04 Lab doing USB hub reviews, dashcam rant 26:32 Lab publishing a chart of tested products 28:02 Linus wants to show off a minimally viable product 30:52 Testing throughput, website design, Chroma UPS 41:14 WAN hoodie & backpack promo 41:36 Linus's & Luke's favorite freeware software 45:46 Woman sizes update 46:48 LTTStore version of wrist rests 50:28 Labs' reply to testing USB power banks & hubs 54:12 Impact of China V.S. Taiwan on the tech community 57:16 Hasbro pulse selfie to figures 1:02:24 Boomer "garbage", testing range 1:06:36 Whether labs would do durability testing 1:09:50 Paw patrol, favorite dog plush 1:10:38 LTT Backpack warranty 1:12:30 Ethernet cable routing in brick walls 1:13:06 TV video & charging solutions 1:14:32 Sponsor - Shortform 1:16:01 Sponsor - Squarespace 1:16:56 Sponsor - MSI 1:17:32 Discussing LTTStore support tickets 1:18:24 Topic #2 - Amazon buys iRobot, creator of Roomba 1:21:48 Topic #3 - Europeans upset about LTT shipping 1:22:46 Linus on subsidized shipping costs 1:25:38 Taxes on the free stickers being refunded 1:26:54 Shopify development takes time 1:28:26 Idea to have variable costs dependent on areas 1:30:30 Another warehouse would not lower the costs 1:32:30 Backpack release went greatly, different ideas 1:35:58 Labs testing headphones 1:36:38 Topic #4 - Whale LAN highlights 1:36:48 Whale LAN L4D tournament, Linus & OG crew 1:40:10 Halo CE Blood Gulch 1:42:36 Linus rages is not a quiet gamer 1:48:24 Miner VGA tournament 1:52:04 Space cadet on Steam Deck, CS tournament 1:53:58 Topic #5 - Google now has two Google Meets 1:55:00 Linus rants about the stupidity of the matter 1:56:14 Discussing changes & Duo changes 1:59:02 Meet app is now updated to "Meet (Original)" 1:59:24 Merch Messages #2 1:59:32 LTT HDR update 2:01:20 Thoughts on smartwatches 2:03:12 What IT freelancer Luke did to find work 2:05:10 Exercise routines 2:06:38 PSU SATA cables are not cross-compatible 2:09:14 LTTStore wallets idea 2:10:32 How Linus feels about VTubers & smart speakers 2:16:52 Would Linus get an RFID implant? 2:17:20 Luke on road mapping, developing & planning 2:21:06 Transferring data between phones 2:22:14 Outro

Thunderbird Sync is ahead of schedule! FFmpeg adds support for AV1 decoding, Installing Davinci Resolve on Linux, and customizing GRUB for fun and profit.

Sigmund and Devon discuss the release of tvOS 15.6, recap Apple's Emmy awards nominations, and highlight two of this week's releases: Best Foot Forward and the return of Trying. Send us a voice message all week via iMessage to mrolfm@screentimes.net.   Subscribe to our Apple TV Release Calendar.   ScreenTimes.net | Tweet Screen Times   Sigmund Judge | Tweet Sigmund   Devon Dundee | Tweet Devon Notes - Apple Public Beta Program Best Foot Forward | Apple TV+   Trying | Apple TV+   Up Next | Only Murders in the Building   Up Next | This Week's Apple TV Releases - James Lees   Dickinson Props Featuring in Emily Dickinson Museum   Fifteen Games Leaving Apple Arcade Soon | TouchArcade   Apple is seemingly preparing to add AV1 video codec support - FlatpanelsHD HD Fury for Dolby Vision Projection Aqara Curtain Motors    HidrateSpark Pro Smart Water Bottle Review Magic Rays of Light is a podcast from ScreenTimes.net  

Mint Mobile: Save money on your phone plan today at https://www.mintmobile.com/wanshow Gusto: Get three months of Gusto FREE at: https://gusto.com/wan NordSec: Get Exclusive NordSecurity deals here: https://nordsecurity.com/wan All products are risk-free with Nord's 30-day money-back guarantee! Timestamps: (Courtesy of NoKi1119) 0:00 Chapters 1:08 Intro 1:27 Topic #1 - Community reaction to Linus's RAM notes ft. special guests 3:39 Buildzoid's video on YouTubers & RAM 5:13 Discussing NForce, Intel & XMP 7:45 Linus tried to push NCIX into boutique PC building 11:24 Enabling XMP can void warranties 12:11 Summarizing Buildzoid's video 14:40 Crucial's blog posts on RAM technology 17:45 FP poll: Intel's ARC Jersey, showcasing A770, discussing games 23:00 FP Poll result, opening & showing off ARC 25:02 Linux support for ARC 27:58 Possibility of a 900 trim, families 29:02 Linus requests a good naming scheme 31:40 Discussing the RGB limited edition 33:38 Intel's view on efficiency, FP's rack & database 37:58 Shadow tech invites Linus to France, Luke wanting to go 40:36 Device sharing services, latency & encoding 43:26 AV1 codec, supporting encoders 46:56 Streaming community, cross-brand support 53:20 Discussing limitations on ARC, other features 56:30 Quadro branding, FP poll on supporting features 59:48 Intel plans to talk with the community 1:07:30 Linus wants a disruption in the GPU market 1:09:03 Guests leave the set, ARC's jersey shirt 1:10:20 Sponsor - Squarespace 1:11:24 Sponsor - Wealthfront 1:12:17 Sponsor - Axiom 1:13:11 Topic #2 - New LTT pop-up shop for backpack 1:13:55 Limited in-person & back orders 1:17:32 Pricing & location for the pop-up shop 1:19:22 The shop will NOT include the screwdriver 1:20:25 In-stock notification will show pop-up shop 1:21:50 Topic #3 - Whale LAN event 1:25:35 Topic #4 - Unity acquiring IronSource 1:25:48 John Riccitiello & IronSource ft. Luke's F-bomb 1:28:53 Topic #5 - Sony's Playstation Star 1:31:50 Complaint on LTT content being mainstream 1:32:32 Merch Messages #1 1:32:51 Companies growing on a positive way 1:35:09 Polium 1 NFT Web3 gaming console 1:37:49 Topic #6 - Dr DisRespect's Project Moon 1:42:37 Topic #7 - BMW's subscription on seat warmers 1:45:40 Topic #8 - Linus showcases Miner VGA 1:54:18 Topic #9 - Cole-Bar Hammer update 2:01:36 Linus dies, last attempt 2:05:15 Luke's YouTube channel on Assassin Creeds 2 2:10:00 Outro

Mint Mobile: Save money on your phone plan today at https://www.mintmobile.com/wanshow Gusto: Get three months of Gusto FREE at: https://gusto.com/wan NordSec: Get Exclusive NordSecurity deals here: https://nordsecurity.com/wan All products are risk-free with Nord's 30-day money-back guarantee! Timestamps: (Courtesy of NoKi1119) 0:00 Chapters 1:08 Intro 1:27 Topic #1 - Community reaction to Linus's RAM notes ft. special guests 3:39 Buildzoid's video on YouTubers & RAM 5:13 Discussing NForce, Intel & XMP 7:45 Linus tried to push NCIX into boutique PC building 11:24 Enabling XMP can void warranties 12:11 Summarizing Buildzoid's video 14:40 Crucial's blog posts on RAM technology 17:45 FP poll: Intel's ARC Jersey, showcasing A770, discussing games 23:00 FP Poll result, opening & showing off ARC 25:02 Linux support for ARC 27:58 Possibility of a 900 trim, families 29:02 Linus requests a good naming scheme 31:40 Discussing the RGB limited edition 33:38 Intel's view on efficiency, FP's rack & database 37:58 Shadow tech invites Linus to France, Luke wanting to go 40:36 Device sharing services, latency & encoding 43:26 AV1 codec, supporting encoders 46:56 Streaming community, cross-brand support 53:20 Discussing limitations on ARC, other features 56:30 Quadro branding, FP poll on supporting features 59:48 Intel plans to talk with the community 1:07:30 Linus wants a disruption in the GPU market 1:09:03 Guests leave the set, ARC's jersey shirt 1:10:20 Sponsor - Squarespace 1:11:24 Sponsor - Wealthfront 1:12:17 Sponsor - Axiom 1:13:11 Topic #2 - New LTT pop-up shop for backpack 1:13:55 Limited in-person & back orders 1:17:32 Pricing & location for the pop-up shop 1:19:22 The shop will NOT include the screwdriver 1:20:25 In-stock notification will show pop-up shop 1:21:50 Topic #3 - Whale LAN event 1:25:35 Topic #4 - Unity acquiring IronSource 1:25:48 John Riccitiello & IronSource ft. Luke's F-bomb 1:28:53 Topic #5 - Sony's Playstation Star 1:31:50 Complaint on LTT content being mainstream 1:32:32 Merch Messages #1 1:32:51 Companies growing on a positive way 1:35:09 Polium 1 NFT Web3 gaming console 1:37:49 Topic #6 - Dr DisRespect's Project Moon 1:42:37 Topic #7 - BMW's subscription on seat warmers 1:45:40 Topic #8 - Linus showcases Miner VGA 1:54:18 Topic #9 - Cole-Bar Hammer update 2:01:36 Linus dies, last attempt

Microsoft nerfs Xbox Cloud Gaming on Linux, Anbernic launches a budget Deck competitor, QR code powered Steam logins, AV1 hardware encoding on the Arc A380, and FEX-Emu learns how to Proton.

Ramzi Khsib  LinkedIn profileAWS Elemental website---------------------------------------------------Join our LinkedIn Group so that you can get the latest video insider news and participate in the discussion.Email thevideoinsiders@beamr.com to be a guest on the show.Learn more about Beamr

The 16:9 PODCAST IS SPONSORED BY SCREENFEED – DIGITAL SIGNAGE CONTENT If a company wants to hang its business hat on the proposition that it is very good at visualizing real-time data to screens, it helps to have a big, very familiar client that heavily uses that sort of thing. A small New York City start-up called Zignage has that in the New York Stock Exchange - providing and maintaining a platform that shows the numbers and trends charting on screens around the hyper-kinetic trading floor in Wall Street. The company grew out of an NYU media lab and spent its first few years working mostly behind the curtains, developing signage and data-handling capabilities to software firms and end-user clients. But a few years ago, the company made the decision to develop a brand and start selling its data-centric capabilities directly to end-users. I had a great chat with Alex Epshteyn, the CEO and Founder of the company, about how it got started, where its headed, who it all serves, and how there can be a huge gulf between software shops that can take a number from a shared data table somewhere, and running mission-critical, hyper-secure visualizations on a stock exchange floor. Subscribe to this podcast: iTunes * Google Play * RSS TRANSCRIPT Alex, thank you for joining me. Can you give me a rundown on what Zignage is all about, how they started and how long you've been around?  Alex Epshteyn: Absolutely. Thank you for having me, Dave. Zignage started in 2009 formally, and we started at the NYU Incubator while I was doing my graduate work at the Media Lab in NYU and suffice to say the company was more interesting than the graduate works. So I started doing that, even though I'm from the east coast and this doesn't typically happen, it kinda happened here. So initially, conceptually, we were gonna get into the digital out home space and we were gonna build an auction backend that people can bid for spots on digital signs. So kinda a slightly novel idea, especially in digital signage and we couldn't do a big enough raise, and then we found a number of these sort of remnant advertising platforms coming into the market and we decided, since I have a pretty good little black book of enterprise clients, and we built the platform to about 50% at that point, in mid to end of 2009, let's try our hand at some enterprise folks, and what ended up happening is a trajectory that basically pushed us for about eight years, which is we built a middleware and a toolkit, essentially our own toolkit, that enabled us to build very quickly CMSs and builds and anything related to that, data bindings for third party systems like CRM systems and CRP systems, a variety of backends essentially, and we essentially entered OEM space. So we built products for other companies. Some of them were large, some of them were small. We had a tremendous amount of NDAs and non-competes, as you can imagine. These companies would not like you to advertise your own stuff while you were building it for them and typically we would have maybe one or two of these customers at the same time. So from 2009 to about 2017, maybe a little bit later even, we basically did work for third parties and we built a lot of different solutions, and around 2018, we decided that we were gonna attempt to productize. That means, essentially build our own, front facing, become a brand, and move away from a pure sort of project solution, even though we had a product in there. But it was a product for us, not so much for the end customer and to get into the market and so we did, and in the meanwhile we had two direct customers during almost all the time. NYU was one. We had a number of schools at NYU that we were able to pitch, and successfully had running, so NYU Law School, NYU Engineering School, where I was a student and then NYSE where we initially partnered Thomson Reuters. So Thomson Reuters did the data and, most of the application stack actually, and what we provided is a device management framework and advanced players to run the WebGL and all the other things that they needed to run for the New York Stock Exchange. This was under the NYSE-Euronext regime, which has since been bought by the Intercontinental Exchange. This was in 2017, which was a formative year for us. As I mentioned, NYSE under the new ownership came to us and said, “Look, Thomson Reuters is relatively expensive and essentially they're reselling us their data, how about you guys take on their responsibility?” You get nine months to replicate and you get this support contract that basically takes over for them, at a discount for them but it was a nice option for us.  We took on the challenge. Because we were able  in these intermittent years we built up so much experience and know how to deal with realtime sources, realtime data sources, and WebGL specifically to make things pretty bulletproof whereas perhaps some other HTML5 technology that is fairly popular in digital signage would is maybe not robust or maybe not as performant. So we took that toolkit and applied it to over essentially at the New York Stock Exchange and took the contract over and successfully we did that. So at the New York Stock Exchange today, they're actually running two separate solutions from us. They have our more standard on print solution for their marketing group and then they have a much more customized, almost like an OEM version for their trading real time data, which are now classed as a number of financial data widgets.  So if I'm at the NYSE and I'm looking down on the floor, or I'm walking around the floor with all the guys with the funny jackets and everything, those various dashboard screens that I see with all the pricing indicators and everything else, that's all being driven by you? Alex Epshteyn: That is correct. So everything essentially above the workstation level, everywhere above the trader level, if you just look up above the 5'8” level from the ground, you'll basically be looking at our solutions. It actually is a full gambit of our capabilities. We have synchronized video, real time widgets for financial data consumption, charting types of things and a lot of different ticker technologies that we've custom built and some of our generic ones, and streaming as well. The only other company that works with us at the site is Haivision, so they provide the backend system and supplementary streaming solutions. So we consume their feeds and also feed them.  They're a video distribution company?  Alex Epshteyn: That's right. So we're actually partnered with them. So they're one of our partners in space. We like working with them, they are a nice Canadian company to say the least and I know some of the original folks that sort of constituted the company and they have grown as a company tremendously through the years. So we really like working with them.  Yeah, this must have been a really big holy shit moment for you guys when you got that deal because it's not like winning a hundred locations QSR chain or something, this is the New York Stock Exchange. It's on the TV every day with endless photos and everything else, and it's mission critical. Like you can't say, oh, we're just doing a software update and we'll be back in 10 minutes? Alex Epshteyn: Indeed, and the escalations we get are pretty hardcore. We have just a few minutes to get things going, and philosophically, we try to blend some aspects of redundancy with a lot of resiliency because redundancy itself, some folks who deal with these sorts of mission critical situations, could itself present its own set of problems, right? So you want the system, the platform itself to be as resilient or high availability as possible to use a term out of the server space.  So yeah, it was a huge thing for us and ultimately, we specialized in a lot of financial services and non-retail banking is a more generic category or an area we do very well in and we work with some integrators in the space that are known for it as well in terms of channel. Currently our CTO is actually the chief architect of the Thompson Reuter solution. He came on board with us a year ago, a year and a half ago as a full time hire. He was a consultant for many years after Thomson Reuters got customization space, and he worked with us for a long time and then finally our CTO to do other stuff, and Steve came on board. So we're very well positioned for this work.  So for your company, if you had to do an elevator pitch saying what all you do, what do you rattle off for them? Alex Epshteyn: I think what we would do is, as you mentioned, mission critical type of usages, whichever vertical, right? We've done things with SCADA. We've done things in transportation that I wish I was at liberty to say, maybe soon, and it doesn't have to just be financial data. It could be sports feeds. It could be building services, things of that sort that are critical for the use. That's one of our specialty points.  The other is, I would say, while we're very happy to have relationships with a number of hardware companies, we still have really some high end hardware that we field. So what we do is, for very demanding applications, not necessarily mission critical ones, but those overlap obviously, we provide a full-stack solution, and these players, we're getting into the realm of show control type of players, really beefy and professional level graphics capabilities. So we do sell those. Those are fully our stack, and this way we can guarantee basically the solution as opposed to having us do a certain portion system integrated to another and so forth.  The last thing I would say is while we still support some level of OEM work, we currently have two customers that we work with. Our business model changed a bit in the last three years of supporting them. We have our standard SaaS business and in some cases we modified it for on-prem. So it's already flexible, but we also have a platform as a service offering to really support those OEM customers. So it's a lot less expensive in volume, very scalable, and I would say those are the things that really make us stand out. It's real time data, data visualization, full-stack solution with hardware to do very difficult things often, and finally, configuration where people assume real, ad-hocs customization. There's an assumption there, right? If you're doing something very bespoke, the assumption there is that it's gonna be insanely expensive and take a long time to build and that's true if you haven't built two dozen variants of it and you don't have a toolkit to basically assemble it from parts like a LEGO set, which we do. I would assume that your calling card when you go in to talk to opportunities, when you can say, yeah, we do the New York Stock Exchange, we do all the data handling on that, and you could imagine it's more than a little bit secure and mission critically oriented. I suspect that makes the target customers feel pretty comfy? Alex Epshteyn: It does, and even before them, it makes consultants who put us on the bid lists and generally are interested in finding parties that can actually fulfill the scope, call us. So we don't really advertise much, and that's gonna change, I think, maybe next year. We're gonna do maybe a marketing splash at some point next year.  Right now, it's all word of mouth, and we do get a lot of calls. There's a lot of projects we actually pass on because they're not in our sweet spot and they're distractions, but the projects that we do take on are often difficult. We even do work in retail, as I mentioned to you, and the types of deals we take in are always really heavy data integration, visualization, where they are very automated workflows, there's almost no humans involved where the humans are basically special events, and then the system essentially corrects for automation again.  Yeah, I've been writing about data visualization for 6-7 years now, and when I started writing about it, it was pretty rare and beyond FIDS displays and things like that but it's now pretty standard. I'm curious because you guys are obviously super deep and experienced in that area, when you see all the other software companies saying, yeah, we do real time data, we can do realtime data handling, we can integrate, we have APIs and this and that.  When you get into a conversation with a prospect, how do you distinguish what you do versus other companies who say, yeah we do all that too, cuz I suspect it's different?  Alex Epshteyn: It is. One of the first things we've put on a table is that we can mostly guarantee our resolution time SLA, nobody else can pretty much. Most people will be aggressive, pick up the phone and work the problem, but the way that our stuff is built, we can fix the problem. We can guarantee fixing the problem within a certain period of time. Now it's not inexpensive, sometimes it's actually affordable for a lot of types of businesses where a fully custom solution would not be.  The other one is that most data visualization takes a lot of shortcuts, it really leverages, not to get too deep in technicalities unless you want me to, basically JavaScript and CSS, the mainstay of HTML5. But all of our data visualizations are built in WebGL. It's like the difference between driving a car on the road and driving a bullet train on tracks, right? There's no interruptions to the bullet train. It'll just go and it'll be on schedule. There's no interruptions. There's no jitter. There's no movement. That sort of paradigm. So we like to guarantee behavior of our data visualization, especially dynamic like charting or graphing libraries that we use and implement. It's actually extremely difficult to build something that you would think is easy like a ticker or crawler.  Whatever data that's feeding it, I'm sure we both have probably seen a lot of instances where it stutters, it has problems, it doesn't refresh on time and doesn't deal well with different fonts and whatnot. That's just not true of our solution. Our solution is, I would say, cutting edge on dynamic data visualization.  So for an end user or for an integrator, they have to educate themselves that just because a company says they can do real time data doesn't mean they can really do it. That means they might be able to reflect a number that's in a data table and show it on a screen, and that's quite a bit different from what you're talking about.  Alex Epshteyn: It is and maybe the third aspect is most of the companies we work with already have accounts with the big data warehouse places like Refinitive, IBS, and a number of others, so we already are super familiar with these back ends. In fact, we have things that monitor the APIs. We routinely do a lot of monitoring of real time or just dynamic sources. So this is a huge value add in the industry, and I wish more providers would do that because ultimately, if you are a data fed platform, it's up to you to tell the customer something's failing on the back end because they won't know, they'll assume all sorts of things, but you need to critically have the tools inside to tell what's going on, and if you build it out in a smart way, you can also alert the right people at the right time that something's happening and to look into it. So you can be proactive about it. That's the third item, I'd say.  They also change like the schemas and everything without telling people, right? Alex Epshteyn: That's true. But it's a super exciting space. Once you have the core technology built out. You could really do a lot, in terms of, consuming this kind of data and I think generally, signage, we're in a slightly privileged position regarding this, but I think there's a move into industry towards generative and procedural content away from more Codec-heavy content. Although, there's obviously gonna be overlap for many years for both. We certainly support Codec playback in a variety of ways, synchronized, on different players and so forth, and there's nice innovations like AV1 coming onto the market nowadays. But you could do so much more with generative dynamic content, it's a big difference. For instance, we had a client that wanted us to expose much more of the controllability of a layout, standard design tool inside of our platform. Now, typically we would not wanna do that because there's some nice tools on the market like Premiere, like After Effects, real tools that they generally use. But the problem that certain customers power users I would say are having is they don't wanna have to export an After Effects file and have it encoded in something, that's time, that's sometimes money because they do it externally because they don't have a kit on-prem, or in the cloud.  So what we've done is basically have a simpler version of something like Adobe Premiere or After Effects that lets them make quick changes in some key framing or some transitory effects and they don't have to put the whole thing into a codec. So that seemed to really resonate with certain power users that we have and directionally, it's the area that we'd like to innovate in. Is it important to make a distinction between generative data for business applications and generative data for artwork? Because I see a lot of video walls out there that are set and forget. They're driven by generative data and it's just these abstract visuals that are swirl and kind of bloom and everything else, but that's very different from, I think what you're talking about, which is what on the screen in terms of charting or what appears is based on what the data is influencing, it's it's shaping what appears?  Alex Epshteyn: That's correct. A lot of general data is canned, right? It's almost like a video basically, and some experts, some design shops typically would change it for you, and it becomes evergreen content, day two, three, and day four. What we try to do is something a little bit different and we work with some really nice design companies as well. So just to be completely clear, we don't do the design ourselves. We typically either partner with a company that's really good at it. Sometimes the company brings us into the opportunity, right?  The consultant can also spec us to partner with somebody or the end client may have relationships with companies that do this very well. But, I would say the formulation, the recipe for this kind of thing, to make it dynamic is a few things, and that's where this sort of generative content becomes more like a Zignage type of problem, as opposed to something that you could hire a design house to basically build for you, right? One is that you could update content even if the filters or the generative piece is running. Separately you might be able to in CMS have the tools to change the filters of the generative option, just as I explained prior, and finally have trigger conditions. We do mostly casting, right? There are some great companies in space. I think they're very good at that kinda stuff. They do a lot of smart interactive signage. We do a little bit of that, but we mostly do narrowcasting. So in our world trigger conditions come from some sort of backend system. It could be a calendaring system, it could be something smarter, right? Where it's not just a boolean condition. It could be a multivariable that basically has to click off a list of things that can happen. And that's really where we can add a lot of value and it overlaps with the kinda work we do with the New York Stock Exchange. We generally term it as business logic So we really do some smart business logic and I think it's actually, there's a lot of growth in that area once we apply modern sort of machine learning to it to make it extensible to go further.  But with that kind of approach you have an ability to modify a piece of content continuously, right? It's a living piece of generative content, even if it's not dynamically fed with financial data sources, or sports data sources.  I haven't seen your user experience, but I'm guessing people listening to this are thinking, this is really interesting, but I'd be terrified to try to use this software. What's it actually like? Alex Epshteyn: You're not gonna be terrified because we are one of the proponents of nearly or fully automated systems. So often what we do for non-power users is to give a build out to the software that our customers use, and then everything is essentially this business logic that I'm describing to you.  It's kinda like a headless CMS? Alex Epshteyn: It's like a headless CMS for the non-power users. For the power users that really like their tools like Adobe, or you could just use a Dropbox or some sort of hotfolder mechanism. We're also partnered with a number of DAM solutions. There's a lot of workflow that happens in digital asset management solutions, including tag based workflows.  We do a lot of tag based workflows nowadays, where we consume the tags that are done in a DAM, and essentially they find their way onto the right players at the right time, and on the flip side, we do have a standard suite. It's actually going through a major overhaul at the end of the year, what we call Z Cast 6. It does have a number of these power tools. But our CMS generally follows a certain idea. It was popular for a while and it's hard to execute unless you have our kinds of customers, which is what we call an additive UX. So it's the opposite of something like Microsoft Office, right where you have a billion features and there's a long learning curve if you wanna learn everything. What we do is really try to identify the user story behind what needs to be done. We create the access controls that really expose certain parts of the CMS, and even within the same context, add or remove tools as needed. That creates a situation where there's almost really minimal training. I think one of the biggest problems we're trying to solve for our direct customers, or channel customers is the attrition that happens in major enterprises for users of digital signage, right? Like one of the biggest problems we face even in huge banks is the fact that digital signage is consigned to a webmaster subcategory. Like they manage the CMS that's published on their portal, and then somebody in that team or a few people in that team handles digital signage as well. So that's historically been a problem for our whole industry, and what we're trying to tackle is kinda remove both the friction of adoption and also try to give them the tools that they need, and if they use tools, bridge those tools, that's our philosophy on that end. So what's the structure of your company? Are you a private company?  Alex Epshteyn: We are a private company. We're an LLC in New York, and we're about 20 people. Most of our development used to take place until very recently in Ukraine because one of my partners and I from there originally. So as this topic is in the news, unfortunately, forget about our team. The fact is cities in the eastern part of Ukraine are partially destroyed but luckily a lot of the folks that we would use are in the Western part of Ukraine now, and we continue to use them but not all of them unfortunately. So you're having to manage your way through that along with other things, right?  Alex Epshteyn: We did, and they're very talented folks. We have worked on so many projects.  Yeah, it's interesting. I was trading LinkedIn messages with another company and he was talking about operating out of Odessa and they're still like opening QSRs and things like that and putting in menu boards.  Alex Epshteyn: Good for them. That's exactly what they should do.  Yeah, and I was thinking, boy, all the other challenges you have out there, like supply chain and everything else, layer in a hot war on top of that. Good lord. Alex Epshteyn: Our problems are very small compared to the real problems in Ukraine and the world. But it's a small world. You sort of face these things as they come.  Well, hopefully someway or other, it gets resolved. I'm not quite sure how, but this was great. Can you let people know where they can find your company online?  Alex Epshteyn: Sure. It's Zignage.com  So signage with a Z on the front?  Alex Epshteyn: Correct. The last word is Zignage. You find me on LinkedIn, Alex Epshteyn. That's where mostly we do our sort of minimum branding that we do.  All right, but we'll be looking for more later in the year, right?  Alex Epshteyn: Absolutely. We're excited to make some announcements in the transportation space, some more in the financial industry and some more in retail. All right. Great to hear it's going well for you. Thanks so much for spending the time with me. Alex Epshteyn: Thank you, Dave. My pleasure.

Get three months of Gusto FREE at: https://gusto.com/wan Get Exclusive NordSecurity deals here: https://nordsecurity.com/wan All products are risk-free with Nord's 30-day money-back guarantee! Timestamps: (Courtesy of NoKi1119 - Note: Timestamps may be off due to change in sponsors) 0:00 Chapters 1:18 Intro 1:51 Topic #1 - Intel's Arc early review 2:44 Performance compared to competitors 6:43 Thoughts on the naming scheme 9:54 Nvidia's impact on GPU box arts 12:30 The graphic's potential ft. Linus agreements 15:08 Support for AV1, YouTube's HDR & suggestions 22:18 Topic #2 - Leaked TikTok audio, data privacy 24:42 Impact on the internet, cybersecurity risks 29:11 LTTStore HDD hoodie, notebook & discounts 36:26 Topic #3 - Amazon's Alexa voice cloning 37:37 Deepfake Linus, ethicality & security risks 45:44 Sponsors 49:28 Merch Messages #1 ft. side discussions 50:16 Inovelli's "Project Linus" 54:24 Bidding on Artesian Builds, Linus's pitch 58:19 Linus bricks a Linux install before ShortCircuit 1:01:21 Steam summer sale, Linus on game displays 1:12:23 400 Stealth hoodies sold, games discussion 1:14:05 What happened to the Blackmagic cameras 1:15:03 Mattress suggestion 1:15:46 Was LTT ever compromised? LMG's finances 1:22:43 Biohacking, RFID implants 1:25:51 Possible LTT handtools after the screwdriver 1:25:58 Topic #4 - PCIE 70 standard 1:26:18 Specifications Do we really need this? 1:29:11 Topic #5 - Lab acoustics update 1:30:28 Crinacle's & chat's response to LMG's video 1:40:57 Priority for lab testing & hiring 1:42:34 Merch Messages #2 1:42:43 ARM processors, emulating X86 for gaming 1:43:43 Best way to handle a hot PC during the summer 1:44:47 Secure alternative for port-forwarding to NAS 1:46:44 Linus's remote hardware configuration 1:48:41 What happened to the $1 million computer series? 1:49:13 Screen protector creases on Linus's Fold 1:51:11 Unified doorbell 1:52:12 Matter smart home feature 1:52:40 Would Luke consider another mineral PC 1:54:42 eLeap OLED technology 1:55:34 Manufacturers moving to smart bulbs, cybersecurity 1:56:00 Aya Neo 2, AIR, Flip & Slide 1:57:06 Machining a solid block of acrylic 1:59:42 Linus & Luke on Steam Deck, comparing to Aya Neo 2:01:17 Recent books to read, Linus discusses reading 2:02:40 Removing the protector on Fold 3 2:04:55 Long-term hearing loss when sleeping with headphones 2:07:45 Linus's decision on the main TV & monitors 2:09:38 Test driving electric motorcycles, Linus's SV650S 2:13:27 Motivation behind switching from Hangouts to Teams 2:16:22 Outro

Intel® Arc™ is the world's first GPU with hardware-accelerated encoding for AV1, the next-gen and royalty-free video codec. To tell us more about the importance of AV1 and what it means for the future of video, we're joined by Matt Frost, the Chairman of the Board at the Alliance for Open Media, and Director of Product Management at Google. Notices & Disclaimers Intel technologies may require enabled hardware, software or service activation. No product or component can be absolutely secure. Your costs and results may vary. © Intel Corporation. Intel, the Intel logo, and other Intel marks are trademarks of Intel Corporation or its subsidiaries. Other names and brands may be claimed as the property of others.

Linux usage spikes in the latest Steam hardware survey, Microsoft 3D Movie Maker goes open-source, RDNA3 GPUs have AV1 encoding powers, Persona 4 Golden gets Steam Deck verified, and Epic puts Fortnite in a browser. 

2023 será el año de AV1 / Muere el creador del GIF / Caja negra avión estrellado en China / Okta sí fue hackeada / Google Play se abre a pagos externos / Australia presenta Fuerza Espacial / Tailandia prohíbe las criptomonedas

This week we talk about industry challenges with churn and retention and highlight some of the major problems when it comes to the methodology being used to compare services. We also discuss Netflix's recent price increase and the potential impact it could have on their subscriber growth. We also cover the recent sports licensing deals with the news that ViacomCBS secured the exclusive rights to stream English Premier League soccer; Sinclair announced a new distribution rights agreement with the NBA and we've read rumors of Apple talking to MLB. We also highlight new subscriber numbers from fuboTV, the growth of IMAX's revenue in 2021 and our take on the attendance numbers from the CES Show.Companies and services mentioned: Netflix, ViacomCBS, Paramount+, Discovery, Sinclair Broadcast Group, fuboTV, IMAX, Vimeo, Roku, NBA, Apple, MLB, V-Nova, Disney, Salesforce. Links to articles mentioned:Over 58% of OTT Services Surveyed Have “Limited” to “No” Insight Into The Main Reasons for Churnhttps://www.streamingmediablog.com/2022/01/churn-retention-challenges.htmlLCEVC must compete against all other standards, starting with AV1 which is a royalty-free codechttps://www.linkedin.com/feed/update/urn:li:activity:6887822698634870784/Questions or feedback? Contact us at dan@danrayburn.com

Nouar Hamze LinkedIn profile---------------------------------------------------Join our LinkedIn Group so that you can get the latest video insider news and participate in the discussion.Email thevideoinsiders@beamr.com to be a guest on the show.Learn more about Beamr

LINKS:Alex Liu LinkedIn profileNETINT AV1 Hardware Encoding Announcement---------------------------------------------------Join our LinkedIn Group so that you can get the latest video insider news and participate in the discussion.Email thevideoinsiders@beamr.com to be a guest on the show.Learn more about Beamr

Brian Alvarez LinkedIn profileVittorio Giovara Blog---------------------------------------------------Join our LinkedIn Group so that you can get the latest video insider news and participate in the discussion.Email thevideoinsiders@beamr.com to be a guest on the show.Learn more about Beamr

Pierre Seigneurbieux LinkedIn profileBlueJeans Website---------------------------------------------------Join our LinkedIn Group so that you can get the latest video insider news and participate in the discussion.Email thevideoinsiders@beamr.com to be a guest on the show.Learn more about Beamr

Thierry Fautier LinkedIn profile Harmonic websiteBen Mesander LinkedIn profile Wowza websiteWalid Hamri LinkedIn profile SeaChange websiteWade Wan LinkedIn profile Broadcom websiteOur previous panel on extending the life of H.264 is here---------------------------------------------------Join our LinkedIn Group so that you can get the latest video insider news and participate in the discussion.Email thevideoinsiders@beamr.com to be a guest on the show.Learn more about Beamr