Podcast appearances and mentions of tim berners lee

Dobbiamo imparare a fidarci di chi ci aiuta con l'AI. I moniti di Tim Berners-Lee e Jimmy Kimmel. Microsoft blocca i suoi contratti con Israele. Forse l'Europa risolve il banner dei cookie? Queste e molte altre le notizie tech commentate nella puntata di questa settimana.Dallo studio distribuito di digitalia:Michele Di Maio, Francesco Facconi, Massimo De SantoProduttori esecutivi:@Jh4Ckal, Arzigogolo, Massimiliano Sgroi, Fabio Filisetti, Paolo Bernardini, Carlo Alberto Giovannini, Gianfranco Di Summa, Paola Danieli, Nicola Bisceglie, Davide Tinti, Antonio Gargiulo, Elisa Emaldi - Marco Crosa, Manuel Zavatta, Mirto Tondini, Giuliano Arcinotti, @Geckonode, Mattia Lanzoni, Douglas Whiting, @Akagrinta, Luca Di Stefano, @Pier, Andrea Bottaro, Sandro Acinapura, Matteo Tarabini, Fabrizio Mele, Fiorenzo Pilla, Piero Alberto Mazzo, Valerio BendottiSponsor:Squarespace.com - utilizzate il codice coupon "DIGITALIA" per avere il 10% di sconto sul costo del primo acquisto.Links:L'hamburger più caro al mondo: patto di riservatezza per chi lo assaggiaThe Postmark Backdoor That's Stealing Your EmailsWhy I gave the world wide web away for freeJimmy Kimmel calls FCC chairman an embarrassment to RepublicansEveryoness a Free-Speech HypocriteSupporting the future of the open webMicrosoft blocks Israel's use of its technology in mass surveillance of PalestiniansLe sanzioni degli Stati Uniti contro Francesca AlbaneseRegulating AI hastens the Antichrist, says Peter ThielHow AI safety took a backseat to military moneyConsenso sui cookie una tantum integrato nel browser?Apple warns of more feature delays in EuropeApple demands EU repeal the Digital Markets ActF-Droid and Google's Developer Registration DecreeQualcomm CEO: Android for PC is coming and it's 'incredible'Pirateria televisiva: maxi operazione della Polizia.Sono state arrestate 7 persone sospettate di gestire il 70% del mercato dello streaming illegaleAvevano profitti sino a 10 milioni di euro al meseA $1000 Xbox Ally handheld tests the appetite for pricey consolesSony, Microsoft, and the future of game consoles.Il vero pericolo dell'intelligenza artificiale può stravolgere l'umanitàOpenAI really wants you to start your day with ChatGPT PulseCandidato smaschera i recruiter AI con una ricetta di flanPope Leo refuses to authorise an AI PopeWhy AI chatbots can't process Persian social etiquetteAI investment bubble inflated by trio of dilemmasGingilli del giorno:Insta360 Wave - Vivavoce con AICompatibile con l'uomoSuper Mario Bros Remaster - un remaster fatto dalla comunitaSupporta Digitalia, diventa produttore esecutivo.

Watch the full video of this event for free here: https://mailchi.mp/intelligencesquared/lw6gixq1t9 The transcript of this event is available here: https://drive.google.com/file/d/1GvYGaOE-fnDQdFvrTLQjUGcrE6Ra0acN/view?usp=drive_link --- The most influential inventor of the modern world, Sir Tim Berners-Lee is a different kind of visionary. Born in the same year as Bill Gates and Steve Jobs, Berners-Lee famously shared his invention, the World Wide Web, for no commercial reward. Its widespread adoption changed everything — transforming humanity into the first digital species. In September 2025 Berners-Lee came to the Intelligence Squared stage to tell the story of his iconic invention and explore the future of human innovation. Drawing on his new memoir, This is For Everyone, Berners-Lee explored how the web launched a new era of creativity and collaboration, while unleashing a commercial race that today imperils democracies and polarises public debate. As the rapid development of artificial intelligence heralds a new era of innovation, Berners-Lee is the perfect guide to the crucial decisions ahead, and to provide a gripping, in-the-room account of the rise of the online world. With his characteristic optimism, technical insight and wry humour, Berners-Lee discussed the power of technology — both to fuel our worst instincts and to profoundly shape our lives for the better. --- If you'd like to become a Member and get access to all our full ad free conversations, plus all of our Members-only content, just visit intelligencesquared.com/membership to find out more. For £4.99 per month you'll also receive: - Full-length and ad-free Intelligence Squared episodes, wherever you get your podcasts - Bonus Intelligence Squared podcasts, curated feeds and members exclusive series - 15% discount on livestreams and in-person tickets for all Intelligence Squared events  ...  Or Subscribe on Apple for £4.99: - Full-length and ad-free Intelligence Squared podcasts - Bonus Intelligence Squared podcasts, curated feeds and members exclusive series … Already a subscriber? Thank you for supporting our mission to foster honest debate and compelling conversations! Visit intelligencesquared.com to explore all your benefits including ad-free podcasts, exclusive bonus content and early access. … Subscribe to our newsletter here to hear about our latest events, discounts and much more. https://www.intelligencesquared.com/newsletter-signup/ Learn more about your ad choices. Visit podcastchoices.com/adchoices

Watch the full video of this event for free here: https://mailchi.mp/intelligencesquared/lw6gixq1t9 The transcript of this event is available here: https://drive.google.com/file/d/1GvYGaOE-fnDQdFvrTLQjUGcrE6Ra0acN/view?usp=drive_link --- The most influential inventor of the modern world, Sir Tim Berners-Lee is a different kind of visionary. Born in the same year as Bill Gates and Steve Jobs, Berners-Lee famously shared his invention, the World Wide Web, for no commercial reward. Its widespread adoption changed everything — transforming humanity into the first digital species. In September 2025 Berners-Lee came to the Intelligence Squared stage to tell the story of his iconic invention and explore the future of human innovation. Drawing on his new memoir, This is For Everyone, Berners-Lee explored how the web launched a new era of creativity and collaboration, while unleashing a commercial race that today imperils democracies and polarises public debate. As the rapid development of artificial intelligence heralds a new era of innovation, Berners-Lee is the perfect guide to the crucial decisions ahead, and to provide a gripping, in-the-room account of the rise of the online world. With his characteristic optimism, technical insight and wry humour, Berners-Lee discussed the power of technology — both to fuel our worst instincts and to profoundly shape our lives for the better. --- This is the first instalment of a two-part episode. If you'd like to become a Member and get access to all our full ad free conversations, plus all of our Members-only content, just visit intelligencesquared.com/membership to find out more. For £4.99 per month you'll also receive: - Full-length and ad-free Intelligence Squared episodes, wherever you get your podcasts - Bonus Intelligence Squared podcasts, curated feeds and members exclusive series - 15% discount on livestreams and in-person tickets for all Intelligence Squared events  ...  Or Subscribe on Apple for £4.99: - Full-length and ad-free Intelligence Squared podcasts - Bonus Intelligence Squared podcasts, curated feeds and members exclusive series … Already a subscriber? Thank you for supporting our mission to foster honest debate and compelling conversations! Visit intelligencesquared.com to explore all your benefits including ad-free podcasts, exclusive bonus content and early access. … Subscribe to our newsletter here to hear about our latest events, discounts and much more. https://www.intelligencesquared.com/newsletter-signup/ Learn more about your ad choices. Visit podcastchoices.com/adchoices

Linß, Vera www.deutschlandfunk.de, Andruck - Das Magazin für Politische Literatur

Sir Tim Berners-Lee launched the worldwide web on Christmas day 1990; an invention which has undeniably and profoundly changed the world.In this episode of Ways to Change the World, Sir Tim spoke with Krishnan Guru-Murthy about why addictive algorithms should be made illegal, the potential for artificial intelligence to outsmart humans, and how the internet has been both a powerful force for good and a source of significant harm to the world.

The inventor of the World Wide Web Sir Tim Berners-Lee, flicks through his book This Is For Everyone.Neuroscientist & bestselling author Dr Tara Swart tells us all about her new book, The Signs.The delightful Davina McCall joins us for the third time as Chris had 'interviewers regret'!Join Chris and the Class Behind The Glass every morning from 6.30am! Listen on your smart speaker, just say: "Play Virgin Radio." Hosted on Acast. See acast.com/privacy for more information.

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

In this episode of The Digital Executive, host Brian Thomas sits down with Mark Weinstein—renowned tech entrepreneur, privacy expert, and one of the original pioneers of social networking. With over 25 years in the industry and 13 U.S. patents focused on data anonymization, Mark has dedicated his career to building platforms that protect users rather than exploit them.Mark shares insights from his new book, Restoring Our Sanity Online, praised by Sir Tim Berners-Lee as “a vital read” and by Steve Wozniak as “a must read.” He reflects on the early days of Web1, the rise of surveillance capitalism in Web2, and the stubborn hold Big Tech maintains over the social media landscape. He also introduces his concept of “Restoration Networking,” a new framework for user-centric design that prioritizes privacy, data portability, and safeguarding future generations.The conversation dives into the dangers of manipulative algorithms, the failures of Web3 in delivering on its promises, and the dual-edged role of AI—both as a manipulative force and as a powerful tool for eliminating bots and trolls. Despite the challenges, Mark remains hopeful, pointing to bipartisan legislative efforts, data ownership initiatives, and a growing movement toward digital sanity.If you liked what you heard today, please leave us a review. Apple or Spotify.See Privacy Policy at https://art19.com/privacy and California Privacy Notice at https://art19.com/privacy#do-not-sell-my-info.

Tim Berners-Lee could be one of the richest men on the planet, why did he forfeit such large profits to make the World Wide Web a free and open space? How do we reclaim the internet from social media companies taking away our sovereignty? Have tech giants like Mark Zuckerberg, Jeff Bezos and Elon Musk thanked Tim for his invention?  Rory and Alastair are joined by Sir Tim Berners-Lee to discuss all this and more.  Visit HP.com/politics to find out more. To save your company time and money, open a Revolut Business account today via www.revolut.com/rb/leading, and add money to your account by 31st of December 2025 to get a £200 welcome bonus or equivalent in your local currency. Feature availability varies by plan. This offer's available for New Business customers in the UK, US, Australia and Ireland. Fees and Terms & Conditions apply. For US customers, Revolut is not a bank. Banking services and card issuance are provided by Lead Bank, Member FDIC. Visa® and Mastercard® cards issued under license. Funds are FDIC insured up to $250,000 through Lead Bank, in the event Lead Bank fails. Fees may apply. See full terms in description. For Irish customers, Revolut Bank UAB is authorised and regulated by the Bank of Lithuania in the Republic of Lithuania and by the European Central Bank and is regulated by the Central Bank of Ireland for conduct of business rules. For AU customers, consider PDS & TMD at revolut.com/en-AU. Revolut Payments Australia Pty Ltd (AFSL 517589). TRIP Plus: Become a member of The Rest Is Politics Plus to support the podcast, receive our exclusive newsletter, enjoy ad-free listening to both TRIP and Leading, benefit from discount book prices on titles mentioned on the pod, join our Discord chatroom, and receive early access to live show tickets and Question Time episodes. Just head to therestispolitics.com to sign up, or start a free trial today on Apple Podcasts: apple.co/therestispolitics. Instagram: @restispolitics  Twitter: @RestIsPolitics  Email: restispolitics@gmail.com Social Producer: Harry Balden Video Editor: Adam Thornton Assistant Producer: Alice Horrell Producer: Nicole Maslen Senior Producer: Dom Johnson Head of Content: Tom Whiter Exec Producers: Tony Pastor + Jack Davenport Learn more about your ad choices. Visit podcastchoices.com/adchoices

Tim Berners-Lee's Call to Ban Addictive Algorithms & The Future of Tesla In this episode of Hashtag Trending, host Jim Love discusses Tim Berners-Lee's call to ban addictive algorithms designed to keep users hooked. We also delve into the mystery behind bricking SSDs after a Windows update, the potential shift in Tesla's focus from cars to autonomy under Elon Musk, and a new study identifying 32 ways AI could malfunction. Additionally, we touch upon the latest moves by Musk's Starlink to become a global mobile carrier and the broader implications of AI advancements. Don't miss these key tech updates! 00:00 Introduction and Headlines 00:26 Tim Berners-Lee on Addictive Algorithms 01:39 Mystery of the Bricking SSDs Solved 03:25 Elon Musk's Shifting Focus from Cars to Autonomy 04:32 Starlink's Ambitious Expansion Plans 05:55 AI Risks and Future Prospects 07:28 Show Wrap-Up and Contact Information

WBZ's Jordan Rich says Sir Tim Berners-Lee needs extra kudos for inventing the World Wide Web.Get all the news you need by listening to WBZ - Boston's News Radio! We're here for you, 24/7.

A US congressional committee has made public the 'birthday book' allegedly given to Jeffrey Epstein in 2003 to mark his fiftieth birthday. In it, messages, photos and drawings from his friends - including Donald Trump. The White House is furiously denying that the American President ever submitted a drawing to Epstein, insisting that the signature is not his. Democrats have called it "revolting" and "sick". After spending so long shouting about an Epstein cover up, how wounded are Trump and the Republicans by the latest revelations?Later, Sir Tim Berners-Lee, inventor of the World Wide Web, on the "addictive" algorithms he thinks are making the world a more dangerous place - and his proposals to reclaim the internet.And, the Labour deputy leadership race heats up. Why it might have Keir Starmer sweating.The News Agents is brought to you by HSBC UK - https://www.hsbc.co.uk/EXCLUSIVE NordVPN Deal -> https://nordvpn.com/thenewsagents Try it risk-free now with a 30-day money-back guarantee

You might be surprised to learn that the famous “www” in website addresses didn't originate in Silicon Valley or New York, but at the European Organisation for Nuclear Research, known as CERN for short, which is situated on the French-Swiss border close to Geneva.  It was 1989 when British computer scientist Tim Berners-Lee came up with the idea for a hypertext system. Essentially, it was a way to connect different pieces of data through links, creating something like a giant web that would work via the internet. Aren't internet and web the same thing?  What about the other parts of a web address then, like https or “.com” at the end? In under 3 minutes, we answer your questions! To listen to the last episodes, you can click here: ⁠How to protect your art from AI exploitation?⁠ ⁠What is the internet of senses?⁠ ⁠What is Web 3.0?⁠ A podcast written and realised by Joseph Chance. First Broadcast: 30/9/2024 Learn more about your ad choices. Visit megaphone.fm/adchoices

August 6, 1991. British computer programmer Tim Berners-Lee launches a digital information revolution when he uploads the first site to the World Wide Web. This episode originally aired in 2024.Support the show! Join Into History for ad-free listening and more.History Daily is a co-production of Airship and Noiser.Go to HistoryDaily.com for more history, daily.See Privacy Policy at https://art19.com/privacy and California Privacy Notice at https://art19.com/privacy#do-not-sell-my-info.

Il 6 agosto 1991, Tim Berners-Lee pubblica nella rete Internet… il primo sito World Wide Web! Learn more about your ad choices. Visit megaphone.fm/adchoices

Tim Berners-Lee uploaded a photo of parody doo-wop group Les Horrible Cernettes on 18th July 1992 - the first image to be shared online. The photograph was taken at the CERN Hardronic Festival by Silvano de Gennaro, an analyst in the Computer Science department. The girlband were striking a pose for their forthcoming CD cover, little realising their comedy love songs about colliders, quarks, liquid nitrogen, microwaves, and antimatter would soon go down in internet history. In this episode, Arion, Rebecca and Olly consider the spooky social media resonance of this earliest online picture; explain how Berners-Lee used ‘sex' to ‘sell' the world wide web; and check out the Cernette's biggest banger, ‘Collider'... Further Reading: • ‘The true story behind the 'first picture on the internet' myth' (Metro, 2022): https://metro.co.uk/2022/07/18/the-true-story-behind-the-first-picture-on-the-internet-myth-16945088/?ito=article.mweb.share.top.link&fbclid=IwAR1BGGcwPK2HYL1f3-KBtCfQBILTtCtKOlq4aYIcZRfBzUJ8ssN0RwjPwi8 • ‘Was this the 1st photo on the web? 25 years on, Quebec woman tells how she came to be in it' (CBC News, 2017): https://www.cbc.ca/news/canada/montreal/first-internet-photo-features-sherbrooke-woman-1.4206913 • ‘LHC - Collider' (Cernettes, 2000): https://www.youtube.com/watch?v=A1L2xODZSI4 This episode originally aired in 2023 Love the show? Support us!  Join 

Episodio patrocinado gracias a “SEOXAN”. Imagina un mundo sin Google, sin pestañas, sin clics. Un mundo donde la información era un laberinto sin mapa. Así comenzó la historia de los navegadores web, con un científico británico, Tim Berners-Lee, que en 1990, en el CERN, creó el primer navegador y el primer servidor web. Su criatura, llamada simplemente WorldWideWeb, era sofisticada para su tiempo, pero solo funcionaba en los ordenadores NeXT, una rareza en sí misma. NUESTRO PATROCINADOR https://seoxan.es //Enlaces https://seoxan.es https://uptime.urtix.es/login.php https://iina.io/https://www.diabrowser.com/download https://comet.perplexity.ai //Donde encontrarnos Canal Youtube https://www.youtube.com/c/ApplelianosApplelianos/featured Correo electrónico applelianos@gmail.com Amazon https://amzn.to/30sYcbB X https://x.com/ApplelianosPod Apple Podcasts https://podcasts.apple.com/es/podcast/applelianos-podcast/id993909563

National Name your poison day.  Entertainment from 2021.  Bill of Rights proposed to US Constitution, Vacuum cleaner invented, Worlds 1st auto theft.  Todays birthdays - Jerry Stiller, Joan Rivers, Nancy Sinatra, Chuck Negron, Boz Skaggs, Bonnie Tyler, Tim Berners-Lee, Keenen Ivory Wayans, Rob Pilatus, Julianna Margulies, kanye West.  Andrew Jackson died.Intro - God did good - Dianna Corcoran    https://www.diannacorcoran.com/Name your poison - Ted NugentButter - BTSForever after all - Luke CombsBirthdays - In da club - 50 Cent    http://50cent.com/These boots were made for walkin - Nancy SinatraJoy to the world - Three Dog NightLook what you've done to me - Boz SkaggsTotal eclipse of the heart - Bonnie tylerIn Living Color TV themeGirl you know its true - Millie VanilliStronger - Kanye WestExit - You aint no match - Lena Paige   Lena on facebookcountryundergroundradio.com cooolmedia.com

Heute vor 70 Jahren wurde in London Tim Berners-Lee geboren, Physiker und Informatiker – und: Begründer des World Wide Web.

Social media gets a lot of flak. Its critics accuse platforms of causing massive negative externalities on society – everything from crumbling democracies to mental health crises gets blamed on social media.And “social media” as a term has even become so toxic that social media companies themselves prefer to call themselves anything but “social media”. The tagline to Snapchat's marketing campaign last year was: “Less social media. More Snapchat.” TikTok calls itself an entertainment platform.But does social media need to be this way? Perhaps not.WeAre8 is a challenger platform that wants to prove social media can have a positive social impact. The platform has a unique opt-in advertising experience that enables users to be paid to watch ads, with proceeds optionally donated to charities of their choosing.The startup calls itself “The People's Platform” – but does it have the requisite scale to attract advertisers looking for strong business results and not just a morally driven goal of spending with supposedly nicer players?Laura Chase, WeAre8's UK managing director, joins host Jack Benjamin to explain the app's features, commercial model and how it is working to attract investment from brands."We can fix big problems by watching ads," she says.During the interview, Chase also reveals that WeAre8 is launching a voice note ad product in time for less healthy food ad restrictions.Highlights:5:12: WeAre8's mission to "bring the best of social" while removing "the bad bits"9:34: Scale, product development and brand-safety efforts15:12: WeAre8's opt-in ad model: control, effectiveness and charitable benefits28:44: Supporting publishers and partnering The Independent on Bulletin38:09: Moving beyond algorithmic feedsRelated articles:‘This is for everyone': Tim Berners-Lee is continuing his search for a benign online world‘Positive' platforms improve purchase intent, Pinterest saysThe Fishbowl: Laura Chase, WeAre8---Thanks to our production partners Trisonic for editing this episode.--> Discover how Trisonic can elevate your brand and expand your business by connecting with your ideal audienceVisit The Media Leader for the most authoritative news analysis and comment on what's happening in commercial media. LinkedIn: The Media LeaderYouTube: The Media Leader

En este primer episodio de la quinta temporada de Esto es lo que AI, nos atrevemos a hacer apuestas sobre el futuro de la IA. ¿Será capaz de entender el argumento de una película y responder preguntas complejas sin errores? ¿Podrá escribir un guión digno de un Oscar o desarrollar descubrimientos científicos revolucionarios? Nuestra nueva tertuliana, Patricia Charro, se une a la conversación con una visión fresca sobre el impacto de la IA en los próximos años. Además del debate habitual con Adolfo Corujo, Luis Martín, Miguel Lucas, Julio Gonzalo y Roberto Carreras, este episodio incluye una entrevista especial con José Raúl González, CEO de Progreso, sobre Clara, la primera embajadora de sostenibilidad basada en IA en la industria del cemento en Centroamérica. Un ejemplo real de cómo la IA puede servir al propósito, la transparencia y el impacto social. También viajamos al origen de la web con Tim Berners-Lee, de la mano de Margorieth Tejeira, y descubrimos usos inesperados de la IA con Ángela Ortega en una nueva sección. Inspirados en el desafío lanzado por Gary Marcus, analizamos hasta qué punto la IA podrá alcanzar hitos que hoy parecen ciencia ficción. ¿Nos sorprenderá con avances inesperados o seguirá atrapada en la burbuja del hype?

Mark Weinstein is a pioneering tech entrepreneur, privacy advocate, and one of the original inventors of social networking. His 25-year journey includes founding three award-winning social media platforms, such as SuperFamily and SuperFriends, both recognized in PC Magazine's Top 100 Sites. As a leading privacy expert, Mark delivered the landmark TED Talk “The Rise of Surveillance Capitalism” and authored Restoring Our Sanity Online: A Revolutionary Social Framework, which presents a bold vision for transforming social media. His work has earned endorsements from industry leaders like Sir Tim Berners-Lee and Steve Wozniak, reflecting his commitment to ethical technology and user empowerment. In this episode… The internet was once seen as a tool for connection, but today, it often feels like it's controlling us. From social media algorithms that manipulate our thoughts to privacy invasions that track our every move, the online world has shifted in ways few anticipated. So, how can we reclaim our digital autonomy and create a healthier relationship with technology? Mark Weinstein, a social media pioneer and privacy expert, offers insights into the hidden dangers of surveillance capitalism and how users can protect themselves. He explains how algorithms are designed to exploit human psychology, keeping people hooked while collecting vast amounts of personal data. He shares actionable steps, such as limiting screen time, avoiding AI-driven recommendations, and choosing privacy-focused platforms. Mark also stresses the importance of critical thinking, teaching children to discern fact from manipulation, and advocating for ethical tech policies to reshape the future of online interactions. In this episode of the Inspired Insider Podcast, Dr. Jeremy Weisz interviews Mark Weinstein, author of Restoring Our Sanity Online, about the urgent need for ethical social media and enhanced digital privacy. Mark discusses the evolution of social media, the rise of surveillance capitalism, and the impact of AI-driven algorithms on user behavior. He also shares practical strategies for protecting personal data, reducing social media addiction, and fostering critical thinking in the digital age.

I hope that the man who invented the World Wide Web, Tim Berners-Lee, with all of his brilliance, appreciates Donald J. Trump. Berners-Lee, who shares my birthday of June 8,

On this episode of the Crazy Wisdom Podcast, host Stewart Alsop welcomes Jessica Talisman, a senior information architect deeply immersed in the worlds of taxonomy, ontology, and knowledge management. The conversation spans the evolution of libraries, the shifting nature of public and private access to knowledge, and the role of institutions like the Internet Archive in preserving digital history. They also explore the fragility of information in the digital age, the ongoing battle over access to knowledge, and how AI is shaping—and being shaped by—structured data and knowledge graphs. To connect with Jessica Talisman, you can reach her via LinkedIn.  Check out this GPT we trained on the conversation!Timestamps00:05 – Libraries, Democracy, Public vs. Private Knowledge Jessica explains how libraries have historically shifted between public and private control, shaping access to knowledge and democracy.00:10 – Internet Archive, Cyberattacks, Digital Preservation Stewart describes visiting the Internet Archive post-cyberattack, sparking a discussion on threats to digital preservation and free information.00:15 – AI, Structured Data, Ontologies, NIH, PubMed Jessica breaks down how AI trains on structured data from sources like NIH and PubMed but often lacks alignment with authoritative knowledge.00:20 – Linked Data, Knowledge Graphs, Semantic Web, Tim Berners-Lee They explore how linked data enables machines to understand connections between knowledge, referencing the vision behind the semantic web.00:25 – Entity Management, Cataloging, Provenance, Authority Jessica explains how libraries are transitioning from cataloging books to managing entities, ensuring provenance and verifiable knowledge.00:30 – Digital Dark Ages, Knowledge Loss, Corporate Control Stewart compares today's deletion of digital content to historical knowledge loss, warning about the fragility of digital memory.00:35 – War on Truth, Book Bans, Algorithmic Bias, Censorship They discuss how knowledge suppression—from book bans to algorithmic censorship—threatens free access to information.00:40 – AI, Search Engines, Metadata, Schema.org, RDF Jessica highlights how AI and search engines depend on structured metadata but often fail to prioritize authoritative sources.00:45 – Power Over Knowledge, Open vs. Closed Systems, AI Ethics They debate the battle between corporations, governments, and open-source efforts to control how knowledge is structured and accessed.00:50 – Librarians, AI Misinformation, Knowledge Organization Jessica emphasizes that librarians and structured knowledge systems are essential in combating misinformation in AI.00:55 – Future of Digital Memory, AI, Ethics, Information Access They reflect on whether AI and linked data will expand knowledge access or accelerate digital decay and misinformation.Key InsightsThe Evolution of Libraries Reflects Power Struggles Over Knowledge: Libraries have historically oscillated between being public and private institutions, reflecting broader societal shifts in who controls access to knowledge. Jessica Talisman highlights how figures like Andrew Carnegie helped establish the modern public library system, reinforcing libraries as democratic spaces where information is accessible to all. However, she also notes that as knowledge becomes digitized, new battles emerge over who owns and controls digital information​​.The Internet Archive Faces Systematic Attacks on Knowledge: Stewart Alsop shares his firsthand experience visiting the Internet Archive just after it had suffered a major cyberattack. This incident is part of a larger trend in which libraries and knowledge repositories worldwide, including those in Canada, have been targeted. The conversation raises concerns that these attacks are not random but part of a broader, well-funded effort to undermine access to information​​.AI and Knowledge Graphs Are Deeply Intertwined: AI systems, particularly large language models (LLMs), rely on structured data sources such as knowledge graphs, ontologies, and linked data. Talisman explains how institutions like the NIH and PubMed provide openly available, structured knowledge that AI systems train on. Yet, she points out a critical gap—AI often lacks alignment with real-world, authoritative sources, which leads to inaccuracies in machine-generated knowledge​​.Libraries Are Moving From Cataloging to Entity Management: Traditional library systems were built around cataloging books and documents, but modern libraries are transitioning toward entity management, which organizes knowledge in a way that allows for more dynamic connections. Linked data and knowledge graphs enable this shift, making it easier to navigate vast repositories of information while maintaining provenance and authority​​.The War on Truth and Information Is Accelerating: The episode touches on the increasing threats to truth and reliable information, from book bans to algorithmic suppression of knowledge. Talisman underscores the crucial role librarians play in preserving access to primary sources and maintaining records of historical truth. As AI becomes more prominent in knowledge dissemination, the need for robust, verifiable sources becomes even more urgent​​.Linked Data is the Foundation of Digital Knowledge: The conversation explores how linked data protocols, such as those championed by Tim Berners-Lee, allow machines and AI to interpret and connect information across the web. Talisman explains that institutions like NIH publish their taxonomies in RDF format, making them accessible as structured, authoritative sources. However, many organizations fail to leverage this interconnected data, leading to inefficiencies in knowledge management​​.Preserving Digital Memory is a Civilization-Defining Challenge: In the digital age, the loss of information is more severe than ever. Alsop compares the current state of digital impermanence to the Dark Ages, where crucial knowledge risks disappearing due to corporate decisions, cyberattacks, and lack of preservation infrastructure. Talisman agrees, emphasizing that digital archives like the Internet Archive, WorldCat, and Wikimedia are foundational to maintaining a collective human memory​​.

Mark Weinstein, a pioneer in social media, shares his journey from creating one of the first social networks to leading the fight for ethical tech. In this eye-opening conversation, he discusses privacy, leadership, and the importance of human connection in the digital age.00:11- About Mark WeinsteinMark Weinstein is a world-renowned tech entrepreneur, contemporary thought leader, privacy expert, and one of the visionary inventors of social networking.He's the author of "Restoring Our Sanity Online", endorsed by Steve Wozniak (Woz) and Sir Tim Berners-Lee. 

Have you ever felt like success, love, or happiness was just out of your reach? Do you feel like there's something bigger waiting for you, but you're not sure how to grasp it? On our Love University podcast, we explored what it means to step into your Invincible Self—and achieve your dreams—not by forcing change overnight, but by making small, meaningful shifts that open doors you never knew existed. Here are 8 powerful ways to unlock your unstoppable success in 2025: The Thing You Seek Is Seeking You What if your biggest desires—love, success, purpose—are also looking for you? Consider Sara Blakely, the founder of Spanx. With only $5,000, she noticed a problem (uncomfortable shapewear) and realized the solution was calling her just as much as she was searching for it. The same happened with Tim Berners-Lee, who invented the World Wide Web—his vision for a connected world was something humanity was already yearning for. The Dark Room: Desire Versus Resignation Imagine standing in a pitch-black room filled with everything you need, but you can't see it. You fumble for a light switch but come up empty. Frustrated, you think, maybe I should just accept the darkness. Then a thought hits you: What if the switch isn't on the wall? You feel around, find a button on the floor, press it—and suddenly, light floods the room.  You see everything you need. Do You Want It as Much as a Dying Person Wants Life? True desire is intense. Imagine someone fighting to survive—they don't hesitate, doubt, or give up. They fight with everything they have. That's the level of passion you need for your goals. Be the Thing You Long For If you want love, be loving. If you want success, act as if you're already successful. The moment you embody what you seek, the world starts reflecting it back to you. Lift Your Mind Above Effort and Resistance Many people struggle because they fight against life instead of flowing with it. Imagine trying to swim upstream—it's exhausting and gets you nowhere. Now, picture letting go and allowing the current to carry you. When you do this, love, happiness, and success will surely flow to you. Attract High-Value Relationships Your relationships are a direct reflection of your energy. If you radiate confidence, kindness, and self-worth, you'll attract people who have the same qualities. Now your relationships become your golden treasure. Search for Worthier Prizes Sometimes, failure is just a redirection to something better. Consider Lady Gaga who was dropped by her first record label after only three months. Devastated, but determined, she refined her artistry and soon became one of the biggest pop stars in the world. Reverse the Desire Not every desire is meant for you—and that's okay. Sometimes, the greatest act of self-love is letting go. Holding on to something that isn't aligned with your true path—whether it's a relationship, career, or outdated dream—only blocks the right opportunities from finding you. When you release what no longer serves you, you create space for something far greater to take its place. Remember this: What you seek is also seeking you. Align your energy with your desires, and opportunities will follow. Even when life feels like a Dark Room, keep searching—the light switch is there. Success, love, and happiness require full commitment. Sometimes setbacks are actually redirections toward something better, but you must be willing to let go of what no longer serves you. The moment you fully embrace your worth, act with purpose, and let go of what doesn't belong to you, you will naturally attract the success, love, and joy that were always meant for you. Here's to your Invincible Year.

ICYMI (there were problems with the site mid-week), check out my forecasts for 2025, always one of my more popular pieces of the year.He has invented an entirely new digital system of money with the potential to change the world as we know it. He has watched it grow to a market cap of over two trillion dollars, with as many as 100 million users worldwide, including actual nations, and the US President promising a strategic bitcoin reserve in his 2024 election campaign. He has half the internet nosing about and trying to figure out who he is. His own coins are worth about $100 billion, making him one of the richest people on earth.Yet he has managed to stay completely unknown and anonymous. It is almost unbelievable.Never mind Big Foot, the Mary Rose or the Loch Ness Monster, the mystery of ‘Who is Satoshi Nakamoto?' is perhaps the greatest mystery the world has ever known - or not known.There have been thousands of investigative attempts, articles, blog posts and discussion groups involving probably millions of man hours dedicated to pinning down this man, with names bandied about from Elon Musk to little known computer scientists. They have all failed. Satoshi's identity is as bulletproof as his code.For my 2014 book, Bitcoin: the Future of Money?, from which today's piece is taken, I ventured on the same doomed journey. I spent many months poring over the 80,000 words Satoshi wrote in the three years he was active online, looking for clues. What unusual words did he use? Does he make any spelling mistakes? Does he have any quirky grammatical habits? I analysed it in such detail I can tell you where he places brackets, how he uses hyphens, even how many spaces he uses after a full stop and how that changed – all in the hope of finding idiosyncrasies that appear in the writing of other Cypherpunks - clues which might lead me to him.Profiling a genius – some broad brushstrokes‘I've had the good fortune to know many brilliant people over the course of my life, so I recognize the signs.' Hal FinneySatoshi reached such high levels of expertise in so many different fields that many believe he can't possibly be one person. He is a polymath. It is not just the breadth and depth of his knowledge, but, more importantly, its specificity that makes him unique.In order to first conceive a new system of electronic cash, one would have to have thought extensively about the nature of money and its history. Money is a subject that has found more interest in the last few years with the emergence of bitcoin, the 2000s bull market in gold, the financial crisis and the growth of libertarianism, but, in 2007–8, when bitcoin was conceived and first introduced, books and academic papers on the subject were few and far between. The subject did not have broad appeal.How many of those who cared actually had the ability to design a system like this? It is one thing declaring what needs to be done; it is another putting it into practice.Satoshi must have had expertise in computer coding, mathematics, databases, accounting, peer-to-peer systems, digital ownership, law, smart contracts, cryptography and monetary history.He had to have had experience in academia. The act of submitting a white paper, its presentation, the impeccable referencing – it all denotes academia, even government.It's also easy to infer from the way bitcoin was launched that Satoshi had experience in open-source tech start-ups.The resilience of the code suggests he had computer hacking experience. Moreover, his ability to keep his identity hidden, despite the fact that half the internet is trying to figure out who he is, suggests significant practical experience in staying anonymous. It also means he has the trust of those who know him, if anyone did, to keep his secret.Then there's the matter of his prose. It is consistent and of such a high standard it seems he must have had experience as a writer – perhaps he was a blogger, an academic or an author. He was also quite humble and dismissive of his ability in this regard. ‘I'm better with code than with words', he said.It's clear from his posts that he had the awareness to see shortcomings in his system, and the patience not to try to do too much too quickly. He had the foresight to perceive problems before they arose and the meticulousness to prepare for them. He appears to have remained calm and measured in the face of difficulty, but also of his own success. He treated those two imposters just the same. Signs of arrogance are hard to find.Then there's the way that bitcoin was introduced to the world. PR, like economics, is not an exact science. Sometimes something gains traction, sometimes it doesn't – and there's no explaining why. Bitcoin has been a PR masterstroke. The coverage it has received has been enormous. It gets more publicity than gold, which is the oldest form of money there is. Satoshi cannot take all of the credit for this, but he has to take some of it. He understood when to make his ideas known, at what point to release his creation into the open-source world and he had the self-efacement to let go of it for others to develop. He promoted his idea with huge under-statement – but the scheduled creation of bitcoins meant there would be no shortage of bitcoin-holders to do the promoting for him.So we can add an understanding of both PR and psychology to his list of qualities. His knowledge of how people on the internet, in the open source world and in large institutions work, allowed him to progress his creation.Finally, he has a certain honesty. Despite Bitcoin's similarities to a pyramid or Ponzi scheme, he never pumped-and- dumped his creation. Tempting though it must have been, he never sold the bitcoins he mined. That also suggests he already had money.There are not many people like this.From mathematics to computer programming to economics and monetary history to politics to PR and psychology to cryptography to business acumen and vision to plain old written English – in all of these fields he excelled. To cap it all, he's probably good-looking too.It's early in history to be drawing this sort of comparison, I know, but there are many parallels between Satoshi and Isaac Newton. Newton was a brilliant scientist and mathematician, of course, and an alchemist. But he was also Master of the Royal Mint. He redesigned England's monetary system, putting us onto the gold standard on which Britain's colossal progress during the next 200 years was built.If you haven't already, take a look at my buddy Charlie Morris's monthly gold report, Atlas Pulse. It is, in my view, the best gold newsletter out there, and, best of all, it's free. Sign up here.First instinctMany believe that Satoshi was Hal Finney, the veteran programmer, who invented reusable proof of works, one of the models on which bitcoin was based. This was my first instinct. Often such “first instincts”, for reasons I cannot begin to explain, prove correct. When Satoshi first announced bitcoin on the cryptography mailing list, nobody replied. The message was ignored for two days. In the short-attention-span land of the web, two days is a long time to wait for some feedback on something you've spent 18 months working on. Two days is a long time to wait when you might have nailed something Cypherpunks had been dreaming about for 20 years.The first reply came from Finney. Was he replying to himself in order to generate some interest and discussion – to bump his thread? Replying to your own posts, known as ‘sock-puppeting', is not uncommon. Let us pursue this line of thinking a little further.Finney was born in 1956 – in that same two-year golden window as so many computer-scientist geniuses that would change the world (from Bill Gates to Tim Berners-Lee to Steve Jobs) were born – and spent his life working on cryptographic systems. He was number two to Phil Zimmerman, the pioneer in the field, for many years at the Pretty Good Privacy (PGP) Corporation, where they developed the most widely used email encryption software in the world.Such were his beliefs in privacy, freedom, and Cypherpunk, Finney was known to spend many nights writing and developing code for free, just because he believed in the work.In 1993, he published the paper, ‘Detecting Double-Spending'. Solving the double-spending problem (ensuring the same money cannot be used twice) was, of course, the key problem with digital cash. It was what Satoshi was so excited about when he proposed Bitcoin. In 2004, Finney developed the ‘reusable proof-of-work' (RPOW) system, which coders regarded as a brilliant step forward – but his system never saw any economic use until b itcoin.Finney is one of the few people to have the background and expertise to have developed bitcoin – but he is also an obvious person to take an immediate interest.In his very first reply to Satoshi's announcement, he wrote:“As an amusing thought experiment, imagine that Bitcoin is successful and becomes the dominant payment system in use throughout the world. Then the total value of the currency should be equal to the total value of all the wealth in the world. Current estimates of total worldwide household wealth that I have found range from $100 trillion to $300 trillion. With 20 million coins, that gives each coin a value of about $10 million.”The comment shows extraordinary insight. Many now see this “amusing thought experiment” as inevitable. But could it also be somebody trying to get others excited? Very possibly.(By the way, ‘thought experiment' is an expression Satoshi himself uses – though it is not uncommon in coding circles).Of the many names touted as Satoshi, Finney's writing style is one of the few that match. The major difference is Satoshi used British spelling and Finney does not. There is a similar calm, understated tone, similar use of language, similar punctuation habits: two spaces after a full stop. In stylometrics tests carried out by John Noecker Jr., chief scientific officer at text analysis experts Juola & Associates, Finney consistently scored high. (However, veteran cypherpunk blogger, Nick Szabo, scored higher). Then I noticed both Finney and Satoshi had ‘@gmx.com' email addresses. (GMX is a free email provider based in Germany. Many Germans use GMX, while Americans and British tend to gravitate towards Gmail, Hotmail, or Yahoo. Today they would probably gravitate towards P rotonmail). Was this just coincidence – or was it a clue?Why did Satoshi disappear?In December 2010, Satoshi made his final post and then disappeared from the internet.Why?Perhaps to protect his anonymity in the face of rising interest from the media and, more significantly, the authorities: to protect his own safety as the WikiLeaks panic began to erupt. (After Wikileaks was shut out of the financial system, many began sending it bitcoin. The effect, ironically, was thus to make it an extraordinarily wealthy organisation).But there is also the possibility that he disappeared because he was ill.In 2009, Finney was diagnosed with Lou Gehrig's disease – amyotrophic lateral sclerosis – the same disease from which Stephen Hawking suffered. It is, for the most part, fatal and claims its victims within two to five years. ‘My symptoms were mild at first,' he says, ‘and I continued to work, but fatigue and voice problems forced me to retire in early 2011. Since then the disease has continued its inexorable progression.' Finney, eventually died in August 2014.In March 2013 he said, ‘Today, I am essentially paralyzed. I am fed through a tube, and my breathing is assisted through another tube. I operate the computer using a commercial eye-tracker system. It also has a speech synthesizer, so this is my voice now. I spend all day in my power wheelchair. I worked up an interface using an Arduino so that I can adjust my wheelchair's position using my eyes. It has been an adjustment, but my life is not too bad. I can still read, listen to music, and watch TV and movies. I recently discovered that I can even write code. It's very slow, probably 50 times slower than I was before. But I still love programming and it gives me goals.'Could a terrible illness be the reason Satoshi withdrew?Finney was one of the first to mine bitcoins. What did he do with them?I mined several blocks over the next days. But I turned it off because it made my computer run hot, and the fan noise bothered me. In retrospect, I wish I had kept it up longer, but on the other hand, I was extraordinarily lucky to be there at the beginning. It's one of those glass half full, half empty things.The next I heard of Bitcoin was late 2010, when I was surprised to find that it was not only still going, bitcoins actually had monetary value. I dusted off my old wallet, and was relieved to discover that my bitcoins were still there. As the price climbed up to real money, I transferred the coins into an offline wallet, where hopefully they'll be worth something to my heirs. Those discussions about inheriting your bitcoins are of more than academic interest. My bitcoins are stored in our safe deposit box, and my son and daughter are tech-savvy. I think they're safe enough. I'm comfortable with my legacy.Finney sold many of his bitcoins in order to pay for medical care, many at around $100. Satoshi never moved his.If you are buying gold to protect yourself in these uncertain times, I recommend The Pure Gold Company. Pricing is competitive, quality of service is high. They deliver to the UK, the US, Canada and Europe or you can store your gold with them. More here.We are all SatoshiFinney was a key player in the development of Bitcoin, no doubt. He was one of the first to ask real questions. He managed to understand from the start the inner workings of the Bitcoin protocol and its potential. He explored the weaknesses in the Bitcoin code – one of them is even named 'the Finney Attack'. He had many exchanges with Satoshi on the Bitcoin forums as they progressed the code and developed new versions. He asked question after question. But these very exchanges show there were two people talking. On January 10th, 2009, for example, Finney publicly complained to Satoshi that Bitcoin had crashed when he tried to receive a transaction. If it was his own code, and he was transacting with himself, he would surely have quietly fixed it himself.Moreover, coders all agree that Finney's coding style – and the style of the comments written in the code – is different from Satoshi's. Also, Finney preferred to code in the language C, whereas Bitcoin is coded in C++. This is something Finney himself confirms: 'I've done some changes to the Bitcoin code, and my style is completely different from Satoshi's. I program in C, which is compatible with C++, but I don't understand the tricks that Satoshi used.'Shortly before the publication of this book, the Forbes journalist Andy Greenberg published an interview with Hal Finney. Finney was now too ill to even speak – he could only raise his eyebrows to say yes. His son showed Greenberg fifteen email exchanges between Satoshi and Finney from January 2009. They mainly focused on bugs Finney had found in the code, to which Satoshi replied with fixes - and notes of thanks. Greenberg was also shown Finney's bitcoin wallet – with the transfers between Satoshi and Finney made back in 2009. As Greenberg notes, the wallet evidence and the Gmail timestamps in the emails would have been hard to forge. To cap it all, there is the fact that in 2009, at precisely the same moment Satoshi sent time-stamped e-mails, Finney, a keen runner, was photographed in the middle of a ten-mile race. Nobody, not even Satoshi Nakamoto, can be in two places at once.Bitcoin could not have happened without the work of Finney.If Satoshi Nakamoto was several people, Finney might have been one of them. But if Satoshi is an individual, Hal Finney was not him. This is an extract from my 2014 book, Bitcoin: the Future of Money? I hear the audiobook's excellent. ;)If you missed them (there were problems with the site midweek), check out my forecasts for 2025. This is a public episode. If you'd like to discuss this with other subscribers or get access to bonus episodes, visit www.theflyingfrisby.com/subscribe

Time stamps: Introducing Mike Belshe (00:00:42) Mike Belshe's Background (00:01:58) Self-Custody vs. Institutional Custody (00:02:05) Multi-Signature Technology (00:03:56) Understanding Multi-Party Computation (00:04:51) Advancements in Cryptography (00:05:53) BitGo's Role in Tokenizing Bitcoin (00:08:26) Defining DeFi's Importance (00:09:09) Mike's Technology Background (00:12:12) Inspiration from Tim Berners-Lee (00:14:57) Bitcoin's Zero Click Payments (00:17:11) Bitcoin Custodianship Issues (00:17:36) Challenges of Bitcoin Payments (00:18:25) Scaling Bitcoin and Lightning Network (00:19:20) Bitcoin's Role in Digital Money (00:20:13) Layer Two Solutions and Drivechains (00:21:15) Scaling Discussions in Bitcoin's History (00:22:31) Sidechains and Their Limitations (00:23:16) Innovation vs. Immutability (00:24:29) Importance of Real Applications (00:25:32) Privacy and Fungibility in Bitcoin (00:28:42) Lessons from TCP/IP and Blockchain Privacy (00:30:51) Regulatory Concerns and Privacy Solutions (00:32:53) Understanding the Static of Security (00:34:01) SideShift (00:34:59) Bitcoin's Civil War: Block Size Wars (00:35:54) Human Decisions in Bitcoin (00:36:16) Historical Proposals and Interpretations (00:37:10) Challenges of Block Space and Fees (00:37:58) Bitcoin Consensus (00:38:48) SegWit and Its Implications (00:39:41) Gavin Andresen's Role in Bitcoin (00:42:00) Bitcoin's Resilience Against Adversaries (00:42:13) Need for Enhanced Security (00:43:05) Strategic Bitcoin Reserve in the USA (00:44:30) El Salvador's Currency Strategy (00:45:19) Self-Custody Concerns (00:49:13) Security Measures for Self-Custody (00:50:17) Privacy as a Solution (00:50:43) Self-Custody Options (00:51:14) Family Legacy and Custody Challenges (00:52:24) Public Key Cryptography Innovation (00:52:28) HODLING.ch (00:53:29) Protecting Against Government Confiscation (00:54:15) Multi-Custodial Model Explanation (00:54:21) Hardware Wallets Discussion (00:56:03) Safety Deposit Box Concerns (00:58:03) Trade-offs in Security Solutions (00:58:56) Onboarding New Users (01:00:09) Edge Wallet Features (01:01:01) BitGo's Wallet Recovery Wizard (01:03:02) BitGo vs. Casa (01:05:08) Multi-Signature Security (01:05:46) Early Adoption of Multi-Sig (01:09:10) Building a New Monetary System (01:11:54) Regulatory Changes in the US (01:13:49) Impact of MiCA in Europe (01:15:32) War on Cash (01:16:17) Global Financial Systems (01:18:03) Zero Knowledge Proofs (01:19:48) Zcash Discussion (01:20:04) Privacy Technologies in Bitcoin (01:21:18) Challenges of On-chain Traceability (01:22:26) Philosophy on Transaction Privacy (01:23:19) Concerns About Privacy Adoption (01:24:51) Historical Context of TCP/IP Security (01:25:34) Bitcoin as Digital Gold (01:27:24) Ethereum's Role in DeFi (01:29:01) Benefits of Smart Contracts (01:32:01) Reflections on Bitcoin's Journey (01:33:25) Future of Bitcoin (01:34:30) Lightning Network Fees (01:36:12) Trade-offs in Payment Systems (01:38:01) Adoption of Bitcoin and Early Adoption Costs (01:42:01) Long-term Viability of Bitcoin Mining (01:44:38) The Future of Bitcoin and Layer Solutions (01:47:17) Community Response to Bitcoin Vulnerabilities (01:49:01) Satoshi's Vision for Mining (01:51:11) Satoshi's Intentions (01:52:35) Empathy for Satoshi (01:54:16) 0 to 1 Concept (01:54:24) Bitcoin's Anniversary (01:55:53) Centralization in Crisis (01:56:33) Zero Knowledge Proof Bug (01:57:45) Following Mike Belshe's Work (01:58:45)

====================================================SUSCRIBETEhttps://www.youtube.com/channel/UCNpffyr-7_zP1x1lS89ByaQ?sub_confirmation=1==================================================== DEVOCIÓN MATUTINA PARA JÓVENES 2025“HOY ES TENDENCIA”Narrado por: Daniel RamosDesde: Connecticut, USAUna cortesía de DR'Ministries y Canaan Seventh-Day Adventist Church ===================|| www.drministries.org ||===================01 DE ENEROUNA BARRA EN BLANCO «Busquen al Señor mientras puedan encontrarlo, llámenlo mientras está cercano». Isaías 55: 6Todo comenzó un día como hoy, el 1 de enero de 1990, cuando Tim Berners-Lee transformo el mundo de manera irreversible al presentar la world wide web, comúnmente abreviada como www. Este sistema es el que nos permite acceder a la información alojada en internet.Hoy en día, internet se ha vuelto indispensable para la mayoría de nosotros, facilitándonos el acceso a noticias, estudios, comunicación, compras, ventas e incluso el enamoramiento. Cuando Tim Berners-Lee creó el primer "buscador", era imperativo agregar el prefijo "www" antes del nombre de la página. En la actualidad, esta práctica ha quedado obsoleta, pero al ingresar a Internet, aún debemos especificar el tipo de contenido que buscamos.No importa si utilizas Chrome, Firefox o Safari; al abrir tu navegador, te enfrentas a una barra en blanco cuyos resultados dependen de lo que ingreses en ella. Con solo unas pocas palabras, puedes acceder a un portal de noticias, a una universidad en línea, a una plataforma de videos o incluso a sitios de entretenimiento adulto o juegos de azar. Lo que escribas en esa "barra en blanco" marcará la diferencia y determinará si decides dedicarte a una carrera universitaria o pasas cinco horas viendo memes o reels, si optas por aprender un nuevo idioma o si te involucras en actividades cibernéticas ilegales.El comienzo de un nuevo año es equiparable a iniciar una nueva búsqueda en Internet. Hoy, como si Dios te proporcionara un "navegador" nuevo con 365 "pestañas", cada una de ellas presenta una "barra de búsqueda" completamente en blanco. ¿Qué escribirás en ellas? ¿Qué contenido buscarás? Tu éxito o fracaso este año dependerá de lo que vayas ingresando en cada barra a medida que avance el tiempo.Al iniciar cada nuevo año, se nos brinda la oportunidad de decidir qué es lo que buscaremos: una profesión, empleo, pareja, salud, éxito, riquezas, poder, influencia, fama... Las opciones son variadas, pero la primera frase que deberíamos ingresar en esta nueva barra de nuestra vida es aquella que repiten los antiguos profetas hebreos: «Busquen al Señor» (Isaías 55: 6). ¿Y qué pasará si buscamos a Dios cada día de este año que hoy comienza? Dios dice: «Los que me buscan, me encontrarán» (Proverbios 8: 17, NTV). Hoy te puedo asegurar que cuando lo encontramos a él, encontramos la vida (Amós 5:6). 

Text messages on our phones are so easy to use and so common that it's all too easy to forget how useful they are to scammers. Every text message should be treated with suspicion. In Short Circuits: Recently I needed to format a 64GB thumb drive using FAT32, one of the older formatting types. The Windows formatting tool won't allow it, so maybe you think the FAT32 limit is 32GB. It's not and formatting the large drive turned out to be refreshingly easy. • Sometimes I wonder if Tim Berners-Lee or Marc Andreessen had any idea, in the late 1980s and early 1990s, that the browsers they were developing to view simple text files would expand and virtually take over the world.

The full schedule for Latent Space LIVE! at NeurIPS has been announced, featuring Best of 2024 overview talks for the AI Startup Landscape, Computer Vision, Open Models, Transformers Killers, Synthetic Data, Agents, and Scaling, and speakers from Sarah Guo of Conviction, Roboflow, AI2/Meta, Recursal/Together, HuggingFace, OpenHands and SemiAnalysis. Join us for the IRL event/Livestream! Alessio will also be holding a meetup at AWS Re:Invent in Las Vegas this Wednesday. See our new Events page for dates of AI Engineer Summit, Singapore, and World's Fair in 2025. LAST CALL for questions for our big 2024 recap episode! Submit questions and messages on Speakpipe here for a chance to appear on the show!When we first observed that GPT Wrappers are Good, Actually, we did not even have Bolt on our radar. Since we recorded our Anthropic episode discussing building Agents with the new Claude 3.5 Sonnet, Bolt.new (by Stackblitz) has easily cleared the $8m ARR bar, repeating and accelerating its initial $4m feat.There are very many AI code generators and VS Code forks out there, but Bolt probably broke through initially because of its incredible zero shot low effort app generation:But as we explain in the pod, Bolt also emphasized deploy (Netlify)/ backend (Supabase)/ fullstack capabilities on top of Stackblitz's existing WebContainer full-WASM-powered-developer-environment-in-the-browser tech. Since then, the team has been shipping like mad (with weekly office hours), with bugfixing, full screen, multi-device, long context, diff based edits (using speculative decoding like we covered in Inference, Fast and Slow).All of this has captured the imagination of low/no code builders like Greg Isenberg and many others on YouTube/TikTok/Reddit/X/Linkedin etc:Just as with Fireworks, our relationship with Bolt/Stackblitz goes a bit deeper than normal - swyx advised the launch and got a front row seat to this epic journey, as well as demoed it with Realtime Voice at the recent OpenAI Dev Day. So we are very proud to be the first/closest to tell the full open story of Bolt/Stackblitz!Flow Engineering + Qodo/AlphaCodium UpdateIn year 2 of the pod we have been on a roll getting former guests to return as guest cohosts (Harrison Chase, Aman Sanger, Jon Frankle), and it was a pleasure to catch Itamar Friedman back on the pod, giving us an update on all things Qodo and Testing Agents from our last catchup a year and a half ago:Qodo (they renamed in September) went viral in early January this year with AlphaCodium (paper here, code here) beating DeepMind's AlphaCode with high efficiency:With a simple problem solving code agent:* The first step is to have the model reason about the problem. They describe it using bullet points and focus on the goal, inputs, outputs, rules, constraints, and any other relevant details.* Then, they make the model reason about the public tests and come up with an explanation of why the input leads to that particular output. * The model generates two to three potential solutions in text and ranks them in terms of correctness, simplicity, and robustness. * Then, it generates more diverse tests for the problem, covering cases not part of the original public tests. * Iteratively, pick a solution, generate the code, and run it on a few test cases. * If the tests fail, improve the code and repeat the process until the code passes every test.swyx has previously written similar thoughts on types vs tests for putting bounds on program behavior, but AlphaCodium extends this to AI generated tests and code.More recently, Itamar has also shown that AlphaCodium's techniques also extend well to the o1 models:Making Flow Engineering a useful technique to improve code model performance on every model. This is something we see AI Engineers uniquely well positioned to do compared to ML Engineers/Researchers.Full Video PodcastLike and subscribe!Show Notes* Itamar* Qodo* First episode* Eric* Bolt* StackBlitz* Thinkster* AlphaCodium* WebContainersChapters* 00:00:00 Introductions & Updates* 00:06:01 Generic vs. Specific AI Agents* 00:07:40 Maintaining vs Creating with AI* 00:17:46 Human vs Agent Computer Interfaces* 00:20:15 Why Docker doesn't work for Bolt* 00:24:23 Creating Testing and Code Review Loops* 00:28:07 Bolt's Task Breakdown Flow* 00:31:04 AI in Complex Enterprise Environments* 00:41:43 AlphaCodium* 00:44:39 Strategies for Breaking Down Complex Tasks* 00:45:22 Building in Open Source* 00:50:35 Choosing a product as a founder* 00:59:03 Reflections on Bolt Success* 01:06:07 Building a B2C GTM* 01:18:11 AI Capabilities and Pricing Tiers* 01:20:28 What makes Bolt unique* 01:23:07 Future Growth and Product Development* 01:29:06 Competitive Landscape in AI Engineering* 01:30:01 Advice to Founders and Embracing AI* 01:32:20 Having a baby and completing an Iron ManTranscriptAlessio [00:00:00]: Hey everyone, welcome to the Latent Space Podcast. This is Alessio, partner and CTO at Decibel Partners, and I'm joined by my co-host Swyx, founder of Smol.ai.Swyx [00:00:12]: Hey, and today we're still in our sort of makeshift in-between studio, but we're very delighted to have a former returning guest host, Itamar. Welcome back.Itamar [00:00:21]: Great to be here after a year or more. Yeah, a year and a half.Swyx [00:00:24]: You're one of our earliest guests on Agents. Now you're CEO co-founder of Kodo. Right. Which has just been renamed. You also raised a $40 million Series A, and we can get caught up on everything, but we're also delighted to have our new guest, Eric. Welcome.Eric [00:00:42]: Thank you. Excited to be here. Should I say Bolt or StackBlitz?Swyx [00:00:45]: Like, is it like its own company now or?Eric [00:00:47]: Yeah. Bolt's definitely bolt.new. That's the thing that we're probably the most known for, I imagine, at this point.Swyx [00:00:54]: Which is ridiculous to say because you were working at StackBlitz for so long.Eric [00:00:57]: Yeah. I mean, within a week, we were doing like double the amount of traffic. And StackBlitz had been online for seven years, and we were like, what? But anyways, yeah. So we're StackBlitz, the company behind bolt.new. If you've heard of bolt.new, that's our stuff. Yeah.Swyx [00:01:12]: Yeah.Itamar [00:01:13]: Excellent. I see, by the way, that the founder mode, you need to know to capture opportunities. So kudos on doing that, right? You're working on some technology, and then suddenly you can exploit that to a new world. Yeah.Eric [00:01:24]: Totally. And I think, well, not to jump, but 100%, I mean, a couple of months ago, we had the idea for Bolt earlier this year, but we haven't really shared this too much publicly. But we actually had tried to build it with some of those state-of-the-art models back in January, February, you can kind of imagine which, and they just weren't good enough to actually do the code generation where the code was accurate and it was fast and whatever have you without a ton of like rag, but then there was like issues with that. So we put it on the shelf and then we got kind of a sneak peek of some of the new models that have come out in the past couple of months now. And so once we saw that, once we actually saw the code gen from it, we were like, oh my God, like, okay, we can build a product around this. And so that was really the impetus of us building the thing. But with that, it was StackBlitz, the core StackBlitz product the past seven years has been an IDE for developers. So the entire user experience flow we've built up just didn't make sense. And so when we kind of went out to build Bolt, we just thought, you know, if we were inventing our product today, what would the interface look like given what is now possible with the AI code gen? And so there's definitely a lot of conversations we had internally, but you know, just kind of when we logically laid it out, we were like, yeah, I think it makes sense to just greenfield a new thing and let's see what happens. If it works great, then we'll figure it out. If it doesn't work great, then it'll get deleted at some point. So that's kind of how it actually came to be.Swyx [00:02:49]: I'll mention your background a little bit. You were also founder of Thinkster before you started StackBlitz. So both of you are second time founders. Both of you have sort of re-founded your company recently. Yours was more of a rename. I think a slightly different direction as well. And then we can talk about both. Maybe just chronologically, should we get caught up on where Kodo is first and then you know, just like what people should know since the last pod? Sure.Itamar [00:03:12]: The last pod was two months after we launched and we basically had the vision that we talked about. The idea that software development is about specification, test and code, etc. We are more on the testing part as in essence, we think that if you solve testing, you solve software development. The beautiful chart that we'll put up on screen. And testing is a really big field, like there are many dimensions, unit testing, the level of the component, how big it is, how large it is. And then there is like different type of testing, is it regression or smoke or whatever. So back then we only had like one ID extension with unit tests as in focus. One and a half year later, first ID extension supports more type of testing as context aware. We index local, local repos, but also 10,000s of repos for Fortune 500 companies. We have another agent, another tool that is called, the pure agent is the open source and the commercial one is CodoMerge. And then we have another open source called CoverAgent, which is not yet a commercial product coming very soon. It's very impressive. It could be that already people are approving automated pull requests that they don't even aware in really big open sources. So once we have enough of these, we will also launch another agent. So for the first one and a half year, what we did is grew in our offering and mostly on the side of, does this code actually works, testing, code review, et cetera. And we believe that's the critical milestone that needs to be achieved to actually have the AI engineer for enterprise software. And then like for the first year was everything bottom up, getting to 1 million installation. 2024, that was 2023, 2024 was starting to monetize, to feel like how it is to make the first buck. So we did the teams offering, it went well with a thousand of teams, et cetera. And then we started like just a few months ago to do enterprise with everything you need, which is a lot of things that discussed in the last post that was just released by Codelm. So that's how we call it at Codelm. Just opening the brackets, our company name was Codelm AI, and we renamed to Codo and we call our models Codelm. So back to my point, so we started Enterprise Motion and already have multiple Fortune 100 companies. And then with that, we raised a series of $40 million. And what's exciting about it is that enables us to develop more agents. That's our focus. I think it's very different. We're not coming very soon with an ID or something like that.Swyx [00:06:01]: You don't want to fork this code?Itamar [00:06:03]: Maybe we'll fork JetBrains or something just to be different.Swyx [00:06:08]: I noticed that, you know, I think the promise of general purpose agents has kind of died. Like everyone is doing kind of what you're doing. There's Codogen, Codomerge, and then there's a third one. What's the name of it?Itamar [00:06:17]: Yeah. Codocover. Cover. Which is like a commercial version of a cover agent. It's coming soon.Swyx [00:06:23]: Yeah. It's very similar with factory AI, also doing like droids. They all have special purpose doing things, but people don't really want general purpose agents. Right. The last time you were here, we talked about AutoGBT, the biggest thing of 2023. This year, not really relevant anymore. And I think it's mostly just because when you give me a general purpose agent, I don't know what to do with it.Eric [00:06:42]: Yeah.Itamar [00:06:43]: I totally agree with that. We're seeing it for a while and I think it will stay like that despite the computer use, et cetera, that supposedly can just replace us. You can just like prompt it to be, hey, now be a QA or be a QA person or a developer. I still think that there's a few reasons why you see like a dedicated agent. Again, I'm a bit more focused, like my head is more on complex software for big teams and enterprise, et cetera. And even think about permissions and what are the data sources and just the same way you manage permissions for users. Developers, you probably want to have dedicated guardrails and dedicated approvals for agents. I intentionally like touched a point on not many people think about. And of course, then what you can think of, like maybe there's different tools, tool use, et cetera. But just the first point by itself is a good reason why you want to have different agents.Alessio [00:07:40]: Just to compare that with Bot.new, you're almost focused on like the application is very complex and now you need better tools to kind of manage it and build on top of it. On Bot.new, it's almost like I was using it the other day. There's basically like, hey, look, I'm just trying to get started. You know, I'm not very opinionated on like how you're going to implement this. Like this is what I want to do. And you build a beautiful app with it. What people ask as the next step, you know, going back to like the general versus like specific, have you had people say, hey, you know, this is great to start, but then I want a specific Bot.new dot whatever else to do a more vertical integration and kind of like development or what's the, what do people say?Eric [00:08:18]: Yeah. I think, I think you kind of hit the, hit it head on, which is, you know, kind of the way that we've, we've kind of talked about internally is it's like people are using Bolt to go from like 0.0 to 1.0, like that's like kind of the biggest unlock that Bolt has versus most other things out there. I mean, I think that's kind of what's, what's very unique about Bolt. I think the, you know, the working on like existing enterprise applications is, I mean, it's crazy important because, you know, there's a, you look, when you look at the fortune 500, I mean, these code bases, some of these have been around for 20, 30 plus years. And so it's important to be going from, you know, 101.3 to 101.4, et cetera. I think for us, so what's been actually pretty interesting is we see there's kind of two different users for us that are coming in and it's very distinct. It's like people that are developers already. And then there's people that have never really written software and more if they have, it's been very, very minimal. And so in the first camp, what these developers are doing, like to go from zero to one, they're coming to Bolt and then they're ejecting the thing to get up or just downloading it and, you know, opening cursor, like whatever to, to, you know, keep iterating on the thing. And sometimes they'll bring it back to Bolt to like add in a huge piece of functionality or something. Right. But for the people that don't know how to code, they're actually just, they, they live in this thing. And that was one of the weird things when we launched is, you know, within a day of us being online, one of the most popular YouTube videos, and there's been a ton since, which was, you know, there's like, oh, Bolt is the cursor killer. And I originally saw the headlines and I was like, thanks for the views. I mean, I don't know. This doesn't make sense to me. That's not, that's not what we kind of thought.Swyx [00:09:44]: It's how YouTubers talk to each other. Well, everything kills everything else.Eric [00:09:47]: Totally. But what blew my mind was that there was any comparison because it's like cursor is a, is a local IDE product. But when, when we actually kind of dug into it and we, and we have people that are using our product saying this, I'm not using cursor. And I was like, what? And it turns out there are hundreds of thousands of people that we have seen that we're using cursor and we're trying to build apps with that where they're not traditional software does, but we're heavily leaning on the AI. And as you can imagine, it is very complicated, right? To do that with cursor. So when Bolt came out, they're like, wow, this thing's amazing because it kind of inverts the complexity where it's like, you know, it's not an IDE, it's, it's a, it's a chat-based sort of interface that we have. So that's kind of the split, which is rather interesting. We've had like the first startups now launch off of Bolt entirely where this, you know, tomorrow I'm doing a live stream with this guy named Paul, who he's built an entire CRM using this thing and you know, with backend, et cetera. And people have made their first money on the internet period, you know, launching this with Stripe or whatever have you. So that's, that's kind of the two main, the two main categories of folks that we see using Bolt though.Itamar [00:10:51]: I agree that I don't understand the comparison. It doesn't make sense to me. I think like we have like two type of families of tools. One is like we re-imagine the software development. I think Bolt is there and I think like a cursor is more like a evolution of what we already have. It's like taking the IDE and it's, it's amazing and it's okay, let's, let's adapt the IDE to an era where LLMs can do a lot for us. And Bolt is more like, okay, let's rethink everything totally. And I think we see a few tools there, like maybe Vercel, Veo and maybe Repl.it in that area. And then in the area of let's expedite, let's change, let's, let's progress with what we already have. You can see Cursor and Kodo, but we're different between ourselves, Cursor and Kodo, but definitely I think that comparison doesn't make sense.Alessio [00:11:42]: And just to set the context, this is not a Twitter demo. You've made 4 million of revenue in four weeks. So this is, this is actually working, you know, it's not a, what, what do you think that is? Like, there's been so many people demoing coding agents on Twitter and then it doesn't really work. And then you guys were just like, here you go, it's live, go use it, pay us for it. You know, is there anything in the development that was like interesting and maybe how that compares to building your own agents?Eric [00:12:08]: We had no idea, honestly, like we, we, we've been pretty blown away and, and things have just kind of continued to grow faster since then. We're like, oh, today is week six. So I, I kind of came back to the point you just made, right, where it's, you, you kind of outlined, it's like, there's kind of this new market of like kind of rethinking the software development and then there's heavily augmenting existing developers. I think that, you know, both of which are, you know, AI code gen being extremely good, it's allowed existing developers, it's allowing existing developers to camera out software far faster than they could have ever before, right? It's like the ultimate power tool for an existing developer. But this code gen stuff is now so good. And then, and we saw this over the past, you know, from the beginning of the year when we tried to first build, it's actually lowered the barrier to people that, that aren't traditionally software engineers. But the kind of the key thing is if you kind of think about it from, imagine you've never written software before, right? My co-founder and I, he and I grew up down the street from each other in Chicago. We learned how to code when we were 13 together and we've been building stuff ever since. And this is back in like the mid 2000s or whatever, you know, there was nothing for free to learn from online on the internet and how to code. For our 13th birthdays, we asked our parents for, you know, O'Reilly books cause you couldn't get this at the library, right? And so instead of like an Xbox, we got, you know, programming books. But the hardest part for everyone learning to code is getting an environment set up locally, you know? And so when we built StackBlitz, like kind of the key thesis, like seven years ago, the insight we had was that, Hey, it seems like the browser has a lot of new APIs like WebAssembly and service workers, et cetera, where you could actually write an operating system that ran inside the browser that could boot in milliseconds. And you, you know, basically there's this missing capability of the web. Like the web should be able to build apps for the web, right? You should be able to build the web on the web. Every other platform has that, Visual Studio for Windows, Xcode for Mac. The web has no built in primitive for this. And so just like our built in kind of like nerd instinct on this was like, that seems like a huge hole and it's, you know, it will be very valuable or like, you know, very valuable problem to solve. So if you want to set up that environments, you know, this is what we spent the past seven years doing. And the reality is existing developers have running locally. They already know how to set up that environment. So the problem isn't as acute for them. When we put Bolt online, we took that technology called WebContainer and married it with these, you know, state of the art frontier models. And the people that have the most pain with getting stuff set up locally is people that don't code. I think that's been, you know, really the big explosive reason is no one else has been trying to make dev environments work inside of a browser tab, you know, for the past if since ever, other than basically our company, largely because there wasn't an immediate demand or need. So I think we kind of find ourselves at the right place at the right time. And again, for this market of people that don't know how to write software, you would kind of expect that you should be able to do this without downloading something to your computer in the same way that, hey, I don't have to download Photoshop now to make designs because there's Figma. I don't have to download Word because there's, you know, Google Docs. They're kind of looking at this as that sort of thing, right? Which was kind of the, you know, our impetus and kind of vision from the get-go. But you know, the code gen, the AI code gen stuff that's come out has just been, you know, an order of magnitude multiplier on how magic that is, right? So that's kind of my best distillation of like, what is going on here, you know?Alessio [00:15:21]: And you can deploy too, right?Eric [00:15:22]: Yeah.Alessio [00:15:23]: Yeah.Eric [00:15:24]: And so that's, what's really cool is it's, you know, we have deployment built in with Netlify and this is actually, I think, Sean, you actually built this at Netlify when you were there. Yeah. It's one of the most brilliant integrations actually, because, you know, effectively the API that Sean built, maybe you can speak to it, but like as a provider, we can just effectively give files to Netlify without the user even logging in and they have a live website. And if they want to keep, hold onto it, they can click a link and claim it to their Netlify account. But it basically is just this really magic experience because when you come to Bolt, you say, I want a website. Like my mom, 70, 71 years old, made her first website, you know, on the internet two weeks ago, right? It was about her nursing days.Swyx [00:16:03]: Oh, that's fantastic though. It wouldn't have been made.Eric [00:16:06]: A hundred percent. Cause even in, you know, when we've had a lot of people building personal, like deeply personal stuff, like in the first week we launched this, the sales guy from the East Coast, you know, replied to a tweet of mine and he said, thank you so much for building this to your team. His daughter has a medical condition and so for her to travel, she has to like line up donors or something, you know, so ahead of time. And so he actually used Bolt to make a website to do that, to actually go and send it to folks in the region she was going to travel to ahead of time. I was really touched by it, but I also thought like, why, you know, why didn't he use like Wix or Squarespace? Right? I mean, this is, this is a solved problem, quote unquote, right? And then when I thought, I actually use Squarespace for my, for my, uh, the wedding website for my wife and I, like back in 2021, so I'm familiar, you know, it was, it was faster. I know how to code. I was like, this is faster. Right. And I thought back and I was like, there's a whole interface you have to learn how to use. And it's actually not that simple. There's like a million things you can configure in that thing. When you come to Bolt, there's a, there's a text box. You just say, I need a, I need a wedding website. Here's the date. Here's where it is. And here's a photo of me and my wife, put it somewhere relevant. It's actually the simplest way. And that's what my, when my mom came, she said, uh, I'm Pat Simons. I was a nurse in the seventies, you know, and like, here's the things I did and a website came out. So coming back to why is this such a, I think, why are we seeing this sort of growth? It's, this is the simplest interface I think maybe ever created to actually build it, a deploy a website. And then that website, my mom made, she's like, okay, this looks great. And there's, there's one button, you just click it, deploy, and it's live and you can buy a domain name, attach it to it. And you know, it's as simple as it gets, it's getting even simpler with some of the stuff we're working on. But anyways, so that's, it's, it's, uh, it's been really interesting to see some of the usage like that.Swyx [00:17:46]: I can offer my perspective. So I, you know, I probably should have disclosed a little bit that, uh, I'm a, uh, stack list investor.Alessio [00:17:53]: Canceled the episode. I know, I know. Don't play it now. Pause.Eric actually reached out to ShowMeBolt before the launch. And we, you know, we talked a lot about, like, the framing of, of what we're going to talk about how we marketed the thing, but also, like, what we're So that's what Bolt was going to need, like a whole sort of infrastructure.swyx: Netlify, I was a maintainer but I won't take claim for the anonymous upload. That's actually the origin story of Netlify. We can have Matt Billman talk about it, but that was [00:18:00] how Netlify started. You could drag and drop your zip file or folder from your desktop onto a website, it would have a live URL with no sign in.swyx: And so that was the origin story of Netlify. And it just persists to today. And it's just like it's really nice, interesting that both Bolt and CognitionDevIn and a bunch of other sort of agent type startups, they all use Netlify to deploy because of this one feature. They don't really care about the other features.swyx: But, but just because it's easy for computers to use and talk to it, like if you build an interface for computers specifically, that it's easy for them to Navigate, then they will be used in agents. And I think that's a learning that a lot of developer tools companies are having. That's my bolt launch story and now if I say all that stuff.swyx: And I just wanted to come back to, like, the Webcontainers things, right? Like, I think you put a lot of weight on the technical modes. I think you also are just like, very good at product. So you've, you've like, built a better agent than a lot of people, the rest of us, including myself, who have tried to build these things, and we didn't get as far as you did.swyx: Don't shortchange yourself on products. But I think specifically [00:19:00] on, on infra, on like the sandboxing, like this is a thing that people really want. Alessio has Bax E2B, which we'll have on at some point, talking about like the sort of the server full side. But yours is, you know, inside of the browser, serverless.swyx: It doesn't cost you anything to serve one person versus a million people. It doesn't, doesn't cost you anything. I think that's interesting. I think in theory, we should be able to like run tests because you can run the full backend. Like, you can run Git, you can run Node, you can run maybe Python someday.swyx: We talked about this. But ideally, you should be able to have a fully gentic loop, running code, seeing the errors, correcting code, and just kind of self healing, right? Like, I mean, isn't that the dream?Eric: Totally.swyx: Yeah,Eric: totally. At least in bold, we've got, we've got a good amount of that today. I mean, there's a lot more for us to do, but one of the nice things, because like in web container, you know, there's a lot of kind of stuff you go Google like, you know, turn docker container into wasm.Eric: You'll find a lot of stuff out there that will do that. The problem is it's very big, it's slow, and that ruins the experience. And so what we ended up doing is just writing an operating system from [00:20:00] scratch that was just purpose built to, you know, run in a browser tab. And the reason being is, you know, Docker 2 awesome things will give you an image that's like out 60 to 100 megabits, you know, maybe more, you know, and our, our OS, you know, kind of clocks in, I think, I think we're in like a, maybe, maybe a megabyte or less or something like that.Eric: I mean, it's, it's, you know, really, really, you know, stripped down.swyx: This is basically the task involved is I understand that it's. Mapping every single, single Linux call to some kind of web, web assembly implementation,Eric: but more or less, and, and then there's a lot of things actually, like when you're looking at a dev environment, there's a lot of things that you don't need that a traditional OS is gonna have, right?Eric: Like, you know audio drivers or you like, there's just like, there's just tons of things. Oh, yeah. Right. Yeah. That goes . Yeah. You can just kind, you can, you can kind of tos them. Or alternatively, what you can do is you can actually be the nice thing. And this is, this kind of comes back to the origins of browsers, which is, you know, they're, they're at the beginning of the web and, you know, the late nineties, there was two very different kind of visions for the web where Alan Kay vehemently [00:21:00] disagree with the idea that should be document based, which is, you know, Tim Berners Lee, you know, that, and that's kind of what ended up winning, winning was this document based kind of browsing documents on the web thing.Eric: Alan Kay, he's got this like very famous quote where he said, you know, you want web browsers to be mini operating systems. They should download little mini binaries and execute with like a little mini virtualized operating system in there. And what's kind of interesting about the history, not to geek out on this aspect, what's kind of interesting about the history is both of those folks ended up being right.Eric: Documents were actually the pragmatic way that the web worked. Was, you know, became the most ubiquitous platform in the world to the degree now that this is why WebAssembly has been invented is that we're doing, we need to do more low level things in a browser, same thing with WebGPU, et cetera. And so all these APIs, you know, to build an operating system came to the browser.Eric: And that was actually the realization we had in 2017 was, holy heck, like you can actually, you know, service workers, which were designed for allowing your app to work offline. That was the kind of the key one where it was like, wait a second, you can actually now run. Web servers within a [00:22:00] browser, like you can run a server that you open up.Eric: That's wild. Like full Node. js. Full Node. js. Like that capability. Like, I can have a URL that's programmatically controlled. By a web application itself, boom. Like the web can build the web. The primitive is there. Everyone at the time, like we talked to people that like worked on, you know Chrome and V8 and they were like, uhhhh.Eric: You know, like I don't know. But it's one of those things you just kind of have to go do it to find out. So we spent a couple of years, you know, working on it and yeah. And, and, and got to work in back in 2021 is when we kind of put the first like data of web container online. Butswyx: in partnership with Google, right?swyx: Like Google actually had to help you get over the finish line with stuff.Eric: A hundred percent, because well, you know, over the years of when we were doing the R and D on the thing. Kind of the biggest challenge, the two ways that you can kind of test how powerful and capable a platform are, the two types of applications are one, video games, right, because they're just very compute intensive, a lot of calculations that have to happen, right?Eric: The second one are IDEs, because you're talking about actually virtualizing the actual [00:23:00] runtime environment you are in to actually build apps on top of it, which requires sophisticated capabilities, a lot of access to data. You know, a good amount of compute power, right, to effectively, you know, building app in app sort of thing.Eric: So those, those are the stress tests. So if your platform is missing stuff, those are the things where you find out. Those are, those are the people building games and IDEs. They're the ones filing bugs on operating system level stuff. And for us, browser level stuff.Eric [00:23:47]: yeah, what ended up happening is we were just hammering, you know, the Chromium bug tracker, and they're like, who are these guys? Yeah. And, and they were amazing because I mean, just making Chrome DevTools be able to debug, I mean, it's, it's not, it wasn't originally built right for debugging an operating system, right? They've been phenomenal working with us and just kind of really pushing the limits, but that it's a rising tide that's kind of lifted all boats because now there's a lot of different types of applications that you can debug with Chrome Dev Tools that are running a browser that runs more reliably because just the stress testing that, that we and, you know, games that are coming to the web are kind of pushing as well, but.Itamar [00:24:23]: That's awesome. About the testing, I think like most, let's say coding assistant from different kinds will need this loop of testing. And even I would add code review to some, to some extent that you mentioned. How is testing different from code review? Code review could be, for example, PR review, like a code review that is done at the point of when you want to merge branches. But I would say that code review, for example, checks best practices, maintainability, and so on. It's not just like CI, but more than CI. And testing is like a more like checking functionality, et cetera. So it's different. We call, by the way, all of these together code integrity, but that's a different story. Just to go back to the, to the testing and specifically. Yeah. It's, it's, it's since the first slide. Yeah. We're consistent. So if we go back to the testing, I think like, it's not surprising that for us testing is important and for Bolt it's testing important, but I want to shed some light on a different perspective of it. Like let's think about autonomous driving. Those startups that are doing autonomous driving for highway and autonomous driving for the city. And I think like we saw the autonomous of the highway much faster and reaching to a level, I don't know, four or so much faster than those in the city. Now, in both cases, you need testing and quote unquote testing, you know, verifying validation that you're doing the right thing on the road and you're reading and et cetera. But it's probably like so different in the city that it could be like actually different technology. And I claim that we're seeing something similar here. So when you're building the next Wix, and if I was them, I was like looking at you and being a bit scared. That's what you're disrupting, what you just said. Then basically, I would say that, for example, the UX UI is freaking important. And because you're you're more aiming for the end user. In this case, maybe it's an end user that doesn't know how to develop for developers. It's also important. But let alone those that do not know to develop, they need a slick UI UX. And I think like that's one reason, for example, I think Cursor have like really good technology. I don't know the underlying what's under the hood, but at least what they're saying. But I think also their UX UI is great. It's a lot because they did their own ID. While if you're aiming for the city AI, suddenly like there's a lot of testing and code review technology that it's not necessarily like that important. For example, let's talk about integration tests. Probably like a lot of what you're building involved at the moment is isolated applications. Maybe the vision or the end game is maybe like having one solution for everything. It could be that eventually the highway companies will go into the city and the other way around. But at the beginning, there is a difference. And integration tests are a good example. I guess they're a bit less important. And when you think about enterprise software, they're really important. So to recap, like I think like the idea of looping and verifying your test and verifying your code in different ways, testing or code review, et cetera, seems to be important in the highway AI and the city AI, but in different ways and different like critical for the city, even more and more variety. Actually, I was looking to ask you like what kind of loops you guys are doing. For example, when I'm using Bolt and I'm enjoying it a lot, then I do see like sometimes you're trying to catch the errors and fix them. And also, I noticed that you're breaking down tasks into smaller ones and then et cetera, which is already a common notion for a year ago. But it seems like you're doing it really well. So if you're willing to share anything about it.Eric [00:28:07]: Yeah, yeah. I realized I never actually hit the punchline of what I was saying before. I mentioned the point about us kind of writing an operating system from scratch because what ended up being important about that is that to your point, it's actually a very, like compared to like a, you know, if you're like running cursor on anyone's machine, you kind of don't know what you're dealing with, with the OS you're running on. There could be an error happens. It could be like a million different things, right? There could be some config. There could be, it could be God knows what, right? The thing with WebConnect is because we wrote the entire thing from scratch. It's actually a unified image basically. And we can instrument it at any level that we think is going to be useful, which is exactly what we did when we started building Bolt is we instrumented stuff at like the process level, at the runtime level, you know, et cetera, et cetera, et cetera. Stuff that would just be not impossible to do on local, but to do that in a way that works across any operating system, whatever is, I mean, would just be insanely, you know, insanely difficult to do right and reliably. And that's what you saw when you've used Bolt is that when an error actually will occur, whether it's in the build process or the actual web application itself is failing or anything kind of in between, you can actually capture those errors. And today it's a very primitive way of how we've implemented it largely because the product just didn't exist 90 days ago. So we're like, we got some work ahead of us and we got to hire some more a little bit, but basically we present and we say, Hey, this is, here's kind of the things that went wrong. There's a fix it button and then a ignore button, and then you can just hit fix it. And then we take all that telemetry through our agent, you run it through our agent and say, kind of, here's the state of the application. Here's kind of the errors that we got from Node.js or the browser or whatever, and like dah, dah, dah, dah. And it can take a crack at actually solving it. And it's actually pretty darn good at being able to do that. That's kind of been a, you know, closing the loop and having it be a reliable kind of base has seemed to be a pretty big upgrade over doing stuff locally, just because I think that's a pretty key ingredient of it. And yeah, I think breaking things down into smaller tasks, like that's, that's kind of a key part of our agent. I think like Claude did a really good job with artifacts. I think, you know, us and kind of everyone else has, has kind of taken their approach of like actually breaking out certain tasks in a certain order into, you know, kind of a concrete way. And, and so actually the core of Bolt, I know we actually made open source. So you can actually go and check out like the system prompts and et cetera, and you can run it locally and whatever have you. So anyone that's interested in this stuff, I'd highly recommend taking a look at. There's not a lot of like stuff that's like open source in this realm. It's, that was one of the fun things that we've we thought would be cool to do. And people, people seem to like it. I mean, there's a lot of forks and people adding different models and stuff. So it's been cool to see.Swyx [00:30:41]: Yeah. I'm happy to add, I added real-time voice for my opening day demo and it was really fun to hack with. So thank you for doing that. Yeah. Thank you. I'm going to steal your code.Eric [00:30:52]: Because I want that.Swyx [00:30:52]: It's funny because I built on top of the fork of Bolt.new that already has the multi LLM thing. And so you just told me you're going to merge that in. So then you're going to merge two layers of forks down into this thing. So it'll be fun.Eric [00:31:03]: Heck yeah.Alessio [00:31:04]: Just to touch on like the environment, Itamar, you maybe go into the most complicated environments that even the people that work there don't know how to run. How much of an impact does that have on your performance? Like, you know, it's most of the work you're doing actually figuring out environment and like the libraries, because I'm sure they're using outdated version of languages, they're using outdated libraries, they're using forks that have not been on the public internet before. How much of the work that you're doing is like there versus like at the LLM level?Itamar [00:31:32]: One of the reasons I was asking about, you know, what are the steps to break things down, because it really matters. Like, what's the tech stack? How complicated the software is? It's hard to figure it out when you're dealing with the real world, any environment of enterprise as a city, when I'm like, while maybe sometimes like, I think you do enable like in Bolt, like to install stuff, but it's quite a like controlled environment. And that's a good thing to do, because then you narrow down and it's easier to make things work. So definitely, there are two dimensions, I think, actually spaces. One is the fact just like installing our software without yet like doing anything, making it work, just installing it because we work with enterprise and Fortune 500, etc. Many of them want on prem solution.Swyx [00:32:22]: So you have how many deployment options?Itamar [00:32:24]: Basically, we had, we did a metric metrics, say 96 options, because, you know, they're different dimensions. Like, for example, one dimension, we connect to your code management system to your Git. So are you having like GitHub, GitLab? Subversion? Is it like on cloud or deployed on prem? Just an example. Which model agree to use its APIs or ours? Like we have our Is it TestGPT? Yeah, when we started with TestGPT, it was a huge mistake name. It was cool back then, but I don't think it's a good idea to name a model after someone else's model. Anyway, that's my opinion. So we gotSwyx [00:33:02]: I'm interested in these learnings, like things that you change your mind on.Itamar [00:33:06]: Eventually, when you're building a company, you're building a brand and you want to create your own brand. By the way, when I thought about Bolt.new, I also thought about if it's not a problem, because when I think about Bolt, I do think about like a couple of companies that are already called this way.Swyx [00:33:19]: Curse companies. You could call it Codium just to...Itamar [00:33:24]: Okay, thank you. Touche. Touche.Eric [00:33:27]: Yeah, you got to imagine the board meeting before we launched Bolt, one of our investors, you can imagine they're like, are you sure? Because from the investment side, it's kind of a famous, very notorious Bolt. And they're like, are you sure you want to go with that name? Oh, yeah. Yeah, absolutely.Itamar [00:33:43]: At this point, we have actually four models. There is a model for autocomplete. There's a model for the chat. There is a model dedicated for more for code review. And there is a model that is for code embedding. Actually, you might notice that there isn't a good code embedding model out there. Can you name one? Like dedicated for code?Swyx [00:34:04]: There's code indexing, and then you can do sort of like the hide for code. And then you can embed the descriptions of the code.Itamar [00:34:12]: Yeah, but you do see a lot of type of models that are dedicated for embedding and for different spaces, different fields, etc. And I'm not aware. And I know that if you go to the bedrock, try to find like there's a few code embedding models, but none of them are specialized for code.Swyx [00:34:31]: Is there a benchmark that you would tell us to pay attention to?Itamar [00:34:34]: Yeah, so it's coming. Wait for that. Anyway, we have our models. And just to go back to the 96 option of deployment. So I'm closing the brackets for us. So one is like dimensional, like what Git deployment you have, like what models do you agree to use? Dotter could be like if it's air-gapped completely, or you want VPC, and then you have Azure, GCP, and AWS, which is different. Do you use Kubernetes or do not? Because we want to exploit that. There are companies that do not do that, etc. I guess you know what I mean. So that's one thing. And considering that we are dealing with one of all four enterprises, we needed to deal with that. So you asked me about how complicated it is to solve that complex code. I said, it's just a deployment part. And then now to the software, we see a lot of different challenges. For example, some companies, they did actually a good job to build a lot of microservices. Let's not get to if it's good or not, but let's first assume that it is a good thing. A lot of microservices, each one of them has their own repo. And now you have tens of thousands of repos. And you as a developer want to develop something. And I remember me coming to a corporate for the first time. I don't know where to look at, like where to find things. So just doing a good indexing for that is like a challenge. And moreover, the regular indexing, the one that you can find, we wrote a few blogs on that. By the way, we also have some open source, different than yours, but actually three and growing. Then it doesn't work. You need to let the tech leads and the companies influence your indexing. For example, Mark with different repos with different colors. This is a high quality repo. This is a lower quality repo. This is a repo that we want to deprecate. This is a repo we want to grow, etc. And let that be part of your indexing. And only then things actually work for enterprise and they don't get to a fatigue of, oh, this is awesome. Oh, but I'm starting, it's annoying me. I think Copilot is an amazing tool, but I'm quoting others, meaning GitHub Copilot, that they see not so good retention of GitHub Copilot and enterprise. Ooh, spicy. Yeah. I saw snapshots of people and we have customers that are Copilot users as well. And also I saw research, some of them is public by the way, between 38 to 50% retention for users using Copilot and enterprise. So it's not so good. By the way, I don't think it's that bad, but it's not so good. So I think that's a reason because, yeah, it helps you auto-complete, but then, and especially if you're working on your repo alone, but if it's need that context of remote repos that you're code-based, that's hard. So to make things work, there's a lot of work on that, like giving the controllability for the tech leads, for the developer platform or developer experience department in the organization to influence how things are working. A short example, because if you have like really old legacy code, probably some of it is not so good anymore. If you just fine tune on these code base, then there is a bias to repeat those mistakes or old practices, etc. So you need, for example, as I mentioned, to influence that. For example, in Coda, you can have a markdown of best practices by the tech leads and Coda will include that and relate to that and will not offer suggestions that are not according to the best practices, just as an example. So that's just a short list of things that you need to do in order to deal with, like you mentioned, the 100.1 to 100.2 version of software. I just want to say what you're doing is extremelyEric [00:38:32]: impressive because it's very difficult. I mean, the business of Stackplus, kind of before bulk came online, we sold a version of our IDE that went on-prem. So I understand what you're saying about the difficulty of getting stuff just working on-prem. Holy heck. I mean, that is extremely hard. I guess the question I have for you is, I mean, we were just doing that with kind of Kubernetes-based stuff, but the spread of Fortune 500 companies that you're working with, how are they doing the inference for this? Are you kind of plugging into Azure's OpenAI stuff and AWS's Bedrock, you know, Cloud stuff? Or are they just like running stuff on GPUs? Like, what is that? How are these folks approaching that? Because, man, what we saw on the enterprise side, I mean, I got to imagine that that's a huge challenge. Everything you said and more, like,Itamar [00:39:15]: for example, like someone could be, and I don't think any of these is bad. Like, they made their decision. Like, for example, some people, they're, I want only AWS and VPC on AWS, no matter what. And then they, some of them, like there is a subset, I will say, I'm willing to take models only for from Bedrock and not ours. And we have a problem because there is no good code embedding model on Bedrock. And that's part of what we're doing now with AWS to solve that. We solve it in a different way. But if you are willing to run on AWS VPC, but run your run models on GPUs or inferentia, like the new version of the more coming out, then our models can run on that. But everything you said is right. Like, we see like on-prem deployment where they have their own GPUs. We see Azure where you're using OpenAI Azure. We see cases where you're running on GCP and they want OpenAI. Like this cross, like a case, although there is Gemini or even Sonnet, I think is available on GCP, just an example. So all the options, that's part of the challenge. I admit that we thought about it, but it was even more complicated. And it took us a few months to actually, that metrics that I mentioned, to start clicking each one of the blocks there. A few months is impressive. I mean,Eric [00:40:35]: honestly, just that's okay. Every one of these enterprises is, their networking is different. Just everything's different. Every single one is different. I see you understand. Yeah. So that just cannot be understated. That it is, that's extremely impressive. Hats off.Itamar [00:40:50]: It could be, by the way, like, for example, oh, we're only AWS, but our GitHub enterprise is on-prem. Oh, we forgot. So we need like a private link or whatever, like every time like that. It's not, and you do need to think about it if you want to work with an enterprise. And it's important. Like I understand like their, I respect their point of view.Swyx [00:41:10]: And this primarily impacts your architecture, your tech choices. Like you have to, you can't choose some vendors because...Itamar [00:41:15]: Yeah, definitely. To be frank, it makes us hard for a startup because it means that we want, we want everyone to enjoy all the variety of models. By the way, it was hard for us with our technology. I want to open a bracket, like a window. I guess you're familiar with our Alpha Codium, which is an open source.Eric [00:41:33]: We got to go over that. Yeah. So I'll do that quickly.Itamar [00:41:36]: Yeah. A pin in that. Yeah. Actually, we didn't have it in the last episode. So, so, okay.Swyx [00:41:41]: Okay. We'll come back to that later, but let's talk about...Itamar [00:41:43]: Yeah. So, so just like shortly, and then we can double click on Alpha Codium. But Alpha Codium is a open source tool. You can go and try it and lets you compete on CodeForce. This is a website and a competition and actually reach a master level level, like 95% with a click of a button. You don't need to do anything. And part of what we did there is taking a problem and breaking it to different, like smaller blocks. And then the models are doing a much better job. Like we all know it by now that taking small tasks and solving them, by the way, even O1, which is supposed to be able to do system two thinking like Greg from OpenAI like hinted, is doing better on these kinds of problems. But still, it's very useful to break it down for O1, despite O1 being able to think by itself. And that's what we presented like just a month ago, OpenAI released that now they are doing 93 percentile with O1 IOI left and International Olympiad of Formation. Sorry, I forgot. Exactly. I told you I forgot. And we took their O1 preview with Alpha Codium and did better. Like it just shows like, and there is a big difference between the preview and the IOI. It shows like that these models are not still system two thinkers, and there is a big difference. So maybe they're not complete system two. Yeah, they need some guidance. I call them system 1.5. We can, we can have it. I thought about it. Like, you know, I care about this philosophy stuff. And I think like we didn't see it even close to a system two thinking. I can elaborate later. But closing the brackets, like we take Alpha Codium and as our principle of thinking, we take tasks and break them down to smaller tasks. And then we want to exploit the best model to solve them. So I want to enable anyone to enjoy O1 and SONET and Gemini 1.5, etc. But at the same time, I need to develop my own models as well, because some of the Fortune 500 want to have all air gapped or whatever. So that's a challenge. Now you need to support so many models. And to some extent, I would say that the flow engineering, the breaking down to two different blocks is a necessity for us. Why? Because when you take a big block, a big problem, you need a very different prompt for each one of the models to actually work. But when you take a big problem and break it into small tasks, we can talk how we do that, then the prompt matters less. What I want to say, like all this, like as a startup trying to do different deployment, getting all the juice that you can get from models, etc. is a big problem. And one need to think about it. And one of our mitigation is that process of taking tasks and breaking them down. That's why I'm really interested to know how you guys are doing it. And part of what we do is also open source. So you can see.Swyx [00:44:39]: There's a lot in there. But yeah, flow over prompt. I do believe that that does make sense. I feel like there's a lot that both of you can sort of exchange notes on breaking down problems. And I just want you guys to just go for it. This is fun to watch.Eric [00:44:55]: Yeah. I mean, what's super interesting is the context you're working in is, because for us too with Bolt, we've started thinking because our kind of existing business line was going behind the firewall, right? We were like, how do we do this? Adding the inference aspect on, we're like, okay, how does... Because I mean, there's not a lot of prior art, right? I mean, this is all new. This is all new. So I definitely am going to have a lot of questions for you.Itamar [00:45:17]: I'm here. We're very open, by the way. We have a paper on a blog or like whatever.Swyx [00:45:22]: The Alphacodeum, GitHub, and we'll put all this in the show notes.Itamar [00:45:25]: Yeah. And even the new results of O1, we published it.Eric [00:45:29]: I love that. And I also just, I think spiritually, I like your approach of being transparent. Because I think there's a lot of hype-ium around AI stuff. And a lot of it is, it's just like, you have these companies that are just kind of keep their stuff closed source and then just max hype it, but then it's kind of nothing. And I think it kind of gives a bad rep to the incredible stuff that's actually happening here. And so I think it's stuff like what you're doing where, I mean, true merit and you're cracking open actual code for others to learn from and use. That strikes me as the right approach. And it's great to hear that you're making such incredible progress.Itamar [00:46:02]: I have something to share about the open source. Most of our tools are, we have an open source version and then a premium pro version. But it's not an easy decision to do that. I actually wanted to ask you about your strategy, but I think in your case, there is, in my opinion, relatively a good strategy where a lot of parts of open source, but then you have the deployment and the environment, which is not right if I get it correctly. And then there's a clear, almost hugging face model. Yeah, you can do that, but why should you try to deploy it yourself, deploy it with us? But in our case, and I'm not sure you're not going to hit also some competitors, and I guess you are. I wanted to ask you, for example, on some of them. In our case, one day we looked on one of our competitors that is doing code review. We're a platform. We have the code review, the testing, et cetera, spread over the ID to get. And in each agent, we have a few startups or a big incumbents that are doing only that. So we noticed one of our competitors having not only a very similar UI of our open source, but actually even our typo. And you sit there and you're kind of like, yeah, we're not that good. We don't use enough Grammarly or whatever. And we had a couple of these and we saw it there. And then it's a challenge. And I want to ask you, Bald is doing so well, and then you open source it. So I think I know what my answer was. I gave it before, but still interestingEric [00:47:29]: to hear what you think. GeoHot said back, I don't know who he was up to at this exact moment, but I think on comma AI, all that stuff's open source. And someone had asked him, why is this open source? And he's like, if you're not actually confident that you can go and crush it and build the best thing, then yeah, you should probably keep your stuff closed source. He said something akin to that. I'm probably kind of butchering it, but I thought it was kind of a really good point. And that's not to say that you should just open source everything, because for obvious reasons, there's kind of strategic things you have to kind of take in mind. But I actually think a pretty liberal approach, as liberal as you kind of can be, it can really make a lot of sense. Because that is so validating that one of your competitors is taking your stuff and they're like, yeah, let's just kind of tweak the styles. I mean, clearly, right? I think it's kind of healthy because it keeps, I'm sure back at HQ that day when you saw that, you're like, oh, all right, well, we have to grind even harder to make sure we stay ahead. And so I think it's actually a very useful, motivating thing for the teams. Because you might feel this period of comfort. I think a lot of companies will have this period of comfort where they're not feeling the competition and one day they get disrupted. So kind of putting stuff out there and letting people push it forces you to face reality soon, right? And actually feel that incrementally so you can kind of adjust course. And that's for us, the open source version of Bolt has had a lot of features people have been begging us for, like persisting chat messages and checkpoints and stuff. Within the first week, that stuff was landed in the open source versions. And they're like, why can't you ship this? It's in the open, so people have forked it. And we're like, we're trying to keep our servers and GPUs online. But it's been great because the folks in the community did a great job, kept us on our toes. And we've got to know most of these folks too at this point that have been building these things. And so it actually was very instructive. Like, okay, well, if we're going to go kind of land this, there's some UX patterns we can kind of look at and the code is open source to this stuff. What's great about these, what's not. So anyways, NetNet, I think it's awesome. I think from a competitive point of view for us, I think in particular, what's interesting is the core technology of WebContainer going. And I think that right now, there's really nothing that's kind of on par with that. And we also, we have a business of, because WebContainer runs in your browser, but to make it work, you have to install stuff from NPM. You have to make cores bypass requests, like connected databases, which all require server-side proxying or acceleration. And so we actually sell WebContainer as a service. One of the core reasons we open-sourced kind of the core components of Bolt when we launched was that we think that there's going to be a lot more of these AI, in-your-browser AI co-gen experiences, kind of like what Anthropic did with Artifacts and Clod. By the way, Artifacts uses WebContainers. Not yet. No, yeah. Should I strike that? I think that they've got their own thing at the moment, but there's been a lot of interest in WebContainers from folks doing things in that sort of realm and in the AI labs and startups and everything in between. So I think there'll be, I imagine, over the coming months, there'll be lots of things being announced to folks kind of adopting it. But yeah, I think effectively...Swyx [00:50:35]: Okay, I'll say this. If you're a large model lab and you want to build sandbox environments inside of your chat app, you should call Eric.Itamar [00:50:43]: But wait, wait, wait, wait, wait, wait. I have a question about that. I think OpenAI, they felt that people are not using their model as they would want to. So they built ChatGPT. But I would say that ChatGPT now defines OpenAI. I know they're doing a lot of business from their APIs, but still, is this how you think? Isn't Bolt.new your business now? Why don't you focus on that instead of the...Swyx [00:51:16]: What's your advice as a founder?Eric [00:51:18]: You're right. And so going into it, we, candidly, we were like, Bolt.new, this thing is super cool. We think people are stoked. We think people will be stoked. But we were like, maybe that's allowed. Best case scenario, after month one, we'd be mind blown if we added a couple hundred K of error or something. And we were like, but we think there's probably going to be an immediate huge business. Because there was some early poll on folks wanting to put WebContainer into their product offerings, kind of similar to what Bolt is doing or whatever. We were actually prepared for the inverse outcome here. But I mean, well, I guess we've seen poll on both. But I mean, what's happened with Bolt, and you're right, it's actually the same strategy as like OpenAI or Anthropic, where we have our ChatGPT to OpenAI's APIs is Bolt to WebContainer. And so we've kind of taken that same approach. And we're seeing, I guess, some of the similar results, except right now, the revenue side is extremely lopsided to Bolt.Itamar [00:52:16]: I think if you ask me what's my advice, I think you have three options. One is to focus on Bolt. The other is to focus on the WebContainer. The third is to raise one billion dollars and do them both. I'm serious. I think otherwise, you need to choose. And if you raise enough money, and I think it's big bucks, because you're going to be chased by competitors. And I think it will be challenging to do both. And maybe you can. I don't know. We do see these numbers right now, raising above $100 million, even without havingEric [00:52:49]: a product. You can see these. It's excellent advice. And I think what's been amazing, but also kind of challenging is we're trying to forecast, okay, well, where are these things going? I mean, in the initial weeks, I think us and all the investors in the company that we're sharing this with, it was like, this is cool. Okay, we added 500k. Wow, that's crazy. Wow, we're at a million now. Most things, you have this kind of the tech crunch launch of initiation and then the thing of sorrow. And if there's going to be a downtrend, it's just not coming yet. Now that we're kind of looking ahead, we're six weeks in. So now we're getting enough confidence in our convictions to go, okay, this se

How did PEZ candy come to be? Why are Mexicans so into anime? Does every costume deserve candy on Halloween? If you had a time machine would you kill Hitler or something more productive? Where was the internet invented? Kyle and Jheisson answer these questions and more as they dive into the history of PEZ, the Crocs marathon world record, the Flintstones, and the history of the Internet!The students at Wiki U have been drinking Magic Mind every morning to jumpstart their day and get their brains firing on all cylinders! We love Magic Mind because it's filled with all natural ingredients that help you focus on the things you need to get done and the things you WANT to get done. The first thing you should cross off your list today is getting a subscription to Magic Mind. For a limited time Wiki U listeners can get 20% off a one time purchase or subscription by using the promo code Wikiuni20 at checkout at the link below!https://magicmind.com/WIKIUNI20 TikTok: https://www.tiktok.com/@wikiuniversity YouTube: https://www.youtube.com/channel/UCmPDDjcbBJfR0s_xJfYCUvwInstagram: https://www.instagram.com/wikiuniversity/Music provided by Davey and the Chains  TikTok: https://www.tiktok.com/@wikiuniversity YouTube: https://www.youtube.com/channel/UCmPDDjcbBJfR0s_xJfYCUvwInstagram: https://www.instagram.com/wikiuniversity/Music provided by Davey and the Chains

Cet épisode est relativement pauvre en IA, ouaissssssss ! Mais il nous reste plein de Spring, plein de failles, plein d'OpenTelemetry, un peu de versionnage sémantique, une astuce Git et bien d'autres choses encore. Enregistré le 8 novembre 2024 Téléchargement de l'épisode LesCastCodeurs-Episode–318.mp3 News Langages Le createur de Fernflower in decompilateur qui a relancé l'outillage autour de Java 8 est mort, un hommage d'IntelliJ IDEA https://blog.jetbrains.com/idea/2024/11/in-memory-of-stiver/ les decompilateurs s'appuyaient sur des patterns reconnus et étaient fragiles et incomplets surtout quand Java 8 a changé le pattern try catch et ajouté des concepts comme les annotations le champ était moribond quand Stiver s'est lancé dommage l'article n'explique pas comment le control-flow graph est genere a partir du bytecode pour ameliorer la decompilation Librairies On peut maintenant utiliser Jakarta Data Repository dans Quarkus https://in.relation.to/2024/11/04/data-in-quarkus/ petit article avec un projet example aussi un lien sur la presentation de Jakarta Data par Gavin à Devoxx Belgique Quarkus 3.16 https://quarkus.io/guides/opentelemetry-logging logs distribués avec OpenTelemetry (preview) deserialiseurs Jackson sans reflection des améliorations dans la stack de sécurité TLS registry a ratjouté graphql client et keycloak admin client LEs logs des container devservice et des access http sont visible dans la DevUI Les extensions peuvent maintenant ecrire leur doc en markdown (c'etait juste asciidoc avant) Un artcile sur comment débuter en Spring Batch https://www.sfeir.dev/back/planifier-des-taches-avec-spring-batch/ Le support OAuth2 pour RestClient arrive dans Security 6.4 / Boot 3.4. Plus de hack de WebClient dans vos applications Spring-Web ! https://spring.io/blog/2024/10/28/restclient-support-for-oauth2-in-spring-security–6–4 RestClient a été ajouté dans Spring Framework 6.1 API Fluide Spring Security 6.4 simplifie la configuration OAuth2 avec le nouveau client HTTP synchrone RestClient. RestClient permet des requêtes de ressources sans dépendances réactives, alignant la configuration entre applications servlet et réactives. La mise à jour facilite la migration depuis RestTemplate et ouvre la voie à des scénarios avancés. Marre des microservices ? Revenez au monoliths avec Spring Modulith 1.3RC1, 1.2.5 et 1.1.10 https://spring.io/blog/2024/10/28/spring-modulith–1–3-rc1–1–2–5-and–1–1–10-released Spring Modulith 1.3 RC1, 1.2.5, and 1.1.10 sont disponibles. La version 1.3 RC1 inclut des nouvelles fonctionnalités : archiving event publication completion mode compatibilité avec MariaDB et Oracle avec JDBC-based event publication registry Possibilité d'externaliser des événements dans des MessageChannels de Spring. Expressions SpEL dans @Externalized validation d'architecture technique jMolecules. Les versions 1.2.5 et 1.1.10 apportent des correctifs et mises à jour de dépendances. Spring gRPC 0.1 est sorti https://github.com/spring-projects-experimental/spring-grpc c'est tout nouveau et explorationel si c'est un probleme qui vous gratte, ca vaut le coup de jeter un coup d'oeil et participer. Spring Boot 3.3 Integrer Spring avec Open Telemetry (OTLP protocole) https://spring.io/blog/2024/10/28/lets-use-opentelemetry-with-spring rappel de la valeur de ce standard Open Telemetry comment l'utiliser dans vos projets Spring Comment utiliser ollama avec Spring AI https://spring.io/blog/2024/10/22/leverage-the-power-of–45k-free-hugging-face-models-with-spring-ai-and-ollama permet d'acceter aux 45k modeles de Hugging faces qui supportent le deploiement sur ollama il y a un spring boot starter c'est vraiment pour debuter Cloud Google Cloud Frankfort a subit 12h d'interruption https://t.co/VueiQjhCA3 Google Cloud a subi une panne de 12 heures dans la région europe-west3 (Francfort) le 24 octobre 2024. La panne, causée par une défaillance d'alimentation et de refroidissement, a affecté plusieurs services, y compris Compute Engine et Kubernetes Engine. Les utilisateurs ont rencontré des problèmes de création de VM, des échecs d'opérations et des retards de traitement. Google a conseillé de migrer les charges de travail vers d'autres zones. il y a eu une autre zone Europeenne pas mal affectée l'année dernière et des clients ont perdu des données :sweat: Web La fin de la World Wild Web Foundation https://www.theregister.com/2024/09/30/world_wide_web_foundation_closes/ la Fondation World Wide Web ferme ses portes. Les cofondateurs estiment que les problèmes auxquels est confronté le Web ont changé et que d'autres groupes de défense peuvent désormais prendre le relais. Ils estiment également que la priorité absolue doit être donnée à la passion de Tim Berners-Lee pour redonner aux individus le pouvoir et le contrôle de leurs données et pour construire activement des systèmes de collaboration puissants (Solid Protocol - https://solidproject.org/). Release du https://www.patternfly.org/ 6 Fw opensource pour faire de UI, sponsor RH Interessant à regarder Data et Intelligence Artificielle TSMC arrête des ventes à un client chinois qui aurait revenu un processeur à Huawei et utilise dans sa puce IA https://www.reuters.com/technology/tsmc-suspended-shipments-china-firm-after-chip-found-huawei-processor-sources–2024–10–26/ Taiwan Semiconductor Manufacturing Company (TSMC) a suspendu ses livraisons à Sophgo, un concepteur de puces chinois, après la découverte d'une puce fabriquée par TSMC dans un processeur AI de Huawei (Ascend 910B). Cette découverte soulève des préoccupations concernant des violations potentielles des contrôles d'exportation des États-Unis, qui restreignent Huawei depuis 2020. Sophgo, lié à Bitmain, a nié toute connexion avec Huawei et affirme se conformer aux lois applicables. Toutefois, l'incident a conduit à une enquête approfondie de TSMC et des autorités américaines et taïwanaises Open AI et Microsoft, de l'amour à la guerre https://www.computerworld.com/article/3593206/microsoft-and-openai-good-by-bromance-hel[…]m_source=Adestra&huid=4349eeff–5b8b–493d–9e61–9abf8be5293b on a bien suivi les chants d'amour entre Sam Altman et Satia Nadella ca c'est tendu ces derniers temps deja avec le coup chez openAI où MS avait sifflé la fin de la récré “on a le code, les données, l'IP et la capacité, on peut tout recrée” OpenAi a un competiteur de Copilot et essaie de courtises ses clients les apétits d'investissements d'OpenAI et une dispute sur la valeur de la aprt de MS qui a donné des crédits cloud semble etre aui coeur de la dispute du moment Debezium 3 est sorti https://debezium.io/blog/2024/10/02/debezium–3–0-final-released/ Java 17 minimum pour les connecteurs et 21 pour le serveur, l'extension quarkus outbox et pour l'operateur nettoyage des depreciations metriques par table maintenant support for mysql 9 y compris vector data type oracle, default mining strategie changée ehcache off-heap ajouté amelioarations diverses Oracle (offline RAC node flush, max string size for Extended PostgreSQL PGVector etc (Spanner, vitess, …) NotebookLlama: une version Open Source de NotebookLM https://github.com/meta-llama/llama-recipes/tree/main/recipes/quickstart/NotebookLlama Si vous avez été impressionné par les démo de Gemini Notebook, en créant des podcasts à partir de différentes resources, testez la version llama Tutoriel étape par étape pour transformer un PDF en podcast. Outillage Vous aimez Maven? Bien évidemment! Vous aimez asciidoctor? Absolument! Alors la version 3.1.0 du plugin asciidoctor pour maven est pour vous !! https://github.com/asciidoctor/asciidoctor-maven-plugin Le plugin permet soit de convertir des documents asciidoc de manière autonome, soit de les gérer via le site maven GitHub Universe: de l'IA, de l'IA et encore de l'IA https://github.blog/news-insights/product-news/universe–2024-previews-releases/ GitHub Universe 2024 présente les nouveautés de l'année, notamment la possibilité de choisir parmi plusieurs modèles d'IA pour GitHub Copilot (Claude 3.5, Gemini 1.5 Pro, OpenAI o1). Nouvelles fonctionnalités : GitHub Spark pour créer des micro-applications, révisions de code assistées par Copilot, sécurité renforcée avec Copilot Autofix. Simplification des workflows avec les extensions GitHub Copilot Facilitation de la création d'applications IA génératives avec GitHub Models Méthodologies Les blogs de developpeurs experts Java recommandés par IntelliJ https://blog.jetbrains.com/idea/2024/11/top-java-blogs-for-experienced-programmers/ pas forcement d'accord avec toute la liste mais elle donne de bonnes options si vous voulez lire plus de blogs Java Keycloak revient au semantic versioning après avoir suivi le versionage à la Google Chrome https://www.keycloak.org/2024/10/release-updates ne pas savoir si une mise a jour était retrocompatible était problématique pour les utilisateurs aussi les librairies clientes seront délivrées séparément et supporteront toutes les versions serveur de keycloak supportés Sécurité Un exemple d'attaque de secure supply chain théorique identifiée dans le quarkiverse et les détails de la résolution https://quarkus.io/blog/quarkiverse-and-smallrye-new-release-process/ dans le quarkiverse, les choses sont automatisées pour simplifier la vie des contributeurs d'extension occasionels mais il y avait un défaut, les secrets de signature et d'accès à maven central étaient des secrets d'organisation ce qui veut dire qu'un editeur d'extension malicieux pouvait ecrire un pluging ou un test qiu lisait ses secrets et pouvait livrer de faux artifacts la solution est de séparer la construction des artifacts de l'etape de signature et de release sur maven central comme cela les cles ne sont plus accessible Avec Okta pus besoin de mot de passe quand tu as un identifiant long :face_with_hand_over_mouth: https://trust.okta.com/security-advisories/okta-ad-ldap-delegated-authentication-username/ LOL Une vulnérabilité a été découverte dans la génération de la clé de cache pour l'authentification déléguée AD/LDAP. Les conditions: MFA non utilisé Nom d'utilisateur de 52 caractères ou plus Utilisateur authentifié précédemment, créant un cache d'authentification Le cache a été utilisé en premier, ce qui peut se produire si l'agent AD/LDAP était hors service ou inaccessible, par exemple en raison d'un trafic réseau élevé L'authentification s'est produite entre le 23 juillet 2024 et le 30 octobre 2024 Fixé le 30 octobre, 2024 La revanche des imprimantes !! Linux ne les aime pas, et elles lui rendent bien. https://www.theregister.com/2024/09/26/cups_linux_rce_disclosed/ Après quelques heures / jours de rumeurs sur une faille 9.9/10 CVSS il s'avère que cela concerne que les système avec le système d'impression CUPS et cups-browsed Désactivez et/ou supprimez le service cups-browsed. Mettez à jour votre installation CUPS pour appliquer les mises à jour de sécurité lorsqu'elles sont disponibles. Envisagez de bloquer l'accès au port UDP 631 et également de désactiver le DNS-SD. Cela concerne la plupart des distributions Linux, certaines BSD, possiblement Google ChromeOS, Solaris d'Oracle et potentiellement d'autres systèmes, car CUPS est intégré à diverses distributions pour fournir la fonctionnalité d'impression. Pour exploiter cette vulnérabilité via internet ou le réseau local (LAN), un attaquant doit pouvoir accéder à votre service CUPS sur le port UDP 631. Idéalement, aucun de vous ne devrait exposer ce port sur l'internet public. L'attaquant doit également attendre que vous lanciez une tâche d'impression. Si le port 631 n'est pas directement accessible, un attaquant pourrait être en mesure de falsifier des annonces zeroconf, mDNS ou DNS-SD pour exploiter cette vulnérabilité sur un LAN. Loi, société et organisation La version 1.0 de la definition de l'IA l'Open Source est sortie https://siliconangle.com/2024/10/28/osi-clarifies-makes-ai-systems-open-source-open-models-fall-short/ L'Open Source Initiative (OSI) a clarifié les critères pour qu'un modèle d'IA soit considéré comme open-source : accès complet aux données de formation, au code source et aux paramètres d'entraînement. La plupart des modèles dits “open” comme ceux de Meta (Llama) et Stability AI (Stable Diffusion) ne respectent pas ces critères, car ils imposent des restrictions sur l'utilisation commerciale et ne rendent pas publiques les données de formation c'est au details de données de formation (donc pas forcement les données elle meme. “In particular, this must include: (1) the complete description of all data used for training, including (if used) of unshareable data, disclosing the provenance of the data, its scope and characteristics, how the data was obtained and selected, the labeling procedures, and data processing and filtering methodologies; (2) a listing of all publicly available training data and where to obtain it; and (3) a listing of all training data obtainable from third parties and where to obtain it, including for fee.” C'est en echo a la version d'open source AI de la linux fondation En parlant de cela un article sur l'open source washing dans les modèles https://www.theregister.com/2024/10/25/opinion_open_washing/ L'open washing désigne la pratique où des entreprises prétendent que leurs produits ou modèles sont open-source, bien qu'ils ne respectent pas les critères réels d'ouverture (transparence, accessibilité, partage des connaissances). De grandes entreprises comme Meta, Google et Microsoft sont souvent accusées d'utiliser cette stratégie, ce qui soulève des préoccupations concernant la clarté des définitions légales et commerciales de l'open source, surtout avec l'essor de l'IA. Rubrique débutant Un petit article fondamental sur REST https://www.sfeir.dev/rest-definition/ there de Roy Fielding en reaction aux protocoles lourds comme SOAP 5 verbes (GET PUT, POST. DELETE, PATCH) JSON mais pas que (XML et autre pas d'etat inter requete Ask Me Anything Morgan de Montréal Comment faire cohabiter plusieurs dépôts Git ? Je m'explique : dans mon entreprise, nous utilisons notre dépôt Git (Bitbucket) configuré pour notre dépôt d'entreprise. Lorsque je souhaite contribuer à un projet open source, je suis obligé de modifier ma configuration globale Git (nom d'utilisateur, email) pour correspondre à mon compte GitHub. Il arrive souvent que, lorsque je reviens pour effectuer un commit sur le dépôt d'entreprise, j'oublie que je suis en mode “open source”, ce qui entraîne l'enregistrement de mes configurations “open source” dans l'historique de Bitbucket… Comment gérez-vous ce genre de situation ? Comment gérer différents profiles git https://medium.com/@mrjink/using-includeif-to-manage-your-git-identities-bcc99447b04b Conférences La liste des conférences provenant de Developers Conferences Agenda/List par Aurélie Vache et contributeurs : 8 novembre 2024 : BDX I/O - Bordeaux (France) 13–14 novembre 2024 : Agile Tour Rennes 2024 - Rennes (France) 16–17 novembre 2024 : Capitole Du Libre - Toulouse (France) 20–22 novembre 2024 : Agile Grenoble 2024 - Grenoble (France) 21 novembre 2024 : DevFest Strasbourg - Strasbourg (France) 21 novembre 2024 : Codeurs en Seine - Rouen (France) 21 novembre 2024 : Agile Game Toulouse - Toulouse (France) 27–28 novembre 2024 : Cloud Expo Europe - Paris (France) 28 novembre 2024 : OVHcloud Summit - Paris (France) 28 novembre 2024 : Who Run The Tech ? - Rennes (France) 2–3 décembre 2024 : Tech Rocks Summit - Paris (France) 3 décembre 2024 : Generation AI - Paris (France) 3–5 décembre 2024 : APIdays Paris - Paris (France) 4–5 décembre 2024 : DevOpsRex - Paris (France) 4–5 décembre 2024 : Open Source Experience - Paris (France) 5 décembre 2024 : GraphQL Day Europe - Paris (France) 6 décembre 2024 : DevFest Dijon - Dijon (France) 19 décembre 2024 : Normandie.ai 2024 - Rouen (France) 22–25 janvier 2025 : SnowCamp 2025 - Grenoble (France) 30 janvier 2025 : DevOps D-Day #9 - Marseille (France) 6–7 février 2025 : Touraine Tech - Tours (France) 28 février 2025 : Paris TS La Conf - Paris (France) 20 mars 2025 : PGDay Paris - Paris (France) 25 mars 2025 : ParisTestConf - Paris (France) 3 avril 2025 : DotJS - Paris (France) 10–12 avril 2025 : Devoxx Greece - Athens (Greece) 16–18 avril 2025 : Devoxx France - Paris (France) 7–9 mai 2025 : Devoxx UK - London (UK) 16 mai 2025 : AFUP Day 2025 Lille - Lille (France) 16 mai 2025 : AFUP Day 2025 Lyon - Lyon (France) 16 mai 2025 : AFUP Day 2025 Poitiers - Poitiers (France) 11–13 juin 2025 : Devoxx Poland - Krakow (Poland) 12–13 juin 2025 : DevLille - Lille (France) 24 juin 2025 : WAX 2025 - Aix-en-Provence (France) 26–27 juin 2025 : Sunny Tech - Montpellier (France) 1–4 juillet 2025 : Open edX Conference - 2025 - Palaiseau (France) 18–19 septembre 2025 : API Platform Conference - Lille (France) & Online 6–10 octobre 2025 : Devoxx Belgium - Antwerp (Belgium) 9–10 octobre 2025 : Volcamp - Clermont-Ferrand (France) 16–17 octobre 2025 : DevFest Nantes - Nantes (France) 23–25 avril 2026 : Devoxx Greece - Athens (Greece) 17 juin 2026 : Devoxx Poland - Krakow (Poland) Nous contacter Pour réagir à cet épisode, venez discuter sur le groupe Google https://groups.google.com/group/lescastcodeurs Contactez-nous via twitter https://twitter.com/lescastcodeurs Faire un crowdcast ou une crowdquestion Soutenez Les Cast Codeurs sur Patreon https://www.patreon.com/LesCastCodeurs Tous les épisodes et toutes les infos sur https://lescastcodeurs.com/

In this episode, host Marc Aflalo sits down with Mark Weinstein, a tech entrepreneur and one of the pioneers of social media, to discuss the past, present, and future of online privacy and social media. Mark Weinstein shares insights from his new book, Restoring Our Sanity Online, which has been endorsed by industry giants like Steve Wozniak and Sir Tim Berners-Lee. The conversation dives into the origins of social media and how the initial vision of connecting people turned into what Weinstein calls the “data ecosystem” we experience today. He describes the transition from early social media platforms like MySpace and Facebook to the current state, where privacy concerns, bots, and targeted ads dominate. Weinstein reflects on how the promise of social media shifted into something more manipulative, saying, “It's time to take back control from a world where surveillance capitalism is the norm.” Marc and Mark explore whether it's possible to restore privacy and trust in the online space. They discuss the role of government and corporations in this challenge, with Weinstein emphasizing the importance of “data portability” and stronger user identification systems to protect future generations. He explains, “It's not too late for our kids… We can fix this, but it requires strong tools and the right regulations to create real change.” Weinstein also touches on the role of monopolies in shaping the internet, highlighting the challenges companies like Google and Meta pose to a fair and open market. Marc poses tough questions about the motivations behind big tech, privacy promises, and the genuine actions needed to make a difference. With practical solutions and a focus on the future, Weinstein presents an urgent call to action, saying, “We are at a pivotal moment… It's time for an epic reboot, and we've got this if we work together.” Learn more about your ad choices. Visit megaphone.fm/adchoices

You might be surprised to learn that the famous “www” in website addresses didn't originate in Silicon Valley or New York, but at the European Organisation for Nuclear Research, known as CERN for short, which is situated on the French-Swiss border close to Geneva.  It was 1989 when British computer scientist Tim Berners-Lee came up with the idea for a hypertext system. Essentially, it was a way to connect different pieces of data through links, creating something like a giant web that would work via the internet. Aren't internet and web the same thing?  What about the other parts of a web address then, like https or “.com” at the end? In under 3 minutes, we answer your questions! To listen to the last episodes, you can click here: How to protect your art from AI exploitation? What is the internet of senses? What is Web 3.0? A podcast written and realised by Joseph Chance. Learn more about your ad choices. Visit megaphone.fm/adchoices

All links and images for this episode can be found on CISO Series. Check out this post for the discussion that is the basis of our conversation on this week's episode co-hosted by me, David Spark (@dspark), the producer of CISO Series, and Geoff Belknap (@geoffbelknap). Joining us is Davi Ottenheimer, vp, trust and digital ethics, Inrupt. Sir Tim Berners-Lee co-founded Inrupt to provide enterprise-grade software and services for the Solid Protocol. You can find their open positions here. In this episode: LLMs lack integrity controls A valid criticism Doubts in self-policing AI New tech, familiar problems  Thanks to our podcast sponsor, Concentric AI Concentric AI's DSPM solution automates data security, protecting sensitive data in real-time. Our AI-driven solution identifies, classifies, and secures on-premises and cloud data to reduce risk across your enterprise. Seamlessly integrated with tools like Microsoft Copilot, Concentric AI empowers your team to innovate securely and maintain compliance all while eliminating manual data protection tasks. Ready to put RegEx and trainable classifiers in the rear view mirror? Contact Concentric AI today!

Early social media pioneer Mark Weinstein is deeply disturbed by the current state of social media. He's not alone of course, but in his new book, Restoring Our Sanity Online, Weinstein lays out what he boasts is a “revolutionary social framework” to clean up social media. The book comes with blurbs from tech royalty like Sir Tim Berners-Lee and Steve Wozniak, but I wonder if Weinstein, in his attempt to right social media through a more decentralized Web3 style architecture , is trying a fix yesterday's problem. In tech, timing is everything and the future of online sanity, as Gary Marcus noted a couple of days ago on this show, will be determined by our ability to harness AI. Rather than social media, that's what we now need a revolutionary framework to protect us from. MARK WEINSTEIN is a world-renowned tech entrepreneur, contemporary thought leader, privacy expert, and one of the visionary inventors of social networking. His adventure in social media has lasted over 25 years through three award-winning personal social media platforms enjoyed by millions of members worldwide. Mark is frequently interviewed and published in major media including the Wall Street Journal, New York Times, Fox, CNN, BBC, PBS, Newsweek, Los Angeles Times, The Hill, and many more worldwide. He covers topics including social media, privacy, AI, free speech, antitrust, and protecting kids online. During his social media years, Mark's advisors have included Sir Tim Berners-Lee, the inventor of the Web; Steve “Woz” Wozniak, co-founder of Apple; Sherry Turkle, MIT academic and tech ethics leader; Raj Sisodia, co-founder of the Conscious Capitalism movement; and many others. A leading privacy advocate, Mark's landmark 2020 TED Talk, “The Rise of Surveillance Capitalism,” exposed the many infractions and manipulations by Big Tech, and called for a privacy revolution. Mark has also been listed as one of the “Top 8 Minds in Online Privacy” and named “Privacy by Design Ambassador” by the Canadian government.Named as one of the "100 most connected men" by GQ magazine, Andrew Keen is amongst the world's best known broadcasters and commentators. In addition to presenting KEEN ON, he is the host of the long-running How To Fix Democracy show. He is also the author of four prescient books about digital technology: CULT OF THE AMATEUR, DIGITAL VERTIGO, THE INTERNET IS NOT THE ANSWER and HOW TO FIX THE FUTURE. Andrew lives in San Francisco, is married to Cassandra Knight, Google's VP of Litigation & Discovery, and has two grown children.Keen On is a reader-supported publication. To receive new posts and support my work, consider becoming a free or paid subscriber. This is a public episode. If you'd like to discuss this with other subscribers or get access to bonus episodes, visit keenon.substack.com/subscribe

Plongeons ensemble dans les coulisses de l'invention du World Wide Web, un événement qui a profondément marqué l'histoire de l'informatique et des technologies de l'information.

August 6, 1991. British computer programmer Tim Berners-Lee launches a digital information revolution when he uploads the first site to the World Wide Web.Support the show! Join Into History for ad-free listening and more.History Daily is a co-production of Airship and Noiser.Go to HistoryDaily.com for more history, daily.See Privacy Policy at https://art19.com/privacy and California Privacy Notice at https://art19.com/privacy#do-not-sell-my-info.

In this episode of the WP Builds Podcast, Nathan Wrigley and David Waumsley discuss the significant and evolving role of AI on the web, focusing on the World Wide Web Consortium's (W3C) new report titled "AI and the Web, Understanding and Managing the Impact of Machine Learning Models on the Web". The episode delves into AI's dual challenges: data quality and environmental impact. We explore ethical and societal implications, such as privacy, transparency, and the potential for AI to undermine human creativity and entry-level jobs. We also address the importance of standards, regulatory frameworks, and Tim Berners-Lee's optimistic vision of AI, emphasising the need for collaborative and ethical AI development. Go listen...

1991 was a year unlike any other. KFC changed their name to avoid paying royalties to the “trademarked” commonwealth for which they were named (whereas K-Y Jelly could not be reached for comment), Terminator 2:  Judgment Day was blowing up the box office as the number one movie in America, the first ever “world wide web” website was introduced to the world by Tim Berners-Lee, and just 6 days after that, on August 12th, 1991, Coroner's fourth album (Mental Vortex) AND Metallica's self-titled fifth album were BOLTH released on the EXACT same day.    It's time to get in the time machine and get ready to start “shooting ropes & painting walls” with our “squeezies” as we reveal the name of the band many have notoriously deemed “the hawk-tuah of metal”, as well as the frontman who resembled “a hot Canadian chick” (back in the day) before touring with Pantera, because we're going back to a time when high school was everything and the idea of retiring to the swingingest, most syphilis-infested subdivision in The Sunshine State was some abstract, fantastical, utopian concept that stretched far beyond the comprehension of our young, teenage, “brain snagged” minds.   “AwwwwwwwwwwwwwwwwwwwwwMannnnnnn” it's time to learn the key ingredients of “vampire jerky” and remember that “you can still rock with a high voice” (even if you've got on your “gloves of shame”). Find out where you DO NOT want to get “heartworms”, be sure to establish firm boundaries so you'll know exactly where “the aftermarket stuff stops with the ladies”, prepare to enjoy some “tangy flan” (courtesy of the outro-reel super-mix) and JOIN US as we reflect on all the fantastic metal released on August 12th, 1991 and the other 364 days of that year as we travel back in time to THE YEAR OF OUR RIFF LORD: 1991.   Visit www.metalnerdery.com/podcast for more on this episode Help Support Metal Nerdery https://www.patreon.com/metalnerderypodcast Leave us a Voicemail to be played on a future episode: 980-666-8182   Metal Nerdery Tees and Hoodies – metalnerdery.com/merch and kindly leave us a review and/or rating on the iTunes/Apple Podcasts - Spotify or your favorite Podcast app Listen on iTunes, Spotify, Podbean, or wherever you get your Podcasts. Follow us on the Socials: Facebook - Instagram - Twitter Email: metalnerdery@gmail.com   Can't be LOUD Enough Playlist on Spotify Metal Nerdery Munchies on YouTube @metalnerderypodcast   Show Notes: (00:01): #herewego (“The button's red…”) / #vampirejerky / “It's something new…”/ #DryJuly (“Wait…no lube?”) / #oldsmokey #rootbeermoonshine #thisepisodesclinkyoftheepisode / ***WARNING: #listenerdiscretionisadvised ***/ #theverdict / “At the tip…but the back end…”/ “It doesn't have #bubbles …”/ ***WELCOME BACK TO THE METAL NERDERY PODCAST!!!*** / “Wait, do it one more time…”/ #recordscratch / “It's called #discipline …”/ “Just six?”/ “Next money shot was like #PeterNorth …”/ #thisepisodesbeeroftheepisode #CreatureComfort #AthensGeorgia #Tropicalia #sixpointsixpercentABV    (05:58): #RussellsReflectionsASMR regarding the #NickelbackDocumentary on #Netflix / “Their influences totally make sense…”/ #stripclubcore / #billboardtopten / “That's probably why they're hated…”/ “Look at #KISS …”/ #songwriting / “You've got #OneLifeToLive …”/ “That's like a neighborhood…”/ “That's a metal label…”/ The #hawktuah of metal…/ #PATREONSHOUTOUT (Come and #JoinUs on the Patreon at patreon.com/metalnerdery ) / “Have a good June…”/ “He's so nice he joined us twice…”/ “Speaking of…we owe him a shirt.”    (13:47): If you want to send us some correspondence you can email us at metalnerdery@gmail.com or hit us up on #YouTube or #Instagram or #Facebook OR you can GIVE US A CALL AND LEAVE US A VOICEMAIL AT 980-666-8182!!! / #TripSix #WaxAudio (CONFIRM THE NAME) #MuttLange / #isitgay? / “I beg to disagree…”/ #clonesex / “Do they push too far?” / “Does he fuck an octopus?” / #octopushandy vs #peanutbutter / “It's only gross if you…”/ #youreworse #hogstoryparttwo / “I need a shower…”   (19:12): #TheDocket / “What were YOU guys doing in #1991?” / METAL NERDERY PODCAST PRESENTS:  1991 – YEAR IN METAL / ***check out our 1994 episode and our 3-part 1990 episode (30 years in metal) ***/ “Everybody knows what came out in '91…”/ NOTE:  That was March 1992, not 1991. / “Loads everywhere when they came to Atlanta…” / “They had to appeal to all the cooze out there first…”/ “Start off soft and get harder…” / #naturalprogression / #SkidRow SLAVE TO THE GRIND / “I just had a realization…”/ #OzzyOsbourne (MS? “Something happened in '91…”) #allegedly (“I think you just like saying tinker…”) / “They should map over their #cokelines from prior releases…”/ MR. TINKERTRAIN (“Now it does.”) / “Squeezies?” / “Settle your ass…” / #blackdog   (30:12): “We should play something thrashy…”/ “Stop with the yawns, dude…”/ “We're gonna move to that #Florida #SwingingNeighborhood …”/ #roastbeefjerky / #TheVillages / “Isn't that an old school #STD?” / “If the sores aren't there, you're good to go…”/ “AIDS part 2?” / #Athiest MOTHER MAN and some #GhostStory #tangentionalality / #Entombed LIVING DEAD / “It works for them…”/ “The drum mix reminds me of #TheMasquerade …”/ “Let's change things up a little…” / #Primus TOMMY THE CAT (“That's '91 all day long…”) / “And I say unto thee…”/ “They get MY Nickelback hate…”/ #ArmoredSaint (“I'm sorry, who's bush?”) / “Where does the #aftermarket stuff stop with the ladies?” / REIGN OF FIRE #powermetal / “This is a #soundtrack song…” / “He sounds like a younger #JohnBush / “It just seems weird for '91…” / “Things got progressively lighter…” / “Radio kills every star…” / “The song about the dead girlfriend?” / #readthoselyrics   (43:58): #Death SUICIDE MACHINE / “Everything's busy…”/ “I think we did that before we started calling it #InsideTheMetal …”/ “What would be a deep cut, if you had to pick one?” / #Sepultura ALTERED STATE / “It reminds me of #CrashBandicoot and #PlayStationOne …”/ “This almost sounds like a soundtrack tune…”/ #TypeONegative UNSUCCESSFULLY COPING WITH THE NATURAL BEAUTY OF INFIDELITY #IKnowYoureFuckingSomeoneElse (“Slam on the brakes!”) / #AwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwMannnnnn (“What a break down…”) / #justafriend / “That's straight up doom right there…”/ “Hey don't think I don't know what you're doing, you stupid twat!” / #HalloweenVibesASMR / Reflecting on the first time we ever saw #TypeONegative live at #TheInternationalBallroom / #MonsterMagnet (“'94, you were way off!”) MEDICINE #usethoseheadphones    (57:57): #TheAccused had an album in '91, right? / “No, it's not funny, but what's hysterical is…”/ “They all sound like that?” / NO HOPE FOR RELIEF (“That's the #weedlywoo of drums…”) & SATURDAY NIGHT SPECIAL / “Vocals by TAZ…”/ “Where do we wanna go next?” / “I feel like Bill likes #TheBlackAlbum as much as he likes #KISS…”/ #Coroner METAMORPHOSIS (NOTE:  #TBA and #MentalVortex #bolth came out on August 12, 1991) / “A dude named Stacey?”/ #HallowsEve / “What in the world?” / “Can you imagine #FDR introducing #WinstonChurchill as #AdolfHitler?” / “Have you seen the dick on that motherfucker?” / #Venom TRIBES (“That's not #Cronos …”)   (1:11:00): “Just for fun…” / #FatesWarning (“They're part of the Big 3 or 4 of #progressivemetal I think…”) / POINT OF VIEW (“That's kinda rockin'…”) / “Get ready for the #highsinging …” / #glovesofshame (“It sounds like #OperationMindcrime …”) / “Nobody said I was a singer…”/ “What's your favorite?” / THERAPY / “Can we hear the very intro of MONSTER SKANK?” / “We've got a lot to go here…”/ “You've gotta play #COC …”/ #CorrosionOfConformity WHITE NOISE (“This is probably their only real thrash album…”) / “That's European American privilege noise…”/ “Number 1 #Billboard single, 1991…” / #itsnotmetal / “Y'all bang to that?” / “Those were all the metal bands that made it…”/ “Is that what happens when…cut themselves?” / #sackful #Krystals / “Really good bad…”/ “You see all the people getting shot ordering food in the drive thru these days?” / “Oh boy…all the pressure…”/ #Metallica OF WOLF AND MAN / “No shape shift or nothin', huh?” / #Overkill BARE BONES (“It's #Halloween …it's not but it makes you think of it.”) / “You may be right, and I may be crazy…”/ NOTE:  see also #KingDiamond #Them OUT FROM THE ASYLUM / “And for fun…the Halloween theme?” / “Is that a #threesome…does it count?” / “It's coming right before #theendoftheworld …”/ “Y'all are too white to say that…”/ #markthetime please…/ “Once we get bigger than Rogan…” / “Oh yeah, he ripped off #BillHicks persona, set, etc…he stole everything from Bill Hicks…”/ “#DietBillHicks is what you saw…”/ “How are we looking on those #OperationOrangeTits shirts…”/ #3DCheetos / ***THANK YOU ALL FOR JOINING US AND THANK YOU TO OUR PATREONS FOR YOUR SUPPORT!!!*** / #GrungeNerderyPodcast / ***COME ON DOWN TO THE #BUNKERPOONGIFTSHOPPE AND PICK UP SOME #METALNERDERYPODCAST MERCH AT metalnerdery.com/merch *** / #outroreel #supermix #pissandpennies  

Ever wondered how the digital revolution came to be? Was it the work of lone geniuses, or was there something more at play? In this episode, we delve into Walter Isaacson's "The Innovators," uncovering the collaborative efforts and key principles that have shaped our technological landscape.In the world of investing and entrepreneurship, building a multidisciplinary mental model is key to success. "The Innovators" reveals that diverse, collaborative teams have historically been the driving force behind groundbreaking solutions.In my martial arts days, a coach taught me to study exceptional role models – a strategy akin to the famous Harvard Business Cases. Analyze success, discover core principles, then adapt them to your own unique path. After all, as Bruce Lee said, "Absorb what is useful, reject what is useless, and add what is essentially your own."That's the lens I bring to biographies – extracting valuable lessons amidst the complexities of each individual story.This episode dissects 10 crucial tools for fostering innovation, drawing on stories from the book and my own experiences as an entrepreneur and investor. From visionary thinking and customer-centricity to the power of persistence and collaboration, we'll explore the strategies that can help you identify winning teams and create an environment where innovation thrives.Book on Amazon[Link to Amazon]Problems This Solves:Overwhelmed by history books? This concise summary delivers the most relevant insights for entrepreneurs and investors.Unsure how to apply innovation principles? We'll provide actionable takeaways and reflection questions.Curious about the minds behind the digital age? Gain insights into the collaborative spirit that drives technological progress.Why Listen:Discover the 10 tools for innovation: Uncover the strategies that have fueled successful collaborations and groundbreaking technologies.Learn from real-world examples: Hear stories from the book and my own experiences that illustrate these principles in action.Apply the lessons to your own ventures: Reflect on how you can foster innovation and build winning teams in your own organization.Quotes:"Creativity is a collaborative process. Innovation comes from teams more often than from the lightbulb moments of lone geniuses." - Walter Isaacson"The best way to predict the future is to invent it." - Alan Kay (as quoted in "The Innovators")Timestamps:(00:00) Intro(04:18) Walter Isaacson(08:21) Overview of the Book(12:28) Tool #1: Ada Lovelace and the Power of Visionary Thinking(18:01) Tool #2: Collaborative Teamwork(23:13) Tool #3: Craftsmanship(29:00) Tool #4: The Entrepreneurial Spirit and Culture of Innovation(35:32) Tool #5: Leadership that Breeds Innovation(42:13) Tool #6: Persistent Innovation(47:19) Tool #7: Public Awareness and Advocacy(53:48) Tool #8: Customer Centricity(58:51) Tool #9: Technicians Collaborating with Business People(01:03:20) Tool #10: Building Collaborative Ecosystems(01:07:55) Key Takeaways(01:14:00) Tl;dr Episode SummarySend us a Text Message.Support the Show.Join the Podcast Newsletter: Link

Today I'm speaking with Dr. James Hendler, the Director and professor at Rensselaer Polytechnic Institute and a pioneer of the Semantic Web. For those in the tech and academic circles, Jim Hendler is a name synonymous with transformative changes in how we interact with and understand the web.This is a truly enlightening conversation with Jim! He brings a rich tapestry of experiences, having worked at places like DARPA and on foundational projects that have shaped the internet and artificial intelligence as we know them today. During our conversation, Jim talks about his early interests in technology and growing up in New York, his extensive professional journey through the early days of AI and working on the Semantic Web with the likes of Tim Berners-Lee, and his insightful views on emerging technologies like web3.Jim shines a light on a lot of aspects of technology development and application, reflecting on the evolution from early AI research to today's state of the field. We'll explore his significant contributions to the field, including his work on the Semantic Web, his time at DARPA, the early days of AI, and his thoughts on the future of the internet.Show Notes and TranscriptsThe GRTiQ Podcast takes listeners inside web3 and The Graph (GRT) by interviewing members of the ecosystem.  Please help support this project and build the community by subscribing and leaving a review.Twitter: GRT_iQwww.GRTiQ.com 

Voyager 1 update The Web turned 35 and Dad is disappointed Automakers sharing driving data with insurance companies A flaw in Passkey thinking Passkeys vs 2fa Sharing accounts with Passkeys Passkyes vs. Passwords/MFA Workaround to sites that block anonymous email addresses Open Bounty programs on HackerOne Steve on Twitter Ways to disclose bugs publicly Security by obscurity Something you have/know/are vs Passkeys Passkeys vs TOTP Inspecting Chrome extensions Passkey transportability Morris the Second Show Notes - https://www.grc.com/sn/SN-966-Notes.pdf Hosts: Steve Gibson and Mikah Sargent Download or subscribe to this show at https://twit.tv/shows/security-now. Get episodes ad-free with Club TWiT at https://twit.tv/clubtwit You can submit a question to Security Now at the GRC Feedback Page. For 16kbps versions, transcripts, and notes (including fixes), visit Steve's site: grc.com, also the home of the best disk maintenance and recovery utility ever written Spinrite 6. Sponsors: robinhood.com/boost GO.ACILEARNING.COM/TWIT joindeleteme.com/twit promo code TWIT vanta.com/SECURITYNOW

Voyager 1 update The Web turned 35 and Dad is disappointed Automakers sharing driving data with insurance companies A flaw in Passkey thinking Passkeys vs 2fa Sharing accounts with Passkeys Passkyes vs. Passwords/MFA Workaround to sites that block anonymous email addresses Open Bounty programs on HackerOne Steve on Twitter Ways to disclose bugs publicly Security by obscurity Something you have/know/are vs Passkeys Passkeys vs TOTP Inspecting Chrome extensions Passkey transportability Morris the Second Show Notes - https://www.grc.com/sn/SN-966-Notes.pdf Hosts: Steve Gibson and Mikah Sargent Download or subscribe to this show at https://twit.tv/shows/security-now. Get episodes ad-free with Club TWiT at https://twit.tv/clubtwit You can submit a question to Security Now at the GRC Feedback Page. For 16kbps versions, transcripts, and notes (including fixes), visit Steve's site: grc.com, also the home of the best disk maintenance and recovery utility ever written Spinrite 6. Sponsors: robinhood.com/boost GO.ACILEARNING.COM/TWIT joindeleteme.com/twit promo code TWIT vanta.com/SECURITYNOW

Voyager 1 update The Web turned 35 and Dad is disappointed Automakers sharing driving data with insurance companies A flaw in Passkey thinking Passkeys vs 2fa Sharing accounts with Passkeys Passkyes vs. Passwords/MFA Workaround to sites that block anonymous email addresses Open Bounty programs on HackerOne Steve on Twitter Ways to disclose bugs publicly Security by obscurity Something you have/know/are vs Passkeys Passkeys vs TOTP Inspecting Chrome extensions Passkey transportability Morris the Second Show Notes - https://www.grc.com/sn/SN-966-Notes.pdf Hosts: Steve Gibson and Mikah Sargent Download or subscribe to this show at https://twit.tv/shows/security-now. Get episodes ad-free with Club TWiT at https://twit.tv/clubtwit You can submit a question to Security Now at the GRC Feedback Page. For 16kbps versions, transcripts, and notes (including fixes), visit Steve's site: grc.com, also the home of the best disk maintenance and recovery utility ever written Spinrite 6. Sponsors: robinhood.com/boost GO.ACILEARNING.COM/TWIT joindeleteme.com/twit promo code TWIT vanta.com/SECURITYNOW

Voyager 1 update The Web turned 35 and Dad is disappointed Automakers sharing driving data with insurance companies A flaw in Passkey thinking Passkeys vs 2fa Sharing accounts with Passkeys Passkyes vs. Passwords/MFA Workaround to sites that block anonymous email addresses Open Bounty programs on HackerOne Steve on Twitter Ways to disclose bugs publicly Security by obscurity Something you have/know/are vs Passkeys Passkeys vs TOTP Inspecting Chrome extensions Passkey transportability Morris the Second Show Notes - https://www.grc.com/sn/SN-966-Notes.pdf Hosts: Steve Gibson and Mikah Sargent Download or subscribe to this show at https://twit.tv/shows/security-now. Get episodes ad-free with Club TWiT at https://twit.tv/clubtwit You can submit a question to Security Now at the GRC Feedback Page. For 16kbps versions, transcripts, and notes (including fixes), visit Steve's site: grc.com, also the home of the best disk maintenance and recovery utility ever written Spinrite 6. Sponsors: robinhood.com/boost GO.ACILEARNING.COM/TWIT joindeleteme.com/twit promo code TWIT vanta.com/SECURITYNOW

Voyager 1 update The Web turned 35 and Dad is disappointed Automakers sharing driving data with insurance companies A flaw in Passkey thinking Passkeys vs 2fa Sharing accounts with Passkeys Passkyes vs. Passwords/MFA Workaround to sites that block anonymous email addresses Open Bounty programs on HackerOne Steve on Twitter Ways to disclose bugs publicly Security by obscurity Something you have/know/are vs Passkeys Passkeys vs TOTP Inspecting Chrome extensions Passkey transportability Morris the Second Show Notes - https://www.grc.com/sn/SN-966-Notes.pdf Hosts: Steve Gibson and Mikah Sargent Download or subscribe to this show at https://twit.tv/shows/security-now. Get episodes ad-free with Club TWiT at https://twit.tv/clubtwit You can submit a question to Security Now at the GRC Feedback Page. For 16kbps versions, transcripts, and notes (including fixes), visit Steve's site: grc.com, also the home of the best disk maintenance and recovery utility ever written Spinrite 6. Sponsors: robinhood.com/boost GO.ACILEARNING.COM/TWIT joindeleteme.com/twit promo code TWIT vanta.com/SECURITYNOW

Entertaining drama from award-winning writer Matthew Broughton exploring probably the biggest turning point in recent history: the creation of the World Wide Web, and its impact on one family in the decades that follow.In August 1991, the first website goes live. At exactly the same time, a baby is born...Julie....Claudie Blakley Vic....Dana Haqjoo Young Lucy...Astrid le Fleming Lucy....Katie Redford Young Ben....Bertie Creswell Ben....Luke Nunn Narrator....Peter Marinker With the voices of Josh Bryant-Jones, Jessica Enemokwu, Laura Power, Maxim Reston.Technical producers...Keith Graham, Andy Garratt, Peter Ringrose Production co-ordinator...Jonathan PowellWritten by Matthew Broughton Directed by Abigail le FlemingA BBC Audio Production for BBC Radio 4Extract from 2012 Olympics opening ceremony, BBC audio, © International Olympic Committee. Extracts of Sir Tim Berners-Lee from an interview with CNBC, and The Richard Dimbleby Lecture: The World Wide Web - A Mid-Course Correction, BBC

This week, we talk to Carl Malamud, heralded as "The Father of Internet Radio". We trace Carl's journey from the early buzz of bulletin board systems to setting up the first-ever Internet radio station back in 1992. Carl shares tales from the creation of his flagship show "Geek of The Week," where Internet legends like Tim Berners-Lee took the mic, to orchestrating the monumental Internet 1996 World Exposition, a digital World's Fair that connected millions globally. Internet Talk Radio Archives: https://archive.org/details/RT-FM Public.Resource.Org: https://public.resource.org/ Bangalore Literature Festival: https://archive.org/details/bangalore.literature.festival.2023 Internet Talk Radio on Computer Chronicles: https://youtu.be/U_o8gerare0?si=IciilvN84v4DpYqY&t=1027  Contents: 00:00 - The Week's Retro News Stories 49:05 - Carl Malamud Interview Please visit our amazing sponsors and help to support the show: Bitmap Books https://www.bitmapbooks.com/ We need your help to ensure the future of the podcast, if you'd like to help us with running costs, equipment and hosting, please consider supporting us on Patreon: https://theretrohour.com/support/ https://www.patreon.com/retrohour Get your Retro Hour merchandise: https://bit.ly/33OWBKd Join our Discord channel: https://discord.gg/GQw8qp8 Website: http://theretrohour.com Facebook: https://www.facebook.com/theretrohour/ Twitter: https://twitter.com/retrohouruk Instagram: https://www.instagram.com/retrohouruk/ Twitch: https://www.twitch.tv/theretrohour Show notes: Amstrad's Return Under Lord Alan Sugar: https://tinyurl.com/2kerma83 Atari 2600 Movie Experience: https://tinyurl.com/2vna892p Indie Game Thunder Helix Pays Homage to Classics: https://tinyurl.com/2s4jdjz6 Jeff Minter's Interactive Documentary Preview: https://tinyurl.com/4wxrrybm Unearthed Time Splitters 4 Prototype: https://tinyurl.com/3ustfvwh