Podcasts about digital rights management drm

François Daoust, W3C staff member and co-chair of the Web Developer Experience Community Group, discusses the origins of the W3C, the browser standardization process, and how it relates to other organizations like TC39, WHATWG, and IETF. This episode covers a lot of ground, including funding through memberships, royalty-free patent access for implementations, why implementations are built in parallel with the specifications, why requestVideoFrameCallback doesn't have a formal specification, balancing functionality with privacy, working group participants, and how certain organizations have more power. François explains why the W3C hasn't specified a video or audio codec, and discusses Media Source Extensions, Encrypted Media Extensions and Digital Rights Management (DRM), closed source content decryption modules such as Widevine and PlayReady, which ship with browsers, and informing developers about which features are available in browsers. Brought to you by IEEE Computer Society and IEEE Software magazine.

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

Send us a textCheck us out at:  https://www.cisspcybertraining.com/Get access to 360 FREE CISSP Questions:  https://www.cisspcybertraining.com/offers/dzHKVcDB/checkoutGet access to my FREE CISSP Self-Study Essentials Videos:  https://www.cisspcybertraining.com/offers/KzBKKouvDive into the multifaceted world of data security controls with Sean Gerber as he unpacks CISSP Domain 2.6. The episode opens with a fascinating glimpse into the creative ingenuity of technology users—a student who managed to hack a TI-84 calculator to access ChatGPT during exams. This real-world example perfectly illustrates why robust data security controls are more crucial than ever in our interconnected world.Sean meticulously breaks down the three fundamental data states—data at rest, data in transit, and data in use—providing clear explanations of the unique protection mechanisms each requires. You'll discover why data is rarely truly "at rest" unless completely powered off and disconnected, and why this understanding is vital for comprehensive protection strategies. The discussion extends to emerging technologies like homomorphic encryption, which promises to keep data encrypted throughout all states, though it's still evolving.The heart of effective data protection lies in classification and labeling, and Sean offers practical advice on implementing these systems. Starting small with clearly defined data sets, standardizing nomenclature, and utilizing visual cues like color-coding are just a few of the actionable strategies shared. You'll gain insights into Digital Rights Management (DRM), Data Loss Prevention (DLP), and Cloud Access Security Brokers (CASBs)—three critical components of a comprehensive data security framework.Perhaps most valuable is Sean's emphasis on understanding organizational risk tolerance. As he eloquently puts it, "If you don't know the risk for your company, find out somebody who does." This perspective shift from pure protection to risk-aligned security can transform how security professionals approach their role and communicate with leadership.Whether you're studying for the CISSP exam or looking to enhance your organization's data protection strategy, this episode delivers practical wisdom drawn from real-world experience. Visit CISSP Cyber Training for additional resources, and remember—understanding data security isn't just about passing an exam; it's about becoming a more effective guardian of your organization's most valuable assets.Support the showGain exclusive access to 360 FREE CISSP Practice Questions delivered directly to your inbox! Sign up at FreeCISSPQuestions.com and receive 30 expertly crafted practice questions every 15 days for the next 6 months—completely free! Don't miss this valuable opportunity to strengthen your CISSP exam preparation and boost your chances of certification success. Join now and start your journey toward CISSP mastery today!

Send us a textEver wondered about the real difference between a data leak and a data breach? Join me, Sean Gerber, on the latest episode of the CISSP Cyber Training Podcast as we unpack the nuances between these two critical cybersecurity concepts. Learn how data leaks often result from human mistakes like weak passwords, while data breaches involve deliberate cyber attacks. We'll walk through different types of sensitive data—including PII, financial information, PHI, and intellectual property—and emphasize the need for precise language to help cybersecurity leaders communicate more effectively and avoid unnecessary panic. Plus, get a sneak peek into a CISSP exam question focusing on the stringent security controls required for data in use.Choosing the right Data Loss Prevention (DLP) solution doesn't have to be a headache. In this episode, we tackle cost-effectiveness and real-world challenges that come with selecting DLP solutions. Hear about the compatibility hurdles of Digital Rights Management (DRM) solutions, including the struggles between Adobe and Microsoft's products. Discover how DLP and DRM technologies sometimes clash, and learn what to look for to ensure seamless integration. Don't miss these invaluable insights designed to sharpen your cybersecurity acumen and prep you for the CISSP exam.Gain access to 60 FREE CISSP Practice Questions each and every month for the next 6 months by going to FreeCISSPQuestions.com and sign-up to join the team for Free. That is 360 FREE questions to help you study and pass the CISSP Certification. Join Today!

Send us a textEver wondered how a TI-84 calculator can be transformed into a powerful tool for ChatGPT? Join me, Sean Gerber, on this thrilling episode of the CISSP Cyber Training Podcast as we uncover this fascinating tale and explore the evolving landscape of data security. We'll dissect the crucial elements of Domain 2.6 of the CISSP exam, from protecting data-at-rest to data-in-motion, and delve into the significance of Digital Rights Management (DRM) and Data Loss Prevention (DLP). This episode promises to enlighten you on the challenges and solutions of safeguarding data in today's tech-driven world.Next, we'll explore the meticulous process of establishing a robust labeling schema for data within an organization. Learn how to effectively implement physical and digital labels—such as unclassified, secret, top secret, and confidential—using color coding for easy identification. We'll stress the importance of consistent terminology, well-documented procedures, and controlled access to data classification changes. Discover how to tailor security controls to fit various organizational needs and the pivotal role of IT security leaders in guiding departments to enhance their security measures.Finally, we address the critical task of aligning IT security controls with an organization's risk tolerance and operational needs. Understand how focusing on critical assets can optimize data protection without spreading resources too thin. We'll highlight the importance of adhering to security frameworks like NIST, GDPR, or PCI DSS, and the role DRM and DLP play in preventing unauthorized data exfiltration. Plus, we'll introduce Cloud Access Security Brokers (CASBs) and discuss their crucial function in enforcing security policies between organizational networks and cloud service providers. This episode is packed with invaluable insights to prepare you for the CISSP exam and elevate your cybersecurity knowledge.Gain access to 60 FREE CISSP Practice Questions each and every month for the next 6 months by going to FreeCISSPQuestions.com and sign-up to join the team for Free. That is 360 FREE questions to help you study and pass the CISSP Certification. Join Today!

Sasha Mitchell is Head of Operations at Bel2. Imagine if Bitcoin could talk to other blockchains, make deals, execute contracts, and expand its influence without ever compromising its integrity. That's BeL2, the Bitcoin Elastos Layer 2 Protocol. Why you should listen BeL2 transforms EVM-compatible blockchains into Bitcoin Layer 2s, without bridging BTC. It utilizes a secure ZKP data feed, enhancing Bitcoin's utility from a store of value to a foundational layer for BTC-powered applications. BeL2 allows smart contracts to communicate with Bitcoin, utilizing a specialized proof and relayer mechanism. This allows services to connect into the Bitcoin network and its liquidity. ELA, is Elastos' Layer 2 coin merged-mined with Bitcoin since 2018 with over 50% of Bitcoin's miners security. It has a total supply of 28.22 million coins by 2105 and current circulation of 21.3 million. Within BeL2, ELA is essential, serving as collateral for Relayers, powering trust and stability. Stake ELA, earn BTC contributes to network security, empowering holders to shape Bitcoins smart economy. Elacity's Decentralised Digital Rights Management (dDRM) protocol eliminates license servers using blockchain technology and edge computing, delivering secure business models to Web3. Elacity dDRM transforms digital rights and asset management in Web3. It addresses key challenges in Digital Rights Management (DRM), such as packaging, transparency, and secure playback, through the use of blockchain and peer-to-peer (P2P) technologies. By offering a decentralised, scalable networking solution, Elacity enables a digital asset marketplace which features robust IP protection and scarce, tradable access, ownership and distribution rights. Elacity delivers decentralised business models, instant royalties, and inclusive economics to owners in Web3, automating contractual challenges, optimising resource sharing, and enabling equitable control and monetisation of digital assets through a democratised online Access Economy. Supporting links Bel2 Elastos Elacity Slaugherbots Andy on Twitter  Brave New Coin on Twitter Brave New Coin If you enjoyed the show please subscribe to the Crypto Conversation and give us a 5-star rating and a positive review in whatever podcast app you are using.  

Sponsor by ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠SEC Playground⁠ --- Support this podcast: https://podcasters.spotify.com/pod/show/chillchillsecurity/support

Capcom is seemingly at "war" with modders. The video game company is using a new DRM package to seemingly make modding much more difficult for games such as Street Fighter 6 and Resident Evil. As a result, gamers are downvoting affected games to oblivion on Steam. Is Capcom in the right, or are they going to give themselves a bigger PR black eye by cracking down on mods? ➡️ Tip Jar and Fan Support: http://ClownfishSupport.com ➡️ Official Merch Store: http://ShopClownfish.com ➡️ Official Website: http://ClownfishGaming.net Additional Context: Capcom, the video game giant known for hits like "Street Fighter" and "Resident Evil," has recently ignited a firestorm in the gaming community by implementing a new Digital Rights Management (DRM) software, Enigma Protector, in several of its PC titles. This move appears to be part of Capcom's broader strategy to combat modding, which they have previously expressed concerns about, particularly regarding mods that are deemed offensive or could damage the company's reputation. The controversy began when Capcom issued an unannounced update to the 2013 game "Resident Evil Revelations" on Steam. Gamers quickly discovered that this update included the Enigma Protector DRM, which is designed to prevent illegal copying, hacking, and modification of game files. However, this DRM implementation led to several issues, including frame rate drops, random crashes, and broken graphical options, negatively impacting the game's performance and playability​​. Although Capcom later retracted the update due to these problems, stating they would re-release it once the issue is resolved, the damage had already been done. This incident sparked a wave of backlash from the gaming community, with many gamers review bombing "Resident Evil Revelations" on Steam, resulting in a significant drop in the game's rating​​. Further investigation revealed that "Resident Evil Revelations" was not the only game affected. Other titles in Capcom's catalog, including "Capcom Arcade Stadium," "Capcom Arcade 2nd Stadium," "Mega Man Battle Network Legacy Collection," "Mega Man Zero/ZX Legacy Collection," "Resident Evil 5," "Street Fighter 30th Anniversary Collection," and "Strider (2014)," have also received updates that include the Enigma Protector DRM​​. This development has raised questions about Capcom's stance on modding. In October 2023, during Capcom's Open Conference Professional RE:2023, company programmer Taro Yahagi stated that "all mods are defined as cheats, except when they are officially supported," implying a strong anti-modding position. He mentioned that while many mods positively impact games, some can harm the company's reputation and be mistaken for legitimate game features​​. However, it's worth noting that there are differing opinions on the impact of the Enigma DRM on game performance and modding. A prominent Resident Evil modder, known as FluffyQuack, has stated that the claims about Enigma causing performance issues and blocking mods are "nonsense." FluffyQuack pointed out that Enigma has been used in other Capcom games, like "Resident Evil 5" and "Street Fighter 6," without reported performance issues or significant glitches. This modder believes that Capcom's use of DRM is more about combating piracy and cheating rather than specifically targeting modding​​. Capcom's recent actions regarding DRM implementation have sparked a heated debate in the gaming community. While the company aims to protect its intellectual property and maintain the integrity of its games, its approach has led to dissatisfaction among gamers and modders. This controversy highlights the delicate balance between protecting digital rights and preserving the gaming community's creative freedom. About Us: Clownfish Gaming is Video Game News and Commentary, Gaming Let's Plays, Animation, and more. We discuss the current video game industry and retro gaming and do gameplay videos on PC, Nintendo Switch, and PlayStation as well as

Un moment d'égarement, la chronique animée par Laurent Guérin, qui traite avec humour des échecs les plus retentissants de la tech.Cette chronique est extraite de l'épisode : Jean-Noël Barrot - Numérique en France : les chantiers 2024Laurent évoque l'échec des Digital Rights Management (DRM), la solution qui voulait en finir avec les téléchargement illégaux à l'ère de la musique digitalisée. ***** À PROPOS DE TRENCH TECH *****LE talkshow « Esprits Critiques pour Tech Ethique » Écoutez-nous sur toutes les plateformes de podcast

In this final bonus Walled Culture podcast episode - recorded mid-2022 and kept under wraps as a special 1st anniversary episode, we welcome Fred von Lohmann, former Electronic Frontier Foundation (EFF) and Google copyright counsel. Our conversation starts with recalling how he got intrigued by copyright, crediting John Perry Barlow, and explaining how he was at the right juncture to become a tech enthusiast. Fred talks about his role at EFF during what was a unique time from a copyright perspective, characterised by pivotal court cases in the 2000s. He looks back at the impact and effects of the rights holders' battle against peer-to-peer (P2P) technology. Their fierce resistance against anything related to P2P, in his view, crippled the potential transition towards a decentralised Internet back then. He did see one silver lining from the aftermath: the P2P revolution opened music fans' eyes to what could be, pressuring the music industry to start meeting consumers' demand. Fred highlights the Digital Millennium Copyright Act's (DMCA) (invisible) role in shaping our daily lives. On the one hand, the DMCA gave a legal justification to rights holders' control over technology beyond the copyright realm by providing legal protections for Digital Rights Management (DRM). This has impacted various types of content, be it (now old-school) DVDs, eBooks or games. On the other, the DMCA boosted the Internet's success through the safe harbour regime, offering a shelter from the ‘open sea' with hurricanes of lawsuits. The latter troubled rights holders, leading Fred to discuss the emergence of (imperfect) copyright filters. In this context, he touches upon Google's Content ID, rights holder abuses, and the EU Copyright Directive's questionable filtering obligations. He puts forward a crucial, yet unanswered, question in this debate: “how do you build filters that are fair to users and also don't constrict creativity too much?” Finally, Fred briefly shares his insights on how copyright intersects with competition and innovation, especially in the context of software interfaces. In his closing remarks, he echoes some of Cory Doctorow's wisdom, as he emphasises the need to think about copyright's impact on fans and innovators.

Unity, the game engine wizard behind masterpieces like Rust and Pokémon Go, has dropped a bombshell on the developer community. On September 12, Unity unveiled the Runtime Fee, sending shockwaves through the indie developer universe and sparking a myriad of questions. Starting January 1, 2024, Unity will impose a fee based on the number of game installations and its revenue. For Unity Personal and Unity Plus, the thresholds are set at $200,000 annual revenue and 200,000 installs. Meanwhile, games developed on Unity Pro and Unity Enterprise must garner $1 million and hit 1 million installs before the fees apply. The structure is as follows: Unity Personal and Plus: $0.20 per additional install. Unity Pro: $0.02 to $0.15 per additional install. Unity Enterprise: $0.01 to $0.125 per additional install. Developers were left scratching their heads, with many worried about potential financial implications, especially for free-to-play and charity games. Garry Newman of Rust fame voiced concerns, fearing a monthly payment of $200,000 to Unity. The crux of his worry? Trusting Unity's tracking and the audacity of the unilateral fee imposition. https://x.com/garrynewman/status/1701584142570336701?s=20 Indie developers find themselves in a bind. Many, midway into their game development journey, now fear the uncertainty Unity's decision has brought. The concern isn't just about the added costs but the intricacies of measuring installs, potential privacy concerns, and possible impositions of Digital Rights Management (DRM) to track installs. Brandon Sheffield, Creative Director at Necrosoft Games, minced no words in his disdain for Unity's decision, advising developers to steer clear of the platform. https://x.com/necrosofty/status/1701294283331084733?s=20 Unity has been on a roll with changes lately. The company is set to phase out Unity Plus subscriptions, and members will be shifted to its Pro subscription next month. While Unity's innovation in AI integration, like Unity Muse and Unity Sentis, has been lauded, the new Runtime Fee has left many developers wary. The announcement has, predictably, had financial implications for Unity. Their market shares plummeted soon after the revelation. Whether Unity stands firm on its decision or bends to developer feedback is yet to be seen. In a swift response to the negative backlash, Unity attempted to clear the air with an FAQ post. The definition of an “install” was clarified, as was the company's decision to charge for reinstalls. While Unity reassures charity games and bundles will remain unaffected, developers remain skeptical. The potential aftermath of this decision, including ‘revenue bombing' by antagonized user groups, is yet to fully unfold. Talks of a class-action lawsuit against Unity are already in the works, painting a grim picture for the game engine giant. What do you think about these changes and their potential impact on gaming? What is the New Fee About?The Developer ReactionThe Potential AftermathUnity's Recent MovesUnity's Counter

In season 3 episode one of The IoT Podcast, host Tom White speaks with Intertrust's Chris Kalima and Julian Durand to discover how to create trust throughout the IoT data supply chain and the key to achieving seamless interoperability in zero-trust environments, even at scale. Sit back, relax, tune in and be the first to discover... (00:00) The IoT Podcast Intro (00:28) Shout Out to our sponsor Akenza.io (00:43) Intro to Chris and Julian (06:56) What does Intertrust do? (09:09) Interoperability in the EV market (13:39) EIPGRID partnership enabling trusted data for scale organisations (17:09) Why the old ways of securing networks does not work (20:02) Akenza.io 30-day free trial! (21:08) How can we address interoperability issues at scale? (27:43) What effect will the EU Data act have on businesses? (31:00) The evolution of data collaboration and data sharing (39:44) Question from the audience Thank you to today's episode sponsor Akenza.io, sign up for a 30-day free trial of their self-service platform: https://auth.akenza.io/register?utm_medium=referral&utm_source=5vmedia&utm_campaign=theiotpodcast ABOUT THE GUESTS Julian Durand is the VP of Product Management & CISO at Intertrust. He is an accomplished product owner, team leader, and creative inventor with more than 25 years of success in bringing breakthrough products to market at massive scale. He is a named inventor in Digital Rights Management (DRM), Internet of Things (IoT) and virtual SIM technologies, was the technical lead for the first music phone and pioneered vSIM and IoT businesses at Qualcomm. Connect with Julian: https://www.linkedin.com/in/juliandurand/ Chris Kalima is the VP of Product Management. He is an experienced product leader and entrepreneur with a demonstrated history of applying his passion for technology and design to web-based products and applications. Connect with Chris: https://www.linkedin.com/in/ckalima/ ABOUT INTERTRUST Intertrust is a Silicon Valley-based software company specializing in trusted computing products and services. The company was founded in 1990 by the entrepreneur Victor Shear with the vision to enable trusted transactions across open networks. To date, Intertrust has scaled to a prominent enterprise in trusted distributed computing, building on a legacy of invention, and fundamental contributions in the areas of computer security and digital trust. Find out more about Intertrust: https://www.intertrust.com/ SUBSCRIBE TO THE IOT PODCAST: https://linktr.ee/theiotpodcast Sign Up for exclusive email updates: https://theiotpodcast.com/ Contact us to become a guest/partner: https://theiotpodcast.com/contact/ Connect with host Tom White: https://www.linkedin.com/in/tom5values/  

Glyn Moody has been writing about copyright, digital rights, and the Internet for 30 years. He is the editor of the Walled Culture project and author of Walled Culture - the Book (freely available as ebook). He previously wrote ‘Rebel Code: Linux and the Open Source Revolution'. He explains how the Walled Culture project is a reflection on digital copyright going wrong, and how copyright and the Internet have shown to be fundamentally incompatible. Glyn highlights how there's no escaping copyright in an online world. He shares some copyright absurdities, with big content fighting the visually impaired and initiatives like Project Gutenberg and Google Books. He talks about how Big Content put on shackles on libraries thanks to Digital Rights Management (DRM), and reflects on the injustice of the Big Publishers' suing the Internet Archive. Glyn points out how Big Academic Publishers hijacked the shift towards open access to benefit their bottom line, while pointing out that diamond open access shows that we can move away from the academic publishing business. He recalls how Big Record Labels went on a rampage, suing grandmothers and children, neglecting the opportunity to give consumers what they wanted. Glyn describes Big Content's push for copyright enforcement, from the French three strikes mechanism to the SOPA and ACTA battles, while emphasising how copyright laws got skewed towards Big Content. He talks about the failures surrounding the EU Copyright Directive and the looming dangers of upload filters. He further highlights how copyright no longer promotes culture but harms it, and how it's about protecting Big Content, not creators. Glyn concludes by reflecting on a possible way forward: building on creators' true fans.

This week Dave talks with Mike Bursell (https://dgshow.org/guests/mbursell) and Nathaniel McCallum (https://dgshow.org/guests/nmccallum) about confidential computing! Check out Mike on D&G 201 (https://dgshow.org/201) from 2020! Enarx (https://enarx.dev/) Red Hat (https://www.redhat.com/en) Profian (https://www.profian.com/) McCallum-Relyea exchange (https://www.admin-magazine.com/Archive/2018/43/Automatic-data-encryption-and-decryption-with-Clevis-and-Tang) Trusted computing (https://en.wikipedia.org/wiki/Trusted_Computing) Confidential computing – the new HTTPS? (https://aliceevebob.com/2019/12/03/confidential-computing-the-new-https/) Confidential Computing Consortium (https://confidentialcomputing.io/) Trusted Platform Module (TPM) (https://en.wikipedia.org/wiki/Trusted_Platform_Module) Trusted Execution Environment (TEE) (https://en.wikipedia.org/wiki/Trusted_execution_environment) Digital Rights Management (DRM) (https://en.wikipedia.org/wiki/Digital_rights_management) Intel SGX (https://www.intel.com/content/www/us/en/architecture-and-technology/software-guard-extensions.html) AMD SEV (https://developer.amd.com/sev/) AWS Nitro System (https://aws.amazon.com/ec2/nitro/) What is attestation for Confidential Computing? (https://aliceevebob.com/2022/06/14/what-is-attestation-for-confidential-computing/) WebAssembly (https://webassembly.org/) Bytecode Alliance (https://bytecodealliance.org/) Drawbridge (https://github.com/profianinc/drawbridge) Keep (https://github.com/enarx/enarx-keepldr) Secure multi-party computation (https://en.wikipedia.org/wiki/Secure_multi-party_computation) Privacy-Enhancing Technologies (PET) (https://en.wikipedia.org/wiki/Privacy-enhancing_technologies) Homomorphic encryption (https://en.wikipedia.org/wiki/Homomorphic_encryption) Functional equivalence and formal equivalence checking (https://en.wikipedia.org/wiki/Formal_equivalence_checking) What is a Linux Container? (https://www.redhat.com/en/topics/containers/whats-a-linux-container) Functions as a Service (https://en.wikipedia.org/wiki/Function_as_a_service) UEFI (https://en.wikipedia.org/wiki/UEFI) Reproducible builds (https://en.wikipedia.org/wiki/Reproducible_builds) Trusted Computing Base (TCB) (https://en.wikipedia.org/wiki/Trusted_computing_base) Confidential Computing: try it now, for free (https://blog.profian.com/confidential-computing-now-for-free/) FedRAMP (https://www.fedramp.gov/) Bell–LaPadula model (https://en.wikipedia.org/wiki/Bell%E2%80%93LaPadula_model) NVIDIA Confidential Computing (https://www.nvidia.com/en-us/data-center/solutions/confidential-computing/) U.S. and U.K. Launch Innovation Prize Challenges in Privacy-Enhancing Technologies to Tackle Financial Crime and Public Health Emergencies (https://www.whitehouse.gov/ostp/news-updates/2022/07/20/u-s-and-u-k-launch-innovation-prize-challenges-in-privacy-enhancing-technologies-to-tackle-financial-crime-and-public-health-emergencies/) Advancing a Vision for Privacy-Enhancing Technologies (https://www.whitehouse.gov/ostp/news-updates/2022/06/28/advancing-a-vision-for-privacy-enhancing-technologies/) Accelerating the adoption and development of privacy-enhancing technologies (PETs) (https://petsprizechallenges.com/) Trust in Computer Systems and the Cloud (https://www.wiley.com/en-us/Trust+in+Computer+Systems+and+the+Cloud-p-9781119692324) We Give Thanks * Mike Bursell (https://dgshow.org/guests/mbursell) and Nathaniel McCallum (https://dgshow.org/guests/nmccallum) for joining us on the show! * Jen Wike Huger (https://twitter.com/JenWike) for connecting the dots! Special Guests: Mike Bursell and Nathaniel McCallum.

About Andrew Morton and Bloom Health Partners: Andrew Morton Leader with proven track record in Building Teams, Running Operations, Sales, Business Development and Marketing. Global business experience in the tech industry deploying software, SaaS and Hardware at large organizations. I've worked in several segments including LTE, 5G, WiFi, IPTV, CATV, over-the-top (OTT) video, video content, conditional access (CA), Digital Rights Management (DRM), telecom networks, enterprise networks, software management systems, datacenters, digital media, new media, social media, OSS/BSS, and business intelligence (BI). Industry relationships that span service providers, content providers and the business community. Proven track record building businesses, M&A and managing teams in North America, South America, Asia and Europe. Specialties: Complex Sales, Sales Management, Business Development, Channels and Marketing. Bloom Health Partners Even a global pandemic should not slow, delay, or stop production. With the right knowledge and resources, businesses of all sizes can stay safe and operational even through the wildest times. At Bloom, we are transforming healthcare with actionable solutions and meaningful movement. We are your partner. Bloom operates as a single on-the-ground point of contact throughout the entire journey. Our diverse team of doctors, scientists, and logistics experts stay informed and act innovatively to keep your business operational and competitive. Our business operates on your hours.​ When you have a question, we're here to answer it. You have our number. You have one point of contact. And you are fully empowered to get the service you need, when you need it. No hours are off-hours with Bloom. Things change. We adapt. In today's uncertain times, Bloom remains agile and flexible to ever-shifting factors in and outside your organization. We provide a smooth and enjoyable experience through efficiency, humanity and exceptional customer care. We are customer, lab, and technology centered. Bloom provides complete, end-to-end health solutions, including testing, vaccine tracking technology and best-in-class lab capabilities through a nationwide network of highly complex laboratories and a force of qualified healthcare workers.

Digital Rights Management (DRM) is a software or hardware mechanism that restricts what you can do with your digital media. It may limit a movie from playing without your authenticated credentials, or stop a Nintendo cartridge from working in a third-party console. While DRM was created to limit piracy, it also may limit what you can do with your purchases. In this episode we discuss DRM from legal, technological, and consumer perspectives. Show Notes Episode 34: Video Game Distribution and GameStop Episode 26: Napster Episode 17: What is Encryption? Follow us on Twitter @KopecExplains. Theme “Place on Fire” Copyright 2019 Creo, CC BY 4.0 Find out more at http://kopec.live

The second part of our conversation about eGlass with Ji Shen, the CEO of HoverCam, Dr. Matt Anderson, the President and CEO of Learning Glass Solutions and a physics professor at San Diego State University, and Bailey Pierson, the Marketing Director for HoverCam shifted to the experiences they have had using it, and some of the more technical details. eGlass could be the future of live education because it preserves the best of the white board, presentation program, and instructor/student interaction. We also discussed some possible business use cases for both in-person and virtual interactions.  This edition of MacVoices is sponsored by Smile, the makers of world-class software like PDFpen, PDFpen Pro, and TextExpander. Find out more at TextExpander.com/podcast and SmileSoftware.com/podcast. Show Notes: Guests: Ji Shen is founder and CEO of Pathway Innovations and Technologies, Inc., doing business as HoverCam, a leader in educational technology field. HoverCam was founded in 2009 by Shen and is 100% focused on developing instructional audio and video technologies for educators. Since its inception, HoverCam has developed a series of innovative products including industry firsts: USB based document cameras, Android based document cameras, all-in-one digital teaching station, and now eGlass, an embodied teaching transparent glassboard. He has been an entrepreneur in the EdTech field for 16 years.  Previously, he founded iClassmate Learning Management System company.  Prior to iClassmate, Mr. Shen was co-founder of Aegisoft, a leading developer of Digital Rights Management (DRM) technology. Aegisoft was acquired by streaming media leader, RealNetworks, in 2001.  Aegisoft’s DRM technology was used in over 200 million RealPlayers.  Shen has also worked at Arthur D. Little Inc., Ernst & Young LLP, and American Management System (AMS).  Ji received a Ph.D. ABD (all but dissertation) in Computational Statistics, and a M.S. of Applied Statistics and Operations Research from George Mason University. He has received B.S. in Metallurgy from Harbin Institute of Technology in China. Dr. Matt Anderson has nearly three decades of experience in physics research and education. As a professor of physics for the last 20 years at San Diego State University, he has led a highly productive research group, garnering multiple research grants and publishing 29 papers and 5 patents. He has taught a multitude of course offerings, and is consistently one of the top-rated professors. He recently won the Senate Distinguished Professor award from the university (given annually to one professor on campus) and was twice nominated for the prestigious Robert Foster Cherry Award for Teaching Excellence administered by Baylor University (the nation’s highest teaching award). His physics education channel on YouTube has garnered over 8 million views and over 90k subscribers, and he has given invited talks nationally and internationally. Dr. Anderson holds a B.S. in Physics from the University of California at San Diego, a Ph.D. in Physics from the University of Oregon, a postdoctoral fellowship from the University of Rochester, and was a visiting faculty member at the University of Oxford. He is a cofounder of Learning Glass Solutions and serves as the CEO and President for the company. He is married with three kids and a dog, likes to surf, play guitar, hike, and eat fish tacos. Bayley Pierson is the Marketing Director of HoverCam, a technology company dedicated to transforming classrooms into the advanced digital learning spaces of the future. A philanthropist with an interest in embodied learning, Pierson is dedicated to developing collaboration solutions that assist educators in better preparing students for the future while relieving some of the biggest challenges that impede success in the present.   Support:      Become a MacVoices Patron on Patreon     http://patreon.com/macvoices      Enjoy this episode? Make a one-time donation with PayPal Connect:      Web:     http://macvoices.com      Twitter:     http://www.twitter.com/chuckjoiner     http://www.twitter.com/macvoices      Facebook:     http://www.facebook.com/chuck.joiner      MacVoices Page on Facebook:     http://www.facebook.com/macvoices/      MacVoices Group on Facebook:     http://www.facebook.com/groups/macvoice      LinkedIn:     https://www.linkedin.com/in/chuckjoiner/      Instagram:     https://www.instagram.com/chuckjoiner/ Subscribe:      Audio in iTunes     Video in iTunes      Subscribe manually via iTunes or any podcatcher:      Audio: http://www.macvoices.com/rss/macvoicesrss      Video: http://www.macvoices.com/rss/macvoicesvideorss

The second part of our conversation about eGlass with Ji Shen, the CEO of HoverCam, Dr. Matt Anderson, the President and CEO of Learning Glass Solutions and a physics professor at San Diego State University, and Bailey Pierson, the Marketing Director for HoverCam shifted to the experiences they have had using it, and some of the more technical details. eGlass could be the future of live education because it preserves the best of the white board, presentation program, and instructor/student interaction. We also discussed some possible business use cases for both in-person and virtual interactions.  This edition of MacVoices is sponsored by Smile, the makers of world-class software like PDFpen, PDFpen Pro, and TextExpander. Find out more at TextExpander.com/podcast and SmileSoftware.com/podcast. Show Notes: Guests: Ji Shen is founder and CEO of Pathway Innovations and Technologies, Inc., doing business as HoverCam, a leader in educational technology field. HoverCam was founded in 2009 by Shen and is 100% focused on developing instructional audio and video technologies for educators. Since its inception, HoverCam has developed a series of innovative products including industry firsts: USB based document cameras, Android based document cameras, all-in-one digital teaching station, and now eGlass, an embodied teaching transparent glassboard. He has been an entrepreneur in the EdTech field for 16 years.  Previously, he founded iClassmate Learning Management System company.  Prior to iClassmate, Mr. Shen was co-founder of Aegisoft, a leading developer of Digital Rights Management (DRM) technology. Aegisoft was acquired by streaming media leader, RealNetworks, in 2001.  Aegisoft’s DRM technology was used in over 200 million RealPlayers.  Shen has also worked at Arthur D. Little Inc., Ernst & Young LLP, and American Management System (AMS).  Ji received a Ph.D. ABD (all but dissertation) in Computational Statistics, and a M.S. of Applied Statistics and Operations Research from George Mason University. He has received B.S. in Metallurgy from Harbin Institute of Technology in China. Dr. Matt Anderson has nearly three decades of experience in physics research and education. As a professor of physics for the last 20 years at San Diego State University, he has led a highly productive research group, garnering multiple research grants and publishing 29 papers and 5 patents. He has taught a multitude of course offerings, and is consistently one of the top-rated professors. He recently won the Senate Distinguished Professor award from the university (given annually to one professor on campus) and was twice nominated for the prestigious Robert Foster Cherry Award for Teaching Excellence administered by Baylor University (the nation’s highest teaching award). His physics education channel on YouTube has garnered over 8 million views and over 90k subscribers, and he has given invited talks nationally and internationally. Dr. Anderson holds a B.S. in Physics from the University of California at San Diego, a Ph.D. in Physics from the University of Oregon, a postdoctoral fellowship from the University of Rochester, and was a visiting faculty member at the University of Oxford. He is a cofounder of Learning Glass Solutions and serves as the CEO and President for the company. He is married with three kids and a dog, likes to surf, play guitar, hike, and eat fish tacos. Bayley Pierson is the Marketing Director of HoverCam, a technology company dedicated to transforming classrooms into the advanced digital learning spaces of the future. A philanthropist with an interest in embodied learning, Pierson is dedicated to developing collaboration solutions that assist educators in better preparing students for the future while relieving some of the biggest challenges that impede success in the present.   Support:      Become a MacVoices Patron on Patreon     http://patreon.com/macvoices      Enjoy this episode? Make a one-time donation with PayPal Connect:      Web:     http://macvoices.com      Twitter:     http://www.twitter.com/chuckjoiner     http://www.twitter.com/macvoices      Facebook:     http://www.facebook.com/chuck.joiner      MacVoices Page on Facebook:     http://www.facebook.com/macvoices/      MacVoices Group on Facebook:     http://www.facebook.com/groups/macvoice      LinkedIn:     https://www.linkedin.com/in/chuckjoiner/      Instagram:     https://www.instagram.com/chuckjoiner/ Subscribe:      Audio in iTunes     Video in iTunes      Subscribe manually via iTunes or any podcatcher:      Audio: http://www.macvoices.com/rss/macvoicesrss      Video: http://www.macvoices.com/rss/macvoicesvideorss

The second part of our conversation about eGlass with Ji Shen, the CEO of HoverCam, Dr. Matt Anderson, the President and CEO of Learning Glass Solutions and a physics professor at San Diego State University, and Bailey Pierson, the Marketing Director for HoverCam shifted to the experiences they have had using it, and some of the more technical details. eGlass could be the future of live education because it preserves the best of the white board, presentation program, and instructor/student interaction. We also discussed some possible business use cases for both in-person and virtual interactions.  This edition of MacVoices is sponsored by Smile, the makers of world-class software like PDFpen, PDFpen Pro, and TextExpander. Find out more at TextExpander.com/podcast and SmileSoftware.com/podcast. Show Notes: Guests: Ji Shen is founder and CEO of Pathway Innovations and Technologies, Inc., doing business as HoverCam, a leader in educational technology field. HoverCam was founded in 2009 by Shen and is 100% focused on developing instructional audio and video technologies for educators. Since its inception, HoverCam has developed a series of innovative products including industry firsts: USB based document cameras, Android based document cameras, all-in-one digital teaching station, and now eGlass, an embodied teaching transparent glassboard. He has been an entrepreneur in the EdTech field for 16 years.  Previously, he founded iClassmate Learning Management System company.  Prior to iClassmate, Mr. Shen was co-founder of Aegisoft, a leading developer of Digital Rights Management (DRM) technology. Aegisoft was acquired by streaming media leader, RealNetworks, in 2001.  Aegisoft’s DRM technology was used in over 200 million RealPlayers.  Shen has also worked at Arthur D. Little Inc., Ernst & Young LLP, and American Management System (AMS).  Ji received a Ph.D. ABD (all but dissertation) in Computational Statistics, and a M.S. of Applied Statistics and Operations Research from George Mason University. He has received B.S. in Metallurgy from Harbin Institute of Technology in China. Dr. Matt Anderson has nearly three decades of experience in physics research and education. As a professor of physics for the last 20 years at San Diego State University, he has led a highly productive research group, garnering multiple research grants and publishing 29 papers and 5 patents. He has taught a multitude of course offerings, and is consistently one of the top-rated professors. He recently won the Senate Distinguished Professor award from the university (given annually to one professor on campus) and was twice nominated for the prestigious Robert Foster Cherry Award for Teaching Excellence administered by Baylor University (the nation’s highest teaching award). His physics education channel on YouTube has garnered over 8 million views and over 90k subscribers, and he has given invited talks nationally and internationally. Dr. Anderson holds a B.S. in Physics from the University of California at San Diego, a Ph.D. in Physics from the University of Oregon, a postdoctoral fellowship from the University of Rochester, and was a visiting faculty member at the University of Oxford. He is a cofounder of Learning Glass Solutions and serves as the CEO and President for the company. He is married with three kids and a dog, likes to surf, play guitar, hike, and eat fish tacos. Bayley Pierson is the Marketing Director of HoverCam, a technology company dedicated to transforming classrooms into the advanced digital learning spaces of the future. A philanthropist with an interest in embodied learning, Pierson is dedicated to developing collaboration solutions that assist educators in better preparing students for the future while relieving some of the biggest challenges that impede success in the present.   Support:      Become a MacVoices Patron on Patreon     http://patreon.com/macvoices      Enjoy this episode? Make a one-time donation with PayPal Connect:      Web:     http://macvoices.com      Twitter:     http://www.twitter.com/chuckjoiner     http://www.twitter.com/macvoices      Facebook:     http://www.facebook.com/chuck.joiner      MacVoices Page on Facebook:     http://www.facebook.com/macvoices/      MacVoices Group on Facebook:     http://www.facebook.com/groups/macvoice      LinkedIn:     https://www.linkedin.com/in/chuckjoiner/      Instagram:     https://www.instagram.com/chuckjoiner/ Subscribe:      Audio in iTunes     Video in iTunes      Subscribe manually via iTunes or any podcatcher:      Audio: http://www.macvoices.com/rss/macvoicesrss      Video: http://www.macvoices.com/rss/macvoicesvideorss

The creators of eGlass, a new tool that enhances and improves the teaching experience, join us to not only demo the product, but also to discuss how it changes the teaching and presentation experience into something much more personal for both online and in-person situations. Ji Shen, the CEO of HoverCam, Dr. Matt Anderson, the President and CEO of Learning Glass Solutions and a physics professor at San Diego State University, and Bailey Pierson, the Marketing Director for HoverCam, start off the first part of our conversation by explaining the genesis of eGlass and their partnership, and demonstrating exactly how it transforms the teaching experience. (Part 1) This edition of MacVoices is sponsored by Smile, the makers of world-class software like PDFpen, PDFpen Pro, and TextExpander. Find out more at TextExpander.com/podcast and SmileSoftware.com/podcast. Show Notes: Guests: Ji Shen is founder and CEO of Pathway Innovations and Technologies, Inc., doing business as HoverCam, a leader in educational technology field. HoverCam was founded in 2009 by Shen and is 100% focused on developing instructional audio and video technologies for educators. Since its inception, HoverCam has developed a series of innovative products including industry firsts: USB based document cameras, Android based document cameras, all-in-one digital teaching station, and now eGlass, an embodied teaching transparent glassboard. He has been an entrepreneur in the EdTech field for 16 years.  Previously, he founded iClassmate Learning Management System company.  Prior to iClassmate, Mr. Shen was co-founder of Aegisoft, a leading developer of Digital Rights Management (DRM) technology. Aegisoft was acquired by streaming media leader, RealNetworks, in 2001.  Aegisoft’s DRM technology was used in over 200 million RealPlayers.  Shen has also worked at Arthur D. Little Inc., Ernst & Young LLP, and American Management System (AMS).  Ji received a Ph.D. ABD (all but dissertation) in Computational Statistics, and a M.S. of Applied Statistics and Operations Research from George Mason University. He has received B.S. in Metallurgy from Harbin Institute of Technology in China. Dr. Matt Anderson has nearly three decades of experience in physics research and education. As a professor of physics for the last 20 years at San Diego State University, he has led a highly productive research group, garnering multiple research grants and publishing 29 papers and 5 patents. He has taught a multitude of course offerings, and is consistently one of the top-rated professors. He recently won the Senate Distinguished Professor award from the university (given annually to one professor on campus) and was twice nominated for the prestigious Robert Foster Cherry Award for Teaching Excellence administered by Baylor University (the nation’s highest teaching award). His physics education channel on YouTube has garnered over 8 million views and over 90k subscribers, and he has given invited talks nationally and internationally. Dr. Anderson holds a B.S. in Physics from the University of California at San Diego, a Ph.D. in Physics from the University of Oregon, a postdoctoral fellowship from the University of Rochester, and was a visiting faculty member at the University of Oxford. He is a cofounder of Learning Glass Solutions and serves as the CEO and President for the company. He is married with three kids and a dog, likes to surf, play guitar, hike, and eat fish tacos. Bayley Pierson is the Marketing Director of HoverCam, a technology company dedicated to transforming classrooms into the advanced digital learning spaces of the future. A philanthropist with an interest in embodied learning, Pierson is dedicated to developing collaboration solutions that assist educators in better preparing students for the future while relieving some of the biggest challenges that impede success in the present.   Support:      Become a MacVoices Patron on Patreon     http://patreon.com/macvoices      Enjoy this episode? Make a one-time donation with PayPal Connect:      Web:     http://macvoices.com      Twitter:     http://www.twitter.com/chuckjoiner     http://www.twitter.com/macvoices      Facebook:     http://www.facebook.com/chuck.joiner      MacVoices Page on Facebook:     http://www.facebook.com/macvoices/      MacVoices Group on Facebook:     http://www.facebook.com/groups/macvoice      LinkedIn:     https://www.linkedin.com/in/chuckjoiner/      Instagram:     https://www.instagram.com/chuckjoiner/ Subscribe:      Audio in iTunes     Video in iTunes      Subscribe manually via iTunes or any podcatcher:      Audio: http://www.macvoices.com/rss/macvoicesrss      Video: http://www.macvoices.com/rss/macvoicesvideorss

The creators of eGlass, a new tool that enhances and improves the teaching experience, join us to not only demo the product, but also to discuss how it changes the teaching and presentation experience into something much more personal for both online and in-person situations. Ji Shen, the CEO of HoverCam, Dr. Matt Anderson, the President and CEO of Learning Glass Solutions and a physics professor at San Diego State University, and Bailey Pierson, the Marketing Director for HoverCam, start off the first part of our conversation by explaining the genesis of eGlass and their partnership, and demonstrating exactly how it transforms the teaching experience. (Part 1) This edition of MacVoices is sponsored by Smile, the makers of world-class software like PDFpen, PDFpen Pro, and TextExpander. Find out more at TextExpander.com/podcast and SmileSoftware.com/podcast. Show Notes: Guests: Ji Shen is founder and CEO of Pathway Innovations and Technologies, Inc., doing business as HoverCam, a leader in educational technology field. HoverCam was founded in 2009 by Shen and is 100% focused on developing instructional audio and video technologies for educators. Since its inception, HoverCam has developed a series of innovative products including industry firsts: USB based document cameras, Android based document cameras, all-in-one digital teaching station, and now eGlass, an embodied teaching transparent glassboard. He has been an entrepreneur in the EdTech field for 16 years.  Previously, he founded iClassmate Learning Management System company.  Prior to iClassmate, Mr. Shen was co-founder of Aegisoft, a leading developer of Digital Rights Management (DRM) technology. Aegisoft was acquired by streaming media leader, RealNetworks, in 2001.  Aegisoft’s DRM technology was used in over 200 million RealPlayers.  Shen has also worked at Arthur D. Little Inc., Ernst & Young LLP, and American Management System (AMS).  Ji received a Ph.D. ABD (all but dissertation) in Computational Statistics, and a M.S. of Applied Statistics and Operations Research from George Mason University. He has received B.S. in Metallurgy from Harbin Institute of Technology in China. Dr. Matt Anderson has nearly three decades of experience in physics research and education. As a professor of physics for the last 20 years at San Diego State University, he has led a highly productive research group, garnering multiple research grants and publishing 29 papers and 5 patents. He has taught a multitude of course offerings, and is consistently one of the top-rated professors. He recently won the Senate Distinguished Professor award from the university (given annually to one professor on campus) and was twice nominated for the prestigious Robert Foster Cherry Award for Teaching Excellence administered by Baylor University (the nation’s highest teaching award). His physics education channel on YouTube has garnered over 8 million views and over 90k subscribers, and he has given invited talks nationally and internationally. Dr. Anderson holds a B.S. in Physics from the University of California at San Diego, a Ph.D. in Physics from the University of Oregon, a postdoctoral fellowship from the University of Rochester, and was a visiting faculty member at the University of Oxford. He is a cofounder of Learning Glass Solutions and serves as the CEO and President for the company. He is married with three kids and a dog, likes to surf, play guitar, hike, and eat fish tacos. Bayley Pierson is the Marketing Director of HoverCam, a technology company dedicated to transforming classrooms into the advanced digital learning spaces of the future. A philanthropist with an interest in embodied learning, Pierson is dedicated to developing collaboration solutions that assist educators in better preparing students for the future while relieving some of the biggest challenges that impede success in the present.   Support:      Become a MacVoices Patron on Patreon     http://patreon.com/macvoices      Enjoy this episode? Make a one-time donation with PayPal Connect:      Web:     http://macvoices.com      Twitter:     http://www.twitter.com/chuckjoiner     http://www.twitter.com/macvoices      Facebook:     http://www.facebook.com/chuck.joiner      MacVoices Page on Facebook:     http://www.facebook.com/macvoices/      MacVoices Group on Facebook:     http://www.facebook.com/groups/macvoice      LinkedIn:     https://www.linkedin.com/in/chuckjoiner/      Instagram:     https://www.instagram.com/chuckjoiner/ Subscribe:      Audio in iTunes     Video in iTunes      Subscribe manually via iTunes or any podcatcher:      Audio: http://www.macvoices.com/rss/macvoicesrss      Video: http://www.macvoices.com/rss/macvoicesvideorss

The creators of eGlass, a new tool that enhances and improves the teaching experience, join us to not only demo the product, but also to discuss how it changes the teaching and presentation experience into something much more personal for both online and in-person situations. Ji Shen, the CEO of HoverCam, Dr. Matt Anderson, the President and CEO of Learning Glass Solutions and a physics professor at San Diego State University, and Bailey Pierson, the Marketing Director for HoverCam, start off the first part of our conversation by explaining the genesis of eGlass and their partnership, and demonstrating exactly how it transforms the teaching experience. (Part 1) This edition of MacVoices is sponsored by Smile, the makers of world-class software like PDFpen, PDFpen Pro, and TextExpander. Find out more at TextExpander.com/podcast and SmileSoftware.com/podcast. Show Notes: Guests: Ji Shen is founder and CEO of Pathway Innovations and Technologies, Inc., doing business as HoverCam, a leader in educational technology field. HoverCam was founded in 2009 by Shen and is 100% focused on developing instructional audio and video technologies for educators. Since its inception, HoverCam has developed a series of innovative products including industry firsts: USB based document cameras, Android based document cameras, all-in-one digital teaching station, and now eGlass, an embodied teaching transparent glassboard. He has been an entrepreneur in the EdTech field for 16 years.  Previously, he founded iClassmate Learning Management System company.  Prior to iClassmate, Mr. Shen was co-founder of Aegisoft, a leading developer of Digital Rights Management (DRM) technology. Aegisoft was acquired by streaming media leader, RealNetworks, in 2001.  Aegisoft’s DRM technology was used in over 200 million RealPlayers.  Shen has also worked at Arthur D. Little Inc., Ernst & Young LLP, and American Management System (AMS).  Ji received a Ph.D. ABD (all but dissertation) in Computational Statistics, and a M.S. of Applied Statistics and Operations Research from George Mason University. He has received B.S. in Metallurgy from Harbin Institute of Technology in China. Dr. Matt Anderson has nearly three decades of experience in physics research and education. As a professor of physics for the last 20 years at San Diego State University, he has led a highly productive research group, garnering multiple research grants and publishing 29 papers and 5 patents. He has taught a multitude of course offerings, and is consistently one of the top-rated professors. He recently won the Senate Distinguished Professor award from the university (given annually to one professor on campus) and was twice nominated for the prestigious Robert Foster Cherry Award for Teaching Excellence administered by Baylor University (the nation’s highest teaching award). His physics education channel on YouTube has garnered over 8 million views and over 90k subscribers, and he has given invited talks nationally and internationally. Dr. Anderson holds a B.S. in Physics from the University of California at San Diego, a Ph.D. in Physics from the University of Oregon, a postdoctoral fellowship from the University of Rochester, and was a visiting faculty member at the University of Oxford. He is a cofounder of Learning Glass Solutions and serves as the CEO and President for the company. He is married with three kids and a dog, likes to surf, play guitar, hike, and eat fish tacos. Bayley Pierson is the Marketing Director of HoverCam, a technology company dedicated to transforming classrooms into the advanced digital learning spaces of the future. A philanthropist with an interest in embodied learning, Pierson is dedicated to developing collaboration solutions that assist educators in better preparing students for the future while relieving some of the biggest challenges that impede success in the present.   Support:      Become a MacVoices Patron on Patreon     http://patreon.com/macvoices      Enjoy this episode? Make a one-time donation with PayPal Connect:      Web:     http://macvoices.com      Twitter:     http://www.twitter.com/chuckjoiner     http://www.twitter.com/macvoices      Facebook:     http://www.facebook.com/chuck.joiner      MacVoices Page on Facebook:     http://www.facebook.com/macvoices/      MacVoices Group on Facebook:     http://www.facebook.com/groups/macvoice      LinkedIn:     https://www.linkedin.com/in/chuckjoiner/      Instagram:     https://www.instagram.com/chuckjoiner/ Subscribe:      Audio in iTunes     Video in iTunes      Subscribe manually via iTunes or any podcatcher:      Audio: http://www.macvoices.com/rss/macvoicesrss      Video: http://www.macvoices.com/rss/macvoicesvideorss

Welcome to digital publishing’s present!The second in a 3-part mini-series, this episode explores the last 10 years of digital publishing and what’s going on in today’s publishing landscape. Four key trends are discussed: Digital Rights Management (DRM), software for digital publishing (namely, Adobe InDesign CC), self-publishing and publishing in a pandemic.

Sebastiaan van der Lans, founder of WordProof, the startup using blockchain to authenticate content on the internet, interviewed by futurist Trond Arne Undheim.In this conversation, they talk about How to Fix Fake News? Players in the Internet content industry, Emerging challenges (Digital Rights Management-DRM, interoperability, fake news, copyright infringement/protection, trust on the internet). Potential solutions (watermarking, DRM schemes, open source, blockchain, timestamping, Schema.org, search engine content authenticity validation). Emerging use cases. Disruptive forces (tech, regulation, biz modes, social dynamics). Future of the Internet (how to get out of the mess, perspectives on the next decade).The takeaway is that fixing fake news will mean needing to adapt each of the disruptive forces, technological, regulatory, business-model related, and social fixes. After listening to the episode, check out WordProof as well as Sebastiaan van der Lans' social media profile:WordProof (@wordproofio) https://wordproof.com/ Sebastiaan van der Lans (@delans) https://www.linkedin.com/in/basvdlans/ Will Europe Lead the ‘Trusted Web’ after GDPR?Thanks for listening. If you liked the show, subscribe at Futurized.co or in your preferred podcast player, and rate us with five stars. If you like this topic, you may enjoy other episodes of Futurized, such as episode 4 which is on The Future of remote activism or episode 6 which is on Solving for Surveillance Capitalism, episode 25 on The Future of Enterprise Blockchain, or episode 52 on The Future of Peer-to-peer. Futurized—preparing YOU to deal with disruption.

Episode summary 00:00 | Intro 02:14 | Concept, format 06:30 | General advice 11:45 | Pre-production 13:25 | Production (recording) Time.is: a useful site for synchronizing your claps. 21:02 | Post-production Ian's Audacity window during an intense edit. 25:58 | Hosting platforms The Extra Dimension #33: Decentralized Publishing › The Nexus The Extra Dimension #3: Reducing Barriers to Podcast Creation › The Nexus Should You Be Publishing Your Podcast on YouTube? | by Ian R Buck | Medium The Extra Dimension #32: GDPR, the Privacy Policy Reckoning › The Nexus The Extra Dimension #51: COPPA? I Barely Even Know ‘Er! › The Nexus 31:34 | Copyright law The Extra Dimension #20: Copyright Law › The Nexus 34:31 | DRM The Extra Dimension #27: Digital Rights Management (DRM) and the Problems It Introduces › The Nexus 36:16 | Promoting your show Second Opinion #79: Podcast Players Roundup › The Nexus 40:44 | Monetization The Extra Dimension #8: How Can You Support Yourself as a Creator? › The Nexus The Extra Dimension #11: The Complex World of Ad Blocking › The Nexus 44:37 | Outro Connect With The Nexus Discuss this episode on our Subreddit Support us on Patreon Attributions Inspired / Kevin MacLeod Copyright The Extra Dimension is released under a Creative Commons — Attribution 4.0 International license. Feel free to use any or all of it as long as you link back to http://thenexus.tv/ted57. IPM Find transcripts on our website: internationalpodcastmonth.com/transcripts Follow us on Twitter: @podmonth Support us: Via Ko-Fi Via Paypal.me The IPM theme was composed by Benny James

JS and Lance discuss the technical and legal implications of digital rights management systems of the past, leading up to the complex and secretive implementations of today.

Has ALLi ever heard of certain shady publishers? That is among the questions answered this month on our monthly Member Q&A, where ALLi Members’ have their most pressing self-publishing questions analyzed and answered. Join your hosts for the Member Q&A: Partner Liaison and US Ambassador Michael La Ronn and ALLi Director Orna Ross.  Questions this month include: I published my book with a publisher, the publisher did a bad job, and now I got my rights back. I want to self-publish, but "used" copies of the original publication are still available. How do I market my book around the early edition? Has ALLi ever heard of certain publishers that might be suspected of being shady? If I make a change to my book, do I need to register a copyright for it again? How can I find a children's book illustrator? Where can I find information on starting my author business? Also ALLi News Editor Dan Holloway joins Multimedia Manager Howard Lovy to discuss Digital Rights Management (DRM) and why indie authors are choosing not to encrypt their books. Also, they discuss the further rise of audiobooks through the growth of Storytel and other subscription services. Find more author advice, tips and tools at our Self-publishing Author Advice Center: https://selfpublishingadvice.org, with a huge archive of nearly 2,000 blog posts, and a handy search box to find key info on the topic you need. And, if you haven’t already, we invite you to join our organization and become a self-publishing ally. You can do that at http://allianceindependentauthors.org. Now, go write and publish! About the Hosts Michael La Ronn is the author of over 30 books of science fiction & fantasy and authors self-help books. His books include the Galaxy Mavericks series and Modern Necromancy series. You can now find his new writing course on Teachable. Orna Ross launched the Alliance of Independent Authors at the London Book Fair in 2012. Her work for ALLi has seen her named as one of The Bookseller’s “100 top people in publishing”. She also publishes poetry, fiction and nonfiction, and is greatly excited by the democratising, empowering potential of author-publishing. For more information about Orna, visit her website: http://www.ornaross.com Dan Holloway is a novelist, poet and spoken word artist. He is the MC of the performance arts show The New Libertines Earlier this year he competed at the National Poetry Slam final at the Royal Albert Hall. His latest collection, The Transparency of Sutures, is available on Kindle.

Speakers: Parker Lees & Gerardo Amaya How Blockchain is empowering content creators and transforming Digital Rights Management (DRM)

In this week’s show, we go overboard with chit-chat, then respond to some great questions from William, who is fairly new to the show but is working his way through the entire catalog of podcasts.  We cover things like writing technology, Digital Rights Management (DRM) and multiple viewpoints on the same storyline. Thanks so much […] The post TSS135: Taylor Finishes a Project, Listener Questions and WAY Too Much Chit Chat appeared first on The Taylor Stevens Show.

If you consume digital media, chances are you have encountered DRM in the past. Join Ian R Buck, Ryan Rampersad, and Brian Mitchell as they discuss why it exists, the many forms it can take, and the problems it introduces.

This week on BSDNow! We've got Netflix + FreeBSD news to discuss, always a crowd pleaser, that plus EuroBSDCon is just around the corner. Stick around for your place This episode was brought to you by Headlines Protecting Netflix Viewing Privacy at Scale, with FreeBSD (http://techblog.netflix.com/search/label/FreeBSD) This blog post from Netflix tells the story of how Netflix developed in-kernel TLS to speed up delivery of video via HTTPS Since the beginning of the Open Connect program we have significantly increased the efficiency of our OCAs - from delivering 8 Gbps of throughput from a single server in 2012 to over 90 Gbps from a single server in 2016. We contribute to this effort on the software side by optimizing every aspect of the software for our unique use case - in particular, focusing on the open source FreeBSD operating system and the NGINX web server that run on the OCAs. In the modern internet world, we have to focus not only on efficiency, but also security. There are many state-of-the-art security mechanisms in place at Netflix, including Transport Level Security (TLS) encryption of customer information, search queries, and other confidential data. We have always relied on pre-encoded Digital Rights Management (DRM) to secure our video streams. Over the past year, we've begun to use Secure HTTP (HTTP over TLS or HTTPS) to encrypt the transport of the video content as well. This helps protect member privacy, particularly when the network is insecure - ensuring that our members are safe from eavesdropping by anyone who might want to record their viewing habits. The goal is to ensure that your government, ISP, and wifi sniffing neighbour cannot tell which Netflix videos you are watching Netflix Open Connect serves over 125 million hours of content per day, all around the world. Given our scale, adding the overhead of TLS encryption calculations to our video stream transport had the potential to greatly reduce the efficiency of our global infrastructure. We evaluated available and applicable ciphers and decided to primarily use the Advanced Encryption Standard (AES) cipher in Galois/Counter Mode (GCM), available starting in TLS 1.2. We chose AES-GCM over the Cipher Block Chaining (CBC) method, which comes at a higher computational cost. The AES-GCM cipher algorithm encrypts and authenticates the message simultaneously - as opposed to AES-CBC, which requires an additional pass over the data to generate keyed-hash message authentication code (HMAC). CBC can still be used as a fallback for clients that cannot support the preferred method. All revisions of Open Connect Appliances also have Intel CPUs that support AES-NI, the extension to the x86 instruction set designed to improve encryption and decryption performance. We needed to determine the best implementation of AES-GCM with the AES-NI instruction set, so we investigated alternatives to OpenSSL, including BoringSSL and the Intel Intelligent Storage Acceleration Library (ISA-L). Netflix and NGINX had previously worked together to improve our HTTP client request and response time via the use of sendfile calls to perform a zero-copy data flow from storage (HDD or SSD) to network socket, keeping the data in the kernel memory address space and relieving some of the CPU burden. The Netflix team specifically added the ability to make the sendfile calls asynchronous - further reducing the data path and enabling more simultaneous connections. However, TLS functionality, which requires the data to be passed to the application layer, was incompatible with the sendfile approach. To retain the benefits of the sendfile model while adding TLS functionality, we designed a hybrid TLS scheme whereby session management stays in the application space, but the bulk encryption is inserted into the sendfile data pipeline in the kernel. This extends sendfile to support encrypting data for TLS/SSL connections. We tested the BoringSSL and ISA-L AES-GCM implementations with our sendfile improvements against a baseline of OpenSSL (with no sendfile changes), under typical Netflix traffic conditions on three different OCA hardware types. Our changes in both the BoringSSL and ISA-L test situations significantly increased both CPU utilization and bandwidth over baseline - increasing performance by up to 30%, depending on the OCA hardware version. We chose the ISA-L cipher implementation, which had slightly better results. With these improvements in place, we can continue the process of adding TLS to our video streams for clients that support it, without suffering prohibitive performance hits. If you would like more detail, check out the papers from AsiaBSDCon 2015 (https://people.freebsd.org/~rrs/asiabsd_2015_tls.pdf) and the updated one from 2016 (https://people.freebsd.org/~rrs/asiabsd_tls_improved.pdf) *** OpenBSD on HP Stream 7 (http://www.tedunangst.com/flak/post/OpenBSD-on-HP-Stream-7) Recent events have rocked the mobile computing world to its core. OpenBSD retired the zaurus port, leaving users in desperate need of a new device. And not long before that, Microsoft released the Anniversary Update to Windows 10, but with free space requirements such that it's nigh impossible to install on cheap 32GB eMMC equipped devices such as the HP Stream series, leaving users searching for a new lightweight operating system. With necessity as both mother and father, the scene is set for a truly epic pairing. OpenBSD on the HP Stream 7. The HP Stream line is a series of budget computers in a couple form factors. The Stream 11 is a fairly typical netbook. However, the Stream 7 and 8 are tablets. They look like cheap Android devices, but inside the case, they're real boys, er PCs, with Intel Atom CPUs. To install OpenBSD on such a device, we need a few parts. Obviously, the tablet itself. There's a dearth of ports on these things, but there is a micro USB port. Attaching anything useful requires an OTG “on the go” cable that creates a type A port. Attaching more than one useful thing requires a mini hub. And completing the install requires one each USB stick, keyboard, and network adapter. First, we need to prep the machine to boot from USB. Actually, before doing anything, make sure you have a full charge. It's going to be battery only from here on out. Plug everything in. Flash drive, keyboard, and network into the hub, hub into the OTG cable, cable into the port on top of the Stream. Turn on the machine while holding the volume down button. This launches a mini menu from which we can enter the BIOS. There's a little on screen keyboard in the corner, so this can be done even without a keyboard attached, but the USB keyboard should work. We need to change two settings in the boot section. First, turn off secure boot. Second, switch boot order to prefer USB. Save and exit. The first reboot reveals a confirmation screen checking that we really want to disable secure boot. We must enter a PIN and press enter. Enter the PIN shown on the screen and press enter. And we are go. Then boot up OpenBSD from the USB drive Ted then works there a number of kernel panics and device driver issues, but after disabling ACPI and IntelDRM, the device boots OpenBSD. Of course, there's no X at this point. And definitely no touch screen. And no internal networking. However, by keeping our USB hub attached, we can drive the console and access the network. At least until the battery is depleted, even if we have no way of knowing how long that will be since we disabled all the ACPI devices, which also means no suspend or resume. With some xorg.conf hacking, he did get Xorg working *** DragonflyBSD steps towards base LibreSSL (http://lists.dragonflybsd.org/pipermail/commits/2016-September/624493.html) Project: DragonFlyBSD / Switch base to use private LibreSSL libraries (http://freshbsd.org/commit/dfbsd/304ca408000cd34559ef5319b4b5a6766d6eb35b) DragonFly BSD adopts uses of LibreSSL (http://undeadly.org/cgi?action=article&sid=20160911231651) The number of projects beginning to switch over to LibreSSL is growing and it appears we can now throw DragonFly into that camp. Following something that sounds vaguely familiar (Allan!) DFLY is now creating “private” LibreSSL libraries which are only linked against by base system binaries. For the moment OpenSSL is still built, primarily so that various ports and 3rd party apps can continue to function as before. A NO_OPENSSL option has also been added, but doesn't really do much (yet), since it'll still build and install headers / libraries even if set. *** OpenBSD g2k16 Hackathon g2k16 Hackathon Report: Antoine Jacoutot on Binary Patches (http://undeadly.org/cgi?action=article&sid=20160911012316) g2k16 Hackathon Report: Matthieu Herrb on xenodm (http://undeadly.org/cgi?action=article&sid=20160911231712) g2k16 Hackathon Report: Vincent Gross on iked(8), armv7 and sys/netinet[6] (http://undeadly.org/cgi?action=article&sid=20160911000337) g2k16 Hackathon Report: Florian Obser on httpd, networking, acme-client, and more (http://undeadly.org/cgi?action=article&sid=20160911000052) g2k16 Hackathon Report: Jasper Lievisse Adriaanse on ddb(4) and more (http://undeadly.org/cgi?action=article&sid=20160909012520) g2k16 Hackathon Report: Christian Weisgerber on gettext progress, RTC work, removing kernel cruft (http://undeadly.org/cgi?action=article&sid=20160908002430) g2k16 Hackathon Report: Brent Cook on Chromebooks, crypto, and more (http://undeadly.org/cgi?action=article&sid=20160907131655) g2k16 Hackathon Report: Ted Unangst on doas, signify, code removal (http://undeadly.org/cgi?action=article&sid=20160906230610) g2k16 Hackathon Report: Marc Espie on package signing evolution (http://undeadly.org/cgi?action=article&sid=20160905235911) g2k16 Hackathon Report: Adam Wolk on ports, wireless drivers and more (http://undeadly.org/cgi?action=article&sid=20160906004915) g2k16 Hackathon Report: Mike Larkin on vmm + vmd progress (http://undeadly.org/cgi?action=article&sid=20160905134009&mode=expanded) *** News Roundup OpenBSD (with encrypted softraid) on the Chromebook Pixel (https://jcs.org/notaweblog/2016/08/26/openbsd_chromebook/) Looking for a Laptop to make your OpenBSD road-warrior? If so, we have a great blog tutorial on getting OpenBSD setup on the Chromebook Pixel with encrypted softraid! Author Joshua Stein gives us a very verbose look at how to install and dial-in the laptop perfectly. But first for those wondering about the hardware in the pixel: The Chromebook Pixel LS (2015) has an Intel Core i7 processor (Broadwell) at 2.4Ghz, 16Gb of RAM, a 2560x1700 400-nit IPS screen (239ppi), and Intel 802.11ac wireless. It has a Kingston 64Gib flash chip, of which about 54Gib can be used by OpenBSD when dual-booting with a 1Gb Chrome OS partition. Due to this being a chromebook with seaBIOS, some manual key-press trickery will be required to initially get the OpenBSD Installer up and running. From here you'll want to pay special close attention to the disk partitioning. In particular Joshua will show us how to shrink the existing encrypted /home that ChromeOS uses, keeping the dual-boot intact. This will become important if you ever plan on updating the device. From here, we move back to a more traditional setup, but with the added bonus of doing a soft-raid setup. But the fun isn't over yet! If you want to make OpenBSD the default boot, that'll require cracking the lid on the device and removing a special pink write-protect screw. And of course if you want to remove the default splash-screen image, Joshua has you covered as well, although some flashrom magic will be required. At this point you are nearly done. Final details on enabling specific bits of hardware are discussed. Most things work, apart from Audio and Bluetooth as of right now. *** doas mastery (http://www.tedunangst.com/flak/post/doas-mastery) “doas” mastery - Paging MWL! Our buddy Ted Unangst has written up a great ‘mastery' guide of the doas command, which can come in handy if you are among the un-initiated in doas land. UNIX systems have two classes of user, the super user and regular users. The super user is super, and everybody else is not. This concentration of power keeps things simple, but also means that often too much power is granted. Usually we only need super user powers to perform one task. We would rather not have such power all the time. Think of the responsibility that would entail! Like the sudo command, doas allows for subdivision of super user privileges, granting them only for specific tasks. He starts with the basic doas.conf setup, which starts with an empty config file The doas config is much like a pf ruleset, the default is to block everything > We add the root rule second because doas evaluates rules in a last match manner. root is in the wheel group, so the first rule will match, and then we need to override that with a second rule. Remember to always start with general rules, then make them more specific. *** iXsystems iXsystems to host MeetBSD (https://www.ixsystems.com/blog/ixsystems-host-meetbsd-california-2016-uc-berkeley/) FreeBSD Foundation Welcomes New Board Members New Board Members (https://www.freebsdfoundation.org/blog/freebsd-foundation-welcomes-new-board-members/) The FreeBSD Foundation has added two new board members Interview with Kylie Liang (https://www.freebsdfoundation.org/blog/new-board-member-interview-kylie-liang/) Kylie will focus on representing FreeBSD at conferences and businesses in China I live in China. There, I can act as a bridge between Chinese companies and the FreeBSD community to help drive FreeBSD adoption. Through my leadership role in the FreeBSD Foundation, I will help promote FreeBSD in China and also represent the Foundation at conferences and events in my region. Kylie leads the team the ensures FreeBSD runs well on Hyper-V and Azure, including providing commercial support for customers who run FreeBSD or FreeBSD based appliances on the Azure Cloud I joined Microsoft and started to lead the project called FreeBSD Integration Service to get FreeBSD running well on Hyper-V and Azure. To promote our work and to understand the FreeBSD ecosystem, I started to participate in FreeBSD events where I was inspired by this technical community. Interview with Philip Paeps (https://www.freebsdfoundation.org/blog/new-board-member-interview-philip-paeps/) Philip started with FreeBSD in the early 2000s and got his commit bit in 2004 The patches I submitted to make ACPI and input devices work on that laptop led to a src commit bit in 2004. While I haven't worked on ACPI or input devices since, I have been contributing to different areas of the kernel. Taking up maintainership of some ports I cared about also got me a ports commit bit after some time. Philip will continue to help run EuroBSDCon, but is also spreading the word about FreeBSD in India and Africa Primarily, I think I can be useful! I attend (and organize) a number of conferences around the world every year, particularly in regions that have a mostly “stealthy” FreeBSD community. While I clearly don't need to be on the FreeBSD Foundation board to advocate for FreeBSD, joining as a director will provide an additional asset when working in areas of the world where organizational affiliations are meaningful. Philip has also developed network drivers and various other bits and pieces, and has extensive experience working with and for hardware vendors and appliance vendors Despite intending to eventually contribute their code to the FreeBSD Project as open source, many hardware vendors still find it very difficult to engage directly with the FreeBSD development community. The Foundation helps bridge that gap and helps facilitate collaboration between commercial vendors and the FreeBSD community. I hope to make FreeBSD more visible in regions of the world where it is historically under-represented. I expect I will be attending even more conferences and getting myself invited to even more organizations. more, less, and a story of typical Unix fossilization (https://utcc.utoronto.ca/~cks/space/blog/unix/MoreAndUnixFossilization) Chris Siebenmann from the University of Toronto digs into the history of the difference between ‘less' and ‘more' In the beginning, by which we mean V7, Unix didn't have a pager at all. That was okay; Unix wasn't very visual in those days, partly because it was still sort of the era of the hard copy terminal. Then along came Berkeley and BSD. People at Berkeley were into CRT terminals, and so BSD Unix gave us things like vi and the first pager program, more (which showed up quite early, in 3BSD, although this isn't as early as vi, which appears in 2BSD). Calling a pager more is a little bit odd but it's a Unix type of name and from the beginning more prompted you with '--More--' at the bottom of the screen. All of the Unix vendors that based their work on BSD Unix (like Sun and DEC) naturally shipped versions of more along with the rest of the BSD programs, and so more spread around the BSD side of things. However, more was by no means the best pager ever; as you might expect, it was actually a bit primitive and lacking in features. So fairly early on Mark Nudelman wrote a pager with somewhat more features and it wound up being called less as somewhat of a joke. In a sane world, Unix vendors would have either replaced their version of more with the clearly superior less or at least updated their version of more to the 4.3 BSD version. Maybe less wouldn't have replaced more immediately, but certainly over say the next five years, when it kept on being better and most people kept preferring it when they had a choice.” + “This entire history has led to a series of vaguely absurd outcomes on various modern Unixes. On Solaris derivatives more is of course the traditional version with source code that can probably trace itself all the way back to 3BSD, carefully updated to SUS compliance. Solaris would never dream of changing what more is, not even if the replacement is better. Why, it might disturb someone. Oddly, FreeBSD has done the most sensible thing; they've outright replaced more with less. There is a /usr/bin/more but it's the same binary as less and as you can see the more manpage is just the less manpage. OpenBSD has done the same thing but has a specific manpage for more instead of just giving you the less manpage. So, now you can see why I say that less is more, or more, or both, at several levels. less is certainly more than more, and sometimes less literally is more (or rather more is less, to put it the right way around). Beastie Bits PC-BSD listed in the top 8 'best' alternatives to Windows 10 (http://www.computerworlduk.com/galleries/operating-systems/-free-alternatives-windows-10-3639433/) Creating a quick DNS server with a Rapsberry Pi2 and FreeBSD 11.0-RC1 (http://bsdimp.blogspot.co.uk/2016/08/creating-quick-dns-server-with.html) Dual Boot OpenBSD and Linux + UEFI (https://bsdlaptops.wordpress.com/2016/03/07/vaio-pro-11-part-2/) DesktopBSD 2.0 various versions available (Gnome, Lumina, KDE, LXDE) (http://desktopbsd.boards.net/board/10/announcements) FreeBSD gets new ZFS features including: Compressed ARC (https://svnweb.freebsd.org/base?view=revision&revision=305323) and ZFS Allocation Throttle (https://svnweb.freebsd.org/base?view=revision&revision=305331) One Floppy NetBSD Distribution (https://github.com/user340/fdgw2) A Compendium of BUGs (https://github.com/q5sys/BUGtracker) Feedback/Questions Galahad - OpenBSD X setup (http://pastebin.com/b7W6NHqs) Tang - Subtitles (http://pastebin.com/P4MUs3Pa) Ivan - Zpool Options (http://pastebin.com/LQ8yTp0G) Brad - Replication Issue (http://pastebin.com/XTK5gXMU) MJ - HBA (http://pastebin.com/TdYTMSj9) ***

Cory Doctorow is a bestselling author of both science fiction and techno-sociological nonfiction, one of four editors of longtime popular weblog boingboing, and an activist and advocate for intellectual property rights, working extensively with the Electronic Freedom Foundation and others to put control of content back in the hands of the users like you and me. Photo credit: Jonathan Worth 2013 Today, we talk about the EFF's plan to defeat Digital Rights Management (DRM) as a business model of rent-seeking corporations. DRM is the set of digital locks on the content you buy--everything from eBooks to your car's computer have DRM embedded--and while it isn't impossible to break, it is highly illegal for you (or anyone) to do so. That means you don't have control of things that you bought. It also means that security flaws cannot always be researched or revealed. That's a big problem. We also talk about how he became a writer and how he gets his writing done despite a punishing travel and speaking schedule. Spoiler: 250 words a day, every day will result in a finished product very quickly. That's one page per day. You can do that, can't you? Show Links and Notes EFF The EFF on the DRM lawsuit Bunnie Huang on the DRM lawsuit boingboing Cory's website, craphound.com Flickr Twitter The flashbake version control tool Cory's books include: Little Brother Information Doesn't Want to be Free: Laws for the Information Age Down and Out in the Magic Kingdom  

Radio Freethinker Episode 207 – Digital Rights EditionThis week - We talk about a spectacularly bizarre and time disturbing poll from the USA showing, for example, how many people voted Obama believe he WAS the Antichrist.- Canada's first Parliamentary Budget Officer has recently stepped down. It is likely that his office will be "wound down" because it proved to be too embarrassing for the Harper Government. We discuss what it did, why it did it and why you should care.- EA used Digital Rights Management (DRM) to ensure no one pirated its new SimCity game resulting in a horrible PR disaster. HBO felt proud that Game of Thrones was the most pirated TV show in history. We discuss the issue of DRMCheck us out online at www.radiofreethinker.com and email us at info@radiofreethinker.com and follow us on twitter at @citrrft

In his return to the Free From Corporate America podcast series, Morris Rosenthal of FonerBooks.com talks with Jon Reed about the business of eBooks and how self-publishers can add an eBooks revenue stream by selling eBooks from their own marketing … Continue reading →

April 28th, 2007 - Show number 3 was lots of fun. We talked about Copy Protection and why it helps no one. We also shared a bit about ourselves. - Show Notes - Main Topic: Copy Protection – Otherwise known as Digital Rights Management (DRM), Copy Protection prevents consumers from using media they purchased in ways many people feel they should. It also fails to stop pirates from stealing the content, so really the media corporations are only hurting their customers. Chris from Phoenix, AZ called us to add his thoughts on DRM and how he had to "work around" a problem when a CD he had purchased wouldn't import properly into iTunes. Suzanna in Mesa is a musician who called in to give the perspective of copy protection from a content creator. Her music was pirated in Europe, and while she was upset that people were stealing her music she realized that there was no way to prevent it and used it to her advantage by referring to her music as being so good that people were willing to steal it. Support Calls: Mike in Gilbert, AZ called again. He had trouble visiting the website for AVG Antivirus that we mentioned last week. We provided the link again. As always, check these show notes for links, especially the long ones... Mike also asked about a program called System Mechanic 7 that we do not have experience with, but another listener, Gary, called in to inform us that based on his experiences System Mechanic 6 is good, but 7 slows down your computer more than it's worth. Thanks for sharing your knowledge with us, Gary! Pete chimed in to say that if you absolutely feel the need to use a registry cleaner he recommends Microsoft's free registry cleaner RegClean. Gary had a question about his high speed internet connection via cable that appeared to be faster on his old computer compared to his new one. As far as he could tell, the only difference was that the new computer was running Windows XP Service Pack 2. We were stumped as to why this would cause any problems other than maybe firewall issues, but recommended trying to see if the firewall was the issue. Most likely the problem is with the cable company not properly handling the bandwidth of customers in Gary's neighborhood. Pete recommended dslreports.com as a tool for checking his actual speed and comparing it to other people in his area. Chris from Phoenix, AZ had a question about data backups and whether optical media like CDs and DVDs have a high shelf life. We definitely recommend backing up your data, and CDs and DVDs are great for backing up data. Based on our personal experiences we have burned CDs that are over 10 years old and still working just fine. If the data is really important, though, there's nothing wrong with keeping multiple copies and making new backups periodically to ensure that a single hard drive crashing, a disc being unreadable, or a fire in your house will leave you without your important information. News Stories: Thunderbird version 2 released School's failure to change clocks lands student 12-day stint in juvie Googling For Grand Larceny Macworld: News: Hacker breaks into Mac at security conference Confirmed: QuickTime/Java flaw does affect Windows Acer recalls 27,000 laptop batteries for overheating Weekly Website: Windows Live Maps Software Spotlight: Windows Desktop Search Hardware Highlight: Nintendo DS Direct MP3 Download iTunes Subscription RSS Feed

"Trusted computing is considered a dirty word by many due to its use for Digital Rights Management (DRM). There is a different side of trusted computing, however, that can solve problems information security professionals have been attempting to solve for more than three decades. Large scale deployment of trusted computing will fundamentally change the threat model we have been using for years when building operating systems, applications, and networks. This talk will examine the history of trusted computing and the current mindset of information security. From there, we will attempt to demystify the trusted computing architecture and give examples of where trusted computing is being used today. Then, we'll discuss how security constructs that we know an love today (such as firewalls and SSL transactions) fundamentally change when a trusted hardware component is added. Finally, new tools will be released to allow users to examine trusted components in their system. Bruce Potter is the founder of the Shmoo Group of security professionals, a group dedicated to working with the community on security, privacy, and crypto issues. His areas of expertise include wireless security, software assurance, pirate songs, and restoring hopeless vehicles. Mr. Potter has co-authored several books including "802.11 Security" and "Mastering FreeBSD and OpenBSD Security" published by O'Reilly and "Mac OS X Security" by New Riders. Mr. Potter was trained in computer science at the University of Alaska, Fairbanks. Bruce Potter is a Senior Associate with Booz Allen Hamilton."

Trusted computing is considered a dirty word by many due to its use for Digital Rights Management (DRM). There is a different side of trusted computing, however, that can solve problems information security professionals have been attempting to solve for more than three decades. Large scale deployment of trusted computing will fundamentally change the threat model we have been using for years when building operating systems, applications, and networks. This talk will examine the history of trusted computing and the current mindset of information security. From there, we will attempt to demystify the trusted computing architecture and give examples of where trusted computing is being used today. Then, we'll discuss how security constructs that we know an love today (such as firewalls and SSL transactions) fundamentally change when a trusted hardware component is added. Finally, new tools will be released to allow users to examine trusted components in their system. Bruce Potter is the founder of the Shmoo Group of security professionals, a group dedicated to working with the community on security, privacy, and crypto issues. His areas of expertise include wireless security, software assurance, pirate songs, and restoring hopeless vehicles. Mr. Potter has co-authored several books including "802.11 Security" and "Mastering FreeBSD and OpenBSD Security" published by O'Reilly and "Mac OS X Security" by New Riders. Mr. Potter was trained in computer science at the University of Alaska, Fairbanks. Bruce Potter is a Senior Associate with Booz Allen Hamilton."

Big media players are accustomed to watching the ratings for the most popular music video and book content but perhaps they should pay more attention to how consumers feel about three letters at the bottom of most charts -- DRM which stands for digital rights management. Broadly defined DRM encompasses multiple technologies that control the use of software music movies or any other piece of digital content. But media companies are risking a consumer backlash by deploying overzealous systems with draconian restrictions say experts at Wharton who also question whether DRM is worth the effort whether it will survive and what the best approach is for balancing the rights of consumers with the rights of content creators. See acast.com/privacy for privacy and opt-out information.

Sony's latest Digital Rights Management (DRM)-endeavour earned a charge of "fraud, false advertising, trespass and the violation of state and federal statutes prohibiting malware, and unauthorized computer tampering". The technology installs, unnoticed by the user, a piece of software that prevents consumers from unauthorised copying, is able to monitor and report user behaviour back to the firm and, accidentally, holds the door wide open for Trojans. Under other circumstances one would be tempted to describe such a strategy a hostile "spy at-tack". In case of Sony BMG, this seems to be part of a business model to sell digital music to consumers. The talk will have a closer look at the charges of the EFF and a Californian lawyer against Sony BMG's latest DRM strategy. The Sony BMG case adds a number of interesting new dimensions to the 'DRM and Consumer' debate. The talk will explain why the case is so important, also against the background of similar recent case law in Europe, and why it points into an entirely new direction of talking about DRM.