Podcasts about Chromium

Our daily digital tools—browsers, apps, and smart devices—offer convenience but also expose us to hidden security risks. This guide reveals how ordinary technologies can imperil privacy and safety, focusing on three major areas: browser extensions, typo-prone website visits, and internet-connected cameras.The Hidden Spy on Your BrowserBrowser extensions, designed to block ads or save passwords, can also harvest personal data or hide malware. Researchers recently found popular Chromium extensions secretly recording entire conversations with AI chatbots such as ChatGPT and Gemini—logging prompts, responses, and timestamps, then transmitting them to outside servers. Many of these tools were deceptively labeled as privacy enhancers and featured in official stores, masking their data collection practices under carefully worded policies.Another danger, exemplified by the GhostPoster malware campaign on Firefox, showed how malicious code can bypass security. The attackers embedded it in an image file within the extension's icon—an area security software rarely scans. The code then downloaded additional payloads from remote servers in timed stages to avoid detection. Together, these examples illustrate that browser extensions can function as open doors for data theft and hidden malware, exploiting misplaced trust.When a Typo Becomes a TrapEven something as minor as mistyping a web address now carries serious risk. A "parked domain"—an inactive site often resembling a misspelled version of a popular URL—has become a common tool for cybercriminals. Once relatively harmless, these domains are now overwhelmingly malicious. According to Infoblox research, over 90% of visits to parked domains result in exposure to scams, illegal content, or automatic malware downloads, compared to less than 5% a decade ago.Simply visiting one of these pages can trigger pop-ups for fake antivirus subscriptions, redirect you to scam sites, or silently infect your device. In today's environment, a typo is no longer an inconvenience—it's a gateway to immediate compromise.The Camera That Turns on YouInternet-connected security cameras promise safety but can create severe privacy breaches when poorly secured. A massive hack in South Korea exposed footage from over 120,000 cameras in homes, clinics, and salons, which hackers later sold online. Most intrusions stemmed from weak or unchanged default passwords. This event underscores that devices we install for protection can become surveillance tools for attackers if we fail to secure them properly.Staying Smart and SafeThe dangers from compromised extensions, malicious parked domains, and insecure cameras highlight one shared truth: convenience often conceals risk. To navigate safely, users should: 1. Question their tools—research extensions or apps and limit unnecessary permissions. 2. Avoid careless mistakes—double-check URLs before pressing enter. 3. Secure devices—use strong, unique passwords and update firmware regularly.Ultimately, cyber safety depends on ongoing vigilance rather than one-time fixes. Like Santa in a playful ESET report who “tightened his security” after a fictional data breach, users too can—and must—strengthen their defenses. Staying alert, skeptical, and proactive transforms technology from a source of danger into a safer partner in modern life.

C'est un mal bien connu de tous les internautes : cette accumulation incontrôlable d'onglets ouverts, dès lors que l'on cherche des informations sur plusieurs sites à la fois. On s'y perd rapidement, et la mémoire vive de l'ordinateur fond comme neige au soleil. Pour répondre à ce problème devenu presque structurel, Google dévoile une expérimentation ambitieuse : un nouveau navigateur dopé à l'intelligence artificielle Gemini, baptisé Disco.Sa première fonctionnalité expérimentale s'appelle GenTabs. Le principe est radical : confier à l'IA la gestion du contenu de vos onglets. Plutôt que de jongler entre dix pages ouvertes, Gemini analyse l'ensemble des informations affichées et les transforme en une application web interactive, générée à la demande. Une approche qui rappelle le « vibe coding », cette manière de créer des outils à partir d'une simple intention exprimée en langage naturel.Dans les démonstrations publiées par Google, l'interface se divise en deux parties. À gauche, un chatbot Gemini classique. À droite, la fenêtre de navigation. Exemple proposé : l'organisation d'un voyage. L'utilisateur discute avec Gemini, consulte des pages d'activités locales, puis l'IA suggère de créer un outil interactif. En quelques secondes, une carte s'affiche, regroupant toutes les informations collectées, avec filtres par dates, options météo et planification d'itinéraire. Aucun code à écrire, aucune configuration technique à comprendre. Tout est généré automatiquement. Google imagine déjà d'autres usages : des outils pour visualiser des concepts scientifiques, comparer des meubles dans une pièce, créer de petits jeux, planifier ses repas ou organiser un potager. Le navigateur devient ainsi moins un lecteur de pages qu'un atelier de synthèse et d'interaction, piloté par l'IA.Pour l'instant, Disco reste une expérimentation issue de Google Labs. Basé sur Chromium, il n'est pas destiné à un usage quotidien et nécessite une inscription sur liste d'attente. Mais derrière la prouesse technique se pose une question de fond : quel avenir pour les sites web eux-mêmes ? Cette interrogation avait déjà émergé avec les résumés générés par IA dans le moteur de recherche. Si les contenus sont analysés, synthétisés et consommés par des machines plutôt que par des humains, que devient le modèle économique du web ? La publicité, aussi agaçante soit-elle, finance encore une grande partie des sites. Sans lecteurs humains, plus de clics, plus de revenus. En cherchant à résoudre le chaos des onglets, Google esquisse peut-être un futur plus fluide pour les utilisateurs… mais potentiellement bien plus fragile pour l'écosystème du web tel que nous le connaissons aujourd'hui. Hébergé par Acast. Visitez acast.com/privacy pour plus d'informations.

Send us a textA tiny mineral with a big impact can change how you feel during the day -from steadier energy to clearer thinking and fewer snack attacks. So, what is this important mineral? Chromium, the quiet cofactor that helps your body process carbs, fats, and proteins more efficiently. Speaking of Women's Health Podcast Host Dr. Holly L. Thacker explains why “food first” beats a crowded supplement shelf, and how easy wins—broccoli, green beans, quinoa, lean proteins, dairy, and even stainless steel cookware—can boost chromium naturally.Dr. Thacker shares how much chromium we need daily, highlights who might be at risk for deficiency, and explains why more isn't better with trace minerals.Support the show

An open source library used by many of the most well known applications, including VirtualBox, GNOME, Edge, & VLC, has been officially abandoned and is now marked as “unmaintained”.More from The Lunduke Journal:https://lunduke.com/ This is a public episode. If you'd like to discuss this with other subscribers or get access to bonus episodes, visit lunduke.substack.com/subscribe

Curious about how to succeed on a vegan or plant-based diet? In this episode of Nutrition for Noobs, Michelle and Kevin break down the essential nutrients you need to thrive, including B12, zinc, magnesium and chromium, while highlighting why processed plant-based foods can sabotage your health. Learn practical tips on improving diet quality, optimizing nutrient absorption, and understanding common deficiencies that affect vegans and omnivores alike. Plus, discover the science behind supplementation.Whether you're new to plant-based eating or a long-time vegan, this episode is packed with evidence-based advice to help you feel your best.Key Topics Covered:Why B12 is critical for brain and nerve health, and how to supplement effectivelyCommon nutrient deficiencies in vegans and omnivores, and what affects absorptionPractical strategies to optimize diet quality and nutrient intakeTune in and empower yourself to thrive on a plant-based diet without compromising your health!Please subscribe and drop us a review—your feedback helps fellow noobs find their way to better nutrition.Have a question for Michelle? Get in touch at n4noobs@gmail.com or on Facebook at https://www.facebook.com/nutritionfornoobs.Link to Dr. Klapper's study: https://www.doctorklaper.com/vegan-health-studyLink to Dr. Klapper's on demand video (100min) Thriving on a Plant-based Diet: https://vimeo.com/ondemand/thriving

C'est une plainte devenue quasi quotidienne chez les joueurs comme chez les télétravailleurs : Discord consomme de plus en plus de mémoire vive. La plateforme de chat vocal et textuel confirme aujourd'hui ce que beaucoup constataient déjà : lorsque plusieurs serveurs sont ouverts, l'application peut dépasser les 4 gigaoctets de RAM, au point de ralentir sérieusement Windows 11 et les jeux lancés en parallèle.Face à la grogne, Discord teste désormais une solution radicale : surveiller sa propre consommation de mémoire… et se relancer automatiquement lorsqu'elle dépasse un seuil critique. L'objectif est simple : libérer de la RAM pour éviter que la machine ne suffoque. Une mesure présentée comme un garde-fou, mais qui révèle surtout l'ampleur du problème. Cette gourmandise n'est pas qu'une question d'usage intensif. Discord repose sur le framework Electron, qui embarque en réalité un navigateur complet basé sur Chromium. Autrement dit, chaque fenêtre de discussion fonctionne comme une page web à part entière, avec son moteur JavaScript, ses composants, ses modules. Dans des conditions dites « normales », l'application flirte déjà avec le gigaoctet de mémoire. Et après plusieurs heures d'utilisation, entre appels vocaux, partages d'écran et navigation frénétique, la consommation peut exploser.Les développeurs reconnaissent d'ailleurs l'existence de fuites de mémoire. Neuf ont été corrigées ces derniers mois, permettant une réduction d'environ 5 % pour les profils les plus gourmands. Un progrès, certes, mais encore loin de transformer Discord en logiciel léger. D'où cette nouvelle expérimentation : si l'application dépasse 4 Go de RAM, qu'elle tourne depuis plus d'une heure, que l'utilisateur est inactif depuis trente minutes et qu'aucun appel n'est en cours, alors Discord se ferme… puis redémarre automatiquement. L'opération ne peut se produire qu'une fois toutes les 24 heures pour éviter les interruptions en boucle.Sur le papier, la mécanique est rassurante. Dans la pratique, elle ressemble surtout à un pansement posé sur une architecture lourde. Et Discord est loin d'être un cas isolé. D'autres applications comme Microsoft Teams ou la nouvelle version de WhatsApp pour Windows affichent elles aussi des consommations démesurées. Le problème devient d'autant plus sensible que le prix de la mémoire vive remonte. Tout le monde ne peut pas se permettre d'ajouter 16 Go de RAM pour suivre la course aux logiciels XXL. Entre applications toujours plus lourdes et matériel plus cher, les configurations modestes plient rapidement. Hébergé par Acast. Visitez acast.com/privacy pour plus d'informations.

Learn when supplements like chromium and milk thistle might help and when they won’t! Like many supplements, they’re not magic fixes! Dr Mary Barson and Dr Lucy Burns explain why real food, good sleep and movement matter most for your health and weight loss. You’ll find out what to look out for before spending money on supplements, plus get their easy six steps for success you can start today. Listen and discover what really works for better health! For more information about Real Life Medicine and our programs and special offers: https://www.rlmedicine.com/ Episode, show notes & transcript https://www.rlmedicine.com/are-chromium-or-milk-thistle-useful-for-weight-loss See omnystudio.com/listener for privacy information.

This show has been flagged as Clean by the host. A while ago I visited a web site that is an archive for old historical documents. It is a data base from where documents can be downloaded as pdf-files. As a visitor I can login to the archive as a guest. When I find a document of interest after search I can right click on the pdf icon and download the document. But I can not. No download when I click on the pdf icon. This is the first time I visit this archive so I do not know exactly how it works. It was time to investigate the root cause. I use Firefox on a Linux machine. I tested several methods to see if any would solve the issue. I tried by changing settings for pop-ups. I changed Firefox security settings. I disabled VPN. I disabled Firefox extensions for blocking trackers. I tested also the Chromium browser as well as the Epiphany browser. All those methods resulted in no difference; nothing happened. I was in contact to a friend on Windows and also staff at the Archive, both telling me that from Windows it worked, including with Firefox. So now I knew the archive works and that it works on Firefox. So I thought, can this somehow be related to Linux? I asked in a Linux forum if someone on Linux could test to download. One person in the forum tested and solved the problem. I would not define it as a Linux problem, but a site design that affected Linux users. The trouble was something I had not thought of: The User Agent. When my browser contact a web site, my browser can tell the site what kind of browser I use, which operating system I use and more. This information can be used by the site to optimize the presentation of the content for me. For to me unknown reason, maybe a mistake, maybe related to some old design compatibility issue, this site did not accept the information my user agent provided. The solution is to tell the web site I am something else. In the browser has Developer tools. When opening the developer tools from meny, typically a developer window with tools and analytics is opened at the bottom part of the web page. One tool is network. Within network I can simulate how the site looks on different devices, with different network connections and also with different User Agents. The tools are similar in both Firefox and Chromium. The exact list of standard options differ and Chromium has more options preloaded. In this specific case, when I in Developer tools on Firefox change User Agent to Chrome Desktop, which relates to Chrome on Windows as I understand, and then reload the web page I can now download the pdf file from the archive. When this web site interpret me to be this other type of user, they can understand each other without any issue. I have reported back to the site owner and hopefully this specific site will not need this work around for the browser User Agent in the future.Provide feedback on this episode.

פרק מספר 505 של רברס עם פלטפורמה - באמפרס מספר 89, שהוקלט ב-13 בנובמבר 2025, רגע אחרי כנס רברסים 2025 [יש וידאו!]: רן, דותן ואלון (והופעת אורח של שלומי נוח!) באולפן הוירטואלי עם סדרה של קצרצרים מרחבי האינטרנט: הבלוגים, ה-GitHub-ים, ה-Claude-ים וה-GPT-ים החדשים מהתקופה האחרונה.

For over 25 years, Concerned Citizens for Nuclear Safety (CCNS) has fought toprotect surface and groundwater from radioactive, toxic and hazardous contaminationfrom Los Alamos National Laboratory (LANL). In 2004, that campaign expanded tocontain the co-located perchlorate and chromium plume – contamination that migratedinto the top of the 1,000 foot deep aquifer below LANL, Pueblo de San Ildefonso andthe Española Basin Sole Source Drinking Water Aquifer. Despite federal assurancesand repeated promises of a solution, the plume remains unresolved.

✏️ Suscribirse https://youtu.be/rMiaGSWPZ1k WordPress 6.9 trae la Abilities API: el “idioma” que necesita la IA para actuar en tu web. En el episodio 240 de Negocios y WordPress hablamos de una mezcla muy realista: WordPress, inteligencia artificial, herramientas y “vida de autónomo” (con su caos incluido). Pero el centro del capítulo fue claro: WordPress 6.9 y la Abilities API, una pieza que, si trabajas con web y automatización, te cambia el mapa mental. Y sí, también salen temas de Stripe + Make, subidas de precios, Kit Digital, productividad con Todoist, IA en Gmail con Gemini, y ese clásico “tengo 20 suscripciones y debería borrar la mitad”. WordPress 6.9 y la Abilities API: el primer paso serio hacia IA “nativa” WordPress lleva tiempo moviéndose hacia IA, pero en 6.9 se ve un cambio: ya no es “un plugin que hace cosas”, sino infraestructura. La Abilities API introduce un registro central donde WordPress (core), themes y plugins pueden declarar “cosas que saben hacer” de forma estándar: qué hacen, qué entradas aceptan, qué devuelven y qué permisos requieren. Eso convierte WordPress en un sistema descubrible para agentes y automatizaciones. Si te quedas con una frase del episodio, sería esta: Abilities = API autodocumentada para que una IA no tenga que “adivinar” tu WordPress. En vez de pedirle a un modelo que improvise (y se invente macros, endpoints o parámetros), se le ofrece un catálogo de acciones reales. Qué es la Abilities API “en cristiano” y por qué no es solo para IA Abilities como “acciones con contrato” Cada ability es una acción concreta: por ejemplo, “contar posts”, “crear un producto”, “generar un informe”, “crear un CPT”, etc. Se registra en WordPress con wp_register_ability() y debe hacerse en el hook wp_abilities_api_init. Lo interesante es el “contrato”: Input: qué datos necesita (schema). Output: qué devuelve (schema). Permisos: quién puede ejecutarla. Callback: la función real que se ejecuta. Esto no solo sirve a ChatGPT o Claude; sirve a cualquier integración que quiera operar de forma fiable y repetible. Abilities + MCP: el combo que se viene En el episodio se enlaza esto con MCP (Model Context Protocol): si MCP es el “protocolo” para conectar un agente con herramientas, Abilities es el “mapa” de herramientas disponible dentro de WordPress. Por eso se entiende como un paso previo: sin abilities, el agente puede “conectar”, pero no sabe qué puede hacer ni cómo hacerlo. Casos de uso reales: WooCommerce MCP y JetEngine “con esteroides” WooCommerce: hablar con tu tienda (sin tocar la UI) Se mencionó que WooCommerce ya está explorando MCP como feature, activable desde ajustes avanzados (beta), para exponer operaciones de tienda a clientes IA con autenticación y permisos. Esto abre la puerta a cosas como: “¿Qué vendí esta semana?” “Sácame un informe de productos con caída de ventas” “Crea un descuento para esta categoría” “Revisa pedidos pendientes y agrúpalos por estado” WooCommerce lo plantea como una integración MCP estándar para que asistentes interactúen con la tienda. JetEngine: cuando un plugin se vuelve “operable” El ejemplo del episodio con JetEngine (Crocoblock) es justo lo que hace potente este enfoque: si JetEngine expone abilities para crear CPT, metaboxes, taxonomías, queries, etc., el agente ya no “alucina” sobre cómo se configura: ejecuta las operaciones oficiales que el plugin le ofrece. Eso reduce fricción, reduce errores y, sobre todo, reduce la típica situación de: “sí, sí… esto se hace con una macro que no existe”. (Como referencia, Crocoblock ha ido publicando avances de JetEngine 3.8 alrededor de MCP/AI en sus canales). WordPress no va tarde: AI Team y “AI Building Blocks” Otra idea importante del episodio: WordPress no está “desligado” del mundo IA. Existe un trabajo organizado dentro del ecosistema, con iniciativas como AI Building Blocks y el propio equipo de IA publicando avances y guías. Y además, Automattic también está empujando por su lado (WordPress.com, experimentos, etc.). El mensaje de fondo: IA va a entrar “por el core” y por los plugins grandes. Negocio real: cuando subes precios y descubres que Stripe enseña más que un curso En la parte de “vida real”, se contó un caso muy típico pero muy bien aterrizado: subida de precios por un cambio de costes (en el episodio, por el contexto del mercado avícola) y cómo eso te obliga a dominar: Stripe (productos, prices, suscripciones, subscription items) Airtable como fuente de control (campos “price ID actual” vs “price ID anterior”) Make como orquestador SendGrid para el aviso a clientes La clave técnica que se remarca: en Stripe no “editas” un price usado por suscripciones antiguas, sino que acoplas un price nuevo a la suscripción (sin reventar el historial). Eso es lo que te permite hacer una subida ordenada. (Buen recordatorio: el conocimiento útil suele venir de arreglar líos en producción). Productividad y herramientas: menos apps, mejores sistemas Todoist: prioridades y filtros para que no te “manden” las tareas viejas Se habló de algo muy común: no es que el sistema no funcione, es que lo estabas usando de una forma que te empujaba a tareas que no querías hacer hoy. El ajuste fue redefinir el uso de prioridades para separar “mantenimiento que quiero quitarme” del “trabajo duro”. Además, la idea de mover una estrategia grande a un proyecto (para que exista y se ejecute) es oro: si no está en el sistema, se queda en “backlog mental”. Metodología WordPress: tu “caja de herramientas” por defecto Aquí entró un tema muy de especialista: la profesionalización no es solo escribir mejor al cliente, es tener decisiones repetibles: ¿Qué plugin de caché usas según servidor? ¿Cómo haces staging? ¿Qué modo mantenimiento activas? ¿Qué stack aplicas siempre? Aparecen nombres concretos como InstaWP para entornos/staging (con planes y enfoque de gestión de sitios) y el plugin SWIS Performance (del ecosistema EWWW) como alternativa ligera para rendimiento/caché. Y también el apunte de que WP Rocket ha ido moviendo precios/planes en 2025 (lo que, sumado a todo lo demás, refuerza la necesidad de simplificar suscripciones). IA práctica (no humo): Gemini en Gmail, Meet y el coste real del tiempo Aquí hubo un momento muy “esto sí”: Gemini dentro de Gmail para generar borradores con contexto real del hilo (“Help me write”), que no es lo mismo que un redactor externo que se lía con quién dijo qué. Google lo plantea como funcionalidad integrada en Gmail/Workspace con generación de borradores, sugerencias, resúmenes, etc. Además, se mencionó el valor de “notas” en Meet y la idea de sustituir herramientas externas si la integración reduce fricción (y RAM). Punto clave: no es el precio mensual, es cuánto tiempo te devuelve. Manus y el navegador como “agente”: promesa interesante, resultados mixtos Se mencionó Manus como herramienta que, a nivel de “buscar alternativas” (tipo capturas bonitas estilo Pretty Snap), no aportó milagros respecto a ChatGPT. Pero también se comentó algo relevante: Manus lanzó Browser Operator, una extensión para convertir tu navegador Chromium en un entorno donde el agente actúa “dentro” de tus sesiones y logins. Eso, si funciona bien, es un salto práctico para automatizar tareas web reales. Kit Digital: cuando el proyecto se alarga tanto que ya ni sabes cuál es la web buena El episodio cierra con un tema que muchos han vivido: proyectos subvencionados con iteraciones eternas, cambios de interlocutor, silencios, webs duplicadas y la sensación de “otro ultimátum más”. Más allá del desahogo, aquí hay una lección de negocio: la gestión (comunicación, plazos, responsabilidad) es parte del valor, no un extra. Conclusión: Abilities API es el “punto de inflexión” (y lo demás son síntomas) WordPress 6.9 no es solo una versión con mejoras visuales. Con Abilities API, WordPress está preparando el terreno para que la IA deje de ser “un plugin simpático” y pase a ser operativa, conectable y segura, con permisos y contratos claros. Y alrededor de eso, todo encaja: automatizaciones en Make, control de precios en Stripe, herramientas que se integran o estorban, IA que ahorra tiempo de verdad (Gmail), y la necesidad de profesionalizar métodos para no vivir apagando fuegos. Si estás trabajando con WordPress y te interesa el futuro cercano, este es de esos cambios que merece la pena seguir de cerca… y debatir con gente que también está en la trinchera. Enlaces mencionados (internos y externos): Internos: Negocios y WordPress Telegram EliasGomez.pro Externos: Abilities API en WP 6.9 (Field Guide) Introducción Abilities API (Developer News) WooCommerce MCP docs Manus Browser Operator Gemini en Gmail: Help me write FAQ para rich snippets ¿Qué es la Abilities API de WordPress 6.9? Es una API que permite registrar “habilidades” (acciones) de WordPress, plugins y temas en un formato estándar: qué hacen, qué necesitan, qué devuelven y qué permisos requieren. Sirve para IA, automatización e integraciones fiables. ¿En qué se diferencia de la REST API tradicional? La REST API expone endpoints; la Abilities API añade una capa “descubrible” y estandarizada (autodocumentada) para que un agente o herramienta pueda saber qué existe y cómo llamarlo sin leer documentación externa. ¿Qué pinta tiene esto con MCP (Model Context Protocol)? MCP estandariza cómo un agente se conecta a herramientas. Abilities aporta el catálogo de acciones en WordPress para que el agente pueda elegir y ejecutar operaciones con permisos. ¿WooCommerce ya permite esto? WooCommerce ha publicado integración MCP en fase beta y documentación oficial para exponer herramientas de tienda a clientes IA con autenticación y permisos. ¿Qué ganan plugins como JetEngine con esto? Que pueden exponer acciones de su propio sistema (CPT, metaboxes, queries, etc.) para que un agente trabaje “a través del plugin” sin inventarse cómo funciona. Si quieres, lo adapto a tu web con enlaces internos reales por slugs (por ejemplo, a tu página de consultoría, tu categoría de “Medios”, o posts sobre Make/Stripe) y lo dejo listo para pegar en WordPress con bloques.

A internet está cheia de suplementos que prometem o milagre do emagrecimento rápido. Controle da fome, barriga chapada, aceleração do metabolismo e até “estimular o GLP-1” - seja lá o que isso signifique. Mas você sabe o que tem dentro desses potes?Links relacionados:Chromium supplementation in overweight and obesity: a systematic review and meta-analysis of randomized clinical trialsCadastre-se na lista de espera do Desafio Retomada 5Estamos no Instagram: ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠Dr. Souto⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠ - ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠Sari Fontana⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠ Para ser avisado sobre cada novo episódio e receber os links das matérias mencionadas e as referências bibliográficas por e-mail, cadastre-se gratuitamente em ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠https://drsouto.com.br/podcast⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠Adquira seu livro - UMA DIETA ALÉM DA MODA: ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠Amazon⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠ (também na versão Kindle)"Dance of the Sugar Plum Fairy"Kevin MacLeod (incompetech.com)Licensed under Creative Commons: By Attribution 3.0⁠⁠⁠⁠⁠⁠⁠⁠⁠http://creativecommons.org/licenses/by/3.0/

October brought a wave of AI-driven browser launches, shopping enhancements, and ad platform updates, and Jeremy and Emily are here to break down what matters most. In this episode of The Click Brief, they cover OpenAI's new ChatGPT Atlas browser, Google's visual and conversational shopping experience, Amazon's top-of-search reserve share of voice, TikTok's attribution improvements, and Meta's major Q5 lead gen upgrades. They also hit Perplexity's new free browser, Meta's EU ad-free subscription tests, and the official sunset timeline for Google call-only ads. This episode is your October cheat sheet for staying ahead in AI-assisted search and performance media.Top TakeawaysOpenAI ChatGPT Atlas Browser:A new Chromium-based browser with ChatGPT built directly into the interface. Agent Mode allows ChatGPT to take actions across pages like clicking links, filling out forms, and comparing products. Optional browser memories save past preferences and searches. Imports bookmarks, history, and passwords for fast setup. Windows version expected in 2026.Gemini in Chrome + Perplexity Comet Browser:Google adds Gemini tools directly inside Chrome for AI-assisted searching and task completion. Perplexity makes its Comet browser free, offering source-backed answers and agentic research features. All three AI browsers (Atlas, Gemini, Perplexity) are becoming interchangeable—worth testing to compare how each interprets queries and results.Google AI Mode Adds Visual + Conversational Shopping:Search using text and images, refine results with follow-up prompts, and browse product feeds powered by the Shopping Graph. Behaves like a customizable mood board for apparel, décor, and lifestyle shopping. Highlights the importance of accurate Merchant Center titles, attributes, and updated product imagery.Google Sunsetting Call-Only Ads:Advertisers can no longer create call-only ads after February 26. Existing call-only ads will fully stop serving in 2027. Encourages deeper reliance on call extensions, strong landing pages, and chat tools for conversion paths. Affects industries like legal and services that heavily used call-first funnels.Amazon Reserve Share of Voice for Sponsored Brands:Allows brands to lock in top-of-search Sponsored Brand placements for branded keywords at a fixed upfront cost. Pricing is shown instantly based on keywords and date range. A strong option for brands defending category leadership and preventing competitors from overtaking branded queries.Meta Q5 Lead Gen Upgrades:Adds email and phone verification tools to reduce accidental submissions and improve lead quality. Simplifies CAPI and CRM connections. Introduces better nurturing workflows directly within Meta lead ads. A meaningful upgrade for advertisers struggling with low-intent or auto-filled leads.Meta Ad-Free Subscription Tests (EU + UK):Meta begins testing paid, ad-free versions of Facebook and Instagram in Europe. No impact in the US yet, but important to monitor as platforms explore non-ad revenue models.Meta Business AI Tools:Sales Concierge: AI agent that answers product questions and guides purchases across Messenger, Instagram DMs, and WhatsApp.AI Business Assistant: Helps identify delivery issues, explains learning phases or disapprovals, suggests targeting/budget changes, and drafts creative inside Ads Manager.Amazon Branded Search Measurement:New insights include branded searches, branded searches from views/clicks, branded search rate, and cost per branded search. Provides better visibility into how top-of-funnel activity increases branded demand.TikTok Attribution Analytics:Adds a dedicated view to compare CPA and conversions across click and view attribution windows. Useful for aligning ad measurement with real buying cycles. TikTok also launches new travel-focused ad formats to meet growing travel planning behavior on-platform.Snapchat + WordPress Catalog Sync:New integration allows automatic syncing of product data between WordPress stores and Snapchat catalogs. Reduce setup time, but verify product data accuracy before publishing ads.Jeremy's Tip:AI-mode shopping is only as strong as your product data. Keep Merchant Center images, titles, and attributes updated so Google can match user intent more accurately.Emily's Tip:Turn on Meta's lead verification features. Cleaner leads reduce time wasted on low-intent submissions and strengthen Q5 performance.Follow The Click Brief for fast, no-fluff performance marketing updates.Visit The Click Brief blog for more in-depth analysis and updates from October. 

Ahoy, Gang!    Here is a free taste of one of our premiere shows on our Patreon called, "Does This Come In Chromium with host, Matt Anderson!      On this episode Matt and special guest co-host Matthew Dow Smith (writer/artist THE OCTOBER GIRL) turn out the lights to find out if the story contained within the pages of 1993's THE SPECTRE #13 shines brighter than its glow-in-the-dark cover.   How is it that a comic published in 1993, set in a fictional country, featuring (the always cool) Count Vertigo, and starring a character with god-like powers can feel so relevant and relatable to today?   Plus, Matt shares his opinion that the duo of John Ostrander and Tom Mandrake make for one of the greatest collaborations in all of comics (actually, this is not an opinion - it's an undeniable fact), while Matthew shares his true feelings on The Spectre (you'll have to listen to find out what they are).   Also, they discuss Matthew's time as artist on the DAY OF JUDGEMENT series (written by Geoff John) and what it was like helping create a brand new Spectre.   This is a jam packed episode - so don't miss it!   Contact the show: doesthiscomeinchromium@gmail.com

In this episode of the Poultry Nutrition Blackbelt Podcast, Dr. Jerry Spears, Animal Nutrition Consultant, shares his expertise on trace minerals, with a focus on chromium use in turkeys. He explains how chromium impacts insulin sensitivity, stress reduction, and immune function, while also discussing its effect on growth, feed efficiency, and economic return. Listen now on all major platforms!"Studies have indicated that at 16 or 17 weeks of age, turkeys supplemented with chromium showed an additional 1 pound of body weight compared to controls."Meet the guest: Dr. Jerry Spears, Professor Emeritus of Nutrition and Animal Science at North Carolina State University, has specialized in trace minerals for over three decades. His work has shaped advancements in poultry nutrition, especially in understanding chromium's role in metabolism, immunity, and production efficiency. Currently, he consults as an Animal Nutrition Consultant and continues contributing to applied research. Liked this one? Don't stop now — Here's what we think you'll love!Dr. Jerry Spears: Chromium in Poultry Diets | Ep. 53Dr. Michelle Kromm: Clostridial Dermatitis in Poultry | Ep. 83Dr. Karen Vignale: Turkey Dermatitis & Gut Health Solutions | Ep. 115What you'll learn:(00:00) Highlight(01:23) Introduction(02:13) Chromium in turkeys(04:40) Stress reduction(05:35) Meat yield potential(06:37) Economic return(09:20) Future research(10:55) Closing thoughtsThe Poultry Nutrition Blackbelt Podcast is trusted and supported by innovative companies like: Kemin* Fortiva- Poultry Science Association- BASF- Anitox- Kerry- Barentz

This episode features speakers from the 2025 ADSA Applied Nutrition Symposium, “Milk Pricing Dynamics and Strategies for Enhancing Milk Fat Production.” Dr. Lock gave the highlights of his presentation on dietary opportunities for promoting milk fat.  (2:18)Dr. St. Pierre's presentation focused on the change we've had in the way milk and its components are priced. (5:25)Dr. Van Amburgh's symposium talk covered amino acid supplementation to high producing cows eliciting more of a milk fat response than a milk protein response. (9:31)Dr. Van Amburgh and Dr. Lock talk about where butyrate fits into milk fat synthesis. Dr. Van Amburgh shares some of his experiences with grass-based dairy diets in Ireland and how those might influence milk fat production. The group discusses de novo and preformed fat synthesis and how diets may or may not influence those two mechanisms. (12:16)The guests talk about an abstract from Dr. Van Amburgh's lab at the ADSA meetings about supplemental lysine levels. This leads into a discussion of lactose production and fluid milk volume, as well as feedback from cheese processors and the impact of supplemental chromium on milk production parameters. (22:31)Dr. St. Pierre talks about cheese processor concerns with increased milk fat concentrations, milk pricing structures, and milk perishability. (28:27)The panel discusses metabolizable protein, essential, non-essential, and branched-chain amino acids, and how the view of fatty acids and amino acids has changed from simple substrates to make milk components to compounds with biogenic activities. (36:20)Dr. St. Pierre talks about the inaugural Industry Day at the 2025 ADSA meetings and goals for similar future events. (43:01)Panelists share their take-home thoughts. (48:13)Please subscribe and share with your industry friends to invite more people to join us at the Real Science Exchange virtual pub table.  If you want one of our Real Science Exchange t-shirts, screenshot your rating, review, or subscription, and email a picture to anh.marketing@balchem.com. Include your size and mailing address, and we'll mail you a shirt. 

Episode 302 of Absolute AppSec has hosts Ken Johnson and Seth Law speculating on the upcoming Global AppSec DC conference, predicting the announcement of the OWASP Top Ten 2025 edition, with Brian Glass scheduled to discuss it on the podcast. The conversation shifts to a technical discussion of OpenAI's new browser, Atlas, which is built on Chromium and includes AI capabilities. The hosts noted concern over the discovered prompt instructions for Atlas, which direct the ChatGPT agent to use browser history and available APIs to find data from the user's logged-in sites to answer ambiguous queries or fulfill requests. This functionality raises significant security concerns, as the agent's ability to comb the cache and logged-in sites could be exploited, effectively creating a "honeypot for cross-site scripting" with malicious potential like unauthorized money transfers. The hosts discussed the lack of talk submissions on Mobile Context Protocol (MCP) security at the conference, despite its growing relevance in a world of AI agents and tooling. Finally, they highlighted a new tool called SlopGuard, developed to prevent the risk of AI hallucinating non-existent, potentially malicious packages (which occurs 5-21% of the time) and attempting to install them from registries like NPM.

Google Chrome domine le web avec 72% du marché. Mais cette ère s'achève peut-être. La nouvelle guerre des navigateurs est déclarée, et l'arme, c'est l'IA.Comet de Perplexity et Atlas d'OpenAI ne veulent plus seulement concurrencer Google sur la recherche, ils attaquent son bastion : le navigateur.Dans cet épisode 170 du CKC Show, Olivier (qui a testé Comet de Perplexity) analyse cette révolution. Nous passons d'une navigation passive à une assistance active grâce aux "Agents IA".Au programme de cet épisode :Comet : Que valent ces nouveaux navigateurs IA ?Agents IA : Comment l'IA peut désormais agir à votre place (gérer vos emails, créer des playlists, comparer des produits).Migration facile : Faut-il quitter Chrome ? (Spoiler : ils sont basés sur Chromium).Risques : Quels sont les dangers pour votre vie privée et la sécurité de vos données quand une IA voit tout ce que vous faites ?La bataille pour le futur du web commence maintenant.Soutenez le CKB Show Cet épisode vous est proposé par le CKC Show, un média 100% indépendant. Si vous appréciez nos analyses sans filtre et sans publicité, vous pouvez soutenir notre travail sur Patreon :https://www.patreon.com/mychromebookNos coups de coeur:https://chromewebstore.google.com/detail/adobe-photoshop/kjchkpkjpiloipaonppkmepcbhcncedo?hl=frhttps://chromewebstore.google.com/detail/gemini-for-chrome/aajjgdpofhhcjmjoombjdfepplndhgcphttps://aistudio.google.com/apps/bundled/paint_a_place?showPreview=true&showAssistant=truehttps://labs.google.com/pomelli/about/Où nous retrouver ?Nicolas Drolo: https://www.linkedin.com/in/nicolas-drolo-54970155/Olivier Verbreugh: https://www.linkedin.com/in/olivier-verbreugh/

Po rekordowym odcinku (prawie 80 000 wyświetleń!) wracamy z kolejną porcją najważniejszych newsów ze świata sztucznej inteligencji

From a tiny island in Seychelles to the heartland of Ohio, we unpack a wild week in AI. First up: 1X's “Neo” humanoid—$20k to buy or $500/month to rent—promising laundry, dishes, and errands soon…with a lot of teleoperation today. We debate whether tele-ops is a feature (not a bug), who it employs, and how quickly autonomy could follow. Then we zoom out to the money: Nvidia touches a $5T valuation, OpenAI reportedly eyes a $1T IPO, and the industry's circular funding loops raise both eyebrows and opportunity. We also test-drive OpenAI's Atlas browser (a Chromium fork with action-taking ambitions), and dig into Cursor's agentic coding push, new in-house model, and blistering growth—plus the eternal “moat vs. momentum” question. Along the way: a live Neo preorder, enterprise ROI reality checks, and why agents may turn devs into project managers. If you're curious where robotics, chips, and agentic software collide, this one's for you. Ask a question on our Youtube Channel: https://www.youtube.com/@GenerativeAIMeetup Mark's Travel Vlog: https://www.youtube.com/@kumajourney11 Mark's Personal Youtube Channel: https://www.youtube.com/@markkuczmarski896 Attend a live event: https://genaimeetup.com/ Shashank Linked In: https://www.linkedin.com/in/shashu10/ 

In this Facebook Live episode, Shana shares how she naturally lowered her total cholesterol by 58 points and LDL by 41 points in just 11 weeks—without statins—by addressing insulin resistance and easily adding 7 different fibers with the Feel Great System. You'll learn what causes "high" cholesterol beyond diet, how insulin and inflammation play a bigger role than fat intake, and how strategic nutrients like soluble fibers, phytosterols, and chlorogenic acid improve both lipid and glucose metabolism. What You'll Learn The real root of high cholesterol: insulin resistance and poor metabolic signaling. Why statins don't fix insulin resistance—and what they actually do. How Balance (soluble fiber matrix) supports healthy LDL, satiety, and blood sugar control. Guar gum, beta-glucans, gum arabic, citrus pectin → lower LDL, stabilize glucose, support gut microbiota. Phytosterols → reduce LDL and raise HDL. Chromium → enhances insulin sensitivity, reduces sugar cravings. Niacin → supports HDL and energy metabolism How Unimate (yerba mate extract) enhances GLP-1, focus, and fat metabolism. Chlorogenic acid → reduces LDL/triglycerides, improves insulin sensitivity, and supports mitochondrial energy. Theobromine → improves HDL/LDL ratio, boosts mood and alertness without jitters. Mate saponins and polyphenols → lower visceral fat, protect the liver, and calm inflammation How improving GLP-1 naturally helps you feel full longer, lose weight, and stabilize blood sugar. Simple lifestyle rhythms—light, sleep, meal timing—that magnify your results. Key Takeaways Fixing insulin resistance improves both cholesterol and blood sugar markers. The Feel Great System is listed in the Physician's Desk Reference (PDR) and backed by published studies. You can partner with your clinician to explore reducing or avoiding cholesterol meds as metabolic health improves. Supporting GLP-1 naturally with Feel Great can mimic some benefits of popular medications—without side effects. Products Mentioned

In this episode, we explore OpenAI's latest innovation, the Atlas browser, which integrates ChatGPT capabilities directly into a Chromium-based platform. We discuss its potential impact on the browsing experience and how it challenges existing giants like Google Chrome.Get the top 40+ AI Models for $20 at AI Box: https://aibox.aiConor's AI Course: https://www.ai-mindset.org/coursesConor's AI Newsletter: https://www.ai-mindset.ai/Jaeden's AI Hustle Community: https://www.skool.com/aihustle

OpenAI has launched its new browser Atlas built to compete with Comet, Chrome, Edge, and other Chromium based browsers. As with other AI based browsers, Atlas comes with a slew of amazing self-directing features along with the potential for a long term mess of major security flaws, exploitable bugs, and the threat of malicious prompting. These are the earliest generations of AI based browsers so both problems and rapid improvements are inevitable. While AI is being added to virtually everything, two federal judges warn it should not be used in law noting how judges and clerks using AI in their writing have led to serious errors in US court rulings. Meanwhile Microsoft has added Harvard Health sourcing to Copilot. Reddit is suing Perplexity and SerpAPI over their scraping of Reddit data from Google's search index, which contributed to Google's decision to severely limit the size of results sets available to APIs. We get more information about impression loss at GSC. Google notes that links, technical SEO, and migrations can't fix craptastic quality issues. We're assuming they're talking about content but not being as clear as possible. Research shows LLMs are used for research and information and websites are used for buying as conversions from LLM traffic tends to be lower than those sent by Google search. All this and more on a truly browserific edition of Webcology.Support this podcast at — https://redcircle.com/webcology/donationsAdvertising Inquiries: https://redcircle.com/brandsPrivacy & Opt-Out: https://redcircle.com/privacy

ChatGPT just released their agnetic browser, Atlas.

Is the web breaking under the weight of AI crawlers, platform consolidation, and nonstop security breaches? We dive into the state of browsers, developer burnout, and whether tech regulation can actually keep up. In this panel discussion: We debate if robots.txt and AI licensing standards like RSL can realistically control how AI scrapes the web. The fallout from DIA's acquisition by Atlassian and what it means for indie browser innovation (like the Helium browser, Zen) in a Chromium-dominated world. Why Google's antitrust victory might embolden other tech giants, and what that means for competition. How supply chain attacks like the NPM malware and Shai Hulud worm are exploiting GitHub workflows and package vulnerabilities. The pushback against AI mandates at work, including Coinbase's controversial policy requiring developers to use Copilot. Resources Inside the battle for the future of the web: https://www.businessinsider.com/google-microsoft-openai-fight-standards-limit-ai-access-websites-2025-9 The web has a new system for making AI companies pay up: https://www.theverge.com/news/775072/rsl-standard-licensing-ai-publishing-reddit-yahoo-medium The Browser Company, maker of Arc and Dia, is being acquired: https://www.theverge.com/web/770947/browser-company-arc-dia-acquired-atlassian Google stock jumps 8% after search giant avoids worst-case penalties in antitrust case: https://www.cnbc.com/2025/09/02/google-antitrust-search-ruling.html Massive data breach sees 16 million PayPal accounts leaked online - here's what we know, and how to stay safe:https://www.techradar.com/pro/massive-data-breach-sees-16-million-paypal-accounts-leaked-online-heres-what-we-know-and-how-to-stay-safe PayPal's Glitch Puts €10 Billion on Ice Across European Banks: https://fintechnews.ch/payments/paypal-glitch-freezes-european-banks-10-billion-transactions/77974/ npm Author Qix Compromised via Phishing Email in Major Supply Chain Attack: https://socket.dev/blog/npm-author-qix-compromised-in-major-supply-chain-attack Compromised files replace npm packages with a combined 2 billion weekly downloads: https://www.techradar.com/pro/security/compromised-files-replace-npm-packages-with-a-combined-2-billion-weekly-downloads Shai-Hulud: Ongoing Package Supply Chain Worm Delivering Data-Stealing Malware: https://www.wiz.io/blog/shai-hulud-npm-supply-chain-attack Coinbase CEO explains why he fired engineers who didn't try AI immediately: https://techcrunch.com/2025/08/22/coinbase-ceo-explains-why-he-fired-engineers-who-didnt-try-ai-immediately/ Chapters We want to hear from you! How did you find us? Did you see us on Twitter? In a newsletter? Or maybe we were recommended by a friend? Fill out our listener survey (https://t.co/oKVAEXipxu)! Let us know by sending an email to our producer, Em, at emily.kochanek@logrocket.com (mailto:emily.kochanek@logrocket.com), or tweet at us at PodRocketPod (https://twitter.com/PodRocketpod). Follow us. Get free stickers. Follow us on Apple Podcasts, fill out this form (https://podrocket.logrocket.com/get-podrocket-stickers), and we'll send you free PodRocket stickers! What does LogRocket do? LogRocket provides AI-first session replay and analytics that surfaces the UX and technical issues impacting user experiences. Start understanding where your users are struggling by trying it for free at LogRocket.com. Try LogRocket for free today. (https://logrocket.com/signup/?pdr)

GNOME 49 lands with Do Not Disturb, per-monitor brightness, and better scaling. Cloudflare backed Ladybird, the non-Chromium browser. Raspberry Pi has a new $15 M.2 Hat Compact that fits in the Pi 5 case, and LattePanda shows up with a Pi-sized Intel N150 single board computer.

Make way for the next wave of GenAI..... Agentic AI Browsers. And while we've seen rumors that OpenAI is going all-in on an AI browser, the first big player is already here in Perplexity's Comet Browser. Join us as we break down how Perplexity Comet works, what makes it different, and 5 Business Use-Cases for ROI. Newsletter: Sign up for our free daily newsletterMore on this Episode: Episode PageJoin the discussion on LinkedIn :Thoughts on this? Join the convo on today's LinkedIn stream and connect with other AI leaders.Upcoming Episodes: Check out the upcoming Everyday AI Livestream lineupWebsite: YourEverydayAI.comEmail The Show: info@youreverydayai.comConnect with Jordan on LinkedInTopics Covered in This Episode:Rise of Agentic AI Browsers ExplainedPerplexity Comet's Hybrid AI ArchitectureLocal vs. Virtual Browser Agentic WorkflowsPerplexity Comet Key Features and AccessConnecting Google Services with Comet BrowserAgentic AI Browser Live Demo Use CasesMulti-Platform Personalized Business ResearchAutomated Market Research and Competitive AnalysisPerplexity Comet Cross-Tool Workflow AutomationAgentic AI Browsers vs. Traditional AI ChatbotsTimestamps:00:00 Everyday AI for Business Pros04:56 Agentic AI Browsers Revolutionizing Tech07:49 Advancements in AI Computer Agents09:55 Comet: Chromium-Based Browser Essentials14:43 Streamlining Tasks with Perplexity Integration19:01 AI-Powered Google Drive Personalization21:24 Square: Trusted Business Payment Solutions25:53 Preparing Keynote on Agentic AI29:59 Agentic AI: Revolutionizing Web Browsers31:56 "Agentic AI to Revolutionize Workflows"34:46 Streamlined Scheduling and Market AnalysisKeywords:Perplexity Comet, agentic AI browser, agentic AI, AI browser, business use cases, ROI, Perplexity app, hybrid AI, cloud AI, on-device AI, Comet browser, Chromium, browser automation, multi-platform research, deep research modes, AI desktop assistant, iOS assistant, Google Chrome, browser workflows, Chrome extensions, Microsoft Edge, computer using agents, virtual browser, computer vision, connector integration, Gmail integration, Google Drive integration, calendar management, task automation, prompt engineering, personalized research, market research, competitive analysis, social media automation, email management, calendar automation,Send Everyday AI and Jordan a text message. (We can't reply back unless you leave contact info)Ready for ROI on GenAI? Go to youreverydayai.com/partner Send Everyday AI and Jordan a text message. (We can't reply back unless you leave contact info) Ready for ROI on GenAI? Go to youreverydayai.com/partner

pWotD Episode 3060: Google Chrome Welcome to popular Wiki of the Day, spotlighting Wikipedia's most visited pages, giving you a peek into what the world is curious about today.With 394,834 views on Wednesday, 17 September 2025 our article of the day is Google Chrome.Google Chrome is a web browser developed by Google. It was first released in 2008 for Microsoft Windows, built with free software components from Apple WebKit and Mozilla Firefox. Versions were later released for Linux, macOS, iOS, iPadOS, and also for Android, where it is the default browser. The browser is also the main component of ChromeOS, where it serves as the platform for web applications.Most of Chrome's source code comes from Google's free and open-source software project Chromium, but Chrome is licensed as proprietary freeware. WebKit was the original rendering engine, but Google eventually forked it to create the Blink engine; all Chrome variants except iOS used Blink as of 2017.As of April 2024, StatCounter estimates that Chrome has a 65% worldwide browser market share (after peaking at 72.38% in November 2018) on personal computers (PC), is most used on tablets (having surpassed Safari), and is also dominant on smartphones. With a market share of 65% across all platforms combined, Chrome is the most used web browser in the world today.Google chief executive Eric Schmidt was previously involved in the "browser wars", a part of U. S. corporate history, and opposed the expansion of the company into such a new area. However, Google co-founders Sergey Brin and Larry Page spearheaded a software demonstration that pushed Schmidt into making Chrome a core business priority, which resulted in commercial success. Because of the proliferation of Chrome, Google has expanded the "Chrome" brand name to other products. These include not just ChromeOS but also Chromecast, Chromebook, Chromebit, Chromebox, and Chromebase.This recording reflects the Wikipedia text as of 07:31 UTC on Thursday, 18 September 2025.For the full current version of the article, see Google Chrome on Wikipedia.This podcast uses content from Wikipedia under the Creative Commons Attribution-ShareAlike License.Visit our archives at wikioftheday.com and subscribe to stay updated on new episodes.Follow us on Mastodon at @wikioftheday@masto.ai.Also check out Curmudgeon's Corner, a current events podcast.Until next time, I'm neural Matthew.

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 week's short and snappy episode, Copilot Studio gets an increase in the number of files an agent can use in SharePoint and OneDrive. Office Transcriptions can be left to run all day and still not use up your quota of minutes. Lastly, admins should check that they have enabled a setting in Chromium browsers to continue to provide offline capabilities in OneDrive. 0:00 Welcome 5:35 Microsoft Copilot Studio - Use up to 1,000 files per agent for SharePoint and OneDrive uploads - MC1150623 11:36 Teams Admin Center: Control External Access by Domain for Specific Users and Groups - MC1150123 14:45 Office Transcription Quota Increase for Copilot-Licensed Users - MC1150669 19:17 Action Required – Configure Browser Policy to Preserve OneDrive and SharePoint Web Performance and Offline Capability - MC1150662

Matt & Oren discuss the feeling dogging every freelancer: "Will I ever work again?" They dig into who they recommend when they can't take an awesome job, and how that has paid it forward in good ways. Maybe it's all about who you vibe with. But what is that, exactly? And what if a brand or agency does a vibe check on you? Surprisingly, it's like a date, and more of sales pitch so be prepared!But there's a way to show up with a certain enthusiasm for a project and demonstrate a personal connection without sounding like a cold email that falls on its face. This episode is definitely worth a listen if you're trying to rack up more jobs this year!Matt's Endorsement: Deschute's Fresh Squeezed Non-Alcohoilc IPA https://deschutesbrewery.com/products/fresh-squeezed-non-alcoholicOren's Endorsement: Tab Groups in Google Chrome. R-Click on a tab > Add Tab to New Group. Also on Chromium-based browsers like Firefox and Brave. https://support.google.com/chrome/answer/2391819?hl=en&sjid=9324260012388965296-NC#zippy=%2Cgroup-your-tabs Hosted on Acast. See acast.com/privacy for more information.

On this week's show Patrick Gray and Adam Boileau discuss the week's cybersecurity news, including: CISA warns about the path from on-prem Exchange to the cloud Microsoft awards a crisp zero dollar bill for a report about what a mess its internal Entra-authed apps are Everyone and their dog seems to have a shell in US Federal Court information systems Google pays $250k for a Chrome sandbox escape Attackers use javascript in adult SVG files to … farm facebook likes?! SonicWall says users aren't getting hacked with an 0day… this time. This week's episode is sponsored by SpecterOps. Chief product officer Justin Kohler talks about how the flagship Bloodhound tool has evolved to map attack paths anywhere. Bring your own applications, directories and systems into the graph, and join the identity attacks together. This episode is also available on Youtube. Show notes CISA, Microsoft issue alerts on ‘high-severity' Exchange vulnerability | The Record from Recorded Future News Advanced Active Directory to Entra ID lateral movement techniques Consent & Compromise: Abusing Entra OAuth for Fun and Access to Internal Microsoft Applications Cartels may be able to target witnesses after major court hack Federal judiciary tightens digital security as it deals with ‘escalated cyberattacks' | The Record from Recorded Future News Citrix NetScaler flaws lead to critical infrastructure breaches | Cybersecurity Dive DARPA touts value of AI-powered vulnerability detection as it announces competition winners | Cybersecurity Dive Buttercup is now open-source! HTTP/1.1 must die: the desync endgame US confirms takedown of BlackSuit ransomware gang that racked up $370 million in ransoms | The Record from Recorded Future News North Korean cyber-espionage group ScarCruft adds ransomware in recent attack | The Record from Recorded Future News Adult sites are stashing exploit code inside racy .svg files - Ars Technica Google pays 250k for Chromium sandbox escape SonicWall says recent attack wave involved previously disclosed flaw, not zero-day | Cybersecurity Dive Two groups exploit WinRAR flaws in separate cyber-espionage campaigns | The Record from Recorded Future News Tornado Cash cofounder dodges money laundering conviction, found guilty of lesser charge | The Record from Recorded Future News Hackers Hijacked Google's Gemini AI With a Poisoned Calendar Invite to Take Over a Smart Home | WIRED Malware in Open VSX: These Vibes Are Off How attackers are using Active Directory Federation Services to phish with legit office.com links Introducing our guide to phishing detection evasion techniques The State of Attack Path Management

Electron is a framework for building cross-platform desktop applications using web technologies like JavaScript, HTML, and CSS. It allows developers to package web apps with a native-like experience by bundling them with a Chromium browser and Node.js runtime. Electron is widely used for apps like VS Code, Discord, and Slack because it enables a single The post Electron and Desktop App Engineering with Shelley Vohr appeared first on Software Engineering Daily.

Electron is a framework for building cross-platform desktop applications using web technologies like JavaScript, HTML, and CSS. It allows developers to package web apps with a native-like experience by bundling them with a Chromium browser and Node.js runtime. Electron is widely used for apps like VS Code, Discord, and Slack because it enables a single The post Electron and Desktop App Engineering with Shelley Vohr appeared first on Software Engineering Daily.

Contributor: Megan Hurley MD Educational Pearls: Acute toxicity of heavy metals: Gastrointestinal upset is the most common presentation Chronic toxicity of heavy metals: Symptoms depend on the metal ingested Increased risk of cancer Altered mentation Developmental delays (in children) Kidney failure Four heavy metals that are tested for in a general panel and their sources: Lead Old paint (homes built before 1977) or some older toys Pipes of older homes or those with corrosive agents May obtain testing kits from home improvement stores to test water supply Mercury Previously in thermometers, although much less common now Compact fluorescent lightbulbs, LCD screens, and some batteries Large predatory fish like tuna, swordfish, dolphins, and shark Arsenic sources Most commonly found in pesticides Contaminated groundwater (especially private wells) Cadmiun sources Most commonly found in tobacco smoke Batteries Metal plating and welding Additional heavy metals that require specific testing Chromium, Nickel, & Thallium Thallium is found in rodenticides, pesticides, and fireworks Management of heavy metal toxicity depends on the intoxicant Generally, chelation therapy is used for acute and severe cases Arsenic: dimercaprol or DMSA Mercury: DMPS (chronic or mild) or DMSA (severe) Lead: succimer is first line, followed by dimercaprol or EDTA References Baker BA, Cassano VA, Murray C; ACOEM Task Force on Arsenic Exposure. Arsenic Exposure, Assessment, Toxicity, Diagnosis, and Management: Guidance for Occupational and Environmental Physicians. J Occup Environ Med. 2018;60(12):e634-e639. doi:10.1097/JOM.0000000000001485 Balali-Mood M, Naseri K, Tahergorabi Z, Khazdair MR, Sadeghi M. Toxic Mechanisms of Five Heavy Metals: Mercury, Lead, Chromium, Cadmium, and Arsenic. Front Pharmacol. 2021;12:643972. Published 2021 Apr 13. doi:10.3389/fphar.2021.643972 Kinally C, Fuller R, Larsen B, Hu H, Lanphear B. A review of lead exposure source attributional studies. Sci Total Environ. 2025;990:179838. doi:10.1016/j.scitotenv.2025.179838 Jannetto PJ, Cowl CT. Elementary Overview of Heavy Metals. Clin Chem. 2023;69(4):336-349. doi:10.1093/clinchem/hvad022 Järup L. Hazards of heavy metal contamination. Br Med Bull. 2003;68:167-182. doi:10.1093/bmb/ldg032 Zhang H, Reynolds M. Cadmium exposure in living organisms: A short review. Sci Total Environ. 2019;678:761-767. doi:10.1016/j.scitotenv.2019.04.395 Summarized & Edited by Jorge Chalit, OMS4 Donate: https://emergencymedicalminute.org/donate/

Securing Firebase: Lessons Re-Learned from the Tea Breach Inspried by the breach of the Tea app, Brendon Evans recorded a video to inform of Firebase security issues https://isc.sans.edu/diary/Securing%20Firebase%3A%20Lessons%20Re-Learned%20from%20the%20Tea%20Breach/32158 WebKit Vulnerability Exploited before Apple Patch A WebKit vulnerablity patched by Apple yesterday has already been exploited in Google Chrome. Google noted the exploit with its patch for the same vulnerability in Chrome. https://nvd.nist.gov/vuln/detail/CVE-2025-6558 Scattered Spider Update CISA released an update for its report on Scattered Spider, noting that the group also calls helpdesks impersonating users, not just the other way around. https://www.cisa.gov/news-events/cybersecurity-advisories/aa23-320a

Microsoft Edge is the default web browser and PDF reader in Windows 11, and a modern and capable successor to the Internet Explorer browser of yesteryear. It's built on the same Chromium web platform that Google uses for Chrome, and it integrates more deeply with Windows and Microsoft online services–most notably Copilot–than other browsers. But Microsoft Edge is also a vector for some of the worst behaviors in Windows 11. For this reason, it's important to configure Microsoft Edge correctly, whether you expect to use it regularly or not. Host: Paul Thurrott Download or subscribe to Hands-On Windows at https://twit.tv/shows/hands-on-windows Want access to the ad-free video and exclusive features? Become a member of Club TWiT today! https://twit.tv/clubtwit Club TWiT members can discuss this episode and leave feedback in the Club TWiT Discord.

LLMs are so yesteryear. The next wave? Agentic browsers. While we're all rushing to bring personalization, company files and more into front-end large language models, agentic browsers have been quietly staking their claim as the next big thing in AI. We explain why.Try Gemini 2.5 Flash! Sign up at  AIStudio.google.com to get started. Newsletter: Sign up for our free daily newsletterMore on this Episode: Episode PageJoin the discussion: Thoughts on this? Join the convo and connect with other AI leaders on LinkedIn.Upcoming Episodes: Check out the upcoming Everyday AI Livestream lineupWebsite: YourEverydayAI.comEmail The Show: info@youreverydayai.comConnect with Jordan on LinkedInTopics Covered in This Episode:Agentic AI Browsers vs. Chatbots OverviewFive Advantages of Agentic AI BrowsersPerplexity Comet Agentic Browser Case StudyOpenAI ChatGPT Agent and Virtual BrowserMicrosoft Edge Copilot Vision Agentic FeaturesGoogle Project Mariner and Gemini UpdatesStartup Agentic Browsers: Fellow, Opera Neon, DIALogged-In State and Workflow AutomationFuture Trends: Agentic Browser Momentum AnalysisTimestamps:05:10 Unlearning for AI-driven Work09:54 Agentic Browsers: Enhanced Context Utilization10:54 "AI Communication Simplified with MCP"15:28 "Hybrid AI's On-Device Speed"18:10 AI Browser Evolution22:40 Google Project Mariner Overview27:30 Streamlining Analytics with Agentic Browsers30:31 Agentic AI in Browsers32:08 Agentic AI's Rapid EvolutionKeywords:Agentic AI, agentic browsers, agentic AI browser, AI in the browser, agentic workflows, large language models, LLMs, front end chatbots, AI chatbot, Perplexity Comet, virtual browser, browser automation, AI-powered browsers, Google Gemini, ChatGPT agent, OpenAI virtual computer, model context protocol, MCP, agentic workflows, A2A protocol, hybrid AI architecture, Chromium-based browser, Microsoft Edge, Copilot Vision, Project Mariner, teach a task mode, Gemini assistant, logged in content, richer context, task automation, cross-site task automation, multi-step task automation, browser memory, shadow windows, Eco framework, natural language agentic workflows, JavaScript agentic workflows, Neon Opera browser, contextual AI, offline AI tasks, cloud browser, Manus AI, multi-agent architecture, browser cookies, contextual assistance, prompt engineering, personalized AI browser experience, task completion AI, web automation, business workflow automation, 2025 agentic browser predictions, virtual desktops.Send Everyday AI and Jordan a text message. (We can't reply back unless you leave contact info)

Make way for the next wave of GenAI..... Agentic AI Browsers. And while we've seen rumors that OpenAI is going all-in on an AI browser, the first big player is already here in Perplexity's Comet Browser. Join us as we break down how Perplexity Comet works, what makes it different, and 5 Business Use-Cases for ROI. Square keeps up so you don't have to slow down. Get everything you need to run and grow your business—without any long-term commitments. And why wait? Right now, you can get up to $200 off Square hardware at square.com/go/jordan. Run your business smarter with Square. Get started today.Newsletter: Sign up for our free daily newsletterMore on this Episode: Episode PageJoin the discussion:Thoughts on this? Join the convo and connect with other AI leaders on LinkedIn.Upcoming Episodes: Check out the upcoming Everyday AI Livestream lineupWebsite: YourEverydayAI.comEmail The Show: info@youreverydayai.comConnect with Jordan on LinkedInTopics Covered in This Episode:Rise of Agentic AI Browsers ExplainedPerplexity Comet's Hybrid AI ArchitectureLocal vs. Virtual Browser Agentic WorkflowsPerplexity Comet Key Features and AccessConnecting Google Services with Comet BrowserAgentic AI Browser Live Demo Use CasesMulti-Platform Personalized Business ResearchAutomated Market Research and Competitive AnalysisPerplexity Comet Cross-Tool Workflow AutomationAgentic AI Browsers vs. Traditional AI ChatbotsTimestamps:00:00 Everyday AI for Business Pros04:56 Agentic AI Browsers Revolutionizing Tech07:49 Advancements in AI Computer Agents09:55 Comet: Chromium-Based Browser Essentials14:43 Streamlining Tasks with Perplexity Integration19:01 AI-Powered Google Drive Personalization21:24 Square: Trusted Business Payment Solutions25:53 Preparing Keynote on Agentic AI29:59 Agentic AI: Revolutionizing Web Browsers31:56 "Agentic AI to Revolutionize Workflows"34:46 Streamlined Scheduling and Market AnalysisKeywords:Perplexity Comet, agentic AI browser, agentic AI, AI browser, business use cases, ROI, Perplexity app, hybrid AI, cloud AI, on-device AI, Comet browser, Chromium, browser automation, multi-platform research, deep research modes, AI desktop assistant, iOS assistant, Google Chrome, browser workflows, Chrome extensionSend Everyday AI and Jordan a text message. (We can't reply back unless you leave contact info) Square keeps up so you don't have to slow down. Get everything you need to run and grow your business—without any long-term commitments. And why wait? Right now, you can get up to $200 off Square hardware at square.com/go/jordan. Run your business smarter with Square. Get started today.

Just about every big tech company made splashes in AI this week.↳ Google acqui-hired a company that OpenAI failed to straight up acquire↳Microsoft is investing $4 billion into AI training↳ OpenAI is going after the AI browser space↳ and Meta reportedly spent more than $200 million on one employeeSheeeeesh. It's been a whirlwind. Don't get left behind. We'll help you be the smartest person in AI at your company.Newsletter: Sign up for our free daily newsletterMore on this Episode: Episode PageJoin the discussion:Thoughts on this? Join the convo and connect with other AI leaders on LinkedIn.Upcoming Episodes: Check out the upcoming Everyday AI Livestream lineupWebsite: YourEverydayAI.comEmail The Show: info@youreverydayai.comConnect with Jordan on LinkedInTopics Covered in This Episode:OpenAI's AI Browsers vs. Google ChromePerplexity's Comet Browser Launch StrategyXAI's Controversial Grok4 Alignment IssuesTeacher Union's AI Training PartnershipMicrosoft Elevate AI Training InitiativeNVIDIA's $4 Trillion Market Cap MilestoneGoogle Acqui-hires Windsurf for DeepMindMeta's $200M Apple AI Talent AcquisitionTimestamps:00:00 "Everyday AI: Weekly News Recap"05:36 Perplexity's Comet: Agentic Browser Shift06:49 AI-Powered Browsing with Perplexity's Comet10:44 "Grok 4: Aligns with Musk's Views"15:37 AI Workshops for Teachers Nationwide18:32 Microsoft's Elevate Program: AI Access & Trust19:51 AI Strategy and Training Partners23:13 Google Hires Wind Surf Executives29:04 AI Updates: Claude's MCP and Google Gemini31:36 AI Developments: Browsers, Training, Market MovesKeywords:Google acquihire, Windsurf, OpenAI browser, Perplexity, agentic browsers, Meta superintelligence, AI news, Google Chrome dominance, ChatGPT users, Chromium, computer vision, AI agents, reservation booking, AI services, market dominance, browser wars, anthropic, Claude, Perplexity's Comet, AI powered web, conversational interface, AI assistant, natural language, OpenAI's GPT, anthropic claw, Grok four, XAI, Elon Musk AI, AI benchmarks, content moderation, Grok controversy, AI alignment, TechCrunch, contentious questions, AI partnerships, educational AI, American Federation of Teachers, Microsoft Copilot, Microsoft funding, ethical AI, Elevate Academy, NVIDIA market cap, AI chips, Google DeepMind, AI coding, Apple AI executive, AI metrics, Anthropic, Microsoft layoffs.Send Everyday AI and Jordan a text message. (We can't reply back unless you leave contact info) Square keeps up so you don't have to slow down. Get everything you need to run and grow your business—without any long-term commitments. And why wait? Right now, you can get up to $200 off Square hardware at square.com/go/jordan. Run your business smarter with Square. Get started today.

This episode of the PCOS Repair Podcast,  explores two popular supplements, berberine and chromium, and how they compare when it comes to managing insulin resistance and supporting hormone balance in PCOS. While both supplements have gained attention on social media and within the wellness space, this episode takes a research-based look at their effects, how they work, and when they might be appropriate for someone with PCOS.How Berberine Supports Blood Sugar and Hormone HealthIn this episode, you'll learn why berberine's multifaceted benefits make it especially helpful for those dealing with metabolic dysfunction, irregular cycles, and hormonal imbalances. You'll also discover how berberine's effects compare to pharmaceutical options like metformin and why its dosing schedule matters for effectiveness.What Chromium Can Do for Insulin Function in PCOSChromium is a trace mineral with a more targeted role in insulin regulation and carbohydrate metabolism. While it may not directly impact inflammation or cholesterol, chromium is a powerful tool for improving blood sugar control, especially for those with fewer complicating factors. In this episode, you'll hear how chromium supports insulin function at the cellular level and when it might be the right fit, especially for women focusing primarily on glucose balance without broader metabolic concerns.Choosing the Right Supplement for Your PCOS NeedsThis episode provides guidance on how to decide between these two insulin-supportive supplements.  You'll hear why it's important to consider your personal root causes, health history, and what other medications or supplements you're using before adding either berberine or chromium to your routine. This thoughtful comparison gives you the tools to evaluate which supplement might align best with your current PCOS management plan.You can take the quiz to discover your root cause hereEffect and mechanism of berberine against polycystic ovary syndromeChromium supplementation and polycystic ovary syndrome: A systematic review and meta-analysisLet's continue the conversation on Instagram! What did you find helpful in this episode and what follow-up questions do you have?The full list of Resources & References Mentioned can be found on the Episode webpage at:https://nourishedtohealthy.com/ep-152

Diabetes is the fastest-growing disease in America.  This week, Dr. Prather gives a preview of his upcoming free seminar, "Diabetes Decoded:  A Holistic Look At Type 1 and Type 2 Diabetes", happening this Wednesday, June 25th at 6:30 p.m.  in this episode, we talk about:—Why Diabetes is a growing problem. And why this issue is unique to America. —The (really gross!) story behind the name Diabetes and how the Ancient Greek doctors used to diagnose it.—How Dr. Prather finds "there are more people who come into our office who are pre-Diabetic than aren't." —The role of viruses like Coxsackie B in kicking off Type I Diabetes.—The 3 P's of Diabetes symptoms to be aware of.  Plus, how weight LOSS is a "red flag" symptom of Diabetes...which is often caused by weight gain. —How the nerves, the kidneys, and the eyes are damaged by Diabetes.  And the increased risk of Cardiovascular Disease and Cancer that come from Diabetes.—How Type II Diabetes "HAS to be" dealt with through Structure-Function Health Care, while Disease Care is "totally worthless" in getting Type II Diabetes under control.—Why herbals are "amazing" for dealing with Diabetes.  And the role Homeopathy plays in dealing with Diabetes, especially for children. —The WORST food for Diabetes that increases blood sugar more than any other food.  And how fiber is "probably one of the best medicines" for Diabetes.—How Vitamin utilization is decreased by Diabetes, while the need for Vitamins is increased by Diabetes in order to prevent damage to the body.  And why Chromium is described by Dr. Prather as a "magic" mineral for Diabetes.http://www.TheVoiceOfHealthRadio.com

HEALTH NEWS   ·         A combination of exercise and omega-3 reduces the severity of tooth root infections ·         Healthy lifestyle habits may shield aging cells from brain disorders ·         French maritime pine bark improves cellulite in women ·         Chromium-rich fiber supplement keeps you fuller and reduces insulin spikes ·         Household Drinking Water Is Spreading Dangerous Bacteria ·         ‘Junk food' plant diets raise heart risk even if meat is cut out

Our terminal apps are loaded, the goals are set, but we're already hitting a few snags. The TUI Challenge begins...Sponsored By:Tailscale: Tailscale is a programmable networking software that is private and secure by default - get it free on up to 100 devices! 1Password Extended Access Management: 1Password Extended Access Management is a device trust solution for companies with Okta, and they ensure that if a device isn't trusted and secure, it can't log into your cloud apps. Unraid: A powerful, easy operating system for servers and storage. Maximize your hardware with unmatched flexibility. Support LINUX UnpluggedLinks:

On this week's episode, Kyle chats with Jim Esker, the co-creator of chromium cards! This conversation first aired in June of 2020. It's interesting to look back at that time and see what things have changed...and what things have stayed the same!

With AccessKit, Matt Campbell and Arnold Loubriat took on the ambitious task of abstracting over the accessibility APIs of several target OS' to offer toolkit providers one unified way to make their UIs accessible across platforms. This interview was recorded live at RustWeek 2025 with your host Luuk van der Duim. Contributing to Rustacean Station Rustacean Station is a community project; get in touch with us if you'd like to suggest an idea for an episode or offer your services as a host or audio editor! Twitter: @rustaceanfm Discord: Rustacean Station Github: @rustacean-station Email: hello@rustacean-station.org Timestamps & referenced resources [@1:11] - Introducing Matt and Arnold. [@1:45] - “What are you working on?” [@2:00] - “What does it offer?” [@2:28] - “Who would use AccessKit?” [@2:51] - AccessKit bindings in languages besides Rust. [@3:14] - Unifying accessibility protocols. [@4:47] - AccessKit's API. [@6:58] - AccessKit tree concepts. [@8:47] - When Arnold got involved. [@9:08] - 6000 lines of code to find Matt. [@12:56] - Matt's history with Windows and Microsoft. [@14:00] - How Quorum relates to AccessKit, Quorum [@15:52] - Challenges Quorum UI development faced. [@18:12] - Arnold and Matt on the necessity for back-end testing, Android, iOS - Linux. [@21:45] - On Newton and its Chromium relation. Newton [@27:55] - Newton on other compositers. [@29:20] - Wayland protocol purists versus Gnome D-Bus frictions. “Next-generation accessibility architecture” document [@31:03] - Where can people find Arnold? Arnold on GitHub as ‘DataTriny' Arnold Loubriat on LinkedIn DataTriny on Mastodon [@31:39] Where can people find Matt? Matt Campbell on GitHub AccessKit website. [@31:53] Your host can be found on GitHub. Luuk van der Duim Odilia screen reader atspi crate Credits Intro Theme: Aerocity Audio Editing: Luuk van der Duim Samples used in interruption: “Vinyl - 45RPM - Start 2” by: day-garwood License: Attribution 3.0 Record Scratch #3 by: musicvision31 License: Creative Commons 0 Hosting Infrastructure: Jon Gjengset Show Notes: Luuk van der Duim Hosts: Luuk van der Duim

Welcome back to our weekend Cabral HouseCall shows! This is where we answer our community's wellness, weight loss, and anti-aging questions to help people get back on track! Check out today's questions:    Felicia: Hello Dr. Cabral. What are your thoughts on this magnesium supplement ? Magnesium bisglycinate, fillers (microcrystalline cellulose, dicalcium phosphate), anti-caking agents (silicon dioxide, magnesium stearate), coating agents (hydroxypropyl methylcellulose, glycerol). Worth taken or should I look for another one? Thanks for your help                              Audrey: Hi Dr. Cabral, Thank you for being my go to person for all of my health questions! What are your thoughts on taking creatine while pregnant? I am going to keep strength training throughout my pregnancy and am hoping this helps with maintaining some muscle. I've read great things about it helping mom and baby but want to know what you think. I know you cannot give medical advice. Thanks                                                                                                                               Elsa: Hi Dr. Cabral! Thanks for all the information you provide. I'm a fairly recent listener but already have learned so much from you. May God continue to bless you, your family, and your team. My question is regarding my husband. He did a genetic test and came out positive for the MTHFR heterozygous A1298C and COMT heterozygous G472A (Val108/158Met). I've listened to your recent podcasts on COMT, but my question is regarding supplements to avoid if you have this variant. He doesn't take any medications, and already takes methylated B complex to support MTHFR and high homocysteine levels (8.3). He also takes Vit C, Zinc+Copper, Mag, Vit D+K2, Omega 3s, Probiotics. The test results indicate to avoid Quercetin and Green Tea because they are COMT inhibitors? True? Thanks.                                        Bettina: Hello Dr. Cabral. What are your thought on Super CitriMax for weightloss using a combination of 4500 mg Garcinia Cambogia with 60% HCA with 600 mg of Chromium and 1000 mg of B3 Niacinamide or B3 Nicotinamide? Thanks for your thoughts on this.                                                                                             Hannah: Hi Dr Cabral! I wrote in when you said the que was closer to 2-3 weeks and I haven't heard my question yet so this is incase my question got lost- myself and a couple of people I've met recently get an elevated heart rate when drinking alcohol (even 1 drink). This has never happened to me before and I'm very well hydrating prior, what else besides histamines could this be? Second, I have a very scant amount of blood per rectum every couple of days since starting the CBO, have you heard of this happening? I'm thinking to d/c citricidal early, I didn't test prior to CBO and only have 3 days left of that to see if it's related. Thanks for everything!!                           Thank you for tuning into today's Cabral HouseCall and be sure to check back tomorrow where we answer more of our community's questions!    - - - Show Notes and Resources: StephenCabral.com/3389 - - - Get a FREE Copy of Dr. Cabral's Book: The Rain Barrel Effect - - - Join the Community & Get Your Questions Answered: CabralSupportGroup.com - - - Dr. Cabral's Most Popular At-Home Lab Tests: > Complete Minerals & Metals Test (Test for mineral imbalances & heavy metal toxicity) - - - > Complete Candida, Metabolic & Vitamins Test (Test for 75 biomarkers including yeast & bacterial gut overgrowth, as well as vitamin levels) - - - > Complete Stress, Mood & Metabolism Test (Discover your complete thyroid, adrenal, hormone, vitamin D & insulin levels) - - - > Complete Food Sensitivity Test (Find out your hidden food sensitivities) - - - > Complete Omega-3 & Inflammation Test (Discover your levels of inflammation related to your omega-6 to omega-3 levels) - - - Get Your Question Answered On An Upcoming HouseCall: StephenCabral.com/askcabral - - - Would You Take 30 Seconds To Rate & Review The Cabral Concept? The best way to help me spread our mission of true natural health is to pass on the good word, and I read and appreciate every review!  

Judge Blasts Apple For Violating Antitrust Ruling Google's Sundar Pichai Calls US Remedies 'De Facto' Spinoff of Search - Slashdot Firefox could be doomed without Google search deal, says executive Visa Announces Plans to Give AI Agents Your Credit Card Information The Age of Realtime Deepfake Fraud Is Here The TAKE IT DOWN Act: A Flawed Attempt to Protect Victims That Will Lead to Censorship Congress Moving Forward On Unconstitutional Take It Down Act White House Slams Amazon After Report it Will Highlight Tariff Costs The Kickstarter you backed may soon ask for more money to cover Trump's tariffs Microsoft Raises Xbox Prices 20% as Tariffs Drive Up Cost of Development UPS will cut 20,000 jobs because fewer Amazon packages are coming Elon Musk's DOGE ties could get his companies out of $2 billion in potential liability President Trump's fiscal 2026 budget proposal suggests slashing $491M from CISA's ~$3B budget, claiming the cut "refocuses CISA on its core mission" Government Actually Threatens Wikipedia's Editorial Freedom; Self-Proclaimed Free Speech Warriors Suddenly Have Other Plans Mark Zuckerberg Sailed 5,300 Miles With Two Superyachts Only to Helicopter Up a Mountain and Ski Down in Billionaire Style - Sustainability Times Massive power outage in Spain, Portugal leaves millions in dark Wall Street Banks Sell Final Slug of Elon Musk's X Debt Elon Musk's SpaceX gets a company town in Texas Amazon deploys the first Project Kuiper internet satellites Researchers Secretly Ran a Massive, Unauthorized AI Persuasion Experiment on Reddit Users How Badly Did ChatGPT and Copilot Fail to Predict the Winners of the Kentucky Derby? - Slashdot Quantum message travels record distance over fiber optic network Photo appears to show Mike Waltz using Signal-like app that can archive messages Chinese university designed 'world's first silicon-free 2D GAAFET transistor,' claims new bismuth-based tech is both the fastest and lowest-power transistor yet The one interview question that will protect you from North Korean fake workers Host: Leo Laporte Guests: Owen Thomas, Iain Thomson, and Gary Rivlin Download or subscribe to This Week in Tech at https://twit.tv/shows/this-week-in-tech Join Club TWiT for Ad-Free Podcasts! Support what you love and get ad-free shows, a members-only Discord, and behind-the-scenes access. Join today: https://twit.tv/clubtwit Sponsors: canary.tools/twit - use code: TWIT outsystems.com/twit drata.com/weekintech coda.io/twit zscaler.com/security

Michael Truell is the co-founder and CEO of Anysphere, the company behind Cursor—the fastest-growing AI code editor in the world, reaching $300 million in annual recurring revenue just two years after its launch. In this conversation, Michael shares his vision for the future, lessons learned, and advice for preparing for the fast-approaching AI future.What you'll learn:• Cursor's early pivot from automating CAD to automating code• Michael's vision for “what comes after code” and how programming will evolve• Why Cursor built their own custom AI models despite not starting there• Key lessons from Cursor's rapid growth• Why “taste” and logic design will become more valuable engineering skills than technical coding ability• Why the market for AI coding tools is much larger than people realize—and why there will likely be one dominant winner• Michael's advice for engineers and product teams preparing for the AI future—Brought to you by:Eppo—Run reliable, impactful experimentsVanta—Automate compliance. Simplify securityOneSchema—Import CSV data 10x faster—Where to find Michael Truell:• X: https://x.com/mntruell• LinkedIn: https://www.linkedin.com/in/michael-t-5b1bbb122/• Website: https://mntruell.com/—In this episode, we cover:(00:00) Introduction to Michael Truell and Cursor(04:20) What comes after code(08:32) The importance of taste(12:39) Cursor's origin story(18:31) Why they chose to build an IDE(22:39) Will everyone become engineering managers?(24:31) How they decided it was time to ship(26:45) Reflecting on Cursor's success(32:03) Counterintuitive lessons on building AI products(34:02) Inside Cursor's stack(38:42) Defensibility and market dynamics in AI(46:13) Tips for using Cursor(51:25) Hiring and building a strong team(59:10) Staying focused amid rapid AI advancements(01:02:31) Final thoughts and advice for aspiring AI innovators—Referenced:• Cursor: https://www.cursor.com/• Microsoft Copilot: https://copilot.microsoft.com/• Scaling laws for neural language models: https://openai.com/index/scaling-laws-for-neural-language-models/• MIT: https://www.mit.edu/• Telegram: https://telegram.org/• Signal: https://signal.org/• WhatsApp: https://www.whatsapp.com/• Devin: https://devin.ai/• Visual Studio Code: https://code.visualstudio.com/• Chromium: https://chromium.googlesource.com/chromium/src/base/• Exploring ChatGPT (GPT) Wrappers—What They Are and How They Work: https://learnprompting.org/blog/gpt_wrappers• OpenAI's CPO on how AI changes must-have skills, moats, coding, startup playbooks, more | Kevin Weil (CPO at OpenAI, ex-Instagram, Twitter): https://www.lennysnewsletter.com/p/kevin-weil-open-ai• Behind the founder: Marc Benioff: https://www.lennysnewsletter.com/p/behind-the-founder-marc-benioff• DALL-E 3: https://openai.com/index/dall-e-3/• Stable Diffusion 3: https://stability.ai/news/stable-diffusion-3—Production and marketing by https://penname.co/. For inquiries about sponsoring the podcast, email podcast@lennyrachitsky.com.—Lenny may be an investor in the companies discussed. Get full access to Lenny's Newsletter at www.lennysnewsletter.com/subscribe

YOU ARE THE PRODUCT! But... are you? In Russia, Windows 11 uses you! Plus, something happened to Paul on the way to dual-booting Ubuntu 25.04 on Surface Laptop 7, but all is well! Also, you should be using Brave. But if you don't like/trust Chromium, Firefox 138 finally added profile management support. Windows Windows 11 24H2 preview update for April finally arrives Now we know why Microsoft waited: It wanted to announce the "general availability" of Recall, Click to Do, and "improved Windows Search" (we're still struggling with a name for that one) Dev and Beta (24H2) builds add a profanity filter, a Pen shortcut for Click to Do, improved Windows Search for work and school accounts, Accessibility flyout in Quick settings Microsoft (sort of) explains why Windows Insider Preview channels don't follow a logical order anymore Microsoft deprecates Map app in Windows 11 That makes sense. But also VBS Enclaves in pre-24H2 versions, which is interesting Corporate Microsoft says it will defend EU companies against US government Alphabet/Google is doing just great, thanks Intel earnings are flat, and that's as good as that news gets Samsung posts record revenues on strong S25 series sales Dev Build and Google I/O are coming in hot Google is holding a separate Android event for the first time, ahead of I/O What about Surface? At Build last year, the company announced Copilot+ PC AI Microsoft has an OpenAI problem - duh and/or hello Microsoft is part of an AI unholy quaternity on new Moto phones Duolingo announces controversial "AI first" strategy - And then announces 148 new AI-based courses Apple on Apple Intelligence: Just kidding! OpenAI on GPT-4o: Just kidding! ChatGPT goes shopping and OpenAI improves Deep Research Google updates NotebookLM audio overviews with support for over 50 languages YouTube starts testing AI overviews for videos - and Spotify is using AI for playlists Adobe updates Firefly models, adds third party support DuckDuckGo's Duck.ai now supports real-time model switching Meta launches a standalone AI app that no one should want Xbox Xbox-exclusive game Towerborne is here in preview on Xbox, PC, and Game Pass Tips and Picks Tip of the week: Be prepared App pick of the week: Firefox 138 RunAs Radio this week: Modern Work in 2025 with Karoliina Kettukari Brown liquor pick of the week: Highwayman Whisky Abbey 2024 Hosts: Leo Laporte, Paul Thurrott, and Richard Campbell Download or subscribe to Windows Weekly at https://twit.tv/shows/windows-weekly Check out Paul's blog at thurrott.com The Windows Weekly theme music is courtesy of Carl Franklin. Join Club TWiT for Ad-Free Podcasts! Support what you love and get ad-free shows, a members-only Discord, and behind-the-scenes access. Join today: https://twit.tv/clubtwit Sponsors: uscloud.com cachefly.com/twit