Podcasts about gpl

This show has been flagged as Explicit by the host. Freedom 0–3 (verbatim reference) The four freedoms, GNU/FSF: https://www.gnu.org/philosophy/free-sw.html Richard Stallman: https://www.stallman.org/ Named FOSS figures (freedom 3 list) Linus Torvalds (Linux): https://en.wikipedia.org/wiki/Linus_Torvalds Dries Buytaert (Drupal): https://dri.es Guido van Rossum (Python): https://gvanrossum.github.io Ian Murdock (Debian): https://en.wikipedia.org/wiki/Ian_Murdock Brian Behlendorf (Apache): https://en.wikipedia.org/wiki/Brian_Behlendorf Miguel de Icaza (GNOME/Mono): https://en.wikipedia.org/wiki/Miguel_de_Icaza Infrastructure block (post beer 1) curl / Daniel Stenberg: https://curl.se and https://daniel.haxx.se xkcd 2347 (dependency comic): https://xkcd.com/2347/ xz backdoor, CVE-2024-3094: https://en.wikipedia.org/wiki/XZ_Utils_backdoor Andres Freund's original disclosure: https://www.openwall.com/lists/oss-security/2024/03/29/4 Licensing block (beer 2–3) GPL: https://www.gnu.org/licenses/gpl-3.0.html MIT License: https://opensource.org/license/mit FreeBSD: https://www.freebsd.org macOS/Darwin BSD lineage: https://en.wikipedia.org/wiki/Darwin_(operating_system) PlayStation using FreeBSD (Orbis OS): https://en.wikipedia.org/wiki/Orbis_OS Industry acquisitions (beer 4) Microsoft acquires GitHub, 2018, $7.5B: https://news.microsoft.com/2018/06/04/microsoft-to-acquire-github-for-7-5-billion/ FOSDEM field report (beer 4–5) FOSDEM: https://fosdem.org Ladybird browser / Andreas Kling: https://ladybird.org Godot Engine: https://godotengine.org Home Assistant: https://www.home-assistant.io Redis → Valkey fork: https://valkey.io Terraform → OpenTofu fork: https://opentofu.org Homework block (beer 5) Ollama: https://ollama.com Codeberg: https://codeberg.org LibreOffice: https://www.libreoffice.org Firefox: https://www.mozilla.org/firefox Provide feedback on this episode.

À l'occasion de cette rediffusion, nous vous proposons de revenir sur notre échange avec Jean-Baptiste Kempf, co-créateur du logiciel VLC, figure incontournable de l'open source, et aujourd'hui à l'origine du projet Kyber.

Kojo Addae-Mensah, CEO of Databank, weighs in on possible Black Stars returns; GFA statistician Mo Shaban reveals the latest GPL transfers; Vinícius ends Arsenal speculation with Real Madrid renewal & MORE!!

Suze's Forbes piece, and the question under it. Her Telegram reporting found a persistent identifier that survives restarts, network changes and borders, with the credible risk being targeted surveillance rather than mass tracking. Her real question: why is don't-trust-verify never applied to companies and personalities inside Bitcoin? The confessions, and Cory's calibration. American HODL admitted he bought a Coldcard largely as a badge of Maxi Club membership, and Odell described being pulled into a cult of personality. Cory's distinction: someone who bills himself as a technical expert and reviews products carries responsibility a self-described bullshitter does not. He also warned against the new bad heuristic. Treating abrasiveness as a proxy for bad code fails immediately: Core and Blockstream are full of people who read as cocky and their code is sound. He credited NVK as a genuinely good educator while calling the outcome inexcusable. Brandon Quittem: deep in it, not at peak. Maximum wealth inequality is a classic Fourth Turning signpost, and the post-war institutions are a shell of themselves without anyone needing to be malicious. He held his own confidence low throughout, calling the framework a rough way to squint at the world. His bet on the climax. Not a head-to-head with China, which a hyperglobalized economy makes unlikely, but a Cold War 2.0: proxy and economic war, trade policy, supply-chain fights, plausible deniability, and zero-day attacks on each other's infrastructure. AI through the Fourth Turning lens. The authors would say technology is always arriving and the variable is how the generational mood receives it. Facebook landed because millennials were the sharing archetype; Gen X would have refused it. He calls AI pure leverage with no clear direction. Horseshoe theory, and Bitcoin as the through line. Answering Suz on where left and right even are now: both extremes arrive at authoritarianism from the same wealth-inequality catalyst, which is why Bernie and Trump were popular at once. Bitcoin is what pushes back on both. He retracted his own timeline live. Five years ago he would have called a Bitcoin standard likely by 2030 and now says that was far too aggressive. A First Turning looks like exhaustion, inequality easing, culture getting more boring, and it may only be visible in hindsight. The libngu decision, traced. An audience question surfaced that the firmware was rewritten off a GPL library partly out of anger at being cloned, producing an in-house source-available replacement and fewer eyes. Of 300-plus repos the red team has scanned, the one that came back completely clean was libsecp256k1. The synthesis, and the way out. Suz: Bitcoiners who believe they saw through the system struggle to admit deception, because it means admitting they were fooled. Brandon: that lowers the guard rather than raising it. His prescription is local, not global. Be the sewer rat yourself.

In this episode, we spent most of our time unpacking the Coldcard firmware exploit and the chaos that followed across the Bitcoin self-custody world. From our perspective, this was a painful but important conversation about broken trust, weak entropy, and the real-world consequences of software mistakes in security-critical products. We walked through how the vulnerability appears to have stemmed from a flawed random number generation implementation, why so many wallets were exposed, and how quickly attackers were able to sweep funds once the issue became public. We also discussed why this incident has reignited the debate around GPL licensing, open development, and the value of broad community review for Bitcoin hardware and firmware projects.We also zoomed out to talk about what this means for Bitcoin builders and operators going forward. That included the importance of defensive self-custody practices, why simply applying a hotfix may not be enough to restore confidence, and how the broader community responded with audits, tooling, data analysis, and emergency migration help. We wrapped by connecting these lessons to open-source mining development, including updates from the 256 Foundation ecosystem and the latest Mujina developer call, where contributors are working to build community-owned tools the right way: in public, with transparency, shared responsibility, and long-term resilience in mind.

Google wants you to use a selfie video for account recovery, LG will stop apps turning their smart TVs into residential proxy nodes, we disagree about how serious OpenAI’s agent hacking Hugging Face is, FreeBSD removes the last bits of GPL software and suffers an embarrassing git flub , and backing up to an encrypted NAS without ZFS. Plug Support us on patreon and get an ad-free RSS feed with some early episodes News/discussion Introducing selfie for sign-in: a new, easy way to access your Google Account LG to Ban Residential Proxies from Smart TV Apps OpenAI says its AI agent broke out of testing sandbox to hack Hugging Face FreeBSD 16 Retires The Last Of Its GPL Code From Its Base System Ports Repository Freeze Free consulting We were asked about backing up to an encrypted NAS without ZFS. See our contact page for ways to get in touch.

Google wants you to use a selfie video for account recovery, LG will stop apps turning their smart TVs into residential proxy nodes, we disagree about how serious OpenAI’s agent hacking Hugging Face is, FreeBSD removes the last bits of GPL software and suffers an embarrassing git flub , and backing up to an encrypted NAS without ZFS. Plug Support us on patreon and get an ad-free RSS feed with some early episodes News/discussion Introducing selfie for sign-in: a new, easy way to access your Google Account LG to Ban Residential Proxies from Smart TV Apps OpenAI says its AI agent broke out of testing sandbox to hack Hugging Face FreeBSD 16 Retires The Last Of Its GPL Code From Its Base System Ports Repository Freeze Free consulting We were asked about backing up to an encrypted NAS without ZFS. See our contact page for ways to get in touch.

In this episode, we sat down with Ryan, the mastermind behind Mujina Mining Firmware, to dig into what Mujina is, why open-source mining firmware matters, and how the project is evolving. We talked through the difference between simply publishing source code and building a true community-driven open-source project, why Mujina uses the GPL license, and how that protects downstream users and contributors in a mining ecosystem that has been dominated by closed, proprietary firmware for years. Ryan also explained the role of the Mujina dev calls, the distinction between firmware, operating systems, kernels, and images, and why the next big step for the project is shipping full, easy-to-flash Mujina OS images for machines like the S19.We also covered a lot of ground on what's happening around the broader 256 Foundation ecosystem: Ryan's mining workshop in Nairobi and how others across Africa are now reusing those materials, the growing momentum behind HydraPool and open-source mining education, recent mining decentralization events in DC and Nashville, and new hardware progress including the Bitaxe Bonanza, Bitaxe Proto, and support for non-Bitmain chips. Overall, this was a wide-ranging conversation about replacing the proprietary mining stack with open, extensible tools that miners, builders, and educators can actually own, adapt, and improve together.

This show has been flagged as Clean by the host. Hello, again. This is Trey. Welcome to part 8 in my Cheap Yellow Display (CYD) Project series. If you wish to catch up on earlier episodes, you can find them on my HPR profile page https://www.hackerpublicradio.org/correspondents/0394.html It is hard to believe that I started this project and the HPR series to document it more than a year ago. Time flies. Life happens. I spent the last 8 months so focused on work related activities that I had to set the project aside. And once I set it aside, it was difficult to get back to again. The one time I tried, I found that my son's old Windows laptop, which I had commandeered to use for the project, was once and truly dead. We live in a different world now than we did when I began this project. Today, everything is about AI – how it is changing our world, increasing efficiencies, and even displacing certain types of jobs. "Vibe coding" is transforming the way we make software, and now everyone is a developer. Within my organization, we are all being strongly encouraged to learn more about AI and apply it in our daily work. We are blessed to have access to a wide range of training and to powerful tools which support the process. Several colleagues within my organization and outside my organization have recommended Claude Code -- for development, for organization, for brainstorming, and for much more. My role is not that of a developer, and I have had no need for Claude Code at work. There are plenty of other tools for me to use. But at home, I thought... I could install Claude Code at home to experiment with and to learn. And then it hit me. I wonder if I could use Claude Code to help me with my stalled CYD project. "Hello, my name is Trey, and I am a fraud." OK. I don't think I am a fraud, but having never used such a powerful tool to help me code, I feel a little bit like a fraud, with Claude doing the work for me. Let's talk through what we did. As I mentioned, I was unable to use the laptop on which I created the original GUI code. But no worries, because It was all on GitHub, right? So, I began by trying to install Claude Code on one of my Ubuntu machines. That failed miserably, and all the instructions I found online recommended running it on Windows. So I transitioned to installing Claude Code on a freshly built Windows 10 system using some old hardware which will not support Windows 11. Surprisingly, It seems that Claude wants to run within Ubuntu on Windows Subsystem for Linux (WSL). Once I went through all the hoops for installing and setting up my basic subscription, I got to work. I created a new directory to use for all my project files, and another one for Claude to write all its output files to. Everything I have read and heard about using Claude Code for a project like this recommended beginning by using Claude to create the project plan. So my first prompt was as follows: "I am building a project using an ESP32 cheap yellow display. The final goal is to have a device with a graphical user interface which will allow me store several text messages, each assigned to their own specific button. Then, when one of the buttons is pressed, the message will be converted into morse code, and the message will be sent by blinking an onboard LED. I already have the initial design for the GUI coded in my github repository. Please construct a detailed step by step plan for building this application" I wanted to keep it simple at the beginning, so even though I plan to use an opto-isolated relay for the output, I am starting out using the built in LED. Claude asked me for the URL for my Github repository, and I provided it. After thinking for a bit, it produced a project plan. CYD Morse Sender — Step-by-Step Build Plan What You Already Have - 3 fully designed LVGL screens (Send, Config, Keyboard) - 7 send buttons with green styling on the Send Screen - Speed slider (5–30 WPM) and program slot dropdown on Config Screen - Text area + LVGL keyboard widget on Keyboard Screen - Display driver and touchscreen hardware initialized (but touch read was stubbed out) --- Phase 1: Fix Touchscreen Input Initialize the XPT2046 on VSPI, replace the hardcoded touched = false with real touch data, calibrate raw ADC coordinates to screen pixels, and verify all three nav buttons transition screens correctly. Phase 2: Persistent Message Storage Use Preferences.h / NVS to store 7 messages ("msg0" – "msg6") that survive power cycles. Load on boot and populate send button labels. Phase 3: Config Screen — Slot Selection & Speed Wire the Program dropdown to g_selectedSlot, wire the Speed slider to g_wpm with a live WPM label, and wire the Set button to clear the text area and navigate to the Keyboard Screen. Phase 4: Keyboard Screen — Capture and Save Text On keyboard OK (LV_EVENT_READY): read the text area, save to NVS, update the send button label, navigate back. On Cancel: navigate back without saving. Phase 5: Morse Code Engine Build morse.h with the full A–Z / 0–9 lookup table, a textToMorse() converter, and Paris-standard timing (unit_ms = 1200 / wpm). Phase 6: Non-Blocking LED Transmission State machine (IDLE / LED_ON / LED_OFF) driven by millis() in a morseUpdate() function called every loop — no delay(). LED on GPIO 17 (blue). Phase 7: Wire the Send Buttons Each button calls startMorse(getMessage(slot)) if not already transmitting. Disable all send buttons during TX; re-enable when the state machine reaches the end. Phase 8: Integration & Polish Stop button, WPM persistence, empty-slot guard, serial debug output, final touch calibration, end-to-end test checklist. --- Recommended order: Phase 1 → 2 → 7 (partial) → 5 → 6 → 7 (full) → 3 → 4 → 8 This was wild! Claude determined exactly how far along I was in the project, and also alerted me to the fact that the "touch read was stubbed out". Ugh. This means that the files I had uploaded to GitHub were my original GUI files (Episode 05 – HPR4532 - https://hackerpublicradio.org/eps/hpr4532/index.html ) and not the ones that I finally got working properly (Episode 07 – HPR4624 - https://hackerpublicradio.org/eps/hpr4624/index.html ). That was my own fault. Did I mention that I don't get Git? I REALLY need to learn to properly use Git! But, we have a plan, broken down by eight numbered phases. And they seem to address all the functionality I wanted with a few additional things I had not thought about. Interestingly, even though these phases are sequentially numbered, Claud recommended that we approach them in a bizarre order: Phase 1 → 2 → 7 (partial) → 5 → 6 → 7 (full) → 3 → 4 → 8 . Alright. Let's see what we can do. The first phase is to fix the touchscreen input. Claude took me through it step-by-step, asking as it needed to read specific project files. Finally, it wrote a new ui.ino code file to my speficied output directory for me to test. I copied it into the correct file location, said a quick prayer, compiled in Arduino IDE, and downloaded to the CYD. Well, that is... interesting. The display looked nothing like it was supposed to. There were vertical green bars with smaller dashed green vertical stripes in them. I will include a picture in the show notes so that you can see what it looked like and why it was so difficult to describe. I spent the next hour or so trying to explain what I was seeing to a chat bot. Claude recommended potential fixes which either did nothing or made the situation worse. I began questioning whether this was a good idea, how people actually gained efficiencies talking to a bot, and even several life choices. Then I had a thought. I prompted Claude: If I were to take a picture of the screen on the cheap yellow display and copy it into the output folder, would you be able to analyze it to better determine what is wrong and how to fix it? Shockingly, Claude answered in the affirmative, and told me to copy the picture to the output folder and let it know when to proceed. It analyzed the picture and more of the supporting files it had copied from my GitHub, asking each time if it could access that file. It determined that my original code was written for a flavor of LVGL version 8 and I was now using LVGL 9.5. It recommended changes, and then asked permission to make those changes, file by file. .h files & .c files, Finally, I just gave it permission to edit the files in the project folder without asking for permission for each file each time. Claude was still explaining each change, showing me exactly what would be changed, and asking for permission, so that I could review all of the changes. But now it was not asking additional permission to write to each of the impacted files. Next, Code compiled and downloaded. Different screen, but not right. Again, I took a picture and gave it to Claude to analyze. So, Claude paused and altered the code to generate a specific test pattern overtop of the GUI. The test pattern was supposed to cover the entire rectangular screen. But parts of the pattern were in a square on the screen and parts were not. Another photograph and analysis, told Claude that there were some rotation/screensize issues. We repeated this several times. Some resulted in improvement, and others did not. This is the point where I noticed something interesting. Not about Claude, specifically, or about the app. But I noticed something interesting about myself and about the process. Previously, when I was working through some of these challenges without Claud, I found myself becoming more and more stressed, frustrated, and angry, until I found a solution. Then another problem would repeat the cycle. Success in the end was great, but the emotional extremes during the process were not always pleasant. Now, I was effectively managing the project, and relaying information to the resource responsible for fixing the problems -- a very different experience. But I also ran into another issue. Claude became absolutely certain that the problem revolved around the device not accurately knowing where the 4 corners of the screen were. But in reality, the output of the test pattern was rotated 90 degrees from the actual screen. It took several iterations of me insisting that the problem had to do with screen orientation and not corner coordinates. It was interesting to experience the tool doubling down on an obvious mistake, but we finally resolved that. Again, while it was frustrating, it was much less stressful. We proceeded to Phase 2: Persistent Message Storage where we ensured that the button labels on the send screen were stored in the devices persistent storage, so that, when they are edited to contain the message they should send, that information would survive a reboot. Next, we combined elements of Phase 5: Morse Code Engine , Phase 6: Non-Blocking LED Transmission , and Phase 7: Wire the Send Buttons together. Building the morse code engine was an area I had been thinking about for a while. I already had working parts of something similar in the Arduino practice oscillator I have referenced a few times in this series. The code for the practice oscillator may be found on my GitHub, but it was all based on original code from jmharvey1, with my only contribution being making pin assignments variables so that the code could easily be ported to different devices. So, I was happy that we were building the morse code engine directly. The code for it may be found in morse.h, which uses a constant character lookup table to define each character. Without any specific direction from me, Claude used the PARIS timing methods I have already described within Episode 6 of this series. It defines timing for DOT, DASH, LETTER_GAP, and WORD_GAP, and all are based on a simple calculation of 1200 ms / the number of words per minute (WPM) we wish to transmit. Along the way, we discovered that, if we tried to use the delay() function, it would crash the program due to a conflict with the LVGL timer used for touchscreen inputs. Claude altered all the delays accordingly. Then, Phase 3: Config Screen — Slot Selection & Speed allowed us to configure the WPM we wished to use in addition to selecting a specific Send button to reconfigure. This forced us to work on Phase 4: Keyboard Screen — Capture and Save Text which is used to type the entries for each Send button. At this point, I also decided that we would want to also use the Keyboard Screen to send ad hoc morse as we typed it. During this phase we discovered several bugs which seemed to cause random freezes. Careful troubleshooting with messages output to the Arduino IDE's serial console helped us narrow down the causes and remedy them. Finally all the tests worked and I am able to merrily pre-configure macro buttons with custom messages and use the CYD to send the morse code for those messages to the on-board LED at whichever rate I specify. I have noticed in my presentation of this narrative that I repeatedly slip into the first person plural terms "we" and "us" instead of the first person singular terms "I" and "me". I have unconsciously personified Claud and recognized it as an integral part of my (formerly one person) development team. I finally configured Claude to connect to my GitHub repo and upload all the files and documentation. We additionally created a CYD-Narrative.md file which describes in more detail all the work which was done on the project. I still do not 100% get git, but we are successfully using it. You can find all these files in my GitHub repo ( https://github.com/jttrey3/CYD_MorseSender ) where they are shared under a GPL 3.0 license. There are still several additional steps I plan to complete in the next few months. 1. I will be integrating an opto-isolated relay which will allow me to plug the device into the straight key input on any amateur radio. This will require a battery power source, charge controller, and more hardware. I... make that "We" (Claude & I) will be modifying the code to support an audio side tone through an attached speaker when sending code We will add an output selection switch to the config page to choose any combination of speaker, relay, or LED as output. We will develop a downloadable firmware which I hope to share with the Cheap Yellow Display community. If you can think of any additional features you would like to see integrated, please drop me an email using the address in my HPR profile. I may also work with a friend to attempt to 3d print a case for the entire contraption, and I will be sure to record additional episodes sharing the process. I have learned so much throughout this project, about the CYD, ESP32, GUIs, Claude Code, GitHub, and most of all, about myself. Does using AI to develop this code make me a fraud? It still feels like it in some ways. Does it make me more productive? ABSOLUTELY! I made consistent forward progress when I only had 30-60 minutes each day to work on it, and everything discussed in this episode was completed in less than a week. If I had been able to work on it for a few hours uninterrupted, it may have only taken me 3-5 hours. Does it empower and inspire me to do more projects like this? 100% I feel like I had support working with me the whole way. I was less stressed overall, and it had less of an impact on the amount of and quality of time I spent with my family. I will be wrapping up this series soon, without any more 6 month gaps, I hope. Until next time... Provide feedback on this episode.

Official native Linux Jagex Launcher for Old School RuneScape, revenue estimates for Valve's Steam Machine, a static recompilation of Castlevania: Symphony of the Night, and FreeBSD 16 removing all GPL code from its base system.Video version of the show is available to Patrons, along with the Extended Chaos podcast featuring over an extra hour of LWDW content every week.⁠⁠⁠⁠⁠⁠Patreon⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠Discord⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠YouTube⁠⁠⁠⁠⁠⁠⁠⁠TIMESTAMPS00:00 Welcome to the Show & Weekly Catchup01:11 Testing NVENC, OBS, and NVIDIA Jetson Hardware04:35 Weekend Outing at the Park & Outdoor Fun06:12 Old School RuneScape Launches Official Linux Bet14:51 Steam Machine sales data 22:05 Castlevania Syphyony of the Night on Linux30:48 BSD is GPL freeTOPICSOld school penguins https://secure.runescape.com/m=news/jagex-launcher-for-linux-beta-out-now?oldschool=1Steam Machine Sales Uphttps://www.techspot.com/news/113169-valve-steam-machine-may-selling-between-12000-15000.htmlSymphony of the Night recomphttps://github.com/birabittoh/NocturneRecompFreeBSD - GPLhttps://www.phoronix.com/news/FreeBSD-16-Goes-GPL-Free

Bun quitte Zig pour Rust en 11 jours à coups de Claude Code, pour 165 000$ payés par Anthropic : la réaction du créateur de Zig ne se fait pas attendre. TypeScript 7 débarque, réécrit en Go, 8 à 12x plus rapide. Entre les deux, Vidocq réimplémente Jakarta EE en souverain, le COBOL met un uppercut aux microservices, et un CTO demande à son équipe combien de temps il lui faudrait pour revenir à sa vélocité antérieure sans Claude Code. De quoi réfléchir avant le prochain rewrite. Enregistré le 17 juillet 2026 Téléchargement de l'épisode LesCastCodeurs-Episode-342.mp3 ou en vidéo sur YouTube. News Langages Est-ce qu'on peut aussi utiliser des double, des longs, ou autre pour gérer les montants monétaires en Java ? https://blog.frankel.ch/bigdecimal-vs-double/ double (IEEE 754) Usage : Calculs scientifiques, métriques, statistiques. Avantages : Très performant (matériel), idéal pour l'approximatif. Risques : Erreurs d'accumulation, égalité (==) trompeuse, NaN / -0.0. Bonnes pratiques : Utiliser une tolérance (epsilon ou ULP) pour comparer ; utiliser des algorithmes de sommation compensée (Kahan/Neumaier) pour la précision. BigDecimal Usage : Finance, comptabilité, fiscalité (précision décimale stricte). Avantages : Contrôle total des arrondis et de l'échelle. Risques : Lent (allocations), immutabilité (risque de mauvaise réaffectation), confusion equals() vs compareTo(). Bonnes pratiques : Initialiser via String ou valueOf() ; utiliser compareTo pour l'égalité. Point fixe (long) Usage : Trading, systèmes haute performance, paiements. Avantages : Très rapide, déterministe, zéro allocation. Risques : Gestion manuelle de l'échelle et des débordements (Math.addExact). Points de vigilance en production Sérialisation (JSON) : Préférer les String pour BigDecimal pour éviter la perte d'échelle. Atomicité : double n'est pas atomique ; utiliser volatile ou DoubleAdder (pour les compteurs). Tests : Toujours définir un delta ou Offset pour les tests de flottants. Bibliothèques recommandées Moneta (JSR 354) : Standard bancaire complet. decimal4j : Optimisé pour le point fixe haute performance. Apache Commons Numbers : Outils robustes pour la précision et les sommations. Typescript 7 est de sortie devblogs.microsoft.com/typescript/announcing-typescript-7-0 Performance majeure : Portage natif en Go offrant des gains de vitesse de 8x à 12x et une consommation mémoire réduite. Architecture optimisée : Utilisation du multithreading (mémoire partagée) et parallélisation native (analyse, vérification de types,émission). Nouvelles options de contrôle : Introduction des flags –checkers, –builders (parallélisation) et –singleThreaded (mode mono-cœur). Nouvel observateur de fichiers : Passage à une solution basée sur @parcel/watcher pour une meilleure réactivité et stabilité du mode –watch. Compatibilité et transition : Compatible avec les bases de code TypeScript 6.0. Utilisation du package @typescript/typescript6 recommandée pour maintenir des outils dépendants de l'ancienne API. Changements de configuration : Durcissement des défauts (ex: strict activé par défaut) et suppression de nombreuses options obsolètes (target: es5, baseUrl, etc.). Amélioration de l'expérience éditeur : Serveur de langage (LSP) plus stable avec une réduction de 80 % des erreurs et 60 % des crashs. Limitations actuelles : Support incomplet pour les frameworks utilisant des plugins de langage (Vue, Svelte, Astro, Angular) en attendant une API stable. "Java, the documentary" est sur YouTube, retraçant l'histoire du langage youtube.com/watch?v=… La vidéo n'était pas encore disponible à l'heure de l'enregistrement. Sortie officielle le 17 juillet. Avec des interviews de James Gosling, Brian Goetz, Venkat Subramaniam, et bien d'autres. Librairies What's New in 8.0 - Hibernate docs.hibernate.org/orm/8.0/whats-new L'intégration de Jakarta Persistence 4.0 apporte des nouveautés majeures comme EntityAgent (qui standardise la StatelessSession), les mappings de result set en SQL natif, et de nouvelles options de configuration de session et de requêtes (Session Creation Options, Query Options). Le support de Jakarta Data 1.1 est ajouté pour les Hibernate Data Repositories, incluant l'intégration avec les requêtes statiques JPA4, les projections @Select, et les repositories asynchrones via Jakarta Concurrency ou Hibernate Reactive. L'introduction du Graph-based Flushing remplace l'ancienne approche basée sur des heuristiques par un modèle de dépendances utilisant les contraintes relationnelles, afin d'améliorer la fiabilité des tris, la gestion des batchs et les performances globales (bien que l'ancienne méthode reste temporairement disponible). L'API ProcedureCall a été améliorée pour faciliter le casting des résultats (asResultSetOutput) et permettre la déclaration paresseuse (lazy) du mapping des ResultSet. Hibernate supporte désormais la sécurité au niveau de la ligne (Row-Level Security) de manière native pour les bases de données compatibles (PostgreSQL, Db2, SQL Server, CockroachDB) afin de gérer la visibilité en contexte multi-tenant. Une nouvelle méthode getReference() permet dorénavant de récupérer la référence d'une entité directement à partir de son natural id. Le mode Safe Mode Validator (hibernate.query.safe_mode_enabled=true) fait son apparition pour bloquer les opérations risquées comme sql(), function() ou column() dans les requêtes HQL et Criteria, ce qui est particulièrement utile pour les applications exposées aux LLMs. La gestion des associations bidirectionnelles lors de la phase de flush peut maintenant être prise en charge automatiquement par Hibernate (hibernate.bidirectionality_management=true), synchronisant la référence côté inverse de l'association. Le Subselect Fetching est considérablement amélioré, supportant dorénavant les associations "to-one" pour le bulk select fetching (au lieu de se limiter aux collections) et devenant une option de premier ordre via FetchMethod.BY_SUBQUERY. Un des papas de Cucumber et Gherkin lance Var, une alternative pour le test et le BDD var.oselvar.com Lancement de Vár : Nouvel outil de test créé pour pallier les défauts de Cucumber. Limites de Cucumber : Syntaxe Gherkin trop rigide, intégration difficile avec les exécuteurs de tests et support éditeur limité. Usage avec l'IA : Conçu spécifiquement pour vérifier que les agents IA respectent les intentions et spécifications de l'utilisateur. Fonctionnement : Utilisation du Markdown plutôt que du Gherkin ; sert à la fois de guide et d'outil de vérification. Développement assisté : Code et documentation générés en grande partie par Claude sous supervision humaine. Appel aux retours : Projet ouvert aux tests et aux critiques de la communauté. Web Une nouvelle méthode HTTP : QUERY https://kreya.app/blog/new-http-query-method-explained/ Méthode HTTP QUERY (RFC 10008) pour les recherches complexes. Problème : GET (limité par l'URL) vs POST (sémantique inadaptée). Avantages : Permet un corps de requête, sûr, idempotent et cacheable. Limites : Support infrastructurel faible, non partageable par lien, cache complexe. Usage : À réserver aux requêtes complexes si l'environnement le permet. Comment je fais du design en tant que dev backend eventuallycoding.com/p/comment-je-fais-du-design-en-tant-que-dev-backend Hugo Lassiège retrace l'évolution de son workflow de création d'interfaces en tant que développeur backend, depuis ses débuts avec Bootstrap jusqu'à l'ère de l'intelligence artificielle. L'article explique comment la structuration des éléments visuels a progressé grâce à l'Atomic Design, l'émergence des design systems et l'adoption des design tokens via un framework comme Tailwind. L'auteur détaille son processus actuel qui s'appuie fortement sur Claude Design pour générer et itérer sur des maquettes à partir d'un brief, d'un screenshot ou d'un design system de référence. Il aborde également le risque de slopification et de standardisation extrême apporté par ces outils, rappelant que si l'IA simplifie la technique, il reste crucial d'injecter de l'identité et de l'originalité pour éviter un web trop aseptisé. Data et Intelligence Artificielle De l'utilisation de SKILL.md et de "loop engineering" pour augmenter sa productivité glaforge.dev/posts/…/of-skills-and-loops-with-ai-assistance Les skills permettent d'encoder une procédure de manière répétable et automatisable Le loop engineering enlève l'humain de la boucle afin que l'agent atteigne un objectif donné de façon plus autonome Pour écrire des Codelabs (sorte de tutoriel guidé pas à pas) Guillaume a transformé une séance de création de codelab avec son agent préféré (Antigravity) en skill réutilisable pour l'écriture de ses prochains codelabs Il a également utilisé l'approche de "loop engineering" à la mode en ce moment pour que son agent IA compile, exécute, teste les instructions et le code de son codelab, pour qu'il soit complètement fonctionnel Gain estimé : passer de 2 jours de travail à moins de 2 heures ! Redeploying Claude Fable 5 anthropic.com/news/redeploying-fable-5 Anthropic a annoncé le rétablissement de l'accès à ses modèles Claude Fable 5 et Mythos 5, qui avaient été suspendus suite à des restrictions d'exportation imposées par le gouvernement américain le 12 juin 2026. Cette suspension faisait suite à un rapport d'Amazon démontrant une méthode pour contourner les garde-fous de Fable 5, lui permettant d'identifier et d'exploiter une vulnérabilité logicielle (un jailbreak). Pour y remédier, Anthropic a renforcé ses mécanismes de sécurité en déployant un nouveau classifieur capable de bloquer cette technique spécifique dans plus de 99 % des cas, acceptant en contrepartie une augmentation des faux positifs sur des requêtes bénignes. Face à l'absence de consensus sur l'évaluation des jailbreaks, Anthropic s'associe à Amazon, Microsoft, Google et d'autres partenaires pour développer un standard industriel évaluant la sévérité de ces failles selon quatre critères : gain de capacité, étendue du gain, facilité d'arsenalisation et découvrabilité. L'entreprise s'engage également à approfondir sa collaboration avec le gouvernement américain, notamment via des évaluations pré-déploiement, un partage rapide d'informations sur les failles, et des ressources dédiées à la recherche conjointe sur la sécurité de l'IA. Outillage La réécriture de Bun en Rust et la réaction du créateur de Zig bun.com/blog/bun-in-rust et andrewkelley.me/post/my-thoughts-bun-rust-rewrite.html Bun, le runtime JavaScript et TypeScript écrit à l'origine en Zig, a été entièrement réécrit en Rust pour des raisons de stabilité et de gestion de la mémoire. Cette migration massive d'un demi-million de lignes de code a été bouclée en seulement 11 jours grâce à l'utilisation intensive de Claude Code fonctionnant en parallèle, pour un coût d'API estimé à 165 000 dollars financé par Anthropic. Andrew Kelley, le créateur de Zig, a réagi publiquement en qualifiant l'ancienne base de code de Bun de "slop" remplie de hacks et de fuites mémoire accumulées par une course aux fonctionnalités. Kelley exprime son soulagement face à ce départ, expliquant que les plantages incessants de Bun devenaient un passif réputationnel toxique pour le langage Zig et sa fondation. Le rachat de Bun par Anthropic fin 2025 avait déjà mis fin aux donations financières de Bun envers la Zig Software Foundation, facilitant cette séparation. La nouvelle version Rust de Bun passe désormais la quasi-totalité des tests, réduit la taille du binaire et est déjà déployée de manière transparente en production dans Claude Code. Nouveautés de Git 2.55 github.blog/open-source/git/highlights-from-git-2-55 Support natif de FSMonitor sous Linux via inotify pour accélérer les commandes comme git status sur les grands dépôts Intégration de la compaction incrémentale MIDX (multi-pack index) dans git repack pour optimiser la réécriture des métadonnées Amélioration drastique des performances de génération des bitmaps et des pseudo-merge bitmaps lors des tâches de maintenance Nouvelle commande expérimentale git history fixup pour intégrer facilement des modifications locales dans un commit antérieur Possibilité d'exécuter des hooks configurés en parallèle pour optimiser le temps de build et de validation Utilisation d'un autostash automatique lors d'un git checkout -m en cas de conflit de fusion pour éviter de bloquer l'espace de travail Nouvelle commande git format-rev permettant de formater rapidement des commits reçus via l'entrée standard (stdin) Support du push simultané vers un groupe de remotes configuré Protection contre l'exécution de séquences de contrôle de terminal malveillantes via les flux de progression distants Vidocq, une réimplémentation souveraine et sans dépendance de Jakarta EE et Microprofile vidocq.dev/posts/vidocq-a-sovereign-jakarta-ee-and-microprofile-runtime Lancement de Vidocq : Runtime Java open source complet, compatible Jakarta EE Core Profile et Souveraineté numérique : Projet européen hébergé sur Codeberg, sous licences EUPL 1.2, EPL 2 et GPL 2.0. Standardisation totale : Implémentation fidèle des spécifications (CDI, REST, JSON, etc.), validée par 5 650 tests TCK officiels. Sécurité radicale : Zéro dépendance externe et aucune bibliothèque tierce. Aucune manipulation de bytecode à l'exécution (« magie » générée à la compilation via JDK 25). Compatible JPMS, AOT, GraalVM et Leyden CDS. Disponibilité : Projet en phase alpha, code et documentation accessibles sur vidocq.dev. Article complémentaire qui revient sur la genèse de Vidocq, en utilisant l'IA et les TCKs pour driver l'aspect spec-driven development vidocq.dev/posts/the-story-of-vidocq Le "selfware" : Guillaume s'est fait plais' en vibe-codant son propre éditeur de texte glaforge.dev/posts/…/selfware-building-my-own-text-editor-without-knowing-swift Concept de « Selfware » : création de logiciels conçus exclusivement pour soi-même, sans monétisation ni contraintes liées aux utilisateurs tiers. Le rôle de l'IA : les agents de programmation (comme Antigravity) suppriment la barrière technique de l'apprentissage des langages (Swift, APIs) pour les non-développeurs. Développement minimaliste : privilégier la performance et l'utilité directe (démarrage instantané, interface native) au détriment des fonctionnalités complexes (plugins, télémétrie, gestion de comptes). Absence de pression : libération des contraintes liées à la compatibilité, à la maintenance logicielle et aux retours utilisateurs ; le logiciel n'a besoin d'être « assez bon » que pour ses propres besoins. Incitation à l'autonomie : encourager la création d'outils sur mesure pour résoudre les frictions quotidiennes plutôt que de subir les limitations des logiciels commerciaux. Architecture Le cobol a donné un uppercut au microservices https://freedium-mirror.cfd/@maahisoft20/your-microservices-lost-to-cobol-let-that-sink-in-8ce2e236d007 Retour d'expérience sur la migration d'un système COBOL vers des microservices cloud-native qui s'est soldée par un retour en arrière après avoir constaté que le traitement batch initial était plus rapide, moins cher et plus fiable Là où le batch COBOL traitait 2.4 millions d'enregistrements en 11 minutes, le système distribué modernisé à base de message queues, retries et Kubernetes prenait 47 minutes et tombait sous la charge COBOL brille par ses caractéristiques conçues spécifiquement pour la finance comme le calcul décimal précis sans floating point errors et l'absence totale d'overhead réseau, de conteneurs ou de cold starts Rappel que distribuer un système multiplie les points de défaillance silencieux et complexifie la gestion de la cohérence transactionnelle par rapport à une exécution locale séquentielle Une invitation à se demander si les projets de décomposition en microservices apportent réellement un gain de performance de bout en bout pour l'utilisateur final ou s'ils optimisent seulement le diagramme d'architecture Méthodologies Ma meilleure question d'entretien Spring beaufume.fr/articles/spring-interview Florian beaufumé partage sa question d'entretien favorite pour évaluer des développeurs Spring de niveau intermédiaire à avancé : "Que pouvez-vous me dire sur le paramètre spring.jpa.open-in-view ?". Ce paramètre détermine l'activation du pattern Open Session In View (OSIV) qui, lorsqu'il est à true (la valeur par défaut dans Spring Boot), maintient l'un EntityManager JPA ouvert durant toute la requête HTTP. Si l'OSIV facilite le développement en évitant les fameuses LazyInitializationException lors de la sérialisation des entités en JSON, il pose d'importants problèmes de performance en provoquant des requêtes SQL non maîtrisées (comme le problème du N+1 select) en dehors de la couche service. Maintenir l'OSIV actif augmente également le temps de rétention des connexions au sein du pool de la base de données, limitant la scalabilité de l'application. La recommandation est de désactiver ce comportement en le positionnant à false, et de gérer explicitement le chargement des données requises au sein des transactions (via des DTOs, des requêtes JOIN FETCH ou des Entity Graphs) pour garder le contrôle sur les accès à la base de données. 10 points à retenir du rapport AI Engineering 2026 : The Acceleration Whiplash faros.ai/blog/ai-acceleration-whiplash-takeaways L'IA a franchi un cap et est devenue l'auteur principal du code : le taux d'acceptation du code généré est passé de 20% à 60% dans les équipes étudiées par Faros AI. La vélocité métier est bien réelle, avec une augmentation de 66% des epics livrées et une hausse de 33,7% du throughput des tâches par développeur. Ce volume cache un code churn massif (+861%), ce qui signifie qu'une quantité énorme de code est supprimée ou remplacée peu après avoir été ajoutée. La qualité en aval se dégrade fortement : les bugs par développeur ont augmenté de 54% et le nombre d'incidents par pull request a explosé de 242,7%. Le processus de code review est complètement saturé, entraînant un temps médian de relecture multiplié par cinq et une augmentation de 31,3% des PRs mergées sans aucune revue. Le système repose de plus en plus sur les développeurs seniors qui subissent une "senior engineer tax", devant relire un volume insoutenable de code à l'apparence correcte mais structurellement fragile. Contrairement à certaines hypothèses récentes de DORA, une forte maturité DevOps ne protège pas les entreprises contre cette détérioration ; le "Acceleration Whiplash" frappe de la même manière les équipes très performantes. En résumé, les outils d'IA inondent les pipelines de livraison avec un volume de code pensé pour un rythme machine, alors que les systèmes de vérification reposent toujours sur un rythme de validation humain. Loi, société et organisation Le coût d'une equipe d'engineering qui ne sait plus ce qu'elle fait dans un contexte d'augmentation de coût des coding agents https://freedium-mirror.cfd/@developer_programmer/i-spent-47-000-on-claude-code-in-90-[…]-asked-me-one-question-and-i-couldnt-answer-it-af3b203f81bb Une équipe de 8 ingénieurs a vu sa vélocité de développement exploser en utilisant Claude Code de manière intensive, jusqu'à recevoir une facture d'API salée de 47 213 $ pour seulement trois mois d'utilisation. Face à cette dépense, la question piège du CTO n'était pas sur le montant, mais sur la dépendance : "Si nous arrêtions Claude Code demain, combien de temps faudrait-il pour que notre vélocité revienne à son niveau initial ?". L'auteur s'est rendu compte qu'il était incapable de répondre car son équipe, en particulier les profils juniors, avait commencé à perdre l'habitude de concevoir et d'implémenter des fonctionnalités complexes sans l'aide permanente d'un agent. Le deuxième risque stratégique soulevé est celui de la dépendance tarifaire et du vendor lock-in : si l'outil devient une infrastructure indispensable au quotidien, l'entreprise perd tout pouvoir de négociation face aux augmentations de prix de l'éditeur d'IA. Pour éviter que l'IA ne devienne une béquille qui atrophie les compétences de l'équipe, l'article suggère de poser des limites budgétaires strictes, d'organiser régulièrement des sprints sans IA ("AI-free sprints") et de concevoir des processus de développement portables. Retour de Nicolas Delsaux sur jqwik qui donne une perspective plus complète concernant jqwik, il me semble que vous oubliez (comme tous les gens qui parlent de LLM dans "l'industrie") que l'auteur n'a pas fait ça juste pour faire chier le monde, mais parce que ces outils ont des externalités incroyablement négatives, ce dont l'auteur s'explique dans son blog (blog.johanneslink.net/2026/06/09/the-jqwik-anti-ai-affair) Vous oubliez également de signaler que le ticket (github.com/jqwik-team/jqwik/issues/708) par lequel un utilisateur se plaint de cette fonctionnalité a été écrit par un agent. N'oubliez pas non plus que l'enthousiasme pour ces technologies n'est en fait pas universel, et que ces technologies sont loin d'être inévitables (les gains de vitesse ne sont, d'après circle CI - circleci.com/resources/2026-state-of-software-delivery, pas des gains de productivité ) OkHttp, Okio, Retrofit et SQLDelight rejoignent Commonhaus ! commonhaus.org/activity/315.html La fondation Commonhaus, via une publication de Andres Almiray, annonce l'arrivée de quatre projets majeurs de l'écosystème Java et Kotlin : OkHttp, Okio, Retrofit et SQLDelight. Ces projets, initialement créés chez Square (devenu Block), sont désormais regroupés et gérés sous la bannière lysine.dev au sein de la fondation. Jesse Wilson et Jake Wharton, créateurs et mainteneurs historiques de ces outils, rejoignent Commonhaus en tant que leaders de lysine.dev. Suite à leur départ de Block, ils expliquent avoir choisi Commonhaus pour offrir à leur immense communauté d'utilisateurs un cadre de gouvernance pérenne, stable et digne de confiance. Conférences La liste des conférences provenant de Developers Conferences Agenda/List par Aurélie Vache et contributeurs : 28-30 août 2026 : State of the Map - Champs-sur-Marne (France) 4 septembre 2026 : JUG Summer Camp 2026 - La Rochelle (France) 10-11 septembre 2026 : Nantes Craft - Nantes (France) 17 septembre 2026 : dotAI - Paris (France) 17-18 septembre 2026 : API Platform Conference 2026 - Lille (France) 18 septembre 2026 : WordCamp Bretagne - Rennes (France) 18 septembre 2026 : dotJS - Paris (France) 18 septembre 2026 : WordCamp Bretagne - Rennes (France) 22 septembre 2026 : Salon Data 2026 - Nantes (France) 22-23 septembre 2026 : Agile en Seine & IA 2026 - Paris (France) 24 septembre 2026 : aMP Day Montpellier 2026 - Montpellier (France) 24 septembre 2026 : OWASP AppSec Days France 2026 - Paris (France) 24 septembre 2026 : PlatformCon Paris - Paris (France) 24 septembre 2026 : React Native Connection 2026 - Paris (France) 24-26 septembre 2026 : Paris Web 2026 - Paris (France) 25 septembre 2026 : SAP Inside Track Paris 2026 - Paris (France) 28-29 septembre 2026 : 4th Tech Summit on AI & Robotics - Paris (France) & Online 1 octobre 2026 : WAX 2026 - Marseille (France) 1-2 octobre 2026 : Volcamp - Clermont-Ferrand (France) 2 octobre 2026 : DevFest Perros-Guirec 2026 - Perros-Guirec (France) 5-9 octobre 2026 : Devoxx Belgium - Antwerp (Belgium) 8-9 octobre 2026 : Forum PHP 2026 - Marne-la-Vallée (France) 12 octobre 2026 : Dev With AI - Paris (France) 22-23 octobre 2026 : Agile Tour Bordeaux 2026 - Bordeaux (France) 26 octobre 2026 : Agile Tour Montpellier - Montpellier (France) 27-29 octobre 2026 : Directions EMEA 2026 - Paris (France) 29-30 octobre 2026 : Campus Agile Grenoble - Grenoble (France) 29-30 octobre 2026 : BDX I/O 2026 - Bordeaux (France) 29-30 octobre 2026 : Agile Tour Nantais 2026 - Nantes (France) 29 octobre 2026-1 novembre 2026 : Pycon FR - Biarritz (France) 30 octobre 2026 : Cloud Nord 2026 - Lille (France) 4-5 novembre 2026 : Devoxx Morocco - Casablanca (Morocco) 14-15 novembre 2026 : Capitole du Libre - Toulouse (France) 19 novembre 2026 : DevFest Toulouse 2026 - Toulouse (France) 19 novembre 2026 : Agile Laval 2026 - Laval (France) 19 novembre 2026 : OVHcloud Summit - Paris (France) 19 novembre 2026 : Codeurs en Seine - Rouen (France) 27 novembre 2026 : DevFest Paris 2026 - Paris (France) 1-3 décembre 2026 : Apidays Paris - Paris (France) 2-3 décembre 2026 : Cloud Native AI Summit Europe - Paris (France) 4 décembre 2026 : DevFest Lyon 2026 - Lyon (France) 4 décembre 2026 : DevFest Dijon 2026 - Dijon (France) 9-10 décembre 2026 : OpenSource Expérience - Paris (France) 9-10 décembre 2026 : DevOps REX - Paris (France) 10 décembre 2026 : KCD Provence - Aix-en-Provence (France) 10 décembre 2026 : DevCon 28 : sécurité | post-quantique | hacking édition 2027 - Paris (France) 14-16 janvier 2027 : SnowCamp 2027 - Grenoble (France) 7-9 avril 2027 : Devoxx France 2027 - Paris (France) 3 juin 2027 : Cloud Native Days France 2027 - Paris (France) Nous contacter Pour réagir à cet épisode, venez discuter sur le groupe Google https://groups.google.com/group/lescastcodeurs Contactez-nous via X/twitter https://twitter.com/lescastcodeurs ou Bluesky https://bsky.app/profile/lescastcodeurs.com Faire un crowdcast ou une crowdquestion Soutenez Les Cast Codeurs sur Patreon https://www.patreon.com/LesCastCodeurs Tous les épisodes et toutes les infos sur https://lescastcodeurs.com/

How has new research changed the way we see nutritional health? What role do ultra-processed foods, fibre, gut microbes, inflammation and insulin resistance play in the new paradigm? Why does the gut microbiome affect our mental health? How can simply diversifying the quantity of plants in your diet change health outcomes radically?In this episode we have the complex topic of nutrition to get up to date on. There's been so much research over the last 20 years that has contradicted some of our most deep seated preconceptions about food, so today we clarify science's new take. We discuss the rise of lifestyle medicine as a solution to western health crises; individualised diet; ultra processed foods; fibre; glycemic index issues; the gut microbiome; inflammation; a variety of foods over restrictive diets; how to support the use of new GPL-1 weight loss drugs; and what the nutritional organisation Zoe is doing to make this all easier for the public to put into practice.Fortunately our guest is a master at untangling all this nuance in a way that's so easy for us Joe public to understand - medical scientist and clinical nutritionist, senior lecturer and researcher at Imperial College London and King's College London, Dr. Federica Amati. She's also Head Nutritionalist at ZOE and Head of Nutrition Science at WellFounded Health. She's written 12 scientific papers and 3 books, “EveryBODY should know this”, “Recipes for better menopause”, and her brand new book “The Appetite reset”, which we discuss today.What we discuss: 00:00 Intro06:30 Worldwide pandemic of previously western-only diet related chronic diseases.07:00 Western diet, exported to the rest of the world is a big part of the problem.08:45 Sedentary lifestyle is also part of the metabolic dysfunction crisis.09:15 The “Diabesity” crisis.10:15 Dysfunctional food environments.10:55 One size dos NOT fit all for diet.11:45 Influencers are confusing the public.16:25 Personalised diet issues: more required from the patient, more expensive.18:00 Ultra-processed foods damage 1: quick energy uptake.20:30 U.P.F. damage 2: High palatability - more delicious, harder to stop eating.21:45 U.P.F. damage 3: Synthetic additives - unknown consequences & cocktail effect.23:35 Processed food risk scale from Zoe nutrition can help people consider.24:15 %60 of Uk calories are coming from ultra processed food.30:45 Fibre - How much do we eat and should we eat?32:45 Plant diversity: 30 per week, leads to Intestinal microbe diversity.35:15 Mapping the microbiome. 39:05 Microbiome and mental health - Vagus gut-brain axis, 42:55 Inflammation theory of depression - withdraw from society to heal.43:50 Chronic inflammation caused by western diet and stress.46:45 Your habits are more important than exceptions.48:15 Restrictive calorie-counting diets aren't sustainable for losing weight because of metabolic adaptation.52:05 “The Appetite Reset” book - GLP1 weight loss drugs.56:45 Adult obesity has doubled, adolescent obesity has quadrupled.References:Federica Amati, “The Appetite reset”.Federica Amati, “EveryBODY should know this”.Francesco Asnicar et al.,'Gut micro-organisms associated with health, nutrition and dietary interventions' paper. Zoe Nutrition - microbiome testing, glycemic monitoring, and personalised diet guidance.The microbiome, mental health & rethinking hygiene - Dr. Graham Rook episodeMood Food: The gut, diet and inflammation - Alex Laird episodeNot all U.P.F's are equal - Zoe Nutrition article

Mauro Moretti si costituisce e va in carcere a 17 anni dalla strage di Viareggio: era il 29 giugno del 2009 quando per il deragliamento di un treno e l'esplosione di una cisterna di Gpl morirono 32 persone. L'ex amministratore delegato di Rete Ferroviaria Italiana e Ferrovie dello Stato è stato condannato definitivamente a cinque anni per disastro ferroviario colposo e incendio.

פרק מספר 516 של רברס עם פלטפורמה - קרבורטור מספר 41. הפעם רן ואורי מארחים את נתי לשיחה על נקודת המפגש המרתקת שבין קוד פתוח לקידוד מבוסס סוכנים (Agentic Coding). דיברנו על העתיד הדיסטופי והאופטימי של מפתחי קוד פתוח, איך משווקים מוצרים ל-Agents, ולמה שורת הפקודה (CLI) חוזרת אלינו בענק. [01:04] העתיד המדומיין של AI (סיפורו של OpenClaw) נתי משתף סיפור משעשע על ניסיון לחקור את "OpenClaw". הזיות (Hallucinations) של מודלים: Claude מאשר את העובדות, בעוד ש-Gemini מנתח שמדובר בהמצאה עתידית (פברואר 2026). הבנה שמודלי שפה (LLMs) הם מנועים הסתברותיים ולא מנועי חיפוש עובדתיים. [05:58] החזון הדיסטופי: האם AI יהרוג את הקוד הפתוח? בעיית ההעתקה: בעבר קוד הוגן על ידי רישיונות (כמו AGPL), היום קל לבקש מהמודל לשכתב קוד משפה אחת לאחרת (למשל מ-NodeJS ל-Rust) בעלויות אפסיות. קריסת מודלים עסקיים: עלויות התמיכה והאופרציה (Operation) יורדות כי ה-Agent מתקן תקלות לבד, מה שחותך את ההכנסות של חברות כמו Red Hat. עומס על ה-Maintainers: קוד מג'ונרט על ידי Agents נראה מעולה ומתועד היטב, אבל לא תמיד נכון ארכיטקטונית או לוגית. גישות התמודדות: חלק דורשים לקבל את ה-Prompt (הכוונה) ולא את הקוד עצמו, בעוד שאחרים (כמו יוצר שפת Zig) אוסרים לחלוטין גישה של AI לפרויקט. [15:15] החזון האופטימי: שיווק לסוכנים (GEO) מעבר מ-SEO ל-GEO (Generative Engine Optimization): סוכני AI הם הלקוחות החדשים. איך Agent בוחר כלים? לפי איכות הקוד, הפופולריות שלו ב-GitHub, ובעיקר לפי התיעוד. קוד פתוח הופך לכלי שיווקי קריטי (Open Core) כדי שהסוכנים יוכלו למצוא, להבין ולהמליץ על המוצר. מודלים היברידיים ו-Freemium: מוצרים (כמו Postits) מציעים גישה ללא חומת תשלום (Paywall) בשלבים הראשונים, מה שמאפשר ל-Agents לעבוד איתם בקלות דרך API (Headless SaaS), ואפילו לבצע רכישות בעצמם בהמשך דרך Stripe. [30:29] שובו של ה-CLI ומגבלות ה-MCP הדיבייט סביב MCP (Model Context Protocol): הפרוטוקול כבד, "זולל" טוקנים (Token hungry) עבור הקונטקסט, ודורש תחזוקה של שרתים נוספים. למה Agents כל כך אוהבים CLI (שורת פקודה)? גישה ישירה לאקוסיסטם המקומי והרשאות (כמו Kubernetes או סביבות ענן) בלי לחשוף מפתחות לשירות חיצוני. יכולת לבצע מניפולציות מורכבות בצד הלקוח (Chaining, Grep, Sed) מבלי לשנות קוד ב-Backend, מה שהופך את המודלים לאנשי DevOps מעולים. [36:17] רישיונות קוד פתוח וה"נשמה" של המוצר האתגר באכיפת רישיונות (כמו GPL) בעולם שבו קשה להוכיח על איזה קוד המודל התאמן ואם בוצעה העתקה. הבדל חשוב בטרמינולוגיה: מודלים של "Open Weights" לעומת מודלים שה-Training Data שלהם באמת פתוח. תוכנה כיצירת אומנות מול קומודיטי (Commodity): האם קוד מג'ונרט יכול להחליף את החזון וה"נשמה" (Soul) של מפתחים בולטים? ההשוואה לעולם המוזיקה מדגישה שמשתמשים הולכים אחרי האומן והחזון, לא רק אחרי הקוד היבש. [50:25] רגולציה ומודלי Open Weights אורי מעלה נקודה מעניינת על החסימה של מודל Fable 5 / Mytos 5 (של Anthropic) למשתמשים מחוץ לארה"ב על ידי הממשל האמריקאי. ההשפעה של רגולציה: ה"תקרת זכוכית" הזו עלולה לפגוע בחברות המסחריות האמריקאיות בטווח הקצר, ודווקא לדחוף קדימה מודלים פתוחים (Open Weights) סיניים או אירופאים שאינם כפופים לאותן מגבלות. האזנה נעימה!

This show has been flagged as Clean by the host. 01 Introduction This is a follow up to my 4 part series on simple podcasting. In this episode I will discuss a number of experiments with audio filtering. These experiments were inspired by comments by listeners and by other discussions about audio on HPR. I am not an audio expert, so I am doing this partly in order to learn something, but mainly in order to have a bit of fun. I hope that you find this entertaining as well. In a comment on the first episode a listener mentioned something called Solocast and said that the method bore a resemblance to the method that I was using. Here is his comment -------------------- 02 Comment #3 posted on 2026-04-03 07:49:58 by Reto It reminds me about Solocast Hi Whiskeyjack, I really liked your podcast and the topic. I cannot remember about your last, but the sound quality of this one was good on my mobile speakers :) The concept reminded me about the program from Norrist (another host on HPR), while similar does it have some differences HPR 3496 https://hackerpublicradio.org/eps.php?id=3496 As I am not on the future feed, I look forward to your next episode. Cheers, Reto -------------------- 03 End of comment. I did not recall having heard the episode on Solocast, but this sounded very interesting. Solocast was in HPR episode 3496 and was released by norrist on the 27th of December 2021. I listened to that episode and does indeed use use the same basic concept of recording short segments of audio and combining them later instead of creating one big recording and editing it with an audio editor. 04 The main difference is that the work flow that I described involves a lot of manual steps, while Solocast is a short Python program that automates the entire process of presenting your script, recording the segments, combining the segments, and filtering and normalizing the result. I won't try to describe Solocast in detail, instead I would recommend just listening to HPR episode 3496 to get norrist's explanation directly. -------------------- 05 While I wanted to make sure that I credited norrist with having come up with this concept four years before I did, this won't be the focus of this episode. Instead I will talk about audio filtering and various experiments that I ran on several different methods. 06 While looking at the source code for Solocast I noticed that it used a filtering method that resembled one used by Jivetalk, a podcast production program that caught the attention of one of the HPR community news presenters. This method involves taking a sample of quiet audio where there is no speaking taking place, and then using this as input to a noise reduction filter which is applied to the voice recording. The filter subtracts the quiet sample from the voice audio, which should theoretically remove the ambient noise. 07 I decided to apply this method to a number of different audio test recordings which were recorded under different circumstances using different hardware. In this way I could see if the method worked equally well under all circumstances or if there were some sorts of noise which it was suited to and some sorts that were not. 08 While I was at it, I also picked several other filter methods to see how they worked as well. Potentially, some methods may be better under some conditions while other methods were better suited to others. -------------------- 09 I won't present all of my experiments, as that would be a bit dull to listen to. Instead I will describe each method and then present audio samples which illustrate my conclusions. There are two pieces of audio software involved, both of which were also used in my series on simple podcasting. 10 The first is Sox, spelled s o x , and which is short for Sound Exchange. Sox is a command line program for audio manipulation. Sox is Free Software, released under the GPLv2 or later. The other is FFMPEG, which is also a command line program. FFMPEG is also Free Software, released under the LGPL V 2.1 or later, and GPL v 2 or later. Sox actually uses FFMPEG for certain operations. -------------------- 11 Audio Hardware For recording hardware I used the following. 12 Maxwell Headset The first is a cheap Maxwell headset that has an electrical noise problem. Unfortunately I don't have a model number for this headset. I described this hardware, the noise problems that I had with it, and how I created filters to deal with the noise in my series on simple podcasting. Briefly though, this is a headset that has a build in microphone on a boom which allows the microphone to be positioned close to the mouth. It connects with a USB cable. 13 Borne Earpiece and In-line Microphone This is a set of earplugs that go in your ears and connected by wires and a very small microphone built into a small bulge in the cable. It connects using a 3.5mm jack. The model number seems to be BUD250-BL. 14 XTrike Headset This is a gaming headset similar to the Maxwell headset described above. The model number is GH-510 It uses a USB connection. 15 Yanmai Condenser Microphone This is a microphone that comes with a small tripod stand. The model number is SF-910 It uses a 3.5mm audio jack. -------------------- 16 This is not a review of the hardware. Rather, I was trying to create audio problems so that I could test ways to fix them. Therefore, do not take the above list as a recommendation of what to buy. However, you can see that I am not using any expensive audio hardware. If you want to make an HPR podcast, you do not need professional level hardware. -------------------- 17 Audio Samples The audio samples are as follows 18 Quiet This was recorded in a quiet environment at my desk. This is my normal podcasting environment and represents optimal conditions. The main reason for this method is to see how the various filter methods perform when dealing with the electrical noise from the Maxwell headset. 19 Small fan This is a small USB powered table fan approximately 10 cm in diameter. It was located roughly 40 cm or less to the left of the microphone, although this varies depending on the microphone. 20 Traffic This was along a busy street with traffic noise in the background. -------------------- 21 Filter Methods Sox noisered Filter with Audio Profile This method uses the Sox noisered filter. Here is a brief quote from the Sox documentation on this filter. Quote Reduce noise in the audio signal by profiling and filtering. This effect is moderately effective at removing consistent background noise such as hiss or hum. To use it, first run SoX with the noiseprof effect on a section of audio that ideally would contain silence but in fact contains noise - such sections are typically found at the beginning or the end of a recording. End of quote For these tests I recorded a separate noise profile to go with each test. -------------------- 22 Basic Manual Filter This is a basic high and low pass filter pair based on the work I had done in my previous series on simple podcasting. However, based on the tests that I have done for this episode, I decided to get a bit more aggressive in terms of filtering. I use a high pass filter of 120 Hz, and low pass filter of 8 kHz. The each filter is then applied twice to increase its effect. I also added band reject filters to deal specifically with 50 and 60 Hz line noise. -------------------- 23 Complex Manual Filter This uses the manually constructed filter described in my series on simple podcasting. This uses the basic manual filter plus a series of custom bandreject filters to fix specific noise problems with the Maxwell headset. -------------------- 24 FFMPEG afftdn Filter The documentation describes this as "Denoise audio samples with FFT." -------------------- 25 FFMPEG arnndn Filter The documentation describes this as "Reduce noise from speech using Recurrent Neural Networks." -------------------- 26 FFMPEG agate Filter I will pronounce this as "agate" for convenience. The documentation describes this as "A gate is mainly used to reduce lower parts of a signal. This kind of signal processing reduces disturbing noise between useful signals." -------------------- 27 Method The experimental method used was to take each noise sample and apply the different filter methods to it. Where there are parameters which can be adjusted, a script was used to generate a series of different sample files with different parameter values. Not all possible parameters were experimented with, as the goal is to see which method produces what sorts of results under different circumstances, not to get the best possible result for the samples that I happen to have. The method in each case was as follows 28 Step 1 Convert the audio file to FLAC if it is not already in that format. 29 Step 2 Apply a basic high and low pass filter described previously to each sample. The reason for this basic filtering is that it eliminates at least some undesired noise in a fairly fool proof manner, leaving less for the more advanced filter to deal with. This should allow for a better test of the filter under realistic conditions. 30 Step 3 Apply the noise reduction filter being tested. 31 Step 4 Normalize the filtered sample to 17 LUFS according to the EBU R128 standard. The EBU standard is described in my series on simple podcasting. Normalizing adjusts the audio signal to a desired loudness level. This allows for more more consistent sound levels and allows us to hear the results under realistic conditions. I normalize the audio individually for each sample as different recording hardware requires different amounts of loudness adjustment. This is different from the typical podcast process where normalizing takes place as the very last step in the process, but it was necessary in this case. 32 Step 5 Concatenate selected sample audio files to one another to allow for better review and comparing. -------------------- 33 Results The results are grouped according to the type of noise which is being mitigated. This allows for easier comparison of the effectiveness of each technique under different circumstances. I have only picked a few examples of interest out of the numerous experiments that I conducted. -------------------- 34 Quiet Recording Environment with Maxwell Headset This compares how well the various filtering methods work on the noise induced by the electronics in the Maxwell headset. This electronic noise consisted of a noise spike every 1 kHz. This should be representative of electronic noise caused by problems in recording hardware. 35 Manual Filter The manual filter applied a narrow band reject filter every 1 kHz from 1 kHz to 12 kHz. This completely removed the otherwise audible whine caused by the noise. 36 FFMPEG afftdn This method allows for setting a noise floor and then specifying how much the noise floor should be reduced by. The method is very sensitive to getting the noise floor correct for that recording. Set the floor too low and nothing happens. Set it too high, and some distortion results. However it seemed to be moderately effective, but it would seem to require checking it and possibly adjusting it each time it is used. 37 FFMPEG agate This method allows setting a noise floor and then suppressing all sound which falls below that level. This method is very sensitive to getting the noise floor correct for that recording. If set too low (or quiet), it is ineffective. If set too high (or loud), it distorts words which come after a pause, which would typically be between sentences. 38 When set correctly, it completely removes noise in the silences between sentences. However, the noise is still audible during speech. This is because the noise in this case is a higher frequency than normal speech, and so stands out more. It may not be a significant problem for noise which is closer to the main vocal frequency band. Overall, this method is not suitable for this particular problem. 39 FFMPEG arnndn This method used the standard model. A variety of different noise reduction models are available. I only tested it with one, std.rnnn It does not seem to introduce much distortion in the voice signal even with a high amount of mix parameter. 40 However, it is only slightly effective at removing the whine from the signal, even with a high amount of mix parameter. Overall, this method does not appear to be useful for this sort of noise problem. 41 Sox noisered Filter This was effective in removing noise between words, but noise can be heard while words are being spoken. It was better than agate however. 42 Overall Conclusion for the Maxwell Headset Noise When dealing with narrow noise bands that occur at known frequencies, the manual filter is leagues ahead of any of the other tested alternatives. 43 Sample Audio Here is a sample audio recording showing the best overall results The sample is repeated, first with only basic low and high pass filtering, and then with the manually constructed filtering. In the first sample you should hear a high pitched background whine. In the second sample, the high pitched whine is completely removed. 44 (Audio sample inserted here.) -------------------- 45 Traffic Noise This was recorded using the Borne in-line microphone connected to a mobile phone while walking along beside a busy street. This was in dry cool spring weather, and the road was paved with asphalt. This should be reasonably representative of podcasting while walking outdoors in a noisy environment. 46 Basic Manual Filter This used the basic manual filter with high and low pass filters. This did nothing very useful in this case as the signal was already filtered within those limits by the recording hardware anyway. The low sample rate of 8 kHz in the phone limited the upper frequency to 4 kHz. Recall that the sample rate has to be twice the highest frequency that you want to detect. Overall, this is not suitable for this sort of problem. 47 FFMPEG afftdn With a high noise floor, background noise is reduced, but not eliminated. There was not much distortion in the voice. This is only slightly useful for this sort of problem. 48 FFMPEG agate With a high threshhold, background noise is reduced, but not eliminated. There was some distortion in the voice. The background noise could also be heard when speaking, but because the frequency of the background signal was similar to the louder voice signal, it was not as noticeable as it would have been if the two were very different. This is moderately useful for this sort of problem. It may be more useful in situations where the background noise was not quite as loud. 49 FFMPEG arnndn With high amounts of noise reduction, much of the background noise is suppressed, but there is not a lot of distortion in the voice. The background traffic noise is still present, but is significantly less. This offers only a moderate improvement. 50 Sox noisered Filter With small amounts of noise reduction voice is clear but traffic noise is present as a very significant continuous warbling sound in the background. This is no improvement on the original and in fact could be seen as making it worse. With moderate amounts of noise reduction, traffic noise is mostly gone, but there are still various squeaks present. Voice is noticeably distorted. With large amounts of noise reduction, traffic noise is gone but voice is highly distorted. This is moderately useful for this sort of problem, but requires careful adjustment. 51 FFMPEG arnndn Followed by FFMPEG agate This combined two different filters. First, it used arnndn to suppress the background noise to a lower level without much voice distortion. Then it applied the agate filter to suppress the noise levels between words still further. This used the same amount of mix and threshold as was found to be most effective when each of these filters was used on its own. The background noise is almost completely gone while distortion of the voice signal is low. 52 Overall Conclusion for Traffic Noise The arnndn combined with agate filters was the most successful at suppressing background noise while limiting the amount of voice signal distortion. 53 Sample Audio Here is an audio sample for what I felt to be the best overall results, the arnndn filter combined with the agate filter. First is the original audio with basic filtering. This is followed with the same audio after being passed through the arnndn and agate filters. 54 (Insert arnndn plus agate audio sample here) 55 Another Sample Here is a second audio sample showing the Sox noisered profile based filter. I have included this to show how a profile based filter can make things worse if you are not careful how you use it. This repeats the test audio 4 times. The first is with basic filtering only. The second uses low amounts of noise reduction. The third uses moderate amounts of noise reduction. The fourth uses high amounts of noise reduction. 56 (Insert noisered audio sample here) -------------------- 57 Small Fan Noise with Yanmai Microphone This was recorded using the Yanmai condenser microphone. A small fan was set up behind and to the left of the microphone. This is intended to represent situations where someone may have a fan or air conditioner running in the background due to hot weather, or has a loud computer fan. 58 A condenser microphone was used for this test as they are more prone to picking up unwanted noise. However, for practical recording purposes, this sort of microphone is unsuitable for this type of environment. 59 Basic Manual Filter This used the basic manual filter with high and low pass filters. This did nothing useful as the fan noise was in the same frequency range as the voice signal. This may be of more help in cases where the noise is below the 120 Hz cut off used in the low pass filter. 60 FFMPEG afftdn With high amounts of noise reduction, much of the background noise is suppressed, but there is some distortion in the voice. The background fan noise is still present, but is significantly less. Overall this is moderately effective. 61 FFMPEG agate This was effective in removing noise between words, but noise can be heard while words are being spoken. However, this was a small voice sample and it is possible that more problems could occur. With less fan noise than was in this sample this technique may work much better. 62 FFMPEG arnndn With high amounts of noise reduction, much of the background noise is suppressed, but there is not a lot of distortion in the voice. The background fan noise is still present, but is significantly less. Overall this was fairly effective. 63 Sox noisered Filter With small amounts of noise reduction voice is clear but fan noise is present as a slight warbling sound in the background. With moderate amounts of noise reduction, fan noise is gone, but voice is somewhat distorted. With large amounts of noise reduction, fan noise is gone but voice is very distorted. 64 In general this method is fairly successful at dealing with this sort of problem. However, there is a trade off between background noise and voice quality. Getting that trade off correct takes experiment and judgment for each specific situation. 65 FFMPEG arnndn Followed by FFMPEG agate This combined two different filters. First, it used arnndn to suppress the background noise to a lower level without much voice distortion. Then it applied the agate filter to suppress the noise levels between words still further. This got rid of virtually all of the background noise between words. If you listen carefully however, there is a slight buzzing sound in the voice signal. 66 Overall Conclusion for Fan Noise with Yanmai Microphone. Of the methods tested, the arnndn followed by agate filter seemed to offer the most improvement for the least effort and least voice distortion. The arnndn filter on its own seemed the next most preferable to me despite leaving some fan noise in the background. 67 Audio Sample Here is an audio sample for what I felt to be the best overall results, the arnndn filter combined with the agate filter. First is the original audio with basic filtering. This is followed with the same audio after being passed through the arnndn and agate filters. 68 (Insert audio sample here) -------------------- 69 Small Fan Noise Recorded with Headset The following is an observation rather than a filtering technique. When a recording was made using the Maxwell headset and listened to on the headset later or with speakers, the fan was virtually inaudible. When the same recording was listened to with the XTrike headset, it was barely audible with careful listening and only identifiable as a fan because I knew it was there. 70 In situations where there is ambient noise, the best noise reduction technique is probably to move the microphone as close to your mouth as possible, although not directly in front of it, and reduce the gain if there is a gain adjustment in the microphone. This will work far better than trying to remove the noise later. If you are recording an HPR episode at a desk, then an inexpensive headset with boom mike may do the job just fine with minimal effort and expense. -------------------- 71 Conclusions I have tested three noise scenarios - Electronic noise in the audio hardware at specific frequencies. Recording outdoors with an inline microphone in a noisy traffic environment. A noisy fan creating background noise in an office. My conclusions on these are as follows. 72 Electronic Noise in the Audio Hardware at Specific Frequencies If you can use Audacity or some other means to find the frequencies which are causing the noise, the best solution, assuming you don't just replace the hardware, is to manually construct filters to remove those specific frequencies. This is the safest solution in terms of only doing what you tell it to and not producing unexpected surprises some time down the road when something changed in the environment. 73 If you are looking for a fairly automatic filtering method, the Sox noisered profile based filter seems to work fairly well. There is an equivalent filter in ffmpeg, but I did not include that in my experiments as it is harder to use in a script because it does not use a separate noise profile file. 74 Recording Outdoors with an Inline Microphone in a Noisy Traffic Environment. In this situation, the FFMPEG arnndn combined with agate filters seem to be the most successful. The Sox noisered filter may work, but at the cost of more distortion in the voice than is seen in the other methods. 75 An inherent problem with any profile based noise reduction method is that if the background noise is not constant, which it seldom is in that sort of environment, the profile may not represent the background noise which is present later on in the recording. This risks adding more distortion in the voice as the profile and later environments diverge. 76 However, for this application a different microphone that provided a better recording would appear to be advisable. A solution which brought the microphone much closer to the mouth and so resulted in a better ratio of voice signal compared to background noise would appear to be necessary, after which the question of what sort of noise reduction to use would need to be re-evaluated. 77 A Noisy Fan Creating Background Noise in an Office. The Sox noisered filter and the FFMPEG arnndn, afftdn, and agate methods all work to some degree. However, they all need correct selection of parameters to achieve the proper results. When I compared all four methods side by side, I found the arnndn combined with the agate filter to be preferable in terms of the trade off between background noise reduction and distortion of the voice signal. The arnndn filter on its own seemed the next most preferable to me despite leaving some fan noise in the background. 78 However, that is a subjective judgment of a specific noise sample when recorded using a specific microphone. Keep in mind though that many listeners will not be listening in an idea environment. They may be doing things where background noise is present rather than in a very quiet room and so may find a small amount of background noise in the recording to be less of a problem than distortion in the voice signal which may make some words harder to understand. 79 When I conducted the same experiment recorded with the XTrike headset I found that arnndn seemed to offer no noticeable improvement. This may be because the amount of audible fan noise was far less with the XTrike headset to begin with. In other words, there is no single best solution here, and you may have to be prepared to try different options to see which one works in your situation. The important thing is to avoid making things worse by applying filtering that is not appropriate for that situation. The best method may be to use a recording method that doesn't pick up the fan noise to begin with. This can include just using a gaming headset with boom mic. 80 I have one final observation on this point regarding headsets. The Maxwell headset has a foam cover over the microphone while the XTrike headset does not. There was some slight audible wind buffeting noise picked up by the XTrike headset that was not observed with the Maxwell. This seemed to cause particular problems with the Sox noisered profile based filter, as this noise was irregular and after filtering would show up as a warbling sound. If you use a headset and plan to use it in conjunction with a fan, it may be advisable to apply some sort of wind cover over it. 81 Combining Complex Filters In several cases I found that combining several complex filters offered better results than using any single one on its own. The basic strategy though is to first use a method which is good at reducing undesirable noise without introducing excessive voice distortion. Then apply a different filter which is good at reducing small levels of background noise to an even lower level while affecting the voice signal as little as possible. This uses the relative strengths of different filter types to compensate for the weaknesses of the other. 82 Different combinations of filters were most effective for different types of problems. I did not try all possible combinations however. Perhaps a further exploration of this would be worth doing in a later podcast. -------------------- 83 Case Study - Noise in Another HPR Episode Audio In the comments to my second episode on Simple Podcasting (which is HPR4618) where I discussed basic filtering, a couple of listeners brought up an interesting point. Antoine mentioned "declicking" in a post. -------------------- Vance replied 84 Antoine, thanks for mentioning the click removal capability in Audacity! While I already knew about its noise removal filter, I wasn't aware it also had click removal. It might have helped me for HPR4637, where some sort of electromagnetic signal was picked up by my microphone/recorder, a Zoom H2 (the tapping sound was *not* present in the room where I recorded). While click removal does seem to distort speech when applied to it (though to my ears, it doesn't sound as weird as when noise removal is done with speech), I could have applied the filter only to the pauses, where the "tapping" is most noticeable. I will consider doing this in the event that I'm not able to eliminate the source of interference in the future, which would be the best way to go. -------------------- 85 End of quote. I found this interesting as it sounded like another audio problem that could be experimented with. I found a sample of the episode which had the clicks and cut a copy of that segment out to experiment with. These sounds are a series of clicks, or "ticks" would be another way to describe them, in the quiet part of the audio between sentences or phrases. 86 Next I used Audacity to study the sound spectrum. I found a massive 60 Hz noise spike. However, my speakers won't reproduce sound that low, and filtering this out didn't reduce the clicks. The clicks turned out to be bursts of noise across the 100 to 800 Hz band, which is right where the main vocal band also is. This makes it difficult to filter based on frequency. The most promising approach would seem to be to filter based on sound level. 87 I tried all of the individual audio filter techniques mentioned in the other experiments above. None produced satisfactory results except for agate, which makes quiet audio quieter. This completely suppressed the clicks. However, when applied to the entire episode it also distorted the start of a few sentences which began with single short syllables. 88 The agate filter has a number of parameters which could be adjusted to try to deal with these cases, although I did not spend the time to do so. Another solution to this distortion problem is to simply not apply the filter to those parts of the audio which are affected. If you record the audio as a series of small individual files, it would be easy enough to filter before concatenating the files together while skipping those files which contain audio which is not suited to this method. Here are the results of the experiments. 89 FFMPEG afftdn This reduces the size of of the ticks, but they are still present. However, they may be reduced to a level which is considered acceptable. 90 FFMPEG agate This was very effective in removing ticks with the right parameters. However, it can introduce some voice distortion in the form of cutting out the start of a few sentences which began with single short syllables. This can be corrected with a very short "attack" parameter to turn off the filter when it detects sound above a set threshhold. 91 FFMPEG arnndn This was relatively ineffective. 92 Sox noisered This was effective in removing the sounds between phrases. However, it introduces some distortion in the voice signal. 93 I also tried combining filters. FFMPEG afftdn Followed by agate This combined two different filters. First, it used afftdn to suppress the background noise to a lower level without much voice distortion. Then it applied the agate filter to suppress the noise levels between words still further. This got rid of virtually all of the background noise between words. 94 Here is a short audio sample from HPR4637. First is the unfiltered audio. Second is the filtered audio using the combined afftdn plus agate filters. Since the "clicks" are very quiet, you may not hear them unless you are in quiet environment. Quite a few listeners would probably not be aware of the perceived audio problem in this episode if it had not been discussed here. None the less, it makes for an interesting experiment. Here it is: 95 (Insert sample audio here) 96 Overall Conclusion for Noise "Ticks" The afftdn combined with agate filters seemed to offer the best overall results when used with the right parameters. However, the author, Vance, speaks very clearly and evenly, and so his voice is ideally suited for use with this filter. Another author's voice may not be as suited to this filter. 97 The Sox noisered profile based filter offers various degrees of trade off between suppressing noise and distorting the voice signal. As to whether this is an acceptable trade off depends on the particular voice in question and how easily understood it is under normal circumstances with out additional distortion. The afftdn filter may be a fairly safe filter to use on its own while producing acceptable if not perfect output. -------------------- 98 Overall Conclusions I have presented only a few of the experiments that I conducted. My overall conclusion after all of this is that there is no universal audio filtering method that works best in all circumstances. There are instead a number of tools in the toolbox, and picking the right one for the job takes a bit of trial and error. 99 However, if you have a repeatable recording environment, then once you have decided what tool you need you should create a script for it so you can have a repeatable processing setup. These conclusions apply to voice podcasting. Music has a different set of criteria and techniques that work well with basic voice podcasting may produce poor results when applied to music which has a broader range of frequency and just as importantly, a broad range of loudness. 100 If you are used to using filters and effects in Audacity, many of the settings on those correspond to arguments in the command line version of ffmpeg. It is worth learning how to use ffmpeg directly to automate your recording process. 101 The experiments that I conducted were greatly assisted by writing scripts which created multiple versions of audio files with different settings, thereby allowing me to try many different alternatives relatively easily. It also allowed me to concatenate different audio samples into a single audio file and so listen to different versions in quick succession, making subjective listening judgments more reliable. 102 It is important to keep in mind in all this that I am playing with audio filtering mainly to have fun. It is not necessary to do any of this if you think your podcast episode sounds just fine without it. So, don't let any of what I have talked about in all this discourage you from simply recording a podcast and sending it in as is. I will include copies of the filters I have described here in the show notes. -------------------- 103 Related Matters Hardware Characterization Using Audio Signals I found it useful to characterize the hardware that I had in order to understand its limitations better before starting the experiments. This involved playing a signal out through a set of speakers and then recording it through a microphone. 104 I used two types of signal for this. One is type of signal is known as a "chirp" signal. This is a sine wave that steadily increases in frequency as it sweeps across the audio spectrum. The standard audio range is 20 Hz to 20 kHz, but for my purposes I limited the upper frequency to 15 kHz to save time as anything beyond that is not very useful for voice podcasts. 105 By recording the chirp signal with a microphone and analyzing it with a Fourier transform, I could quickly see what each device was capable of. See my previous series on simple podcasting for an explanation of what a Fourier transform is and what software to use to see the results of it. Here is a chirp signal. 106 (Insert Audio Sample Here) 107 In addition to a chirp signal, I also used a series of simple tones of specific frequencies. By using these tones of known frequency I could gain an understanding of the limitations of my speakers and headphones, and just as importantly, my own ears. By understanding these limitations I was able to narrow the range of frequencies that I need to deal with quite considerably and set the high and low pass filters accordingly. These tones are a series of flac files generated with ffmpeg. 108 Here is a a sample audio tone at a 2 kHz frequency. 109 (Insert Audio Sample Here) 110 Copies of the script to create the chirp signal and the tones are in the show notes. -------------------- 111 A "Not a Review" of some of the Hardware that I Used I said that I would not do a review of the hardware that I used. However, some of it deserves mention for either how good or bad it was. I will record each section using the hardware being described. 112 Maxwell Headset This is my original recording hardware. This is a headset with boom mic and USB connection. There is no model number on it, so I don't know the model. This probably cost somewhere between 10 and 25 dollars. The earpieces sit on the ears and do not fully enclose them. This makes it light weight and comfortable to wear for extended periods of time. It has a problem however with electronic noise consisting of a noise spike every 1 kHz. I was able to fix this with a series of filters using FFMPEG. Fixing this problem is what got me started in understanding audio. I will probably continue to use this headset to make podcasts. 113 XTrike Headset, Model GH-510 This is also a headset with boom mic and USB connection. I purchased this headset for the purposes of experimentation for this podcast episode. It cost $12.88. I found it to be surprisingly good for the price. It has fully enclosed ear pieces however, which may make it uncomfortable to wear in hot weather. I may try doing some of my future podcasting using this headset. 114 Borne Earpiece and In-line Microphone This is a set of earplugs that go in your ears and connected by wires and a very small microphone built into a small bulge in the cable. It connects using a 3.5mm jack. The model number seems to be BUD250-BL. It cost approximately $3.00. I bought several sets of these and use them for listening to podcasts from an MP3 player. The ear pieces are pretty good for listening with. The microphone works reasonably well when used in a quiet location. It is less good when in a noisy environment. It is very important however to secure the microphone to your lapel or other location reasonably near your mouth and to point the microphone (that is the small hole) outwards and not simply let it dangle freely. If you let it just hang, you will get poor quality and inconsistent audio. 115 Yanmai Condenser Microphone, Model SF-910 I purchased this microphone for the purposes of experimentation for this podcast episode. It cost $3.88. As it is a condenser microphone, it is prone to picking up background noise more and as such is probably not a good choice for podcasting by single person sitting at a desk. However, it is none the less a surprisingly good microphone for surprisingly little money. 116 iCan USB Microphone, Model M-306 I purchased this microphone for the purposes of experimentation for this podcast episode. This has a USB connection. This was also relatively inexpensive at $7.99, or roughly twice the price of the Yanmai microphone. Unlike the Yanmai however, it is absolutely wretched. There was such a high degree of distortion when recording through it that I found I could not use it in the fan experiments which I had bought it for. I ended up buying the Yanmai microphone for that instead. -------------------- 117 Easy Effects Software The techniques described so far all involve recording audio files and then processing them later to produce the desired result. This is probably the simplest and most straightforward way of doing things if you are making a typical podcast. However, there may be instances where you want to apply filtering or other effects on the "live" signal immediately and not after the fact. 118 There is audio software which can hook into your computer's audio system and do this with a live signal. For Linux, there is a package called "Easy Effects". This is Free Software and comes under a GPL V3 or later license. I installed it from the Debian repository under Ubuntu 24.04. 119 You can create various filters and even chain them together to combine them. I played with it a bit but do not know enough about it to discuss it seriously at this time. However, I thought it would be worth mentioning for the sake of those who may wish to try it out themselves. -------------------- 120 Episode Conclusion After having had some fun with audio and listening to other HPR members talk about audio, I thought I would have some more fun by playing with noise reduction filters. I have no intention of becoming an audio professional, but by doing some experiments I learned a few things and had some fun doing it. I hope that the rest of you found this interest as well. I will see you all again later in another episode of Hacker Public Radio. -------------------- Scripts Basic Filter This shows basic high and low pass filters ( 120 Hz and 8 kHz respectively) and band reject filters for 50 and 60 Hz. # The high and low pass filters. hlpfil="highpass=f=120, highpass=f=120, lowpass=f=8000, lowpass=f=8000" # Band reject filters filter for 60Hz and another for 50Hz. linefil="bandreject=f=60:width_type=h:w=20, bandreject=f=50:width_type=h:w=20" # Filter using ffmpeg. ffmpeg -i inputfile.flac -af "$hlpfil, $linefil" outputname.flac # ====================================================================== afftdn Filter # noisefloor should be between 20 and 80. noisefloor=$1 # Run the noise reduction. ffmpeg -i testrec-filtered.flac -af "afftdn=nr=10:nf=-""$noisefloor" tmptestrec.flac # ====================================================================== agate Filter # threshold shoud be between 10 and 80. threshold=$1 # Run the noise reduction. ffmpeg -i testrec-filtered.flac -af "agate=threshold=-"$threshold"dB:range=-60dB" tmptestrec.flac # ====================================================================== arnndn Filter # mix should be between 0 and 1. mix=$1 # Run the noise reduction. ffmpeg -i testrec-filtered.flac -af 'arnndn=model=std.rnnn:mix='"$mix" tmptestrec.flac # ====================================================================== sox noisered Filter # Generate the noise profile from a sample of background noise. sox silencefiltered.flac -n noiseprof noise.prof # nramount shoudl be between 0 and 1 sox testrec-filtered.flac noiseout-testrec.flac noisered noise.prof "$nramount" # ====================================================================== Manual Filter for Maxwell Headset Noise # Create a series of band reject filters, from 1 kHz to 11 kHz. ftemplate="bandreject=f=%s000:width_type=h:w=100" kilospikefil=$( seq 1 11 | xargs printf "$ftemplate," ) # Using ffmpeg ffmpeg -i testrec-filtered.flac -af "$kilospikefil" tmptestrec.flac # ====================================================================== Create a "chirp" signal # Start frequency. f0=20 # End frequency. f1=15000 # Duration of signal. duration=10 ffmpeg -f lavfi -i "aevalsrc=sin(2 * PI * (0.5 * ($f1 - $f0)/$duration * t^2 + ($f0 * t))):s=44100:d=$duration" -c:a flac -af "aformat=sample_fmts=s16" chirp.flac # ====================================================================== Generate Audio Tones toneout () { printf -v freqval "%05d" $1 ffmpeg -f lavfi -i "sine=frequency=$freqval:duration=3" tmptone.flac # Normalize ffmpeg -i tmptone.flac -af loudnorm=I=-17:TP=-2.0:LRA=4.0 -ar 44.1k -sample_fmt s16 tone$freqval.flac rm tmptone.flac } # List of frequencies in hertz. freqlist="50 60 100 120 130 140 150 160 170 200 500 1000 2000 3000 4000 5000 6000 7000 8000 9000" for freq in $( echo $freqlist ); do toneout $freq done # ====================================================================== Provide feedback on this episode.

Our 4th annual Coronado Golf Retreat was one for the books — and this episode takes you behind the scenes of one of the most meaningful Golf Party Live experiences we've ever created. This year's retreat had a completely different vibe because everyone stayed together under one roof at our beach house. The connection, laughter, vulnerability, friendships, and community became the true heartbeat of the trip. Because Golf Party Live retreats are about so much more than golf. These retreats are about women putting themselves out there, building confidence, trying new things, making memories, and forming friendships that continue long after the final putt drops. Joining us for this recap episode is retreat attendee Heather Bower, who shares her perspective and experience from the week. Heather is a newer golfer and a wonderful example of the supportive and welcoming environment that makes these retreats so special. In this episode, we recap the entire retreat experience:

We often have well-baked ideas about how we would like things to tunr out, which gets combined with beliefs that are being shaped by the environment we're in. Despite of human nature, we need to follow our intuition and revisit whether or not what we had learned in the past has reached the point where we would benefit from re-evaluating it.In this episode of the My Open Source Experience podcast Rick Sanders talks about how his law career has evolved over time, along with his perception of open source and the GNU General Public License (GPL). GPL is a very controversial open source license, which created some fear and confusion that the tech industry and lawyers in this space have had to overcome.Learn more about:- How your social network affects your career- GNU GPL license- Using copyright against copyright#opensource #community #collaboration #experience #podcast Hosted on Acast. See acast.com/privacy for more information.

Malgré des avancées dans les négociations, la guerre entre l'Iran et les États-Unis plonge toujours le commerce mondial dans la tourmente. L'Inde est l'un des pays qui en subit le plus les conséquences, notamment à travers des difficultés d'approvisionnement en gaz de cuisine. Des perturbations qui ont des conséquences à 13 000 kilomètres de là, en Californie. L'Inde est très dépendante du gaz de pétrole liquéfié (GPL) pour son économie. C'est d'ailleurs le principal combustible utilisé dans la cuisson. Environ 60 % de ce gaz est importé de l'étranger, dont 90 % provenait du Moyen-Orient avant la guerre. Mais avec le blocage du détroit d'Ormuz et les perturbations des chaînes d'approvisionnement, New Delhi a dû revoir sa copie. En mars, pour éviter la pénurie, le gouvernement a publié un décret ordonnant aux raffineurs indiens de maximiser la production de gaz de pétrole liquéfié. Pour augmenter leur production, ces raffineurs n'ont eu d'autre choix que de réduire drastiquement celle d'alkalyte, une sorte de carburant issu d'un procédé chimique complexe, qui aboutit à une essence très pure, dépolluée de plusieurs matières dangereuses, comme le benzène. Reliance Industries, entreprise indienne qui exploite la plus grande raffinerie du monde, fait tourner son unité d'alkylation au strict minimum. Ainsi, d'après le cabinet Kpler, les exportations totales d'alkylates indiennes ont chuté à 33 000 barils par jour. Soit leur plus bas niveau en trois ans. À lire aussiFermetures, rationnements: en Inde, le blocage du détroit d'Ormuz provoque des pénuries de gaz Risque de pénurie en Californie ? Or, à 13 000 kilomètres de là, sur la côte ouest américaine, la Californie est très gourmande en alkylate. C'est un additif très pur, dont la combustion est un peu moins polluante. Il est donc très recherché dans cet État où les normes environnementales sont plus strictes que dans le reste des États-Unis. L'American Fuel & Petrochemical Manufacturers va même plus loin : sans alkylate, la Californie ne peut pas produire son carburant dit « propre ». La Commission de l'énergie de Californie se veut toutefois rassurante : l'État dispose de stocks suffisants et il n'y a pas de pénurie à prévoir. Mais tout de même, la baisse des exportations indiennes signifie moins d'offre, alors que la demande, elle, ne faiblit pas. Résultat : les prix augmentent dans le Golden State. En moyenne, les Californiens paient plus de 6 dollars le gallon (1,36 euro le litre), contre 4,50 dollars le gallon pour la majorité des Américains. À lire aussiPétrole : la crise profitera-t-elle aux producteurs africains?

As the GPL season nears its end, GFA statistician Mo Shaban breaks down the title race and predicts who will ultimately lift the trophy. PLUS: Cristiano Ronaldo finally claims the Saudi Pro League title, celebrating on the pitch with his family!

Nations FC fans vandalize coach Frimpong Manso's car following a home loss to Vision FC. Medeama SC secures its second GPL title in four years; Antoine Semenyo latest & MORE!!!

Parce que… c'est l'épisode 0x2F7! Shameless plug 3 au 5 juin 2026 - SSTIC 2026 24 et 25 juin 2026 - Troopers 26 et 27 juin 2026 - leHACK 19 septembre 2026 - Bsides Montréal 1 au 3 décembre 2026 - Forum INCYBER - Canada 2026 24 et 25 février 2027 - SéQCure 2027 Description Le déclencheur : une attaque publique au WordCamp US En septembre 2024, Matt Mullenweg, fondateur de WordPress et dirigeant d'Automattic, profite de sa présentation de clôture au WordCamp US pour s'en prendre violemment à WP Engine, un hébergeur spécialisé WordPress. Il les qualifie de « cancer pour l'écosystème ». Le ton est d'autant plus choquant que les WordCamp sont des événements communautaires accessibles et abordables, portés par l'esprit de l'open source — le WordCamp Montréal, par exemple, ne coûtait que 50 dollars pour un weekend complet. WP Engine est un acteur majeur qui a bâti tout son modèle d'affaires autour de WordPress, offrant de l'hébergement dédié et ayant acquis plusieurs produits populaires, dont Advanced Custom Fields (ACF), un plugin utilisé par des millions de sites. Mullenweg reproche à WP Engine de générer d'importants revenus grâce à WordPress sans contribuer suffisamment au projet. Il avait d'ailleurs lancé l'initiative « Five for the Future », invitant les entreprises bénéficiant de l'écosystème à y consacrer 5 % de leurs ressources. Or, aucune obligation légale ne contraint quiconque à contribuer, et Mullenweg lui-même tire profit de l'écosystème via Automattic et WordPress.com. L'escalade : actions légales et blocages Trois jours après l'attaque publique, WP Engine réplique par une mise en demeure pour diffamation et extorsion. Le 25 septembre, Mullenweg bloque l'accès des serveurs de WP Engine au dépôt officiel de plugins et thèmes WordPress, empêchant des centaines de milliers de sites clients de recevoir leurs mises à jour, y compris les correctifs de sécurité. WP Engine doit alors développer en urgence des solutions de contournement. Le 30 septembre, la communauté découvre que WordPress.org — la plateforme qui héberge tout l'écosystème open source — appartient personnellement à Matt Mullenweg et non à la fondation WordPress, créée pourtant pour assurer transparence et gouvernance indépendante. Cette révélation amplifie l'inquiétude : une seule personne contrôle l'infrastructure sur laquelle repose près de 40 à 50 % des CMS du web, alors que le deuxième concurrent plafonne sous les 5 %. Le 2 octobre, WP Engine dépose une plainte officielle pour pratiques anticoncurrentielles et abus de pouvoir, rendant publics des échanges compromettants entre Mullenweg et la direction de WP Engine. Le chaos interne et la prise de contrôle d'ACF En parallèle, les employés d'Automattic s'interrogent sur les agissements de leur patron, qui communique de façon impulsive sur les réseaux sociaux et son blogue. Mullenweg pose un ultimatum à ses employés : être avec lui ou partir, avec un délai de 24 à 48 heures. Environ 159 personnes, soit près de 10 % de l'effectif, choisissent de quitter l'entreprise. Mullenweg reprend ensuite le contrôle du plugin ACF au nom de la sécurité de l'écosystème, s'appuyant sur la licence GPL qui régit les extensions déposées sur le dépôt WordPress. Il crée un clone baptisé SCF (Secure Custom Fields) et redirige silencieusement les mises à jour d'ACF vers SCF, de sorte que la plupart des utilisateurs changent de plugin sans même s'en rendre compte. Cette manœuvre soulève de sérieuses questions sur la pérennité de SCF, un produit gratuit sans modèle économique ni équipe dédiée à long terme. Pour les agences comme celle de Maxime, la situation est un casse-tête : faut-il informer les clients, revenir à ACF, attendre ? L'équipe de Maxime décide de redéployer ACF sur les sites concernés, estimant que les clients sont pris en otage dans ce conflit. Les conséquences sur l'écosystème Mullenweg réduit drastiquement les contributions d'Automattic au projet open source, passant de 4 000 heures par semaine à environ 45, provoquant une stagnation du développement. La version 6.8 de WordPress accumule les retards. BlackRock, investisseur dans Automattic, dévalue ses parts. Des développeurs commencent à remettre en question la pertinence de publier sur le dépôt WordPress. Face à cette centralisation problématique, des initiatives émergent pour décentraliser la distribution des extensions. WP Engine rachète WP Packagist et Roots lance WP Packages, offrant des alternatives au dépôt officiel. L'adoption reste cependant un défi majeur pour les utilisateurs non techniques. L'arrivée de EmDash par Cloudflare Le 1er avril 2025, Cloudflare lance EmDash, une solution de gestion de contenu basée sur le framework Astro. Son approche distingue le contenu statique du contenu dynamique grâce au concept d'« îles », offrant de meilleures performances. EmDash isole également les plugins dans des sandbox pour renforcer la sécurité, contrairement à WordPress où un plugin défaillant peut compromettre tout le site. Maxime reconnaît l'intérêt technique de cette solution, mais tempère l'enthousiasme : aucun écosystème de plugins, aucune communauté établie, aucun expert disponible. Cloudflare a les moyens financiers de soutenir le projet, mais il est trop tôt pour y migrer des projets clients. WordPress n'est ni mort ni véritablement menacé à court terme. Perspectives La bataille juridique entre Automattic et WP Engine devrait connaître des avancées en juin 2025. Maxime anticipe une tentative de règlement hors cour de la part de Mullenweg, face à un WP Engine soutenu par un fonds d'investissement de plusieurs milliards déterminé à aller jusqu'au bout. Plus le conflit dure, plus il nuit à l'ensemble de l'écosystème. L'espoir reste qu'un retour à la maturité permette à chacun de poursuivre son activité dans un marché suffisamment vaste pour tous. Collaborateurs Nicolas-Loïc Fortin Maxime Jobin Crédits Montage par Intrasecure inc Locaux virtuels par Riverside.fm

The System76 endorsed "Open Source Exemption" added to Colorado SB26-051 means BSD licensed code would be exempt... but GPL code (like Linux) would still require Age Verification.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

Les références : Circulaire logiciel libre L'administration étudie un poste de travail sous Linux, une circulaire prône l'open source quand « c'est pertinent » Annonces de la DINUM (Direction interministérielle du numérique) Communiqué de la DINUM : Souveraineté numérique : l'État accélère la réduction de ses dépendances extra-européennes Communiqué de l'April : Logiciel libre : La DINUM va-t-elle enclencher un mouvement de fond dans l'État français ? La DINUM largue Windows en faveur de Linux et veut enclencher un mouvement de fond L'Etat réaffirme son intention de réduire ses dépendances numériques La direction du numérique de l'État quitte Windows pour Linux et demande aux ministères de préparer leur plan Commission d'enquête sur les dépendances structurelles et les vulnérabilités systémiques dans le secteur du numérique et les risques pour l'indépendance de la France Le site de la commission d'enquête Vidéo de l'audition de Nicolas Guillou, juge à la Cour pénale internationale Allemange, ODF (Open Document Format) Commniqué de l'April : L'Allemagne impose l'ODF et exclut le format Microsoft : la souveraineté numérique commence par vos fichiers->https://april.org/l-interoperabilite-au-coeur-de-la-politique-d-autonomie-strategique-de-l-allemagne] Allemagne : le format ODF obligatoire dans l'administration L'Allemagne impose l'ODF et exclut le format Microsoft : la souveraineté numérique commence par vos fichiers Sciences non faites en informatique Quand des scientifiques « phosphorent » pour faire de l'informatique autrement Le programme de la conférence « Can We Rigorously and Verifiably Determine How Little the Industry complies with Copyleft Licenses such as GPL ? » Missions Artemis VLC est à bord de la mission Artemis Artemis II : quand un bug Outlook s'invite à bord d'une mission vers la LuneVous pouvez mettre un commentaire pour l'épisode. Et même mettre une note sur 5 étoiles si vous le souhaitez. Il est important pour nous d'avoir vos retours car, contrairement par exemple à une conférence, nous n'avons pas un public en face de nous qui peut réagir. Pour mettre un commentaire ou une note, rendez-vous sur la page dédiée à l'épisode.Aidez-nous à mieux vous connaître et améliorer l'émission en répondant à notre questionnaire (en cinq minutes). Vos réponses à ce questionnaire sont très précieuses pour nous. De votre côté, ce questionnaire est une occasion de nous faire des retours. Pour connaître les nouvelles concernant l'émission (annonce des podcasts, des émissions à venir, ainsi que des bonus et des annonces en avant-première) inscrivez-vous à la lettre d'actus.

In this episode, we kick things off with the joys and perils of being “nerd‑sniped” by new open-source hardware ideas—from sketching a $20 USB Bitcoin miner concept we jokingly dubbed Bitaxe Latte, to unveiling a tiny AC Infinity fan adapter board that lets miners control powerful, quiet duct fans via standard 4‑pin headers. We dive into firmware nuances, like PWM frequency tweaks and RPM reporting workarounds using Mujina, and how open-source collaboration accelerates progress across the stack. We celebrate a big week for solo miners: three blocks found in just a few days (4 blocks as of publishing): CKPool (x2), Public Pool's first hosted-instance block, and Node Runners' pool—while unpacking pool mechanics, coinbase verification protections in AxeOS, and why transparent, GPL-aligned software matters. We also share April roadmaps: HydraPool improvements for password-field difficulty/hashrate hints and better logging; Mujina's push toward a universal Bitmain-chip driver; and LibreBoard v3's power design updates. Rounding out the shop talk, we swap stencil printer and solder paste tips, touch on Ember One v6.1 reliability upgrades, ASIC RS community growth, Telehash/Austin plans, and upcoming appearances in Vegas and Bitcoin Park Nashville—all in service of making Bitcoin mining more open, hackable, and fun.

Con un cessate il fuoco che traballa il governo si prepara a misure straordinarie anche se per ora non scatterà alcuna misura. Il messaggio che filtra dal Governo e che sarà reiterato dalla premier Giorgia Meloni giovedì nell informativa alle Camere al momento è uno: «Lavoriamo per essere pronti a gestire l emergenza, ma senza allarmismi». Perché le scorte di gas sono al 44%, contro una media europea di poco superiore al 20 per cento.Ieri il ministro dell Ambiente e della sicurezza energetica, Gilberto Pichetto Fratin, ha riunito al Mase i tecnici per aggiornare il «Piano di emergenza del sistema italiano del gas naturale» che risale al 2023 (un anno dopo l invasione russa dell Ucraina) e il «Piano di azione preventivo per il sistema italiano del gas», che contemplava tra gli scenari disordini in diverse aree del pianeta, dalla Libia all Azerbaijan fino alla Turchia, ma non in Iran e nel Golfo persico.Alla base del lavoro, che sarà trasmesso a Meloni con il quadro e le previsioni sugli stoccaggi, c è il decalogo stilato il 20 marzo scorso dall Agenzia internazionale per l energia (Iea), Sheltering from oil stocks , che riconosce come la guerra in Medio Oriente scatenata da Stati Uniti e Israele abbia prodotto la più grande interruzione delle forniture nella storia del mercato petrolifero globale, a causa della paralisi della navigazione nello Stretto di Hormuz.Tra le dieci misure raccomandate per reagire allo shock - richiamate dal Commissario Ue all Energia, Dan Jørgensen, nella lettera ai Ventisette inviata a fine marzo - ci sono targhe alterne, smart working, spinta all uso dei mezzi pubblici, car sharing, riduzione di almeno 10 chilometri orari dei limiti di velocità in autostrada (che potrebbe abbattere dal 5 al 10% il consumo , guida efficiente per i veicoli commerciali e per la consegna delle merci, riduzione dell uso del Gpl dal settore dei trasporti. E ancora: evitare i viaggi aerei laddove esistano alternative, passare a soluzioni di cottura elettriche o alternative al gas, dare priorità alla lavorazione delle materie prime petrolifere con maggiori disponibilità di volumi.Nulla di tutto questo, sostengono dall Esecutivo, è per ora alle viste, neppure il ricorso al lavoro agile. Men che mai l ipotesi di un ritorno alla didattica a distanza (Dad) nelle scuole in quest ultimo scorcio di anno scolastico. «Non è contemplata», ha tagliato corto il ministro Giuseppe Valditara. Ma l allarme potrebbe scattare da fine mese, quando lo stop alle forniture annunciato da QatarEnergy per i danni subiti dai missili iraniani all impianto di Ras Laffan potrebbe cominciare a farsi sentire. Per questo, l ipotesi che campeggia in cima alla lista degli interventi più probabili riguarda una razionalizzazione dell uso dei condizionatori in estate: attraverso il taglio di un grado oppure di un ora. Interviene Manuela Perrone, Il Sole 24 ORE.Autotrasporto, allarme sul caro gasolio: ANITA chiede un bonus rafforzato. Le misure non bastanoLa crisi del settore dell autotrasporto torna al centro del dibattito parlamentare. In audizione al Senato, ieri, sul decreto carburanti, le principali associazioni della logistica tra cui ANITA hanno chiesto un rafforzamento immediato delle misure di sostegno, a partire da un credito d imposta più incisivo sul gasolio. Il punto sollevato dalle imprese è chiaro: il prezzo del carburante, ormai stabilmente sopra i due euro al litro, ha già assorbito gli effetti del taglio delle accise, riducendo drasticamente i benefici previsti dal decreto e comprimendo i margini in un settore che già opera con livelli di redditività molto bassi. Secondo ANITA, le misure adottate dal governo, pur intervenendo correttamente sul fronte fiscale, finiscono per ridurre indirettamente il beneficio complessivo riconosciuto alle imprese. La diminuzione delle accise, infatti, abbassa anche la base di calcolo del rimborso spettante agli autotrasportatori, con il risultato che il vantaggio reale si riduce sensibilmente proprio mentre i costi continuano a crescere. A questo si aggiungono tempi di rimborso ancora troppo lunghi e difficoltà persistenti nel trasferire gli aumenti lungo la filiera logistica, dove spesso gli adeguamenti tariffari non vengono riconosciuti con sufficiente rapidità. L associazione propone quindi un intervento più strutturato per questa fase di emergenza, chiedendo l introduzione di un credito d imposta parametrato ai consumi di gasolio pari a 200 euro per mille litri, una misura che garantirebbe la normale gestione del bonus riconosciuto ai Tir che a fronte del taglio delle accise sono passati da 269 euro di credito di imposta per 1000 litri di carburante a soli 69 euro, come spiega Anita. Sul nodo dei rimborsi, poi, per l associazione è necessario emanare subito un atto di indirizzo del Mef rivolto all Agenzia delle dogane per velocizzare il versamento dei benefici alle imprese, così da compensare la perdita di beneficio generata dal taglio delle accise. Le richieste del settore si inseriscono in un quadro in cui il governo è già intervenuto con una serie di misure emergenziali. Il decreto-legge n. 33 del 2026 ha introdotto un credito d imposta straordinario per l autotrasporto, un taglio temporaneo delle accise sui carburanti e un rafforzamento delle attività di controllo sui prezzi, con l obiettivo di contenere gli effetti inflattivi lungo la filiera. A queste misure si è aggiunta una proroga della riduzione delle accise fino all inizio di maggio. Secondo le associazioni, però si tratta di interventi che agiscono nel breve periodo ma che non riescono a compensare un aumento dei costi che sta assumendo carattere strutturale. Il caro gasolio, alimentato dalle tensioni geopolitiche e dall instabilità dei mercati energetici, continua infatti a incidere direttamente sui costi operativi e sulla sostenibilità economica delle imprese. Ne parliamo con Elio Schettino, Vicesegretario Generale ANITA.Apertura su deroga al Patto di stabilitàDopo le chiusure dei giorni scorsi, oggi è arrivata la prima apertura. Non ho mandato" per parlare di evetuali deroghe o meno al patto di stabilità "ma il messaggio di fondo che posso trasmettere qui e che ho potuto trasmettere alla stampa italiana è che la Commissione europea non lascia sprofondare le proprie imprese, la propria industria, abbiamo sempre dimostrato che c'è un margine di flessibilità che si può dare in caso di crisi sistemiche". Lo ha detto il vicepresidente della Commissione Ue Stephane Séjourné, in audizione presso ,le Commissioni Ambiente, Attività produttive e Politiche Ue della Camera e le Commissioni Industria e Politiche Ue del Senato. Ieri in un editoriale sul Sole il professor Piga ha ricordato come l'Italia sia un Paese economicamente immobilizzato, come emerge inequivocabilmente dai dati OCSE, che indicano una crescita dello 0,4% nel 2026, l anno in cui il PNRR dovrebbe dare la sua spinta maggiore, certificando non solo come grazie ad esso si sia evitata la recessione, ma anche come si sia tornati ormai stabilmente alle consuete e ben magre performance sotto la media UE. Nel biennio 2025-26, ci dice infatti l OCSE, l Italia sarà cresciuta metà dell area dell euro, che a sua volta sarà cresciuta metà di Spagna o Stati Uniti, le due sole eccezioni dinamiche del mondo occidentale.Siamo quindi stati "quelli del doppio zero" (spread e crescita ai minimi), come la Germania, mentre avremo potuto essere come la Spagna, con alta crescita economica e debito-PIL in declino, grazie a consumi pubblici fortemente in espansione (non limitandosi invece ad aumentare la sola spesa per la difesa, priva nell'attuale contesto di moltiplicatore in quanto diretta solo verso fornitori esteri).La strada dell'austerità, saldamente mantenuta anche con la legge di bilancio per il 2026, viene oggi messa in dubbio dallo stesso Ministero dell'Economia e delle Finanze che, nonostante abbia spinto a votare in extremis in Europa la riforma "scellerata" del Patto stesso, ne chiede ora un'ennesima sospensione, ricevendo subito dalla Commissione risposta negativa, a chiara testimonianza di quanto anche le istituzioni di Bruxelles soffrano e causino immobilismo.Che fare oggi dunque? Certamente sospendere il Patto, evitando però di sperperare le risorse in mancette a questa o quella lobby elettorale: ci penserebbero quei giovani che vogliono un Paese migliore a riconoscere il trucco e, rivotando, a dire nuovamente no . C è quindi enorme bisogno di garanzie serie che accompagnino una spesa efficace, per mitigare gli effetti della tempesta perfetta attualmente in corso nel mondo: e quindi non solo di quantità ma anche di qualità. Le garanzie stanno sempre dove le abbiamo da anni indicate: in una spending review volta a rassicurare i nostri partner europei sul fatto che, quando spendiamo, spendiamo bene. Senza tagli lineari alla spesa buona, con investimenti immediati in capitale umano, per migliorare la qualità delle nostre stazioni appaltanti, con un eventuale supporto, stile PNRR , della Commissione europea, per garantire la buona qualità degli acquisti pubblici e dei crediti alle imprese. Poi si vedrà chi vincerà le elezioni: ma a questa coalizione spetta oggi, di salvare il Paese, non solo sé stessa. Il commento è di Gustavo Piga, docente politiche economiche università di Roma Tor Vergata, editorialista Sole 24 OreCome si stanno muovendo i mercati dopo l'annuncio di cessate il fuocoIl mercato sta smaltendo un "premio di guerra" dopo l annuncio di un cessate il fuoco tra Stati Uniti e Iran. La reazione è stata immediata: i prezzi del petrolio sono iniziati a scendere, si sono ridotti i timori per l inflazione e, almeno nel breve, è diminuita la probabilità di una crescita trainata dall energia. È quello che gli operatori definiscono un rally di sollievo , più legato alla distensione geopolitica che a un reale cambiamento strutturale del quadro economico. Per capire questa dinamica bisogna guardare a quello che è successo nelle ore precedenti. I mercati hanno vissuto una giornata in altalena, in balia di indiscrezioni, rumors e dichiarazioni , con le Borse prima in rialzo e poi in calo dopo le parole più dure del presidente Donald Trump e le notizie su trattative interrotte. Il petrolio aveva reagito con forza, arrivando a toccare punte fino a oltre 111 dollari al barile per il Brent, mentre il WTI si era spinto ancora più in alto, riflettendo il rischio concreto di un escalation e di uno shock energetico globale. Il nodo centrale era ed è il rischio legato alle rotte energetiche e in particolare allo Stretto di Hormuz.Una possibile escalation avrebbe avuto un impatto consistente sull economia globale, aggravando la crisi energetica e alimentando nuove pressioni inflazionistiche. Non a caso gli scenari delineati dagli analisti andavano da una normalizzazione sotto i 95 dollari in caso di apertura diplomatica, fino a oltre 160 dollari nello scenario peggiore di escalation totale. È proprio questo contesto che spiega il movimento attuale: con il cessate il fuoco, il mercato sta semplicemente scaricando quel premio di guerra che aveva incorporato nei prezzi del greggio nelle fasi più tese. Da qui il calo del petrolio e il rimbalzo dei mercati azionari. Ma il punto, come sottolineano gli analisti, è che non si tratta di una svolta definitiva. Più che una rivalutazione strutturale, è una reazione di breve periodo a una minore tensione geopolitica. Per questo l indicazione che arriva dagli operatori è di non dichiarare ancora vittoria . A fare davvero la differenza nelle prossime settimane non saranno tanto le dichiarazioni politiche, quanto gli indicatori reali: l andamento dei prezzi del greggio, il traffico delle navi cisterna e le condizioni delle principali rotte marittime. In altre parole, i mercati restano estremamente sensibili agli sviluppi geopolitici e pronti a cambiare direzione rapidamente, in un equilibrio ancora fragile. Sentiamo l'analisi di Morya Longo, Il Sole 24 Ore.

Attimi di paura questa mattina a un distributore Beyfin lungo la maranese dove a causa di uno sversamento di Gpl un autista è rimasto ustionato ad una mano.

Le news dal mondo dell'auto e della mobilitàMentre l’auto rimane per gli italiani un bene indispensabile per la gestione della quotidianità, il settore accelera verso la digitalizzazione burocratica con il debutto dello Sportello Online del PRA. Tale innovazione digitale si affianca alla centralità ancora intatta dei concessionari fisici, scelti per una consulenza personalizzata e per la trasparenza che offrono rispetto ai soli canali web. In parallelo, la ricerca di nuove soluzioni energetiche vede protagonista la Repubblica di San Marino che, insieme a BYD, sperimenta infrastrutture di ricarica ultra-rapide. Contestualmente, l'attenzione per l'efficienza termica e le prestazioni dei motori GPL si rinnova grazie alla partnership tra Petronas e DR Automobiles.

So what is the essence of investing in the GPL if not even up to four local players merit call-ups to the national team? - Abdul Salam Yakubu, CEO of New Edubiase

Rassegna stampa economico-finanziaria del 20 Marzo 2026, strutturata per macro-temi e basata sulle principali testate giornalistiche nazionali. Energia e GeopoliticaTestate coinvolte: Corriere della Sera / la Repubblica / Il Messaggero / Avvenire / Sole 24 Ore / La Stampa * Stretto di Hormuz e "Patto a Sette": Italia, Regno Unito, Francia, Germania, Olanda, Giappone e Canada hanno siglato una dichiarazione congiunta per garantire il transito sicuro delle navi mercantili. L'accordo condanna gli attacchi iraniani alle infrastrutture civili e richiede una moratoria immediata sui raid. * Intervento militare: Il ministro Tajani e il ministro Crosetto hanno precisato che non si tratta di una missione di guerra e che l'Italia interverrà solo sotto l'egida ONU e dopo la cessazione delle ostilità. * Impatto sul mercato energetico: Il prezzo del gas ha toccato i 70 €/MWh. Gli attacchi all'impianto di Ras Laffan in Qatar ridurranno la capacità di export di GNL del 17%, con perdite stimate di 20 miliardi di $ annui e tempi di riparazione tra i 3 e i 5 anni. * Variazioni prezzi petrolio: Scarto del 50% tra i prezzi euro-americani e quelli asiatici. Il WTI è quotato a 95 $/barile, il Brent a 107 $, mentre le varietà Oman e Dubai hanno raggiunto rispettivamente 153 $ e 136 $.Fisco e NormativaTestate coinvolte: Corriere della Sera / la Repubblica / Il Sole 24 Ore / La Stampa * Decreto Carburanti e Accise: Il governo ha varato un taglio temporaneo delle accise di 25 centesimi al litro su benzina e diesel e 12 centesimi sul GPL. La misura ha una durata di 20 giorni (scadenza 7 aprile) e un costo stimato di 500 milioni di €. * Controlli di "Mr Prezzi": Solo il 20% dei distributori ha applicato immediatamente lo sconto. Il Garante ha segnalato alla Guardia di Finanza una lista di distributori per mancati adeguamenti e potenziali manovre speculative. * Revisione sistema ETS: Italia e Polonia premono in sede UE per una revisione o sospensione del sistema di scambio delle quote di emissione di CO2 per abbassare i costi dell'energia. In Italia, il sistema ha generato 18 miliardi di € complessivi, ma solo il 9% è stato destinato a politiche ambientali.Investimenti e MercatiTestate coinvolte: Corriere della Sera / la Repubblica / Il Messaggero / Milano Finanza * Andamento Borse: Giornata pesantemente negativa con 420 miliardi di € bruciati sui mercati europei. Milano ha ceduto il 2,32%, Francoforte il 2,82% e Parigi il 2,03%. * Decisioni BCE: Il Consiglio direttivo ha confermato i tassi invariati al 2%. Tuttavia, le previsioni inflattive per il 2026 sono state riviste al rialzo al 2,6% (rispetto all'1,9% precedente), mentre la stima di crescita del PIL è stata tagliata allo 0,9%. I mercati prezzano ora due rialzi entro fine anno. * Rischio Recessione: Eurasia Group stima che la crisi in Medio Oriente potrebbe costare all'Italia 1 punto percentuale di PIL nel 2026, portando potenzialmente il Paese in recessione.Executive Takeaway (Managerial Insight) * Resilienza Operativa e Costi Energetici: L'aumento dei costi del gas (fino a 70 €/MWh) e la riduzione della capacità export del GNL qatariota impongono alle aziende un monitoraggio stretto dei margini e una pianificazione energetica prudenziale per i prossimi 3-5 anni. * Monitoraggio Macroeconomico: La revisione al ribasso della crescita UE (allo 0,9%) e le previsioni di rialzo dei tassi BCE entro giugno suggeriscono cautela nell'esposizione debitoria e una gestione attenta del capitale circolante. * Opportunità nel Settore Turismo: Nonostante la crisi geopolitica, il comparto turistico italiano rimane solido con 11 milioni di italiani in viaggio per Pasqua. La proposta di un "Fondo Europeo per il Turismo" potrebbe aprire nuove linee di finanziamento strutturale. * Stabilità Politica: Nonostante l'esito incerto del referendum e il caso Delmastro, la leadership di governo appare intenzionata a mantenere la barra dritta fino al 2027, garantendo una continuità normativa favorevole agli investimenti a lungo termine. * Focus sulla Sostenibilità Strategica: La discussione sulla revisione degli ETS a Bruxelles indica una possibile transizione verso meccanismi di decarbonizzazione più flessibili e orientati alla tutela della competitività industriale nazionale.

This show has been flagged as Clean by the host. We'll explain why we're doing it, what it is, and cover some useful tools along the way. I've been watching movies recommended to me by my colleagues. As I work for a global company, the recommendations are often “Foreign Language”, which by definition is every movie to someone. It's often difficult to read the subtitles, or they are distracting from the acting. So I thought of converting the subtitles to speech for inclusion as an audio track, to produce a Voice Over or Lectoring audio track. Lectoring aka Voice Over Translations First used is soviet countries to read the news and propaganda from a lectors - the first podcasts ? In Polish, lektor is also used to mean “off-screen reader” or “voice-over artist”. A lektor is a (usually male) reader who provides the Polish voice-over on foreign-language programmes and films where the voice-over translation technique is used. This is the standard localization technique on Polish television and (as an option) on many DVDs; full dubbing is generally reserved for children's material. https://en.wikipedia.org/wiki/Lector#Television Example: Night of the Living Dead To give you an idea of what this sounds like I'm going to play you an example of the out of copyright movie, Night of the Living Dead . In the United States, Night of the Living Dead was mistakenly released into the public domain because the original distributor failed to replace the copyright notice when changing the film's name Original First the original sound track, then the same clip with the voice over track. Voice Over Proof of Concept As a native English speaker I find it difficult to follow those Voice Over tracks as I am trying to focus on the underlying audio. In discussions with Polish friends, it seems that this is not a problem when Polish is your native language. To put that to the test I wanted to try it out on a movie to see if that were indeed the case. I asked on Mastodon for a non English movie that was Creative Commons but did have English Subtitles, and HPR host Windigo had the answer. 2009 Nasty Old People is a 2009 Swedish film directed by Hanna Sköld, Tangram Film. It premiered on 10 October 2009 at Kontrapunkt in Malmö, and on file sharing site The Pirate Bay. The film is available as an authorized and legal download under the Creative Commons license CC BY-NC-SA. So my idea was to take each bit of subtitle text, convert it to audio, then have the generated audio play at the same time the subtitle appears on the screen. We use piper to process shows here on HPR, and we also generate srt, or SubRip subtitle files for each show. SRT or SubRip files are the easiest subtitle file to work with. From https://en.wikipedia.org/wiki/SubRip The SubRip file format is described on the Matroska multimedia container format website as “perhaps the most basic of all subtitle formats.” SubRip (SubRip Text) files are named with the extension .srt , and contain formatted lines of plain text in groups separated by a blank line. Subtitles are numbered sequentially, starting at 1. The timecode format used is hours:minutes:seconds,milliseconds with time units fixed to two zero-padded digits and fractions fixed to three zero-padded digits (00:00:00,000). The comma (,) is used for fractional separator . A numeric counter identifying each sequential subtitle The time that the subtitle should appear on the screen, followed by –> and the time it should disappear Subtitle text itself on one or more lines A blank line containing no text, indicating the end of this subtitle I downloaded the movie from the Internet Archive , and then used Piper voice to convert a minutes worth of subtitles. piper_voice: A fast and local neural text-to-speech engine that embeds espeak-ng for phonemization. GPL-3.0 license Once I had the audio prepared for a sample of the subtitles, it was over to audacity to create a new subtitle audio track. Audacity is the world's most popular audio editing and recording app GPL v2 or later, Timing the segments would be a problem, if it were not for the fact that Audacity supports srt files as Labels. File > Import > Lables. Then select the srt file The subtitle track with the text of the audio will be displayed. I could then Import each Audio segment and line them up with the subtitle track for to get the correct timing. Each subtitles segment created a new separate audio file which I then exported. I then used Kdenlive to open the video and import the audio and subtitle tracks. Kdenlive: is the acronym for KDE Non-Linear Video Editor. It works on Linux, Windows, macOS, and BSD. GPL-3.0-or-later There is a good article on adding by Jean-Marc on How to Add Subtitles Easily in Kdenlive Project > Subtitles > Add Subtitle Track Select the Subtitle file Align the subtitle and audio track. After rendering the segment out I was satisfied that this was something worth doing. The script The script can be found on the episode page for this show on the HPR site, and I put it together as a proof of concept. It creates a new audio track for the subtitles, and merges this with the original sound track to create a new selectable sound track. It begins by creating a length of silent audio that is as long as up to the first subtitle time segment begin timestamp. The first subtitle segment is converted from text to speech using Piper voice That segment of audio is added to the initial silence track. We check the total length so far, and then see if there is supposed to be silence between the last and next subtitle segment begin timestamp. If there is, then a filler piece of silence is added until the next subtitle should appear. If not then the audio for both subtitles play immediately after one another. I was worried that the subtitle audio would then lag behind the on screen dialogue but it works surprisingly well. Even long series of dialogue sort themselves out after a bit. We do this over and over again for each subtitle, right up to the very end of the movie. This new subtitle to speech audio track is then merged back into the media file as a new audio track. 96 00:15:06,240 --> 00:15:10,640 It will be two years before it's this big 97 00:15:12,840 --> 00:15:17,840 But don't you bother. By then I'll be long gone 98 00:15:19,840 --> 00:15:22,400 It was just a question 99 00:15:22,880 --> 00:15:25,480 Porridge? Original First the original sound track, then the same clip with the voice over track. Voice Over Lessons learned Now that I have done this for a lot of movies, there a few tips for getting the best output. The creation of the audio track usually goes well, but you can run into issues with the merging of the new track back into the movie. Preparation The first thing you need is a subtitle file which will be the basis of the voice you will be listening to. It should be good quality so that it matches when the actors speak. It's important to clean up this before you use it, fixing spelling mistakes and removing html that will get rendered. Listening to three hours of “I L Zero ve y Zero u”, or “less than forward slash I, greater than”, or “L am from Lndia” can get a bit tedious. You should also try and get versions that translate the songs as well. Getting a SRT file from the media. As many Subtitles are taken from a DVDs they can often be poor Optical character recognition versions of the bitmap-based streams. So a picture of string “Hello World” rather than the letters. ffmpeg By far the easiest and best way to get the subtitles is to extract it from the movie itself, provided it's a separate track. ffmpeg is a complete, cross-platform solution to record, convert and stream audio and video. LGPL-2.1-or-later, GPL-2.0-or-later https://ffmpeg.org/ ffmpeg -y -hide_banner -loglevel error -txt_format text -i "${this_movie_file}" "${this_srt_file}" Getting a SRT file from the web. If that fails you can try to get the subtitle files from the Internet. https://www.opensubtitles.org Select your language with the highest subtitle rating. You can check the media using the mpv media player. mpv is a media player based on MPlayer and mplayer2. It supports a wide variety of video file formats, audio and video codecs, and subtitle types. GPLv2+, parts under LGPLv2.1+, some optional parts under GPLv3 https://mpv.io/manual/master/ Name the srt file with the same prefix as the movie and mpv will play it. You can also use the --sub-files= option as well. mpv "${this_movie_file}" --sub-files="${this_srt_file}" Scrub through the file to see if the timing is correct. The subtitles can be toggled using the j key. Fixing Timing issues It's very important to get the subtitles to align, otherwise the voices will be out of sync. When the subtitles don't match up, it's usually that they need to have the start offset corrected. ffsubsync will automatically try and adjust the offset of the first subtitle to the first use of speech in a movie. ffsubsync: Language-agnostic automatic synchronization of subtitles with video, so that subtitles are aligned to the correct starting point within the video. MIT license https://github.com/smacke/ffsubsync pip install ffsubsync ffs video.mp4 -i unsynchronized.srt -o synchronized.srt LosslessCut will allow you to quickly remove additional trailers, or ads, at the beginning, so that ffsubsync will have a better chance of working if they are trimmed away. LosslessCut: aims to be the ultimate cross platform FFmpeg GUI for extremely fast and lossless operations on video, audio, subtitle and other related media files. GPL-2.0 license https://github.com/mifi/lossless-cut If that fails to match up the subtitles, you can use mpv keyboard shortcuts , move to the first speech segment an then press the Ctrl+Shift+Left and Ctrl+Shift+Right to adjust subtitle delay so that the next or previous subtitle is displayed. It will also show a number giving the miliseconds the delay is, eg -148416 miliseconds or -148.416 seconds. You can use many tools to adjust the subtitles, and I tried out SRT Offset . srt-offset: A simple command-line tool to offset SRT subtitle files. This tool allows you to adjust the timing of subtitles in SRT files, which can be useful when subtitles are out of sync with the video. MIT license srt-offset -i input.srt -offset -148.416 -o output.srt Manually adding the new subtitle to speech audio track If that presents an issue then you can use avidemux to just add the new audio track. Avidemux: is a free video editor designed for simple cutting, filtering and encoding tasks. GPL V2 Open Avidemux, and select “File > Open”, to select the movie. Then go to “Audio > Select Track” Select the next unselected track and tick “Enabled”, “Add Audio Track” Then pick the new mixed track, in this example .~NastyOldPeople_mixed.mp3 Conclusion I now find it much easier to watch a movie with the voice over track. It gets to a point where I don't even notice it is there and just hear the actors speak in their own language, and I just know what they are saying. Links 2009 Nasty Old People A Spanish voice-over translation avidemux by Jean-Marc on How to Add Subtitles Easily in Kdenlive container format Decimal separator extension ffmpeg ffmpeg on wikipedia ffsubsync GPL-3.0 license GPL v2 or later Kdenlive LGPL-2.1 LosslessCut Matroska MIT license Movie on Archive.org mpv mpv keyboard shortcuts mpv wikipedia Nasty Old People from the Internet Archive Night of the Living Dead Noc żywych trupów | Film grozy | Polski lektor OpenSubtitles opensubtitles.org Optical character recognition Piper voice SRT Offset srt, or SubRip subtitle files SubRip Timecode Voice-over translation Whisper Provide feedback on this episode.

La crisi nello Stretto di Hormuz ha ridotto di oltre il 90% i transiti commerciali e lasciato circa 1.100 navi bloccate nel Golfo Persico. L'area resta strategica perché vi passa una quota rilevante del commercio energetico mondiale: 38% del petrolio via mare, 30% del GPL e 20% del GNL. Per l'Italia il rischio è diretto: nel 2025 oltre il 13% delle importazioni energetiche proviene dal Golfo. Confitarma ha chiesto al Governo il rafforzamento della presenza navale italiana nell'area, anche con unità della Marina Militare, per proteggere navigazione commerciale, marittimi e continuità delle catene logistiche internazionali. Il commento è di Mario Zanetti, Presidente Confitarma e Delegato del Presidente di Confindustria per l'Economia del Mare.Uiv, export vino italiano -3,7% nel 2025, perdita da 300 milioniNel 2025 l'export del vino italiano chiude a 7,78 miliardi di euro, in calo del 3,7% rispetto al 2024, con una perdita di circa 300 milioni e volumi in flessione dell'1,9% a 21 milioni di ettolitri. A pesare soprattutto è il mercato Usa, che arretra del 9,2% (-178 milioni), penalizzato dai dazi e dalla svalutazione del dollaro. L'extra-Ue segna -6,4%, mentre i mercati europei reggono (+0,5%), con Germania stabile e crescita di Francia e Paesi Bassi. Tra le regioni calano Veneto, Toscana e Piemonte; meglio gli spumanti (-2,5%) rispetto ai vini fermi (-4,3%). Per Uiv l'Europa ha contenuto le perdite, ma resta necessario rafforzare il mercato interno e superare ostacoli normativi che pesano sulla competitività. Interviene Lamberto Frescobaldi, presidente Unione italiana vini (Uiv).Energia, Meloni chiede all'UE lo stop temporaneo agli EtsGiorgia Meloni ha chiesto all'Unione europea la sospensione urgente dell'Ets applicato alla produzione elettrica da fonti termiche, almeno finché i prezzi energetici non torneranno ai livelli precedenti alla crisi mediorientale. Secondo la premier il sistema europeo del carbon pricing gonfia artificialmente il prezzo dell'elettricità, incidendo fino a 30 euro per MWh in Italia. Il Governo propone anche una revisione dei costi regolatori sul gas e strumenti di liquidità per stabilizzare il mercato nazionale. Da Bruxelles arriva apertura a interventi temporanei sulle bollette da parte degli Stati membri, mentre la Commissione insiste sull'accelerazione delle rinnovabili e sul rafforzamento dell'autonomia energetica europea. Ne parliamo con Adriana Cerretelli, Il Sole 24 Ore Bruxelles.

Bienvenue à l'écoute d'INNOVATEURS, une nouvelle série de Monde Numérique consacrée à celles et ceux qui font l'innovation. Pour ce premier numéro, je reçois Jean-Baptiste Kempf, co-créateur du logiciel VLC, figure de l'open source, aujourd'hui à l'origine du projet Kyber.PunchlinesRefuser l'argent sur VLC, c'était la bonne chose à faire.L'open source, ça appartient à tout le monde.Innover, c'est déplacer l'état de l'art.La qualité pour innover, c'est ne pas avoir peur.L'IA est un accélérateur, pas un remplaçant.C'est une histoire qui fait désormais partie de la saga française des technologies. Au début des années 2000, des étudiants de l'école Centrale Paris créent VLC, un logiciel capable de lire tous les formats vidéo. Cela deviendra le logiciel français le plus téléchargé au monde, utilisé par des centaines de millions de personnes. Jean-Baptiste Kempf, co-créateur de VLC, raconte cette aventure. Il dévoile l'envers du décor, comment une technologie open source a suscité bien des appétits, et il explique pourquoi il a refusé des offres de rachat mirobolantes. Il raconte aussi ce qui se cache derrière VLC : les cyberattaques, les fausses versions et les tentatives de détournement. Il partage aussi son parcours hors VLC, avec Shadow, Vente Privée, Scaleway et aujourd'hui Kyber, une solution de transmission à très faible latence pour contrôler à distance ordinateurs, robots ou drones, en open source avec une licence commerciale. Enfin, il livre sa vision de l'innovation qui, pour lui, consiste à “déplacer l'état de l'art", à condition de "ne faut pas avoir peur". L'occasion d'évoquer la culture du risque et de l'échec en France. Il se confie également sur son usage de l'IA, un “super stagiaire” pour coder plus vite, qui ne remplace pas l'humain, mais qui pose un vrai défi pour la formation des juniors.Interview : Jean-Baptiste Kempf, co-créateur de VLCComment est né VLC ?VLC n'a pas été conçu comme un produit standard. C'est l'aboutissement de plusieurs projets étudiants à Centrale, liés au réseau du campus. À l'origine, il y avait l'idée de faire transiter un flux vidéo sur le réseau local, et ensuite le projet a été relancé en open source. Il a fallu trois ans pour convaincre l'école de passer en licence GPL, et ça s'est fait le 1er février 2001. Le logiciel “client” s'appelait Vidéolan Client, puis c'est devenu VLC, et la plupart des gens l'utilisent juste comme lecteur vidéo.Pourquoi avoir refusé des offres financières énormes pour VLC ?Parce que cela n'aurait pas été moral. VLC n'est pas à moi, c'est des milliers de personnes qui ont contribué, des générations d'étudiants. On aurait pu faire énormément d'argent avec notre base installée énorme, surtout via la marque et le site web. Mais détruire la confiance, détruire la communauté en deux ans “par calcul”, je ne pouvais pas. Je n'aurais pas pu dormir la nuit. Donc j'ai refusé des sommes à huit chiffres.En quoi consiste ton nouveau projet Kyber ?Kyber, c'est hérité de Shadow, où je suis passé également : c'est l'idée de contrôler des machines à distance, avec de très faibles latences. Ça peut être des ordinateurs puissants avec GPU pour l'IA, du rendu 3D ou du gaming, mais aussi des drones, des robots, des véhicules autonomes qui ne sont pas totalement autonomes. On apporte les briques réseau, l'encodage/décodage vidéo à très faible latence, et la synchronisation de tous les flux : audio, vidéo, capteurs, clavier, souris, gamepad. Et il faut aussi s'adapter aux conditions réseau, sans pouvoir “attendre” comme Netflix : quand tu contrôles un robot, c'est la vraie vie.Qu'est-ce que l'innovation pour toi et quelles qualités faut-il pour innover ?Pour moi, innover, c'est déplacer l'état de l'art : soit en recherche, soit avec des produits vraiment nouveaux. Le problème, c'est quand tout le monde se dit innovant : à la fin, plus personne ne l'est. Et la qualité indispensable, c'est ne pas avoir peur. En France, on a eu un vrai changement culturel : l'échec fait moins peur, beaucoup plus de diplômés veulent aller en start-up qu'avant. Et il faut éviter la monoculture : c'est la diversité qui fait apprendre.Hébergé par Audiomeans. Visitez audiomeans.fr/politique-de-confidentialite pour plus d'informations.

Who's to blame for GPL's problems: referees or club administrators? - Kobby Stonne asks

This show has been flagged as Clean by the host. Offline Translator tools Translate text offline LocalTranslate is an offline translation application that uses Firefox's neural translation models (from the mozilla/firefox-translations-models project) to perform high-quality translations locally on your device. Note: LocalTranslate is not affiliated with The Mozilla Foundation in any way. Links LocalTranslate by Shriram Ravindranathan on flathub.org GPL-3.0 license Source Code Offline Translator - On-device translation of text and images A translator app that performs on-device translation of text and images without sending your data to external servers. Features: On-device translation using Mozilla's translation models Transliteration of non-latin script OCR (Optical Character Recognition) for translating text in images Automatic language detection Image translation overlay that preserves original formatting Support for multiple language pairs No internet required for translation once models are downloaded All translation happens locally Links Offline Translator by David Ventura on F-droid [GNU General Public License v3.0 or later]( https://spdx.org/licenses/GPL-3.0-or-later.html Source Code hpr3315 :: tesseract optical character recognition Provide feedback on this episode.

No décimo oitavo episódio do Hipsters.Talks, PAULO SILVEIRA , CVO do Grupo Alura, conversa com EDUARDO SANTOS , especialista em inteligência artificial na Lopti, sobre O VERDADEIRO SIGNIFICADO DE SOFTWARE LIVRE, a diferença entre free software e open source e POR QUE LLAMA E OUTROS MODELOS NÃO SÃO TÃO “ABERTOS” QUANTO PARECEM. Uma discussão sobre licenças (GPL, MIT, BSD), comunidades brasileiras e o futuro do código aberto na era da IA! Sinta-se à vontade para compartilhar suas perguntas e comentários. Vamos adorar conversar com você!

This week we celebrate the announcement of the new Mozilla CEO, cover the news in that GPL lawsuit that's been slowly making progress, and talk about what's new in OpenZFS. There's an AMD vs NVIDIA GPU showdown, we cover the Linux Foundation's annual report, and Plasma 6.6 is promising some late Christmas presents for us all. For tips, we cover sot for system observation, a quick primer on moving between the desktop and command line, and dog/doge for a better DNS tool. You can find the show notes at https://bit.ly/4b0mImI and Merry Christmas! Host: Jonathan Bennett Co-Hosts: Jeff Massie and Rob Campbell Download or subscribe to Untitled Linux Show at https://twit.tv/shows/untitled-linux-show Join Club TWiT for Ad-Free Podcasts! Support what you love and get ad-free audio and video feeds, a members-only Discord, and exclusive content. Join today: https://twit.tv/clubtwit Club TWiT members can discuss this episode and leave feedback in the Club TWiT Discord.

This week we celebrate the announcement of the new Mozilla CEO, cover the news in that GPL lawsuit that's been slowly making progress, and talk about what's new in OpenZFS. There's an AMD vs NVIDIA GPU showdown, we cover the Linux Foundation's annual report, and Plasma 6.6 is promising some late Christmas presents for us all. For tips, we cover sot for system observation, a quick primer on moving between the desktop and command line, and dog/doge for a better DNS tool. You can find the show notes at https://bit.ly/4b0mImI and Merry Christmas! Host: Jonathan Bennett Co-Hosts: Jeff Massie and Rob Campbell Download or subscribe to Untitled Linux Show at https://twit.tv/shows/untitled-linux-show Join Club TWiT for Ad-Free Podcasts! Support what you love and get ad-free audio and video feeds, a members-only Discord, and exclusive content. Join today: https://twit.tv/clubtwit Club TWiT members can discuss this episode and leave feedback in the Club TWiT Discord.

Podcast: Exploited: The Cyber Truth Episode: When Open Source Gets You Into Hot Water: Copyleft Risk in Embedded SystemsPub date: 2025-12-11Get Podcast Transcript →powered by Listen411 - fast audio-to-text and summarizationOpen source accelerates development in embedded systems, but hidden license obligations can quickly create legal and operational risk. In this episode of Exploited: The Cyber Truth, host Paul Ducklin is joined by RunSafe Security Founder and CEO Joseph M. Saunders and Salim Blume, Director of Security Applications, for a look at how copyleft risk emerges and why compliance in embedded products is more challenging than many teams expect. Salim breaks down how restrictive licenses, such as GPL and AGPL, can force the disclosure of proprietary code, interrupt product shipments, or create exposure long after devices are deployed in the field. Joe shares why accurate SBOMs, automated license checks, and enforcing policy at build time are critical to preventing surprises in downstream products. The discussion also touches on the ongoing Vizio case, where the TV manufacturer faces litigation that could compel public release of source code under the GPL, highlighting how open source obligations can surface years after products hit the market. Together, Paul, Joe, and Salim explore: How copyleft obligations can require source-code disclosureWhy embedded environments complicate license complianceReal-world cases where unnoticed GPL dependencies caused major issues, such as Vizio's GPL lawsuit and Cisco's WRT54G router familyThe growing implications of AGPL for SaaS and connected servicesHow build-time SBOMs and automated controls reduce long-term risk Whether you're building connected devices, managing software supply chain compliance, or protecting proprietary IP, this episode offers practical guidance to reduce copyleft risk before it becomes a costly problem.The podcast and artwork embedded on this page are from RunSafe Security, which is the property of its owner and not affiliated with or endorsed by Listen Notes, Inc.

In this episode, we go deep on the shifting landscape of Bitcoin mining hardware, open-source firmware, and why trustless stacks matter for miners big and small. Fresh off the local Bitcoin++ in Durham, we recap the vibe: a developer-heavy crowd, real collaboration between devs and miners, and our announcement of the Mujina developer preview—an open-source mining firmware now publicly accessible for hands-on testing. We discuss practical demo plans for the HeatPunk Summit, creative power ideas (from inverter gens to EVs like the F-150 Lightning/Cybertruck), and what it takes to stage quiet, controlled mining demos. From secure boot cat-and-mouse games to aftermarket control boards, we unpack why closed firmware is antithetical to Bitcoin's trust-minimized ethos, the history from CGMiner and GPL violations, and how LibriBoard, Hydro Pool, and Start9 packaging can radically reduce friction for at-home and pro operators. We also cover Stratum v2 progress, open-source community wins (Home Assistant integrations, config-first setups), and tangible on-ramps for developers—including free Auradine chips from 256 Foundation for reverse engineering and Bitaxe-based Mujina dev workflows. We close with a candid segment on Freedom Tech, the chilling effects of targeting software developers, and why building and supporting open-source tools is essential for a free society. Resources and links mentioned (non-sponsor): - Mujina developer preview: github.com/256foundation/mujina - 256 Foundation chips request: 256foundation.org (contact form at page bottom) - Hydra Pool (self-hosted pool software) - LibriBoard (open control board initiative) - ESP-Miner and Bitaxe (dev-friendly hardware) - Start9 Office Hours (service packaging) and Hydra Pool packaging efforts - Exergy docs and forum: support.exergyheat.com - Bitcoin++ local edition (Durham), BitDevs communities - Stratum v2 discussions and implementations - Home Assistant miner integrations, Node-RED and shell-script config approaches

An airhacks.fm conversation with Paul Sandoz (@paulsandoz) about: Devoxx conference experiences and Java's evolution over the past decade, energy efficiency studies comparing Java to C/Rust/Ada from 2017, Java performance improvements from Java 8 to Java 25, Code Reflection as manipulation of method bodies versus traditional reflection, tornadovm optimizations for GPU inference achieving 6-10x speedup over CPU, using pointers to keep data on GPUs avoiding transfer overhead, Metal support development for Apple Silicon, relationship between Project Babylon and TornadoVM, HAT project collaboration opportunities, Python's GPU performance through optimized NVIDIA libraries, enterprise challenges with Python in production versus Java's packaging simplicity, BLISS library for NumPy-like operations in Java, DJL.ai for tensor manipulation and Deep Learning, JTaccuino for Jupyter-style notebooks with JavaFX, MCP protocol implementation challenges with poor specification quality, minimal JSON API design philosophy for OpenJDK, cognitive overhead reduction in API design, pattern matching with JSON values, assertion-style API for fail-fast programming, JSON-P versus JSON-B trade-offs in enterprise applications, versioning challenges with data binding approaches, embedded HTTP server use cases for testing and development, JSON-java library as reference implementation, zero-dependency approach becoming more popular, Java 25 instance main methods with automatic java.base imports, zb zero-dependency builder project, marshalling and serialization rethinking in OpenJDK, trusted builds and dependency management in enterprise Java, comparison of Maven/Gradle complexity for simple projects, GPL licensing for OpenJDK code, the java.util.json experiment Paul Sandoz on twitter: @paulsandoz

Episode 71: James Tallarico and Kevin Flasch, Risk Strategies Joining me in the Tokens of Wisdom Studio today are James Tallarico and Kevin Flasch from Risk Strategies to discuss the evolving landscape of insurance in the crypto space. They delve into the differences between insurance brokers and providers, the challenges faced in obtaining adequate coverage for crypto-related businesses, and the importance of tailored insurance policies. The conversation covers essential coverages for fund managers, the evaluation of insurance costs, and common mistakes made by new managers when purchasing insurance.  Key Points From This Episode: Difference between an insurance brokerage and a provider.Insurance for the crypto space was historically inadequate.Risk Strategies created a proprietary GPL policy form for crypto.What are D&O and E&O?What other kinds of insurance should fund managers obtain?Insurance costs are influenced by assets under management (AUM).New fund managers often underinsure or misallocate costs.Understanding policy language is vital to avoid coverage gaps. Disclaimer: This show is for informational purposes only. Nothing presented here constitutes legal, investment or tax advice. The guests that join us share their considerable fund-related wisdom, but everything they share here is their personal opinion and for educational purposes only. On this show, they are speaking for themselves, and not for their employer or any affiliated entity. Tokens of Wisdom is produced by Dave Rothschild, partner at Cole-Frieman & Mallon LLP headquartered in San Francisco, California. For more information, visit https://colefrieman.com/ Links Mentioned in Today's Episode: Dave Rothschild - https://www.linkedin.com/in/davidcrothschild/James Tallarico - https://www.linkedin.com/in/james-tallarico-466290100/Kevin Flasch - https://www.linkedin.com/in/kevin-flasch-749412339/Cole-Frieman & Mallon LLP - https://colefrieman.com/Risk Strategies - https://www.risk-strategies.com/Music by Joe Ginsberg - https://www.instagram.com/thejoeginsbergFor any questions or comments, email: tow@colefrieman.com 

DO THINGS RIGHT! Don't violate open source licenses, give credit where it is due, and, ultimately, help further the community development of software and hardware. That is the goal of Open Source, for everyone to benefit from community development. Since its launch, the  @ElegooOfficial  Centauri and Centauri Carbon have been in violation of GPL v3 open source as they are built on Klipper, however, the source code is not available and Elegoo is not releasing it upon request. A HUGE Thank you to the Filament Sponsor of these streams,  @printedsolid ! Check them out: https://printedsolid.comWant to get some of the UK's fastest, and the first REAL Bamboo printer out there? Check out  @construct3d  https://b.link/Construct3DNeed HIGH END 3D Scanning ANYWHERE in the world?? Check out  @3DMusketeers !! Utilizing over $250k in scanners, projects both big and small they can easily handle! Fully portable, able to bring the gear to you, 3D Musketeers is your one stop shop for all things Physical to Digital and even Digital to Physical. Full Service Art To Part rapid prototyping, product development, and of course, 3D Printing with 3D Musketeers! https://b.link/3DM__________________________________Do you have an idea you want to get off the ground? Reach out to the Making Awesome Podcast through https://3DMusketeers.com/podcast and someone will get you set up to be a guest!

WEDNESDAY HR 2 RRR Trivia - In 1992 this artist signed his 100 million dollar contract. Not settling. Being Happy. Catching feelings Big food is battling GPL-1's

WEDNESDAY HR 2 RRR Trivia - In 1992 this artist signed his 100 million dollar contract. Not settling. Being Happy. Catching feelings Big food is battling GPL-1's See omnystudio.com/listener for privacy information.

Former Gopher Nick Angell along with lawyer and 20+ year GPL'er Eric Brever joined the show to talk about NIL and their new collective, Golden Helmet Collective. With all the craziness with NIL and college hockey happening over the summer, it was a great learning experience to hear from the both of them. Much of the show was NIL related, but we did get in to some off-season hockey talk and things happening at the U.

Una forte esplosione a Roma in un distributore di GPL e benzina ha scatenato un grosso incendio in via dei Gordiani, che ha provocato diversi feriti e generato la diffusione di diossine nell'aria, i cui valori ora sono rientrati nella norma. Le cause dell'incidente dello scorso 4 luglio alla pompa GPL di Roma non sono ancora note, ma potrebbe essersi trattato di un errore umano. Ma com'è possibile che si verifichi un incidente del genere? Quanto sono sicuri i distributori di GPL? E come funziona tecnicamente il rifornimento? In questo video vedremo cos'è il GPL (Gas di Petrolio Liquefatto), qual è la differenza con il gas metano, come funzionano i distributori di GPL, quali sono i suoi sistemi di sicurezza, come vengono ricaricati i serbatoi con le autocisterne e perché un'esplosione è un evento così raro. Prendi parte alla nostra Membership per supportare il nostro progetto Missione Cultura e diventare mecenate di Geopop: https://geopop.it/Muh6X Learn more about your ad choices. Visit megaphone.fm/adchoices

Are you ready to live, celebrate and enjoy your life to the fullest? Tune in as Constance interviews Tracey Howse and learn how to heal your life. Tracey shares how she healed her trauma from the unexpected transition of her Son and healed from breast Cancer and unresolved childhood pain. She reveals how tapping into her Spirituality and attending Healing and Recovery Support Groups that she healed her life. She acknowledges that her inner healing has resulted in the release of 30 pounds. Even though she has been using GPL-1 Medication for 3 years, it was only the release of her inner emotional weight that caused her 30 pound weight loss on the outside. This is an amazing and inspirational episode!

Wes and Scott talk with Chad Whitacre, the newest member of the Syntax team, about all things open source—licenses, controversies, economics, and ethics. Chad breaks down what most people misunderstand, and how companies can support sustainable software development the right way. Show Notes 00:00 Welcome to Syntax! 00:39 Meet Chad Whitacre 03:39 Chad's retro headphones Retrospekt 05:00 Chad's role at Syntax https://syntax.fm/oss Open Path 09:41 What do people get wrong about open source? 11:11 Why is open source so divisive? 13:01 The evolution of open source and free software 17:55 Single vendor vs. community open source 20:22 How do people build businesses off of a GPL license? 24:40 What's the most pure version of open source? 26:55 Fair source licensing explained 30:30 Brought to you by Sentry.io 33:09 Should you be concerned about dependencies in your app in relation to licensing? Fair Source 35:16 What's the most interesting/unusual open source license? Beerware License 40:00 What is Open Source Pledge? Open Source Pledge 45:41 Choosing the right open source license 48:31 Wes' most popular open source project wait 49:39 Interesting open source projects Mercedes-Benz embraces Open Source Porsche Open Source Platform 51:33 Licensing for educational content 53:46 The beauty of open source Plausible 56:12 Scott's various open source projects 56:44 The importance of contributing to open source projects 59:16 Sick Picks + Shameless Plugs Sick Picks Chad: Save The Cat! Shameless Plugs Chad: Coming soon Hit us up on Socials! Syntax: X Instagram Tiktok LinkedIn Threads Wes: X Instagram Tiktok LinkedIn Threads Scott: X Instagram Tiktok LinkedIn Threads Randy: X Instagram YouTube Threads

Feeling exhausted, dealing with brain fog, or noticing unexplained weight gain—even though you're doing all the right things? This episode dives into the surprising root cause behind symptoms often blamed on hormone imbalance or stress. It's something most women overlook, and it could be sabotaging your energy, focus, and sleep. Tune in to uncover what might really be going on beneath the surface—and why your environment could be playing a bigger role than you think.

We have Kernel resignations, A GPL court case of some importance, and Mozilla's potentially broken promise. Curl maintainers have thoughts, Some gaming classics have gone open source, COSMIC has another Alpha, and ROCm probably isn't ready for the 9070. For tips we have Chronic out of MoreUtils, pipewire's pw-loopback for audio looping fun, wall for sending terminal messages, and usbip for spooky USB actions at a distance. You can find the show notes at https://bit.ly/4h3ggLi and we'll see you next time! Host: Jonathan Bennett Co-Hosts: Rob Campbell, Jeff Massie, and Ken McDonald Download or subscribe to Untitled Linux Show at https://twit.tv/shows/untitled-linux-show 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.