Podcasts about Raspberry Pi

This show has been flagged as Clean by the host. -------------------- 01 Introduction This is the second episode in an 8 part series. 02 In the previous episode we discussed the predecessors of PLCs, in particular relay logic. In this episode we will discuss how relay logic came to be expressed in software rather than in actual hardware components. 03 The topics to be covered include * Early computers in industry. * The first PLC. * PC versus PLC - what's in a name. * Who the major brands are. * What does a PLC actually look like. * Machine architecture. * PLC programs. * The scan. * PLC programming languages. * Relative popularity of PLC programming languages versus more conventional computer programming languages. -------------------- 04 Early Computers in Industry Computers came to be used in industry fairly early on. Minicomputers were used in some large industries to control things like electric power plants. For example, the DEC PDP8 was used to control the refuelling machines in CANDU nuclear power plants. These would load and unload fuel from the reactor, which happens continually on a daily basis while the reactor is running. 05 The first microprocessor based computer sold on the commercial market was the MICRAL from France, based on the Intel 8008. It was sold as a cost effective replacement for minicomputers used in industry. It preceded what are generally considered to be the first Personal Computers. So you can see that industry were not reluctant to adopt new technology. 06 However, mini computers were large complex systems that did not fit well into a factory floor. They had particular niches in very large complex integrated systems, but were not suited to controlling many individual machines in a factory that produced things like automobiles or appliances. 07 What was needed was something that would fit into a standard electrical enclosure, withstand the temperatures found in a factory, could stand up to vibration and noise, was tolerant of voltage fluctuations, interfaced directly to sensors and actuators, and could be readily programmed by engineers, technicians, and tradesmen who were familiar with the processes to be controlled, but had little or no experience with computers. 08 This required a complete integrated package covering hardware, software, and product distribution through industrial supply retailers. Something that could meet these criteria is what was needed to become the PLC. -------------------- 09 History Many histories point to a US developer that became Modicon. However, their first hardware was more a proof of concept than a viable commercial product. In fact multiple companies in the US, Europe, and Japan were working on the problem and released comparable products all at around the same time in the early 1970s. 10 The idea preceded the implementation by a number of years. For example, General Motors had asked industrial control equipment suppliers in the mid 1960s for some sort of programmable control device to replace relay logic. This showed potential suppliers that there was a market for this sort of thing, and gave them a clearer idea of what customers were looking for. 11 What made this possible was the development of the first 8 bit microprocessor in that time period, combined with readily available bit slice processors from the minicomputer industry and other components. 12 People knew what to do, the problem was waiting for the development of suitable component hardware. Minicomputers were already being used in industry, but were normally located in control rooms. PLCs were an effort to take that technology out of control rooms and put it on the shop floor. 13 PC Versus PLC - What's in a Name In the early days, these systems were known as either PLC, which means "Programmable Logic Controller", or PC, which means "Programmable Controller". Different vendors favoured different terminology, but both were common. I have a book which was at one time one of the standard reference handbooks for this industry which was published in 1989, and refers to them as Programmable Controllers, or PCs. 14 The term PC was also used to mean "Personal Computer", but that wasn't really a problem in the early days. However, a certain large company decided to call their entry into the personal computer market the "IBM PC", and suddenly "PC" became a generic term for desktop computers. 15 After a long struggle to keep referring to their products as "PCs", even the biggest vendors caved in and gave up the fight and switched to using the "PLC" term. I will therefore use the term "PLC" in this podcast series even when talking about products which were originally called "PCs" at the time they were introduced. 16 Who the Major Brands Are The companies that came to dominate the industry fairly early on were generally companies that already made industrial electrical hardware. These were Siemens Allen Bradley, later known as Rockwell Schneider Mitsubishi Omron 17 These are still the dominant companies in the business, although there are many small brands, particularly at the cheaper end of the market. All of them were suppliers of a wide range of industrial control hardware, such that you could build all or nearly all of the parts of your control system using only their products. 18 Each of these sells an integrated hardware and software package, including development software, that is completely proprietary. If you thought that the mainframe business had a lot of vendor lock-in, you haven't seen the industrial market. -------------------- 19 What Does One of These Things Actually Look Like? At this point you are probably still very confused as to what a PLC actually is. I will attempt to describe one in basic terms by giving an example of one. The smallest and simplest ones are what are termed "shoebox" PLCs. These are basically a rectangular box with a plastic case. 20 Here are the dimensions for a typical low end model, a Mitsubishi FX3U-32M. According to specs in the manual, it is 150mm wide, 90mm high, and 86mm deep. 21 It can be mounted to the panel in an electrical enclosure by snapping it onto what is termed a DIN rail. DIN rails are standard mounting systems which use a strip of metal which is U shaped with a lip at the top of each end of the U. You screw the DIN rail to the electrical panel in the enclosure, and most industrial components such as PLCs, terminal blocks, circuit breakers, and all sorts of other things will simply snap onto it and be ready to wire together. 22 Along the top and bottom of the PLC are terminals to which you can attach wires from the things you want to sense or control in the rest of the machine, such as push buttons, pilot lights, proximity sensors, and valves. 23 Inputs are along the top, and outputs are along the bottom. The FX3U-32M has 16 inputs and 16 outputs. These I/O can be 24 volts DC, or 100 to 120 volts AC, depending on the model. Alternatively it may have small relays for outputs. While AC I/O once predominated, 24VDC became the standard in most industries several decades ago as it interfaced with electronic devices more readily and also allowed for cheaper and more compact wiring. 24 More inputs and outputs can be added by connecting additional I/O modules to the main PLC next to it on the same DIN rail, up to a total of 256 I/O The connection is typically via short ribbon cables which plug into the adjacent module. These I/O modules look like the main PLC, but just add I/O. 25 Inside the PLC are a CPU, memory, and firmware. This model has 64K "steps" of memory, which can be thought of as how many instructions you can have. The program runs in RAM, but you can add a small flash memory device to save the program to. There is a run/stop switch that allows you to start or stop the user program. There is a port that you can use to connect the PLC to a laptop computer with a cable so you can download your program to it. 26 The biggest part of the market for PLCs is for these "shoebox" style. However, there are bigger ones as well which have more I/O, more memory, faster CPUs, etc. These are meant for tasks such as coordinating large assembly lines and things like that. These are what are termed rack systems, where the rack is an empty box which is open at the front and has a backplane bus running along the back. You plug the main CPU into the bus, normally in the leftmost position, and then plug I/O modules into the rack. The I/O modules are tall, thin, fully enclosed boxes with the I/O terminals along the front. 27 You should have a rough idea of their appearance at this stage, so I'll leave the physical description aside for now and go on to the concepts behind how they actually work and what makes them different from something like say a Raspberry Pi. -------------------- 28 Machine Architecture It is not really the hardware which defines the PLC. Rather, it is the software system architecture. Every PLC that I am aware of has a common set of features. 29 Data Table A data table is simply a block of memory which may or may not be subdivided into different parts. All logic, and all, or nearly all, I/O works by writing to and reading from addresses in the data table. 30 I/O Every input and output point maps to a fixed memory address in the PLC. To read the state of an input, you read its memory address. To change the state of an output, you write to its memory address. 31 These digital I/O appear as single bit boolean values. The PLC programming language has instructions which allow single bits to be read or written to directly without have to mask off other bits as you would have to do if you were using a conventional programming language. I have so far only mentioned digital I/O, which are single bit on/off values. 32 Other types of I/O Many PLCs also have other types of I/O such as Analogue I/O, which represent variable voltages rather than just on/off values. For example you may wish to read a temperature from a thermocouple where the voltage level varies with the temperature. Often these are mapped into the data table as byte or word values. 33 Internal Bit or Boolean Memory There will be a range of single bit or boolean memory which is used for internal logic state. Your program may need to come up with a series of intermediate logical values, and you store them in these internal bits or flags. 34 Timers and Counters Control of machinery often involves timing and counting. Timer and counters are mapped into the data table. Timer and counter presets and values can be read as words, and there will be bit addresses which indicate the status of the timer or counter, such as whether it has reached its preset and is "done". 35 Integer and Floating Point Values There will be word addresses where integer and floating point words can be stored. If you need to do some mathematical calculations and store the results, you would save them in an integer or floating point word. 36 Typed Memory Unlike when programming something like a PC where you simply have a range of undifferentiated bytes and it is up to your software to impose meaning on it, PLC data table memory has defined types and meanings and the system firmware enforces the correct memory access methods. 37 Size of Data Table Data tables vary greatly in size. A bigger data table allows for bigger and more complex program. Generally, new PLCs will have bigger data tables than older ones, and more expensive PLCs will have bigger data tables than cheaper ones of the same generation. 38 Example Having picked a current PLC as an example for physical dimensions, I will pick an old and obsolete one for an example of a data table. The Siemens S5-100 series was a small PLC that came in several sizes. The basic S5-100 had the following data table size. 39 Digital I/O had a maximum of 128 inputs and outputs taken together. Analogue inputs and outputs had a maximum of 8 taken together. Flag, or bit, memory was 1024 Timers - 16 Counters - 16 40 The S5-103 offered more of everything in the same basic package, but of course at a higher cost. Digital I/O had a maximum of 256 inputs and outputs taken together. Analogue inputs and outputs had a maximum of 32 taken together. Flag, or bit, memory was 2048 Timers - 128 Counters - 128 -------------------- 41 The PLC Program A PLC will come with what amounts to an operating system and virtual machine built into it. You as the programmer use the vendor's proprietary development software, what is generally called the "PLC programming software" to write an application for it. 42 You then connect your PC to the PLC using a cable of some sort, and download your program into it. The program gets stored in the PLC's RAM. There may be flash memory which serves to back up the RAM when the power is off so you don't lose the program. Before flash was available, a battery was typically required to hold the static RAM memory. 43 There is just one program in the PLC. There is no file system, just the program memory and the data table. When the PLC starts up, it runs the program that you wrote. It continues running the program until you turn off the power or you set the run/stop switch to the stop position. 44 I will come back to programming later, but we needed to cover these basic points before I could describe some further concepts we need to cover. -------------------- 45 The Scan A key thing to understand about PLCs is the "scan" concept. This works as follows. There is a repeated cycle called the scan. 46 First, the PLC reads all the physical inputs and updates the corresponding input addresses in the data table. Next it runs the user program once. Finally it reads the output addresses in the data table and writes them to the corresponding physical outputs. Then it repeats the scan from step 1. 47 A scan can take anywhere from a few milliseconds to hundreds of milliseconds, depending on the model of PLC. Older PLCs and cheaper PLCs tended to be slower. However, as integrated circuit technology advanced, programs got faster. 48 The PLC has a watchdog timer. This is a timer which runs in the background and resets at the start of a scan. 49 If a scan takes too long, the watchdog will trip and stop the program and set the outputs to some defined state, either turning them all off or holding them at the last value. This is known as "faulting" the processor. 50 A watchdog fault may be caused by a program that is too long, or uses a lot of very slow instructions, or in some cases it may be due to a bug in your program. However, this last cause is not as common or as easy to cause as you may think when it comes to faults. -------------------- 51 PLC Programming Languages The key to all of this is the unique way in which the programming languages used in PLCs work. I will first briefly describe the two main programming languages and then explain how they work in a PLC as part of a complete system. 52 Ladder Logic There are several programming languages, but the main one is called ladder logic. If you listened to the previous episode, the word "ladder" will ring a bell. When machines were controlled by electromechanical relays, the electrical drawings which specified and documented the types of relays and the connections between them were called "ladder diagrams". 53 PLCs simply take these ladder diagrams and reproduce them on your computer screen in the programming software using the same standard schematic symbols. 54 You do not need to draw the symbols like it was CAD. Instead you simply use your keyboard or mouse to say that you want this symbol to be entered in the current cursor location or you want this wire to be connected from here to there. When your rung is complete the software will check at some point if it is syntactically correct. You then go on to entering the next rungs one after another until you have your complete program. 55 Instruction List An alternative representation is something called "instruction list", although various vendors may use other terms. This is a text representation that looks like a sort of assembly language. However, it's actually really ladder, just shown in a different way as text and some types of programming software will allow you to toggle between ladder and instruction list mode, translating between them automatically. 56 This should give you a clue as to how a PLC can execute a schematic diagram. Behind the scenes the programming software will translate the diagram into instruction list, and then the PLC will either execute those instructions in an interpreter, or compile them to machine code and execute those. 57 Other Programming Languages There are other programming languages, but they are rarely seen. I won't go into detail in terms of describing them, just briefly mention them. 58 One is called Sequential Function Chart. This is a type of flow chart which is designed to show complex sequences, including ones with alternate or parallel paths. The original name for this is Grafcet, spelled G R A F C E T. This stands for "Graphe Fonctionnel de Commande Étape Transition". As well as being a programming language, it is also a very good design and analysis tool even if the PLC being used doesn't support it. 59 Another is Function Block Diagram. This is another graphical language which resembles flow diagrams used in process industries. This is supposedly used mainly in industries such as chemical manufacturing. However it appears to be very niche and most people who use PLCs will never have seen it, and many will not have even heard of it. 60 Yet another language is Structured Text. This is very obviously derived from Modula-2 and strongly resembles it. If you are not familiar with Modula-2, it was created by Nikolas Wirth and intended as the successor to Pascal, which it was derived from. Structured Text seems to be much loved by a small number of academics, but seems to have little actual use in the field. You lose pretty much all of the monitoring and debugging facilities built into a PLC if you use it, so it's kind of pointless except perhaps for a few niche applications. There are a few other languages as well, mainly proprietary ones, often using flow charts or the like. 61 PLC Languages are Non-Blocking The important thing about a PLC program is that it executes from top to bottom, left to right, without stopping or blocking. There is no waiting on input or output or for a system call to return. Each rung immediately yields a result which is written to a memory address or which enables a timer or counter. Every rung is executed every scan. 62 You can reproduce this in a traditional computer programming language. In ladder logic it is inherent to the syntax and it is either very difficult or impossible to do it any other way. I'll give an example in Python of what I mean. 63 a = (b or c) and not d 64 If b or c are true and d is false, then a is set to true. If b and c are false or d is true, then a is false. 65 Now imagine that we are not executing this statement once, but rather are executing it repeatedly. This statement will never block execution. It will always immediately yield a result. Now let's modify that a bit. 66 a = (b or a) and not d 67 Note that we have replaced c with a. Now the value of a depends the previous value of a as well as b and d. However, once a becomes true, the value of b no longer matters because b is in an or condition with a. Now if we execute it over and over again, only d becoming true will make a go false. 68 This is a standard push button circuit, also known as a "seal in circuit", because it "seals" around the start condition. 69 b is the start push button with a normally open contact. d is the stop push button with a normally closed contact. a is a relay with one of its contacts being used to hold it on. 70 If you wired this up with actual push buttons and relays or if you programmed it into a PLC with ladder logic it would work the same way. A PLC program will consists of rung after rung of logic like this and executes it repeatedly scan after scan, only pausing to update its I/O. 71 Async Programming Some of you may be thinking that this cyclical scan sounds like the async programming that is all the rage with web server applications these days. Essentially it is exactly the same principle. 72 With async programming, your program must never use blocking instructions and execution proceeds on a repeated cycle. PLCs solve this by not having any instructions which block, and many PLCs do not allow backwards jumps. Tradesmen in coveralls in factories were doing async programming decades before the cool kids heard about it. 73 Most PLC Programming Languages are Visual or Graphical Languages If ladder, Sequential Function Chart, or Grafcet and Function Block Diagram sound like visual programming languages, they are. In fact ladder is probably one of the earliest visual languages in commercial use. Wikipedia defines a visual programming language as: 74 In computing, a visual programming language (visual programming system, VPL, or, VPS), also known as diagrammatic programming, graphical programming or block coding, is a programming language that lets users create programs by manipulating program elements graphically rather than by specifying them textually. A VPL allows programming with visual expressions, spatial arrangements of text and graphic symbols, used either as elements of syntax or secondary notation. For example, many VPLs are based on the idea of "boxes and arrows", where boxes or other screen objects are treated as entities, connected by arrows, lines or arcs which represent relations. VPLs are generally the basis of low-code development platforms. Scratch is an example of a VPL 75 End of quote. As you can see, what is cool today was on the factory floor more than 40 years ago. -------------------- 76 Popularity of PLC Programming Languages PLCs are about as proprietary as you can get. Pretty much every vendor has his own proprietary take on each language. How you can program any particular PLC is determined by that vendor's programming software. If the vendor doesn't support it, you can't use it. An individual vendor may even have multiple incompatible product lines which have to be programmed in different ways with different software, although that is not as common these days as it once was. 77 Nearly all PLCs support programming in Ladder. Some support programming in instruction list as well as ladder. Anything else is much less common. 78 Ladder logic happens to be on the Tiobe Index by the way. For those who have not heard of it, the Tiobe Index, that is T I O B E, is a web site that lists the popularity of numerous programming languages based on various criteria. 79 Number one on their list happens to be Python, currently at 19.98%. Number two is C, at 11.55%. 80 At the time of writing this script, Ladder Logic was at number 46 with a 0.28% rating, which put it just below Erlang and just above Haskell. I'm not sure whether that means that Ladder Logic is not as obscure as you thought it was, or whether it means that Erlang and Haskell are in fact more obscure than you thought they were. -------------------- 81 Episode Summary In this episode we covered we covered The early history of computers in industrial control The early history of PLCs, including how they got their name Who the major brands are What they look like physically 82 A basic description of the abstract machine architecture A very brief look at what a PLC program is like The scan concept The main PLC programming languages The minor PLC programming languages The relative popularity of each of the programming languages 83 In the next episode we will take a look at one of the early PLCs from the era when they began seeing widespread use. This PLC was hugely successful and was for many companies the first PLC they used. This is the Allen Bradley PLC2. 84 This has been the second episode in an 8 part series. -------------------- Provide feedback on this episode.

Cerramos la octava temporada con un episodio que me apetecía grabar desde hace meses. Igual te ha pasado como a mí: empecé hablando de un laboratorio de IA para cualquiera, y terminé recomendando GPUs de 3000 euros. Me fui creciendo, pero no hace falta. Te cuento cómo montar un laboratorio de IA local con el equipo que ya tienes. Da igual si tienes 8 GB de RAM o 16, CPU modesta o sin GPU. La clave está en elegir los modelos adecuados. Muchas veces nos perdemos buscando el modelo más grande, cuando con uno pequeño y bien cuantizado tenemos de sobra para el 80% de las tareas.Te hablo de Ollama, el gestor de modelos estándar para ejecutar modelos locales. Más de 180.000 estrellas en GitHub, API compatible con OpenAI, modelos para todos los presupuestos: desde Phi 3.5 con 3.8B parámetros hasta Qwen 1.5B que ocupa 1 GB. También la cuantización: reduces la precisión numérica de los pesos para que ocupen menos y vayan más rápido. El punto dulce es Q4_K_M, que reduce el tamaño a menos de un tercio. Para 8 GB de RAM, Q3_K_S puede ser tu salvación.También te hablo de Open WebUI, la interfaz que le da mil vueltas a ChatGPT. No solo chateas: tiene RAG local, Whisper integrado para transcribir voz (75 MB en CPU), TTS con Kokoro-82M para que el modelo te hable en tiempo real, búsqueda web, plugins y memoria persistente. Todo en un contenedor Docker que levantas con un solo comando.Y de SQLite Vec, extensión de SQLite sponsorizada por Mozilla para búsqueda semántica sin servidores vectoriales. Ni ChromaDB, ni Qdrant, ni Milvus. C puro que funciona hasta en Raspberry Pi. Creas tablas virtuales para vectores de 768 dimensiones, generas embeddings con nomic-embed-text, y buscas por similitud coseno en milisegundos. RAG local sin complicaciones.Y te explico cómo organizarlo todo con Docker o Podman. Un docker-compose.yml que levanta Ollama y Open WebUI en segundos, con healthchecks, redes separadas y volúmenes persistentes. También a limitar recursos con --memory y --cpus. He preparado scripts: inicialización que comprueba requisitos, crea directorios y descarga modelos; otro para descargar por niveles según tu hardware (nivel 1 para 8 GB, nivel 2 para 16 GB, nivel 3 para 32 GB); y uno de respaldo.Y la estrategia híbrida local + nube, que es lo que realmente tiene sentido. El enfoque Minions del Stanford Hazy Research Lab: el modelo local hace el trabajo pesado, y solo consulta al grande en la nube para tareas complejas. El 90% de las consultas se resuelven localmente. Ahorras dinero, mantienes privacidad de tus datos, y cuando necesitas potencia, la tienes.Con 16 GB de RAM y un SSD te sobra para el 80% de las tareas: traducciones, resúmenes, código, asistentes, RAG, transcripción de audio, texto a voz... Todo en tu máquina, sin enviar datos a servidores, sin suscripciones, sin depender de internet. Con 8 GB también puedes, con modelos más pequeños. Cerramos temporada, la novena arranca en el episodio 828. Capítulos del episodio:0:00 - Introducción — cierre de temporada 8 y replanteamiento2:30 - Hardware mínimo: 8-16 GB RAM + SSD obligatorio5:00 - Software base: instalar Ollama en tu distribución7:30 - Contenedores: Docker vs Podman para el laboratorio10:00 - Modelos pequeños: Phi 3.5, Qwen 1.5B y cuantización13:00 - Herramientas complementarias: SQLite Vec, Whisper, TTS16:00 - Organización del laboratorio: script y estructura de directorios19:00 - Demo: probando Ollama en local con modelos ligeros22:00 - Combinación local + nube: lo mejor de ambos mundos24:30 - Cierre, avance temporada 9 y despedidaMás información y enlaces en las notas del episodio

Jon Westfall and I welcomed back Sven Johannsen for episode 624 to a number of personal hardware updates. Sven shared his hands-on review of a pair of affordable RayNeo Air 4 Pro AR glasses that provide a 120-inch head-mounted virtual display but require external power and computing. Since it lacks internal batteries, the glasses relies on a connected device like an iPhone or a $100 portable "pocket TV" accessory that runs Google TV. Meanwhile, I shared my latest workaround for my beloved MacBook Neo: a bioluminescent keyboard skin that glows in the dark without drawing power, which helps make the non-backlit keys visible in low-light environments. I also whined (uh, noted) 101 hours and 2 minutes of power outages across 16 incidents this year—falling far below the "five nines" reliability standard. To lobby state legislators about local infrastructure, I've been using Google NotebookLM to dynamically analyze my outage spreadsheets directly from linked Google Sheets. Jon detailed how he's leveraging AI agents like Codex as a diligent "junior system administrator" to inventory his home Raspberry Pi servers, document configurations, and even run virtual disaster recovery drills. Jon has also integrated ChatGPT with his Apple Health data to analyze his jogging routine and pinpoint the cause of some recent ankle pain, and he's even using LLMs to flesh out fictional characters for creative writing. We agreed that while some dismiss AI as "social media slop," it becomes incredibly powerful once you find a highly specific use case—like Jon's colleague who used AI to condense a week-long project into just two days. Jon also shared a clever Apple Shortcuts automation that automatically toggles his iPad's Wi-Fi off when he's home to stop background VPN battery drain. We finished up with some speculation on Apple's upcoming September 9th event, which Jon noted is on a Wednesday this year rather than a Tuesday. We're keeping an eye out for a rumored "iPhone Ultra" with a third party folding phone case already spotted on Amazon, and Sven is planning to buy the next Apple Watch Ultra. We expressed minor frustration with Google's Gboard "Rambler" feature, which automatically filters out verbal pauses like "ums" and "ahs" but is restricted to the new Pixel 11, leaving my Pixel 10 Pro out in the cold. Despite the minor upgrade hurdles, we agreed there is still plenty of fun in testing the boundaries of these evolving personal ecosystems.

How manufacturers can start digital transformation with low-cost tools, real shop-floor data, and minimal risk.In this episode, Harry Baxter from Defence Materials Technology Centre (DMTC) and Matthew Doolan from UNSW Canberra explain how manufacturers can begin their digital manufacturing journey without investing in large-scale MES projects or expensive infrastructure. Shane and Paul explore practical examples from Digital Manufacturing on a Shoestring and Smart Enough Factory initiatives, covering:How low-cost sensors, Raspberry Pi devices and simple dashboards can provide immediate visibility of factory operationsUsing energy monitoring to identify hidden power consumption and reduce operating costsHow job-tracking systems help identify bottlenecks and improve production flowWhy air-quality monitoring can improve workplace transparency and operational awarenessThe cultural challenges of digital adoption and how to build operator engagement from the shop floor upWhy manufacturers should focus on solving business problems first and then select the appropriate technologyWhether you're a plant manager, operations leader, continuous improvement specialist, or SME owner, this episode provides practical examples of how to start capturing meaningful production data and build momentum for broader digital transformation.Follow Manufacturing Tech Australia on Spotify and leave a review if this episode helped you.Show notes and links for this episode: https://www.manufacturingtech.au/episodes/

Meta pays up in a landmark teen safety settlement & establishes new online safety measures for teens, Raspberry Pi goes official on the cyberdeck craze, and looking at what Apple unveiled earlier this week & looking ahead to Apple's September event. Meta settled a lawsuit with over 47 states and territories over harms to teens, agreeing to independently tested age verification, daily time limits, notification restrictions, and parental alerts on Instagram and Facebook. Raspberry Pi is getting in on the cyberdeck craze as the company published an official cyberdeck tutorial with a parts list and build instructions. And D. Griffin Jones joins the show to talk about Apple's updates to its Mac mini and Mac Studio, and what the expectations may be for its "Surprise and Shine" September event. Hosts: Mikah Sargent and Jennifer Pattison Tuohy Guest: D. Griffin Jones Download or subscribe to Tech News Weekly at https://twit.tv/shows/tech-news-weekly. 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 Sponsors: horizon3.ai/technews threatlocker.com/twit outsystems.com/twit cirasync.com/TNW

Meta pays up in a landmark teen safety settlement & establishes new online safety measures for teens, Raspberry Pi goes official on the cyberdeck craze, and looking at what Apple unveiled earlier this week & looking ahead to Apple's September event. Meta settled a lawsuit with over 47 states and territories over harms to teens, agreeing to independently tested age verification, daily time limits, notification restrictions, and parental alerts on Instagram and Facebook. Raspberry Pi is getting in on the cyberdeck craze as the company published an official cyberdeck tutorial with a parts list and build instructions. And D. Griffin Jones joins the show to talk about Apple's updates to its Mac mini and Mac Studio, and what the expectations may be for its "Surprise and Shine" September event. Hosts: Mikah Sargent and Jennifer Pattison Tuohy Guest: D. Griffin Jones Download or subscribe to Tech News Weekly at https://twit.tv/shows/tech-news-weekly. 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 Sponsors: horizon3.ai/technews threatlocker.com/twit outsystems.com/twit cirasync.com/TNW

Meta pays up in a landmark teen safety settlement & establishes new online safety measures for teens, Raspberry Pi goes official on the cyberdeck craze, and looking at what Apple unveiled earlier this week & looking ahead to Apple's September event. Meta settled a lawsuit with over 47 states and territories over harms to teens, agreeing to independently tested age verification, daily time limits, notification restrictions, and parental alerts on Instagram and Facebook. Raspberry Pi is getting in on the cyberdeck craze as the company published an official cyberdeck tutorial with a parts list and build instructions. And D. Griffin Jones joins the show to talk about Apple's updates to its Mac mini and Mac Studio, and what the expectations may be for its "Surprise and Shine" September event. Hosts: Mikah Sargent and Jennifer Pattison Tuohy Guest: D. Griffin Jones Download or subscribe to Tech News Weekly at https://twit.tv/shows/tech-news-weekly. 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 Sponsors: horizon3.ai/technews threatlocker.com/twit outsystems.com/twit cirasync.com/TNW

Meta pays up in a landmark teen safety settlement & establishes new online safety measures for teens, Raspberry Pi goes official on the cyberdeck craze, and looking at what Apple unveiled earlier this week & looking ahead to Apple's September event. Meta settled a lawsuit with over 47 states and territories over harms to teens, agreeing to independently tested age verification, daily time limits, notification restrictions, and parental alerts on Instagram and Facebook. Raspberry Pi is getting in on the cyberdeck craze as the company published an official cyberdeck tutorial with a parts list and build instructions. And D. Griffin Jones joins the show to talk about Apple's updates to its Mac mini and Mac Studio, and what the expectations may be for its "Surprise and Shine" September event. Hosts: Mikah Sargent and Jennifer Pattison Tuohy Guest: D. Griffin Jones Download or subscribe to Tech News Weekly at https://twit.tv/shows/tech-news-weekly. 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 Sponsors: horizon3.ai/technews threatlocker.com/twit outsystems.com/twit cirasync.com/TNW

Meta pays up in a landmark teen safety settlement & establishes new online safety measures for teens, Raspberry Pi goes official on the cyberdeck craze, and looking at what Apple unveiled earlier this week & looking ahead to Apple's September event. Meta settled a lawsuit with over 47 states and territories over harms to teens, agreeing to independently tested age verification, daily time limits, notification restrictions, and parental alerts on Instagram and Facebook. Raspberry Pi is getting in on the cyberdeck craze as the company published an official cyberdeck tutorial with a parts list and build instructions. And D. Griffin Jones joins the show to talk about Apple's updates to its Mac mini and Mac Studio, and what the expectations may be for its "Surprise and Shine" September event. Hosts: Mikah Sargent and Jennifer Pattison Tuohy Guest: D. Griffin Jones Download or subscribe to Tech News Weekly at https://twit.tv/shows/tech-news-weekly. 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 Sponsors: horizon3.ai/technews threatlocker.com/twit outsystems.com/twit cirasync.com/TNW

Meta pays up in a landmark teen safety settlement & establishes new online safety measures for teens, Raspberry Pi goes official on the cyberdeck craze, and looking at what Apple unveiled earlier this week & looking ahead to Apple's September event. Meta settled a lawsuit with over 47 states and territories over harms to teens, agreeing to independently tested age verification, daily time limits, notification restrictions, and parental alerts on Instagram and Facebook. Raspberry Pi is getting in on the cyberdeck craze as the company published an official cyberdeck tutorial with a parts list and build instructions. And D. Griffin Jones joins the show to talk about Apple's updates to its Mac mini and Mac Studio, and what the expectations may be for its "Surprise and Shine" September event. Hosts: Mikah Sargent and Jennifer Pattison Tuohy Guest: D. Griffin Jones Download or subscribe to Tech News Weekly at https://twit.tv/shows/tech-news-weekly. 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 Sponsors: horizon3.ai/technews threatlocker.com/twit outsystems.com/twit cirasync.com/TNW

Meta pays up in a landmark teen safety settlement & establishes new online safety measures for teens, Raspberry Pi goes official on the cyberdeck craze, and looking at what Apple unveiled earlier this week & looking ahead to Apple's September event. Meta settled a lawsuit with over 47 states and territories over harms to teens, agreeing to independently tested age verification, daily time limits, notification restrictions, and parental alerts on Instagram and Facebook. Raspberry Pi is getting in on the cyberdeck craze as the company published an official cyberdeck tutorial with a parts list and build instructions. And D. Griffin Jones joins the show to talk about Apple's updates to its Mac mini and Mac Studio, and what the expectations may be for its "Surprise and Shine" September event. Hosts: Mikah Sargent and Jennifer Pattison Tuohy Guest: D. Griffin Jones Download or subscribe to Tech News Weekly at https://twit.tv/shows/tech-news-weekly. 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 Sponsors: horizon3.ai/technews threatlocker.com/twit outsystems.com/twit cirasync.com/TNW

Meta pays up in a landmark teen safety settlement & establishes new online safety measures for teens, Raspberry Pi goes official on the cyberdeck craze, and looking at what Apple unveiled earlier this week & looking ahead to Apple's September event. Meta settled a lawsuit with over 47 states and territories over harms to teens, agreeing to independently tested age verification, daily time limits, notification restrictions, and parental alerts on Instagram and Facebook. Raspberry Pi is getting in on the cyberdeck craze as the company published an official cyberdeck tutorial with a parts list and build instructions. And D. Griffin Jones joins the show to talk about Apple's updates to its Mac mini and Mac Studio, and what the expectations may be for its "Surprise and Shine" September event. Hosts: Mikah Sargent and Jennifer Pattison Tuohy Guest: D. Griffin Jones Download or subscribe to Tech News Weekly at https://twit.tv/shows/tech-news-weekly. 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 Sponsors: horizon3.ai/technews threatlocker.com/twit outsystems.com/twit cirasync.com/TNW

We're back after the summer break, and there's a lot to catch up on.James and Kieran recap this year's Create With Conference in Brighton: 550 attendees (nearly double last year), packed workshops, and a charity hackathon where people built fully functional AI apps in 30 minutes, including a recycling app using image recognition that looked professionally built.They also share how they ran the whole event with AI: a custom conference operating system built with Claude Code as the single source of truth, auto-generated speaker videos, Raspberry Pi signage pulling live schedule data, automated financials and VAT returns, and the Face Hunt selfie game that transformed networking on the day.Also in this episode: first impressions of Anthropic's Fable model, thoughts on GrokBot and the hype around autonomous agents, how scheduled tasks in Codex are quietly automating documentation and SEO, and why self-healing apps that detect and fix their own bugs are already here thanks to PostHog.Got a real case study of AI or no-code in your business? We want to feature it. Get in touch at createwith.com

AI models are starting to act like appliances, locked into one narrow way of working, instead of the flexible infrastructure they used to be. Drew Breunig, an AI and data strategist working with the Overture Maps Foundation, joins us to explain why, and what it means for anyone building something that doesn't look like Claude Code.Drew walks through his "Winchester Mystery House" idea: what happens once code gets so cheap to write that the only real bottleneck left is feedback. From there we dig into DSPy: signatures, the GEPA optimizer, and the brand-new Flex optimizer, which rewrites your code instead of just your prompt, complete with a real before-and-after on cost and accuracy. We also get into why so many AI-built apps and websites end up looking identical, the actual difference between an agent and a workflow, what Drew learned a year after shipping a code library with no code in it, and why he thinks the most valuable thing you can do right now is close the laptop and go talk to people.CMPND: https://www.cmpnd.aiDrew Breunig: https://www.linkedin.com/in/drewbreunig/Demetrios: https://www.linkedin.com/in/dpbrinkmTimestamps:[0:00] Cold open: when Claude Code tries to call itself[1:19] Biggest AI news: labs trading diversity for reliability[2:35] How harnesses get trained into models over time[5:41] The problem: your harness starts fighting the model[9:13] When do you need your own harness?[10:02] The Winchester Mystery House warning[16:13] The blank page problem: why everything looks the same[20:50] Infrastructure vs appliances: the thesis lands[22:40] Current tool loadout: GLM, Kimi, Claude Code, Pi[27:04] The Raspberry Pi personal agent running on Slack[31:00] Crystallizing tasks: when to replace AI with pure code[33:10] DSPy explained: separating what from how[35:23] How prompt optimizers actually work[39:31] DSPy pre-dates ChatGPT: model-agnostic programs[44:00] Why you still need to ship the code, not just the spec[50:00] Don't plan more than a month ahead anymore[54:00] Coaching agents all day feels productive — it isn't[57:58] The dopamine of building with agents vs. why you still need human feedback

The boys are back! Tonight we talk about our favorite apps! ==== Special Thanks to Our Patrons! ==== https://thelinuxcast.org/patrons/ ===== Follow us

Podcasting 2.0 August 21st 2026 Episode 268 - "Dead Hanging Safari" It's always DNS or CORS - and how your right brain is gating bad robots Show Notes ------------------------------------------------------------------------------------------------------------------------------------- 00 - THE LOCATION TAG — SPEC TO DATASET TO GLOBE IN 48 HOURS The lead, and it's yours: Wednesday afternoon Dave posted — "There is a new locations data set on the public datasets page... The db tables are still back-filling since I updated the db and aggregators to support the new tag format. After a couple of days it should be mostly complete." He cc'd @james, @alberto, @js and then @DavidMarzalC. That cc list is the whole story — within 48 hours all four had done something with it. @dave — the locations dataset post (20 Aug) The shipping trail: web-ui PR #608, "add locations export to public data sets," branch public_datasets → merged to master the same afternoon. This is the first public dataset built on the new location tag format rather than the old one. Then somebody built the map. By Friday morning Alberto had radar.rss.io/#globe up — a spinning globe of podcasts made in or about places on earth, drawn from the free dataset, most entries carrying full OpenStreetMap references. James put it in front of the OpenStreetMap community directly: "One for excellent people using @openstreetmap." James's review, and the two asks: "This is so cool. Really shows the power of the location tag. The globe — would be nice to add filters to that (made in vs about). Or maybe just colour the dots differently? The next trick would be some OSM lookups on the IDs to work out what the places are."

Broadcast engineering is a family affair for Amanda Hopp and her father, Cris Alexander. Amanda is Chief Engineer for Crawford Broadcasting’s Denver stations, while Cris serves as Director of Engineering for the entire company. On this episode of TWiRT, they share Amanda’s path into engineering—and what her experience might teach others considering a career in the field. We also explore cybersecurity, IT and networking, the challenges of maintaining multiple transmitter sites, and Amanda’s inventive use of Raspberry Pis and other small computers for monitoring, control and automation. Along the way, we hear how Amanda draws on programming expertise from elsewhere within Crawford to create practical engineering solutions. Join us for an engaging conversation with two highly accomplished engineers who just happen to be father and daughter. Show Notes:Women in Engineering: Amanda Hopp of Crawford Broadcasting - Radio World Guests:Amanda Hopp - Chief Engineer at Crawford Broadcasting, DenverCris Alexander - Director of Engineering at Crawford Broadcasting Host:Kirk Harnack, MaxxKonnect, Delta Radio, Star94.3, South Seas, OMG, & Akamai BroadcastingFollow TWiRT on Twitter and on Facebook - and see all the videos on YouTube.TWiRT is brought to you by:Broadcasters General Store, with outstanding service, saving, and support. Online at BGS.cc. Broadcast Bionics - making radio smarter with Bionic Studio, visual radio, and social media tools at Bionic.radio.Aiir, providing PlayoutONE radio automation, and other advanced solutions for audience engagement.Angry Audio and the new StereoToolBox audio processor for AM, FM, HD, & StreamingThe new MaxxKonnect RMT416 Multi Tuner - 4 to 16 AM/FM/WB/HD web-connected tuners in 1 RU Subscribe to Audio:iTunesRSSStitcherTuneInSubscribe to Video:iTunesRSSYouTube

Broadcast engineering is a family affair for Amanda Hopp and her father, Cris Alexander. Amanda is Chief Engineer for Crawford Broadcasting's Denver stations, while Cris serves as Director of Engineering for the entire company. On this episode of TWiRT, they share Amanda's path into engineering—and what her experience might teach others considering a career in the field. We also explore cybersecurity, IT and networking, the challenges of maintaining multiple transmitter sites, and Amanda's inventive use of Raspberry Pis and other small computers for monitoring, control and automation. Along the way, we hear how Amanda draws on programming expertise from elsewhere within Crawford to create practical engineering solutions. Join us for an engaging conversation with two highly accomplished engineers who just happen to be father and daughter.

PHP Podcast – August 20, 2026 Hosts: Joe Ferguson, Sara Golemon & Holly Schilling Shirley MacLaine is the answer — but what’s the question? RAM prices went up 500%, GitHub fell over for eight hours, and the crew figured out how you can actually contribute to PHP. Glasses optional. Shirley MacLaine, Green Room Shade, and the Show’s New Normal The episode opens with Joe flustered — not because it’s a “flustered day,” but because there’s shade being thrown in the green room backstage chat. Rather than spoil the drama, the crew turns a mysterious green-room answer into a running bit: “Shirley MacLaine” is the answer, and listeners are invited to submit what the question was. It’s declared the first round of PHP Architect’s Jeopardy, complete with its own Easter egg sound cue. Joe also lays out where the show is heading. Eric and John took over the podcast the previous week to relive their glory days, and the plan is for the old guys to step back to roughly one episode a month. Joe and Sara are working on something to fill one slot, another mystery show is in the works pending signed contracts, and Alive and Kicking is confirmed still alive and kicking after a great recent episode with Derek. Joe also plugs the PHP 8.6 Beta 1 tag and Scott Keck-Warren’s PHP Community Podcast interview with release managers Daniel Scherzer and Matteo Bacotti. The RAM Apocalypse: 500% in Twelve Months The big topic of the week is the ongoing memory and chip crisis. Memory prices have climbed 500% in twelve months, and the crew commiserates about the parts they wish they’d bought bigger. Sara explains the brutal math: you can’t build a semiconductor fab fast enough — two or three years minimum — and by the time one comes online nobody knows if we’ll have overproduction or a burst bubble. Worse, Sara notes that essentially every RAM stick through the end of 2027 is already accounted for and sold to vendors. The ripple effects are everywhere. Console prices are going up instead of down late in their cycle, with next-gen consoles projected to start at $1,000 or more. The hobbyist single-board computer market is getting crushed — Pine64 announced they’re stepping back from making hardware, and a Raspberry Pi 5 that debuted cheap now runs over 100 pounds. Holly’s new PC, bought at the start of 2025, ended up shipped 3,000 kilometers the wrong way to California and is stuck awaiting import paperwork, leaving her leaning on a laptop and some now-precious Raspberry Pi zeros. The nostalgia gets thick as the crew reminisces about DIP chips, EDO RAM, Pentiums, Epson 486s, Tandy 1000s, and the TRS-80. Special venom is reserved for Packard Bell (“utter freaking trash”) and Gateway 2000’s cow-pattern branding — which Sara confirms sold better in Wisconsin than anywhere, though hay bales in a Berkeley storefront still boggle the mind. A chat comment about technicians de-soldering and reballing BGA RAM chips becoming economically viable gets a hearty “absolutely.” Memory-Aware Development and Why PHP 7 Doubled Down Bringing the RAM crisis back to PHP, Joe wishes more developers were aware of how their applications consume and release memory — a lesson he credits to learning enough C back in the day, where you have to manage memory yourself. He connects sloppy memory awareness to the N+1 query problems web developers keep tripping over. Sara drops a great deep dive: a significant reason PHP 7 was roughly twice as fast as PHP 5 was changes in the memory layout. Every variable became referenced by one fewer pointer, and while eight bytes sounds trivial, every level of indirection adds time across every single instruction and access. Sara adds the CPU-level detail — one layer of indirection can be a single instruction on most architectures, but adding a second layer can push a lookup from one instruction to three. That leads into a warm tangent about learning C to become game developers. Sara’s evergreen joke: “I’m going to be a game developer” is the programmer’s version of “I’m going to buy a bar.” Great people, brutal hours, endless competition, and the reality of hitting spacebar 400 times to figure out why you can phase through a wall. The cat-reading-the-paper “I should buy a boat” meme makes an appearance to seal it. The GitHub Outage and the Monoculture Problem Monday’s eight-hour GitHub outage hit the crew directly. Holly couldn’t use a site that only offered “log in with GitHub,” and Joe got kicked out of his CLI auth session mid-PR with no way to re-authenticate. To GitHub’s credit, they published an incident update and a follow-up blog post: a service auto-scaled so aggressively to handle network traffic that the sidecar and supporting services couldn’t keep up, bringing the whole thing down. The conversation turns to whether this is self-inflicted. Joe recalls GitHub’s pre-Microsoft, gold-standard reliability and wonders aloud how much the decline lines up with Copilot’s arrival and internal AI adoption, with uptime reportedly slipping below a single nine at points. Sara defends them somewhat — the number of actions, CPU cores, and pull requests has genuinely hockey-sticked, partly because AI has emboldened people who previously wouldn’t have opened a PR. But as Joe puts it, the call is coming from inside the house, since GitHub itself has been pushing AI. On alternatives, Joe says the least-jarring migration for PHP Architect’s clients would be self-hosting GitLab, since GitHub Actions and GitLab runners are nearly identical in syntax — Atlassian’s Bitbucket, by contrast, is a bridge too far, mostly because the entire ecosystem assumes you’re on GitHub. Sara names this the core problem: monoculture. The crew discusses package mirrors, local caches, 12-factor thinking, and Composer’s support for custom mirrors, all while remembering the PHP repo intrusion years ago that came from an unmaintained self-hosted Git server. The takeaway: owning your pipeline end-to-end is the only way an outage can’t stop you — and Joe teases spinning up a self-hosted GitLab now that “the boss” (Sara) has signed off. How to Contribute to PHP (and Handling Security Reports) The crew highlights two PHP Foundation blog posts. First, Matt Stauffer’s “How to Contribute to PHP,” adapted from a talk he gave at Atlanta PHP. It goes well beyond “learn C,” clearly separating the PHP project, the PHP ecosystem, and the Foundation, and lays out approachable on-ramps: testing pre-releases (PHP 8.6 Beta 1 is out, Beta 2 lands next week), improving documentation, and writing tests — which, spoiler, are written in PHP, not C, using PHP’s own test format that’s simple enough to learn from any single example. Other contribution paths include triaging and reviewing issues across PHP repositories — invaluable work that frees core developers from wading through AI-generated slop bug reports — and participating in internals via the well-documented mailing list process, up to and including running for release manager (8.7 managers will be needed before you know it). Sara points folks to discord.phpc.chat for the PHP Discord, with dedicated Internals and Foundation channels for anyone the mailing list intimidates. Second, Sebastian Bergmann’s “So you received a security report. Now what?” is a jump-around reference for application developers rather than a front-to-back read, walking through roughly ten steps to triage, validate, and resolve reported issues the right way. Sara shares a real-world example from mobile: a flagged package that was only exploitable on a rooted device with an actively hostile package installed alongside it — a very different risk profile than a SQL injection on an API endpoint. Cue reminiscing about writing SQL against Access databases over ODBC from PHP (and Perl) back in the 90s, and Joe’s advice for handling any security report: don’t panic, and always know where your towel is. Links from the show: PHP Tek 2027 — April 27–29, 2027 in Chicago; early bird tickets & hotel available now PHP Tek 2027 CFP Audio versions of the podcast at phparch.com Join us live on Discord at discord.phparch.com PHP Discord — discord.phpc.chat Community Corner Podcast: PHP 8.5 + 8.6 Release Manager Daniel Scherzer Memory prices climb 500% in 12 months So You Received a Security Report. Now What? How to Contribute to PHP Shirley MacLaine Host: Joe Ferguson Mastodon: @joepferguson@phpc.social PHPArch.me: @svpernova09 Sara Golemon Mastodon: @pollita@phpc.social Holly Schilling Mastodon: @TheCodeLorax@tech.lgbt Streams: Youtube Channel Twitch Connect & Hire PHP Architect Website Twitter/X Mastodon Hire PHP Developers Looking to hire PHP developers? Email support@phparch.com – Joe and the team are available for consulting, infrastructure work, Ansible playbooks, and code review. Partner This podcast is made a little better thanks to our partners Displace Infrastructure Management, Simplified Automate Kubernetes deployments across any cloud provider or bare metal with a single command. Deploy, manage, and scale your infrastructure with ease. https://displace.tech/ OurCVEs Your security posture, on autopilot with OurCVEs CodeRabbit Cut code review time & bugs in half instantly with CodeRabbit. PHP Architect Consulting Your PHP codebase deserves a partner, not a contractor PHP Architect provides long-term technical partnerships for organizations that need senior-level PHP expertise that you can depend on https://www.phparch.com/consulting/ Music Provided by Epidemic Sound https://www.epidemicsound.com/ Join Us Live Next Week Youtube Channel Got feedback? Join us on Discord at discord.phparch.com The post The PHP Podcast 2026.08.20 appeared first on PHP Architect.

Anna Bicker, Alexander Spier und Malte Kirchner sprechen in dieser Ausgabe der #heiseshow unter anderem über folgende Themen: - Adblocker im Router: Wird die Fritzbox zum Fritzhole? – Mit FritzOS 8.50 will AVM DNS-Filter direkt in die Fritzbox integrieren, die Werbung und Tracker im gesamten Heimnetz blockieren – auf PC, Smartphone und TV, ganz ohne zusätzliche Hardware wie einen Raspberry Pi. Kann ein DNS-basierter Adblocker im Router mit klassischen Browser-Erweiterungen mithalten? Und was bedeutet die neue Funktion für Websites, die von Werbeeinnahmen leben? - Teenager-Modus: ChatGPT soll bei Jugendlichen umdenken – OpenAI startet ChatGPT for Teens für 13- bis 17-Jährige, erkennt Minderjährige künftig automatisch am Nutzungsverhalten und schaltet strengere Inhaltsgrenzen sowie einen Study Mode frei. Wie zuverlässig kann eine verhaltensbasierte Alterserkennung überhaupt sein? Und ersetzt der Study Mode eine echte Lernbegleitung durch Eltern oder Lehrkräfte? - Hat sich nicht ausgezahlt: Warum ist Wero vielen unbekannt? Zwei Jahre nach dem Start kennen laut einer Verivox-Umfrage weiterhin fast zwei Drittel der Deutschen die PayPal-Alternative Wero nicht, obwohl immer mehr Händler den Dienst anbieten. Warum tut sich eine europäische Bezahllösung so schwer gegen etablierte Anbieter? Und braucht es dafür mehr Werbung oder einfach mehr Akzeptanzstellen? Außerdem wieder mit dabei: ein Nerd-Geburtstag, das WTF der Woche und knifflige Quizfragen.

The boys are back! This week we're joined again by @BrodieRobertson to rank all the Linux drama from the last few years. For frun ==== Special Thanks to Our Patrons! ==== https://thelinuxcast.org/patrons/ ===== Follow us

The era of the lone criminal targeting an ATM has ended. Now, organized criminals work together to figure out vulnerabilities and target ATMs. One of their primary techniques in 2026 is man-in-the-middle attacks, which intercept communications between the host and processor to send out fraudulent transactions.In today's episode of the Bank Customer Experience podcast, host Bradley Cooper spoke with Michael Strange, director of technology services, Cook Solutions Group, and Alyssa Luecke, fintech solutions consultant, Cook Solutions Group, about what MITM attacks are and how they have changed in 2026.During the podcast, Strange identified that criminals are able to perform these attacks with much better efficiency and without as much risk of being on site. For example, they can install a black box device, usually a Raspberry Pi, directly into the machine and then communicate with it remotely.Strange said that in the Pacific Northwest these attacks have become the main vector of actors. "I'd say the last 3 months, that's all we've seen. It's been almost exclusively man in the middle."He added that criminal groups have started using Wi-Fi routers so they can control the attack remotely, as well as using server spoofing."They don't need the local Bluetooth connection anymore, they can have that guy off site." They can even use black boxes in bypass mode, which allows customers to do legitimate transactions in between installation of the black box and when the criminal groups device to use it.The process of the overall attack remains the same. A group scouts out the location first, noting any cameras and the overall security of the device. They will then attempt to remove the top box to see if an alarm is triggered or any law enforcement is called. If no alarm sounds, they will replace the top box, then come back at another date to install the black box device. They can then send out cash collectors who can insert a payment card and put in a legitimate transaction. The black box will then take that legitimate transaction and approve a maximum withdrawal.Strange said in many cases, banks only find out about this incident when they run out of cash at the ATM. Even then, Luecke said that the bank may attribute this to a busy week of cash withdrawals.Luecke and Strange also discussed methods for how to prevent attacks, such as installing an alarm on the top hat, from which criminals can access the network cables. They can also use barriers that can block access to the top hat.To learn more about this attack vector and ways to prevent it, listen to the podcast in full above.

Like a lot of parents, Eli struggled over the years to get his kids more into reading and away from screens. He wasn't necessarily on the search for a technological solution, but then an interesting device came our way: the Yoto Player, a screen-free audio player for kids. Eli's 10-year old son has been loving to read along to the Harry Potter books (and he often finds him after he falls asleep, and the player is still going). Visit our Substack for bonus content and more: https://designbetterpodcast.com/p/ben-drury The story behind Yoto is from a similar moment of parental struggle. About a decade ago, Ben Drury was shopping for a stroller in a London department store and found one with an iPad mount built in. For a newborn. He remembers the reaction being physical — this is just wrong. But if you're expecting an anti-screen crusade, that's not quite what happened . The line Ben uses is: we don't say screens are bad, we say audio is good. Listening is good for creativity and imagination — and there's research going back to the 1980s to back that up. Ben is the co-founder and CEO of Yoto, makers of a kids' audio player that works by dropping a physical card into a small speaker. Before Yoto Ben spent about a decade building a B2B digital music platform called 7digital which he took public. What he learned from that experience proved helpful as he and his co-founder started Yoto. Ben and his co-founder became parents at roughly the same time, and wanted a way for their kids to connect with music and books like they did in childhood. So they started hacking on Raspberry Pis with no hardware experience whatsoever. How hard could it be, right? The 3rd Gen Yoto Player Turns out, it's pretty hard. They took a restrained approach. Yoto is a cube, because it was the simplest shape they could think of. It uses NFC cards that have a Pokemon card feel. The 16 by 16 pixel display presents pixel art that gives Yoto a fun personality. In this conversation, we get into the design principles that came out of Montessori, their experience working with Pentagram on product design and branding, why Paul McCartney became an early angel investor, and what changes when you go from a Kickstarter that raised fifty thousand dollars to nine-figure revenue. Bio Ben Drury is the co-founder and CEO of Yoto, the screen-free audio player that lets children control their own listening by dropping a physical card into a speaker. Before Yoto, he spent roughly a decade building 7digital, a B2B digital music platform he took public. He and his co-founder started Yoto in 2017 with a Kickstarter campaign and no hardware experience between them; today the company employs about 220 people across six countries, sells in 1,900 Target stores in the US, and counts Paul McCartney among its early angel investors. He lives in London with his wife and two sons. *** Premium Episodes on Design Better This ad-supported episode is available to everyone. If you'd like to hear it ad-free, upgrade to our premium subscription, where you'll get an additional 2 ad-free episodes per month (4 total). Premium subscribers also get access to the documentary Design Disruptors and our growing library of books. New premium subscriber benefit: we've launched a private Slack workspace…join now to connect with designers, product leaders & creative practitioners in our community. And get a behind-the-scenes pass to every episode with The Roundup, where each week we bring you insights and actionable tactics from recent episodes. You'll also get access to our monthly AMAs with former guests, ad-free episodes, discounts and early access to workshops, and our monthly newsletter The Brief that compiles salient insights, quotes, readings, and creative processes uncovered in the show. And subscribers at the annual level now get access to the Design Better Toolkit, which gets you major discounts and free access to tools and courses that will help you unlock new skills, make your workflow more efficient, and take your creativity further. Upgrade to paid Learn more about your ad choices. Visit megaphone.fm/adchoices

What happens when you hear your own hit song playing in public, but never receive the royalty?In this episode of Riding Unicorns, James sits down with Ryan Edwards, Founder & CEO of Audoo, the music technology company rebuilding how public performance royalties are measured and distributed.The idea for Audoo came from Ryan's own experience as a musician. After hearing one of his songs playing in a London department store and discovering there was effectively no reliable way to track the royalty, he started investigating how the system actually worked.What he found was an industry still relying heavily on proxy data, manual surveys and people physically visiting venues with clipboards.Audoo's answer is the Audio Meter, a small connected device that identifies music being played in public venues without recording or storing conversations. The resulting data allows collecting societies to understand what was actually played and distribute royalties more accurately to artists and rights holders.Today, Audoo operates across 16 countries, with its technology deployed in environments ranging from cafés and retailers to gyms and leisure centres.Ryan shares how he built the first prototype on a Raspberry Pi at his kitchen table, validated the idea with the former Chairman of PRS for Music, and launched the first real-world deployment on the other side of the world in Australia during COVID.We also discuss the unusual group of investors Audoo has attracted along the way, including Björn Ulvaeus of ABBA, Paul McCartney, Elton John, Adam Clayton of U2 and Adele, and how those relationships have helped build credibility and open doors across the music industry.Topics Covered• Why the public performance royalty system needed rebuilding• The personal experience that led Ryan to start Audoo• Building the first Audio Meter prototype on a Raspberry Pi• Why privacy had to be designed into the technology from day one• The challenges of combining software, data and physical hardware• Landing Audoo's first major deployment in Australia during COVID• Why venues are willing to install Audio Meters• How better music recognition data changes royalty distributions• Raising capital from some of the biggest names in music• Expanding Audoo across 16 countries and into the Middle East• What Ryan has learned from eight years as a founder• Why founders need to celebrate wins and know when something can wait until MondayThis is a conversation about spotting an antiquated system, using technology to rebuild it from first principles, and creating the data infrastructure that could finally ensure artists are paid accurately when their music is played.

Walk through almost any corporate facility, QSR, or residential building, and you will find blank TV screens or locked computers requiring manual updates. In this episode of The AC Method, Aaron Clippinger sits down with Chris, CEO of Display Now, to discuss transforming any standard TV screen into a cloud-managed visual communication hub.Chris shares how Display Now grew from a homegrown Raspberry Pi experiment designed for a 59-unit condo building into a cloud SaaS platform operating across 1,200+ companies worldwide. He breaks down why cheap consumer streaming sticks are sabotaging business operations, how purpose-built Android edge players prevent expensive IT support calls, and how Generative AI allows non-technical staff to deploy great designs and local ad networks in seconds.

The boys are back! We have news to talk about. ==== Special Thanks to Our Patrons! ==== https://thelinuxcast.org/patrons/ ===== Follow us

In this episode, James Maude sits down with Ulrich Swart, cofounder and CEO of Subverted, a South African offensive security company built to make pentesting and ethical hacker training more accessible. Ulrich traces his path from tearing apart laptops as a curious kid to being handed a Raspberry Pi and a WiFi card outside a security firm's door and told to prove himself within a week. He shares the chaos of a bank engagement where their laptops vanished mid pentest, and the time he felt like a secret agent hacking in from a stairwell only to spot the security camera watching him the whole time. Find out what motivates Ulrich and his co-founder Jason and why giving back to the community is a key part of what they do.

Chris, Andrew, and David begin with summer heat, home cooling problems, and an IPv6 issue preventing Andrew from playing Battlefield 6. The conversation quickly heads down a Raspberry Pi rabbit hole, with projects ranging from smart-home automation and MagicMirror dashboards to local AI transcription. David then recaps RubyConf in Las Vegas before the group discusses design patterns, the changing conference landscape, and how AI is reshaping programming education, software development, and the economics of building products. Hit download now!LinksChris Oliver XAndrew Mason BlueskyDavid Hill LinkedInJudoscale- Remote Ruby listener giftBrockovich AI Data Center ReportingRaspberry PiRails World, Austin, TX, Sept 23-24, 2026SF Ruby, San Franciso, CA, Nov 10-12, 2026MagicMirror2HoneybadgerHoneybadger is an application health monitoring tool built by developers for developers.JudoscaleMake your deployments bulletproof with autoscaling that just works.Disclaimer: This post contains affiliate links. If you make a purchase, I may receive a commission at no extra cost to you.Chris Oliver X/TwitterAndrew Mason X/TwitterJason Charnes X/Twitter

What becomes possible when enterprise computer vision no longer depends on expensive GPU infrastructure? In this episode of Tech Talks Daily, I speak with Glenn Jocher, founder and CEO of Ultralytics, about YOLO26, CPU inference, edge AI, open vocabulary vision, deployment economics, and the practical work required to move computer vision from a promising pilot into production. Glenn's route into AI began inside the U.S. intelligence community. He worked with the National Geospatial Intelligence Agency and Defense Intelligence Agency on particle physics applications, attempting to detect and track antineutrinos. Antineutrinos are extraordinarily difficult to detect because they pass through almost everything. Glenn describes them as the perfect spy. While searching for better detection methods, he discovered that computer vision researchers were solving similar problems with images. His original attempt to transfer those techniques into particle physics did not succeed. However, the work introduced him to a field where the technology could create a visible effect on everyday life. That led him toward open source development and eventually the YOLO models for object detection, classification, segmentation, and tracking. Glenn believes computer vision research has historically placed too much attention on small gains in accuracy while overlooking deployment economics. A model can perform impressively inside a laboratory and still remain unsuitable for a factory, warehouse, store, vehicle, drone, or medical environment. Price, latency, power consumption, data privacy, and deployment speed can determine whether the technology is commercially useful. This led Glenn and Ultralytics toward smaller models capable of running close to where images and video are generated. YOLO26 continues that approach with architectural changes designed specifically for CPU inference. Glenn says the model can process camera streams in real time at 30 frames per second and run across Intel CPUs, AMD CPUs, and lower power devices such as Raspberry Pi computers. This matters because specialist GPUs can increase the equipment cost and power requirements of a computer vision project. Running inference on existing CPUs or edge hardware can make deployment economically possible across larger numbers of cameras and locations. The scale already involved is difficult to comprehend. Glenn says Ultralytics models now process approximately three billion inference jobs each day, equivalent to around 30,000 every second. These jobs include images, videos, and collections of images being analyzed to detect, segment, or track objects. He attributes the platform's maturity to thousands of mistakes and bugs corrected through a rapid feedback cycle. New models are released, users report problems and request features, and the team incorporates that information into later versions. We also discuss the respective roles of cloud and edge infrastructure. Glenn sees cloud platforms continuing to provide the computing power required for training, while computer vision inference often belongs at the edge. Local processing can reduce latency, control operating costs, and keep sensitive video or medical information closer to where it was created. The smallest YOLO model is approximately three megabytes, according to Glenn. That allows it to reach mobile phones, vehicles, drones, battery powered devices, and other environments where a large language model would be impractical. Open vocabulary vision provides another development. Traditional object detection models are trained to recognize a fixed collection of objects. If a model learns to detect dogs and the user later wants it to detect cats, retraining can cause it to forget earlier knowledge unless both categories appear in the new training data. Glenn explains how promptable models can identify common everyday objects from text or visual instructions without additional training. A user could request a person wearing a blue shirt and white shoes, for example, and the system could search an image for that description. That flexibility could benefit businesses whose requirements change regularly. It reduces the need to create and label a new data set every time the company wants the model to recognize another common object. The range of current applications is already extensive. Glenn describes YOLO being used across robotics, parking, industrial safety, PPE detection, warehouses, aviation, security, traffic management, food quality, and manufacturing. Some of his favorite examples involve environmental problems. One company uses YOLO with underwater vehicles to identify and recover plastic from the ocean. Other applications detect smoke and fire early enough to support forest fire response. For leaders considering computer vision, Glenn recommends beginning with a defined problem and measurable outcome. A manufacturing company may want to reduce defects, but it still needs labeled examples showing the model what acceptable and defective products look like. He advises testing the idea through a limited pilot, measuring the return, and expanding only when the evidence supports further investment. Computer vision has become easier to deploy, but practical problems involving data, cameras, integration, reliability, and operating conditions still separate a demonstration from a production system. Could CPU inference and open vocabulary models make computer vision practical for processes your organization previously considered too expensive? Listen to the episode and share your thoughts with me. Useful Links   Ultralytics website Ultralytics Platform      

Possible price increases for the VR Head Toaster, Google Chrome for ARM Linux desktops, a new 10-inch touchscreen for Raspberry Pi, and NVIDIA doubling the price of Jetson SoCs.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 Intro07:22 AMD 4GB GPUs16:57 Steam Frame VR headset price increases 25:36 Google Chrome for ARM Linux 33:52 10" Raspberry Pi touchscreen37:48 NVIDIA Jetson price increases New 4GB GPUs from AMDhttps://videocardz.com/newz/amd-confirms-radeon-rx-9050-4gb-exists-but-it-is-oem-onlySteam Frame $$$https://www.pcgamer.com/hardware/vr-hardware/more-bad-news-for-valve-and-its-still-unreleased-steam-frame-as-qualcomm-is-set-to-raise-the-price-of-its-chips-like-everyone-else/Chrome on ARMhttps://www.omgubuntu.co.uk/2026/07/chrome-arm64-linux-availableRasPi 10” Touchscreenhttps://www.raspberrypi.com/news/a-new-10-raspberry-pi-touch-display-2-available-now-at-80/Jetson Price increasehttps://videocardz.com/newz/nvidia-raises-jetson-prices-by-up-to-101-agx-thor-now-costs-5499

video: https://youtu.be/mytY-cyk76U This week in Linux, hundreds of Linux security alerts landed but the headlines leave out the most important part. Codeberg, a major open-source code hosting platform, is drawing a new line around AI-generated code, Valve is stretching out their ARM for a new Frame of mind for running Linux, and Jellyfin is entering a major new chapter behind the scenes. All of this and more on This Week in Linux, Your Source for Linux GNews! Download as MP3 Support the Show Become a Member = tuxdigital.com/membership Store = tuxdigital.com/store Chapters: 00:00 Intro 00:30 Become a Member of the channel by July 31st 01:39 Codeberg bans mostly AI-generated projects 05:31 Valve and Collabora develop Arch Linux for ARM64 08:08 Jellyfin Leadership Departures 11:57 Linux publishes 432 kernel CVEs in 2 days 14:53 Canonical fixes 3 Snap vulnerabilities 17:26 Firefox 153 adds Containers and Vulkan Video 21:11 TWIL Speedrun or Linux Lightning Round 21:37 AMD's open-source AI and robotics announcements 22:34 Final MPEG-4 Visual patent expiration 23:31 OBS Studio 32.2 Released 24:05 Raspberry Pi launches a 10-inch Touch Display 2 25:18 Outro Links: Become a Member of the channel by July 31st https://tuxdigital.com/membership Codeberg bans mostly AI-generated projects https://blog.codeberg.org/protecting-our-floss-commons-from-llms.html https://www.omgubuntu.co.uk/2026/07/codeberg-bans-ai-generated-code https://itsfoss.com/news/codeberg-bans-ai-contributions/ OpenAI on Vibe Coding - https://x.com/karpathy/status/1886192184808149383 Valve and Collabora develop Arch Linux for ARM64 https://www.collabora.com/news-and-blog/news-and-events/building-an-arch-linux-aarch64-port-for-holo-core.html https://gitlab.steamos.cloud/holo/holo-core-aarch64-preview https://www.gamingonlinux.com/2026/07/collabora-announce-a-preview-of-holo-core-an-aarch64-port-of-arch-linux-for-steam-frame/ https://www.phoronix.com/news/Holo-Core-Experimental-ARM64 https://9to5linux.com/valve-and-collabora-announce-official-arch-linux-arm64-port-for-steam-frame Jellyfin Leadership Departures https://www.boniface.me/posts/on-my-jellyfin-resignation/ https://itsfoss.com/news/jellyfin-leadership-crisis/ https://linuxiac.com/jellyfin-loses-project-leader-and-core-team-member-in-major-shake-up/ https://jellyfin.org/posts/state-of-the-fin-2026-05-24/ Linux publishes 432 kernel CVEs in 2 days https://lore.kernel.org/linux-cve-announce/ https://seclists.org/oss-sec/2026/q3/198 https://seclists.org/oss-sec/2026/q3/210 https://www.theregister.com/security/2026/07/22/linux_kernel_team_publishes_432_cves_in_two_days/5276497 https://docs.kernel.org/process/cve.html https://utcc.utoronto.ca/~cks/space/blog/linux/KernelBugfixCVEsAStory Canonical fixes 3 Snap vulnerabilities https://ubuntu.com/security/notices/USN-8579-1 https://seclists.org/oss-sec/2026/q3/191 https://blog.qualys.com/vulnerabilities-threat-research/2026/07/21/cve-2026-8933-snap-confine-local-privilege-escalation https://cdn2.qualys.com/advisory/2026/07/21/snap-confine-set-capabilities.txt https://www.cve.org/CVERecord?id=CVE-2026-15226 Firefox 153 adds Containers and Vulkan Video https://www.firefox.com/en-US/firefox/153.0/releasenotes/ https://blog.mozilla.org/en/firefox/firefox-containers-preview/ https://developer.mozilla.org/en-US/docs/Mozilla/Firefox/Releases/153 https://brave.com/blog/containers/ TWIL Speedrun or Linux Lightning Round which do you prefer of those names? AMD's open-source AI and robotics announcements https://www.amd.com/en/corporate/events/advancing-ai.html https://www.amd.com/en/blogs/2026/rocm-ai-the-ai-native-developer-experience-for-building.html https://www.amd.com/en/products/system-on-modules/kria/ai.html https://www.amd.com/en/products/system-on-modules/kria/ai/robotics-developer-platform.html Final MPEG-4 Visual patent expiration https://www.phoronix.com/news/Last-MPEG-4-Patent-Expired https://itsfoss.com/news/mpeg-4-visual-patent-expiry/ https://meta.wikimedia.org/wiki/Have_the_patents_for_MPEG-4_Visual_expired_yet%3F OBS Studio 32.2 Released https://github.com/obsproject/obs-studio/releases/tag/32.2.0 https://9to5linux.com/obs-studio-32-2-released-with-new-filter-to-compose-sdr-into-hdr https://linuxiac.com/obs-studio-32-2-makes-adding-sources-easier/ Raspberry Pi launches a 10-inch Touch Display 2 https://www.raspberrypi.com/news/a-new-10-raspberry-pi-touch-display-2-available-now-at-80/ https://pip-assets.raspberrypi.com/categories/1083-raspberry-pi-touch-display-2 https://www.phoronix.com/news/10-inch-Raspberry-Pi-Touch-2 https://www.theregister.com/2026/07/22/raspberry-pi-goes-large-with-101-inch-touch-display-2/ https://9to5linux.com/raspberry-pi-launches-10-inch-raspberry-pi-touch-display-2-at-80 Support the show https://tuxdigital.com/membership https://store.tuxdigital.com/

In this one, we talk about the hardware we use. ==== Special Thanks to Our Patrons! ==== https://thelinuxcast.org/patrons/ ===== Follow us

The guys are back, this time the wheel of doom returns! We're going to have to defend takes that are not ours. Should be fun. ==== Special Thanks to Our Patrons! ==== https://thelinuxcast.org/patrons/ ===== Follow us

Welcome back to another episode of Linux Out Loud! In this episode, Wendy, Nate, Matt, and Bill dive into the wild world of Linux with tales of netbook resurrection, ESP32 adventures, and AUR nightmares. Nate brings his trusty netbook back from the dead, proving that even the most stubborn hardware can have a second life. Bill takes us on a journey into the ESP32 world, sharing his latest projects and the unexpected challenges that come with tinkering at the hardware level. Wendy shares her harrowing experience with the Arch User Repository, where one wrong move can turn a simple package install into a full-blown disaster. Along the way, the crew discusses Bluetooth relays saving the day, Wazuh tinkering for better security, keyboard battles, 3D printer adventures, finding browser zen, and the surprising benefits of UPS battery backups. Whether you're a seasoned Linux veteran or just starting your open-source journey, there's something here for everyone. Don't forget to subscribe for more Linux fun! Show Links: Veronica Explains Video: https://youtu.be/E7vFdy4BEAY Trinity Desktop: https://www.trinitydesktop.org Marklite.app: https://marklite.app SSHFS: https://github.com/libfuse/sshfs Wazuh (SIEM/XDR): https://wazuh.com MeshCentral: https://github.com/Ylianst/MeshCentral ESP32 Documentation: https://www.espressif.com/en/products/socs/esp32/overview X104 Full-Size Keyboard: https://rkgamingstore.com/products/x104-full-size-keyboard APC UPS 1500VA/900W (BR1500MS2): https://www.amazon.com/dp/B07TBXFHTH Vivaldi Browser: https://vivaldi.com Zen Browser: https://zen-browser.app Linux Out Loud 122: https://youtu.be/wMJsrC122ww Connect with the Hosts on Discord: Matt – @Dark1ltg Wendy – @Wendy.sh Nate – CubicleNate.com @CubicleNate Bill – @ctlinux on Mastodon Special Guest: Bill.

Building a Raspberry Pi powered Stream Deck, Redhat offers forever support, playing Silent Hill natively on Linux, and Cinnamon learned how-to Wayland?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 Intro09:55 DIY Stream Decks20:38 Rent a Redhat26:43 Silent Hill running on Linux 33:57 Cinnamon learns to Wayland TOPICSPro Not Stream Deck https://interfacinglinux.com/2026/07/13/diy-raspberry-pi-powered-stream-deck-server/RHEL For Life (RTheren)https://www.heise.de/en/news/If-14-years-of-support-aren-t-enough-RHEL-for-eternity-11360882.htmlFog Simulator 1999https://interfacinglinux.com/community/linuxgaming/building-the-silent-hill-pc-port-on-linux/Cinnamon Waylandhttps://9to5linux.com/linux-mints-cinnamon-6-8-desktop-environment-will-fully-support-wayland

The guys are back, this time we talk about our worst and best tech purchases ever! ==== Special Thanks to Our Patrons! ==== https://thelinuxcast.org/patrons/ ===== Follow us

Hey friends! Still your grieving pal over here, but also your swarming friend and Protecting My Network Edge host — because this week I've been tinkering with something called Project Swarm and I've got my diapers on regarding it, but I really, really like what I see so far. Then, fair warning, I flip on the tangent light and verbally barf up some personal stuff at the end. I'll make the hand-off super clear, so if you want your free security podcast to do exactly what you want and nothing else — totally fair, and you won't offend me by hopping off. Here's what we cover: What is Project Swarm? This comes to us from our friends over at GreyNoise. It centers around little sensors you deploy to the edges of your network that you can dress up to look like just about anything — attracting flies to the honey, if you catch my drift. You get more enumeration, insight, and logging into whatever shenanigans those flies are using to poke at your edge. Setup was refreshingly easy: You need a very low-powered VM or hardware device (my understanding is it even works on a Raspberry Pi) mapped to a public IP, plus a free GreyNoise account. You generate an API key, copy-paste a one-line install, and off it goes. I threw mine on a tiny Ubuntu VM. The part where I didn't read the flipping manual: Mid-install my SSH connection dropped and I'm going "what the heck?!" Turns out the installer intentionally moves your real SSH to some arbitrary high port — so you can run a fake SSH honeypot on 22 while your legit connection lives elsewhere. Once I spotted the new port in the console, a quick firewall tweak and I was back in. Profiles give me level 14 giggidies: Once your sensor checks in, you assign it a profile. Vulnerable WordPress, Tomcat, a Cisco AnyConnect VPN, FTP honeypot, SSH honeypot — kind of all the honeypots. I went with a vulnerable WordPress instance. My one complaint: you can only assign one profile per sensor. My dream scenario of an SSH honeypot AND an FTP AND a vulnerable Tomcat all on one box will have to wait (or maybe that'd look too suspicious and scare the baddies off — who knows). The results were wild: Within a couple days I had thousands of connections, several flagged as malicious and tied to known botnets. I could see source IPs, malicious labels, whether they were residential or company or Google, and even download raw packet captures. There's clearly more telemetry to dig into (what people tried to spray into the login portal, etc.) — I meant to go deeper before recording and didn't, so consider this a "to be continued." Why do I care, since I'm not defending some huge infrastructure? Honestly it started as a brain break. But I've been testing a ton of external networks lately and nearly every company site is WordPress — which now powers around 43% of the internet. Running my own WordPress honeypot gives real oomph to those "your out-of-date WordPress is a big deal" conversations, where I can say "I run a WordPress honeypot and here's the aggressive password spraying and plugin/theme enumeration I'm seeing right now." See it, don't just hear it: I show the actual portal, sensor config pages, and more over on 7MinSec.club this week. Why not both, right? It's like that meme. GreyNoise also has a Project Swarm user webinar coming up — check their events page. And to be crystal clear: they are not a sponsor, this is all free, and I just think it's clever. Life update (the tangent portion): About the time you hear this, I'll be on my way to my dad's funeral, where I'm sharing some words and singing a song. I've been practicing like a madman per advice from my music director friend and guitar teacher — including a little brain hack of focusing hard on my fingers to stay a half-step removed from the emotion. And if I cry my face off up there? Who cares. This isn't America's Got Talent; it's the gesture. I'll be honest, 2026 has been a rough one, but I promised two bright spots and here they are: my son Cam (about to finish paramedic school) has been keeping grandpa's spirit alive by wearing my dad's shirts, sunglasses, and Apple watch, and getting a Cessna tattoo with my dad's actual handwriting and birth year. And you all — the kind words, the offers to talk, the shared stories — reminded me there are a whole lot of good people out there. Thank you for that. One more thing on the horizon: My brain's been a squirrel on pixie sticks, but for whatever reason I've been happily grinding the CARTP as a little vacation for my mind. I might take a swing at the exam this week — start it in the evening, grind a few hours, sleep, finish in the morning (I'm too old for 24 hours straight). I might pass, I might fail spectacularly. Either way I'll keep you posted, and if I get the cert, that's probably next week's topic!

This show has been flagged as Clean by the host. 01 Introduction In this episode I will describe how to calculate elapsed time in bash or other shell scripts. While this may sound like a very simple and basic thing to do, there is a slightly more complex aspect to it if you wish to calculate elapsed time to a higher resolution than one second. 02 There are many reasons for calculating elapsed time in a shell script. For example you may wish to simply report how long an operation took to run. Another reason may be that you are trying to speed up a script and need to calculate benchmark data to see how different alternative methods perform. 03 What may seem like a simple task gets a bit more complicated if you want to do it for multiple different operating systems even if they are all unix related, as we shall see. -------------------- 04 Operating Systems Tested For the purposes of this episode, I ran tests on the current version of the following operating systems. Alma Alpine Debian FreeBSD OpenBSD RaspberryPi OpenSuse Ubuntu 2604 Alma is a close copy of Red Hat that we can take as representing Red Hat style distros. -------------------- 05 Simple Low Resolution Timing I will start with the simple and obvious method before describing the less obvious ones. This uses the date command to get the current time in seconds since the unix epoch. This is simply date '+%s' 06 Save this to a variable using whatever method you prefer. For example. starttime=$(date '+%s') 07 Next, do whatever operations it is you wish to time. Use the date command to get the current time again. endtime=$(date '+%s') 08 Now simply subtract the start time from the end time using shell arithmetic. This should be very obvious and basic. -------------------- 09 Higher Resolution Timing However, suppose we wish to measure time to greater than one second of precision. We need to do two things. The first is to obtain the current time at a higher degree of precision. The second is to conduct the calculations to a higher degree of precision. 10 Unfortunately, the standard time precision for POSIX shells seems to be 1 second. Some shells offer a higher precision, but others do not. Furthermore, standard shell arithmatic uses integer, which limits calculations to 1 second of precision. -------------------- 11 Bash High Resolution Shell Variable Fortunately, bash is one that does offer a high precision date. If you are using bash 5.0 or newer, there is a shell variable called EPOCHREALTIME which offers time since the the unix epoch (that is, since the first of January 1970, at 00:00:00 UTC) in seconds to 6 decimals of precision. 12 Example echo $EPOCHREALTIME 1779634800.184926 13 This is related to the similar bash variable known as EPOCHSECONDS which gives the number of seconds since the unix epoch. 14 Example echo $EPOCHSECONDS 1779634800 15 So if you are using bash, measuring time is very simple. -------------------- 16 But is it Really Bash? Is your script however actually using bash? Debian and derivatives actually have two shells. The first, the interactive shell is bash. The second, the non-interactive shell is dash, which stands for "debian almquist shell". 17 If you open a terminal, you get bash. If your script starts with a "bin/bash" shebang line, you get bash. However, if your script starts with a "bin/sh" shebang line, you get dash. Some people find themselves getting caught out by this one when they try something out in a terminal but find that it doesn't work in their script which started with "bin/sh". 18 Many other, but not all, Linux distros use bash for both the interactive and non-interactive shells, so "bin/sh" and "bin/bash" work the same with those ones. So if you intend to use bash, make sure your script calls for bash in the first line. -------------------- 19 The SHELL Variable So how can a script tell what shell it is running under? There is a shell variable called "SHELL" which will tell you the name of the shell. Well, sort of. 20 On Debian and derivatives "SHELL" will say "bash" regardless of whether the actual shell is bash or dash. On some other operating systems "SHELL" will simply say "sh" even if it is something else entirely. So we need to do some additional levels of checking to see what we have. 21 To start with though, here's what each of the test distros reports for SHELL. Alma : bash Alpine : sh Debian : bash FreeBSD : sh OpenBSD : ksh Raspberry-Pi : bash Suse : bash ubuntu2604 : bash -------------------- 22 Bash Versus Dash First, let's try to see which ones are bash and which ones are dash. The first thing we can check is for the shell variable BASH_VERSION. 23 Example echo $BASH_VERSION If the shell is bash, then it will report a version string. If the shell is not bash, then it will return an empty value. 24 Using this test, we can see that Alma and Opensuse are indeed using bash. We however need to check Debian, Raspberry Pi, and Ubuntu when running in an "sh" script. To check this we can use the "which" command to see what "sh" actually is. 25 Example echo $( ls -l $(which sh ) | rev | cut -d" " -f1 | cut -d/ -f1 | rev ) 26 "which sh" shows us the path to "sh" However, that is a link so we need to use "ls -l" to find the actual executable. "rev" reverses the string. 27 "cut" takes the first element separated by spaces. The second "cut" takes the first element separated by the "/" characters. The final "rev" takes that string and reverses it again to get it in the correct order. 28 In the case of Debian, Raspberry Pi, and Ubuntu it tells us that this is "dash". -------------------- 29 Openbsd Openbsd reports its shell as "ksh", which stands for Korn Shell. It is indeed Korn Shell, so we simply leave that one as is. -------------------- 30 Alpine and Freebsd Next we have Alpine Linux and Freebsd, which both report as "sh". In the case Freebsd there doesn't appear to be any further we can go that I am aware of. It's simple "sh". It is a basic POSIX shell which seems to be similar to the original unix shell, the Bourne Shell. Older versions of Freebsd used a different shell known as tsch (the C shell), but I haven't tested that so I will ignore that here. 31 With Alpine Linux however, we can get the actual shell using the same method that we used for Debian Linux. This reports as being "busybox". 32 Busybox is a limited shell intended for use in embedded systems. Alpine was originally an embedded distro, but some people started using it for containers. Alpine is Linux, but it is not GNU/Linux, and there are a number of areas which can trip you up if you are not aware of them. So, be extra careful if you are using it for anything, and test everything. -------------------- 33 Summary of Actual Shells Here is our revised list with the actual shell used when asking for "sh", so far as we can determine. Alma : bash Alpine : busybox Debian : dash FreeBSD : sh OpenBSD : ksh Raspberry-Pi : dash Suse : bash ubuntu2604 : dash 34 There are other shells, but none of them are the default shell for any of the distros on our list, so I haven't tested them. -------------------- 35 Solutions for Measuring Time Now we need to find solutions for bash, dash, ksh, sh, and busybox. -------------------- 36 Bash For bash, we can simply use EPOCHREALTIME, as mentioned above. -------------------- 37 Dash For dash, we can use the date command. This is a very conventional method, and is probably the first answer that anyone would give for this situation. However, while it will work in most cases, it will not work in all cases, so it is not a universal solution. 38 To use date we simply call it with the correct format string. This uses %s to get seconds since the epoch, and %N to get nanoseconds of the current second. If you put a decimal separator between the two it will appear in the output. You can use the correct decimal separator for your locale, but I won't go into that here. Instead I will just assume a period or dot. 39 Example date '+%s.%N' 1779634800.358916385 -------------------- 40 Problems with Date on Alpine and Openbsd Date will work for bash, dash, and sh on Freebsd. However it will not work for ksh on Openbsd, or for busybox on Alpine. 41 With busybox on Alpine, it simply ignores the %N format specifier and prints out the epoch in seconds only followed by the decimal separator. = Example date '+%s.%N' 1779634800. 42 With ksh on Openbsd it prints the epoch in seconds followed by the decimal separator and then the %N as a literal N. date '+%s.%N' 1779634800.N 43 Fortunately we have alternatives for these two cases. -------------------- 44 Openbsd Openbsd has the "ts" or timestamp utility installed by default. ts prints a time stamp in front of every line it receives from standard input. I won't go into details on all aspects of ts here, I'll leave that to someone else. Instead I will focus on how to use it for our specific purposes here. 45 We need to provide a format specifier to ts, which in this case is "%.s" We also need to provide something for standard input, or otherwise ts will simply sit there and wait for input. So what we need to do is to echo nothing through a pipe to ts while also giving ts the proper format specifier. 46 Example echo | ts "%.s" 47 This will output the epoch time in seconds to six decimals of precision. ts is installed in Openbsd and Freebsd by default and can be used in either. It can also be installed in many other distros. -------------------- 48 Busybox on Alpine None of the methods discussed so far will work for busybox on Alpine though. However there is a way, but it's a bit non obvious and somewhat hacky. 49 Busybox includes a command called "adjtimex". This is normally used to adjust the time hardware. However if it is run without arguments, it will report the current settings. 50 These include the current epoch time in seconds , and in another field the time in microseconds. These are reported as key value pairs. So what we need to do is to do the following 51 Run adjtimex Capture the output. Grep for "time.tv_sec" Grep for "time.tv_usec" Use cut to extract the time value in each case. Use tr to get rid of excess spaces in each case. Combine the two in a string with a decimal separator between them. 52 This takes a total of 4 lines of shell script. I will just describe them breifly here, see the show notes for details. 53 First we want to capture the output of adjtimex in a single operation. Run adjtimex and pipe the output through grep to capture lines containing "time.tv_" and save this to a variable. # Extract the current high resolution time from adjtimex. # We want two key value pairs, identified by time.tv_sec and time.tv_usec. tvals=$( adjtimex | grep "time.tv_" ) 54 Next echo the contents of this variable and pipe it through grep, cut, and tr to get first the seconds and then the microseconds while also removing excess spaces. Save these to two separate variables. "time.tv_sec" is the time in seconds since the epoch. "time.tv_usec" is the number of microseconds in the current second. # Get the time since the unix epoch in seconds and micro-seconds. timesec=$( echo "$tvals" | grep "time.tv_sec" | cut -d: -f2 | tr -d " " ) timeusec=$( echo "$tvals" | grep "time.tv_usec" | cut -d: -f2 | tr -d " " ) 55 Adjtimex does not zero pad the microsecond time value to provide leading zeros, so we need to take care of this using printf before we can append it to the seconds value. We didn't need to do this with date where the %N format character does this automatically. In this instance, the printf format string is '%06d' padusec=$( printf '%06d' $timeusec ) Now, combine these into a single number with a decimal separator by using simple string concatenation. # Combine them into a single number. timehires="$timesec"".""$padusec" -------------------- 56 Summary of Methods Let's summarize where we are so far in terms of methods we can use to get the current time as a high resolution number. Alma : use EPOCHREALTIME or date Debian (bash) : use EPOCHREALTIME or date Raspberry-Pi (bash) : use EPOCHREALTIME or date ubuntu2604 (bash) : use EPOCHREALTIME or date Suse : use EPOCHREALTIME or date Debian (dash) : use date Raspberry-Pi (dash) : use date ubuntu2604 (dash) : use date Alpine : use adjtimex and parse the output FreeBSD : use date or ts OpenBSD : use ts -------------------- 57 Other alternatives There are a few alternatives that we haven't discussed yet. 58 Bash with Dash In the case of Debian, Raspberry Pi, and Ubuntu running dash, since bash is available it is possible to write a separate bash script which simply echos EPOCHREALTIME and then call it from the dash script and capture the output. While this would work, there's probably not a lot of point to it. If you can rely on bash being there, then just change the first line of the script and make it a bash script. 59 Adding Packages to Alpine The ts or timestamp utility is a common unix utility that can be installed if it is not present by default. This does produce high resolution timestamps on Alpine. On Alpine Linux this comes as part of the "moreutils" package. To add the package, use the following sudo apk add moreutils echo | ts "%.s" 1779634800.959948 60 You can also add the GNU coreutils, which will provide a high resolution date command which works like in the other examples. To add the package use the following sudo apk add coreutils date '+%s.%N' 1779634800.212897332 61 If you can install more packages into your Alpine system, either of the above two is probably going to be preferable to parsing the output of adjtimex. 62 Custom Timestamp Programs You can also write a very short program in python, perl, tcl, or some other language and have it output the current epoch time. I won't discuss that here though. -------------------- 63 Calculating Time Differences Shell arithmetic is integer only. If we wish to use high resolution timing data, we need to do something so we don't lose the precision we have worked so hard to get. There are several possible solutions. 64 Change the Time Base One method is to change the time base from seconds to milli, micro, or nanoseconds. This can be done by simply multiplying the time values by the appropriate amount (e.g. 1000, 1,000,000, etc.) before subtracting them. This allows for integer arithmetic on high resolution values without losing precision. 65 Use the Shell bc Arbitrary Precision Calculator The bc command line calculator will perform calculations using real numbers and is easy to use in scripts. It is present by default in most distros. echo "scale=9; $endtime - $starttime" | bc where endtime and starttime are variables containing time values. 66 However, for some inexplicable reason, neither Debian nor Opensuse install it by default. It is present in Ubuntu and Raspberry Pi which are Debian derivatives, and it can be added to distros which lack it. 67 Use awk awk can also perform calculations using real numbers and it is present in nearly all distros including in all of the ones we tested here. echo "$endtime $starttime" | awk '{printf "%.6fn", $1 - $2}' -------------------- 68 Benchmarks And of course no comparative evaluation would be complete without benchmarks where we see how each method compares to another in terms of speed. In the benchmark test I ran each method in a loop through multiple iterations, measured the elapsed time, subtracted out the time for an empty loop, and then compared it to alternate methods. For anything other than EPOCHREALTIME, the empty loop time is negligible and has no real effect on the results. 69 Rather interestingly I came across a bug which caused date to run very slowly if called immediately after using EPOCHREALTIME in bash. The effect of the bug was to make the date benchmark test roughly 24 times slower. This has been fixed in newer releases, but if you are using an older distro release then beware of this bug. I was able to get around it either putting a sleep delay between benchmarking EPOCHREALTIME and benchmarking date, or by simply testing date before testing EPOCHREALTIME. 70 To be able to conduct additional tests I installed ts in Ubuntu and Alpine, and the GNU version of date in Alpine. 71 EPOCHREALTIME Versus date in Ubuntu 2604 bash The EPOCHREALTIME method is 3103 times faster than date. However, when the same test is run on Ubuntu 2404 when the date test is run before the EPOCHREALTIME test, EPOCHREALTIME is 1240 faster than date. Other Linux distros show performance to Ubuntu 2404. It appears that a side effect of fixing whatever the bug is has the effect of slowing down date. However, this is probably not a significant issue in normal circumstances. 72 date versus ts in Ubuntu 2604 bash The date method is 3.7 times faster than ts 73 date versus ts in Ubuntu 2604 dash The date method is 4.9 times faster than ts 74 date versus ts in Freebsd sh The date method is 2.5 times faster than ts 75 date versus adjtimex in Alpine Busybox The date method is 6.0 times faster than adjtimex 76 date versus ts in Alpine Busybox The date method is 20.0 times faster than ts 77 bc versus awk in Ubuntu 2604 I compared calculating the difference between two numbers when using bc versus awk. The difference is negligible, with bc being only 7% faster than awk. 78 Conclusion for Benchmarks Based on these results, if you need to measure elapsed time to high resolution and care about runing the command with as little overhead as possible, then the order of preference should be the following. 79 If you are using a newer version of bash, then use EPOCHREALTIME. If that is not available, then use date, provided it allows for high resolution times. If the above two cannot be used, then use ts. If you are using Busybox and cannot install either GNU date or ts, then use adjtimex. Date is the closest in terms of being the universal portable solution, but it does not work in all cases. 80 I have not compared different platforms to each other in terms of performance, as that would be a much more involved problem that is outside the scope of this episode. However, different operating systems implement different commands in different ways. 81 For example, on Openbsd and Freebsd, ts appears to be an ELF binary. That is, it is executable machine code, possibly written in C. On Ubuntu however, ts appears to be a perl script. As a result of this, the advantage that date has over ts is much less in Freebsd than it is with Ubuntu (and likely other Linux distros) as on Freebsd it doesn't need to load a perl interpreter to run ts. -------------------- 82 Overall Conclusion You no doubt thought that measuring elapsed time was going to be so simple, and how could someone get an entire podcast out of such a simple subject? And yet here we are half an hour later with just a basic overview of the subject. 83 I hope you found this interesting and informative. Please let us know in the comments if you think that I have done anything incorrectly, or if you have another way of doing things. I hope to see you all again in another future episode of HPR. -------------------- Provide feedback on this episode.

This week Shawn Tierney meets up with Adam Cumick of Synergy Logix to discuss their Modbus TCP SLM-MX I/O as well as their soon to be released Raspberry Pi Based, OpenPLC Compatible SLM-RP4 controller in this episode of #TheAutomationPodcast. Show Notes: Special thanks to Adam for coming on the show, and to Synergy Logic for sponsoring this episode. To learn more, please visit the below link: Synergy-logic.com Until next time, Peace ✌️ Shawn M Tierney Technology Enthusiast, Content Creator, and Automation Instructor

The guys are back, this time we do some news from the world of FOSS ==== Special Thanks to Our Patrons! ==== https://thelinuxcast.org/patrons/ ===== Follow us

In this episode, Hackaday editors Elliot Williams and Tom Nardi start off by taking a trip down the Raspberry Pi memory lane and then tackle a fresh pile of listener mail. The discussion moves on to hacking bike counter, homebrew upgrades to the Nintendo Entertainment System, and building RAM from whats in the parts bin. You'll hear about the latest drop-in upgrade for a classic Casio watch, hosting light bulbs that host subversive literature, and loading Wii U games from a weird disk drive from the 1980s. They'll wrap things up with a dive into the evolving portrayals of brilliant rebels in media, and all the things you can do with a cheap router. Check out the links over on Hackaday if you want to follow along, and as always, tell us what you think about this episode in the comments!

Topics covered in this episode: Backup Docker volumes locally or to any S3 Pyodide 314.0 Release nb-cli: A Command-Line Interface for AI Agents and Notebook Automation Hindsight Agent Memory That Learns Extras Joke Watch on YouTube About the show Sponsored by us! Support our work through: Our courses at Talk Python AWS Community Day Midwest tomorrow Wednesday the 24th in downtown Indianapolis, Six Feet Up is sponsoring and there are 2 Sixies presenting Connect with the hosts Michael: Mastodon / BlueSky / X / LinkedIn Calvin: Mastodon / BlueSky / X / LinkedIn Show: Mastodon / BlueSky / X Join us on YouTube at pythonbytes.fm/live to be part of the audience. Usually Tuesday at 7am PT. Older video versions available there too. Finally, if you want an bonus digest of every week of the show notes in email form? Add your name and email to our friends of the show list, we'll never share it. Michael #1: Backup Docker volumes locally or to any S3 Via Bryan Weber (thanks Bryan!), who spotted it over on Virtualization HowTo. Find Bryan at bryanwweber.com. offen/docker-volume-backup is a lightweight companion container that backs up the volumes your apps actually depend on, then ships them somewhere safe. It's tiny: written in Go and about 25MB compressed, roughly 1/20th the size of the shell-based image (jareware/docker-volume-backup) that inspired it. Drop it into your docker compose file as a backup service, mount the volumes you care about as read-only, and you're off. Push backups to a pile of destinations: a local directory, plus any S3, WebDAV, Azure Blob Storage, Dropbox, Google Drive, or SSH-compatible target. Mix and match as many as you want in one run. Recurring cron-style backups in a Compose setup, or one-off backups straight from the Docker CLI. Production-friendly touches worth calling out: Rotates away old backups so you don't quietly fill the disk. GPG encryption for your archives. Notifications on finished and failed runs (so you find out about failures before you need the backup). Stop a container during backup for a consistent snapshot using a simple docker-volume-backup.stop-during-backup=true label, then auto-restart it. Run custom commands during the backup lifecycle (great for a database dump before the file copy). Docker Swarm support, plus arm64 and arm/v7 builds. Hello, Raspberry Pi homelab. Fun aside from Bryan: he searched our back catalog for this tool and the search came back so fast he thought it hadn't run. Love to hear it. Calvin #2: Pyodide 314.0 Release PEP 783 is the real news — Pyodide maintainers used to hand-build 300+ packages. Now anyone can publish Pyodide wheels to PyPI with cibuildwheel. The version jump from 0.29 to 314.0 is intentional — it now tracks the Python version, so 314.x = Python 3.14. Binary compatibility is locked per Python cycle, meaning packages you build today won't break on the next Pyodide release. sqlite3, ssl, and lzma are back in the default stdlib — no more await pyodide.loadPackage("sqlite3"). Bigger download, but a much smoother experience for newcomers. bigint precision bug is fixed — values above 2^53 were silently losing precision when crossing the Python/JS boundary. The new JsBigInt type makes the roundtrip correct. Worth flagging if anyone is doing numeric work in a browser app. Experimental TCP sockets in Node.js — you can now connect Pyodide to a real database (MySQL, PostgreSQL, Redis tested) when running server-side. Blurs the line between "Python in the browser" and "Python runtime anywhere Wasm runs." Michael #3: nb-cli: A Command-Line Interface for AI Agents and Notebook Automation From Piyush Jain (Jupyter and LangChain maintainer) on the Jupyter blog: nb-cli: A Command-Line Interface for AI Agents and Notebook Automation. nb-cli is an experimental, Rust-based CLI to read, write, execute, and search Jupyter notebooks. The premise: agents are great at CLIs but terrible at hand-editing the nested JSON in an .ipynb, so let them operate on the notebook from the outside instead of running inside it. Works with or without a Jupyter server. No server? It reads/writes .ipynb files directly and talks to kernels over ZeroMQ. Connected to a live JupyterLab, your edits show up instantly via Y.js (the same CRDT Jupyter uses). Smart output format: instead of token-heavy JSON or ambiguous plain markdown, it uses @@cell / @@output sentinels with inline metadata. Less wasted context, unambiguous structure, and it degrades gracefully on truncation. The payoff is composability. "Add a summary section and run it" becomes one shell pipeline instead of six agent tool calls. And nb search notebook.ipynb --with-errors returns only the failing cells, so the agent skips the cells that worked. Claude Code tie-in: it ships as an agent skill. npx skills install jupyter-ai-contrib/nb-cli and your agent can drive notebooks via nb. Out of jupyter-ai-contrib, which aims to become an official Jupyter AI subproject. Still early (crates.io is at v0.0.5), so kick the tires before anything load-bearing. See also marimo-pair. Calvin #4: Hindsight Agent Memory That Learns AI agents forget everything between sessions — Hindsight gives them persistent memory that learns over time Simple three-method API: retain(), recall(), reflect() — store, retrieve, and reason over memories TEMPR retrieval runs semantic, keyword, graph, and temporal search in parallel for accurate results Automatically consolidates related facts into durable observations instead of piling up duplicates pip install hindsight-all runs the entire server in-process; integrates with LangChain, LlamaIndex, Pydantic AI, CrewAI, and more Extras Calvin: Clanker: A Word For The Machine **Ponytail — You know him. Long ponytail. Oval glasses. Has been at the company longer than the version control** **Klangk: Multi-User AI Sandboxing, Collaboration and Coding Platform** Cursor announces Origin performative-ui to quick start your new idea Michael: Astral Joins OpenAI: The Interview SpaceX to acquire Cursor And OpenAI renews Open Source support Portuguese subtitles are now available for Talk Python courses DSF is hiring including Six Feet Up support Joke: Oh Babe…

We're back! Tonight we're doing something special! We finally discuss the results of our challenge from the WHEEL of DOOM! ==== Special Thanks to Our Patrons! ==== https://thelinuxcast.org/patrons/ ===== Follow us

Steam Deck price rises point toward high prices for the new Valve hardware, Lenovo puts its name to a cheap retro handheld and regrets it, Wikipedia management seems to be acting like a typical big tech company and the workers are organising, Bambu pisses off its 3D printer customers and Joe got given a free unrelated 3D printer, and we don’t believe that the Raspberry Pi 6 will arrive as late as 2028. News Steam Deck back in stock, with updated pricing The golden age of handheld gaming is already over [archived] Lenovo pulls its controversial G02 retro handheld from sale – starting a chain reaction that could decimate the retro gaming market Sellers circumvent Lenovo's retro handheld ban with cheap wholesale storefronts Big Tech's Anti-Labor Playbook Has Come for Wikipedia We’re Wiki Workers United, a global solidarity union for the staff of the Wikimedia Foundation Wikipedia editors plot strike and banner sabotage after Wikimedia layoffs Comprehensive Response to Bambu’s AGPLv3 Violations – Software Freedom Conservancy ‘Fuck you, Bambu': How one private message could change the face of 3D printing [archived] No Raspberry Pi 6 before 2028 Don't expect a Raspberry Pi 5 in 2023, says Eben Upton [21st Dec 2022] Introducing: Raspberry Pi 5! [28th Sep 2023] See our contact page for ways to get in touch. RSS: Subscribe to the RSS feeds here

Three Big Conversations: The OKC Thunder have become the NBA's favorite villain - 10:00 Pope Leo publishes an AI manifesto - 20:14 The Mandalorian and Grogu had a disappointing first weekend. - 35:50 → Help us improve our podcast! Click here to fill out this three-minute survey. Song of the Week - "the cure" by Olivia Rodrigo - 3:16 → Click here to read the lyrics → Click here to listen to the song (language) In Other News: - 42:40 Small "dot cakes," baked in cups, and covered in frosting and rainbow nonpareil sprinkles, are going viral. The colorful aesthetic of these cakes is just half of the appeal, with the other part being the satisfying scrape of a spoon being dragged across the top.  A new YPulse report found that 87% of 13- to 24-year-old guys agree with the statement, "I am a gamer," suggesting that online gaming continues to be one of the fastest-growing social spaces for boys and young men. A newly published report from the American Bible Society found that 38% of parents are regularly engaged with the Bible, as opposed to 23% of nonparents. A ton of other interesting statistics are included in the latest chapter of their State of the Bible report, linked here. DIY "cyberdecks" are the latest tech trend on TikTok. Creators are using Raspberry Pi mini computers to build whimsical homemade devices inside of retro purses, Game Boys, or briefcases. Off Campus has become Gen Z's latest #BookTok-adapted TV obsession, landing as Prime Video's biggest debut ever among viewers aged 18-34. Common Sense Media flagged the series for extreme explicit sexual content.

Stewart Alsop sat down with Michael Shackelford to discuss their experiences building applications through vibe coding—the practice of using AI to create software without traditional programming expertise. Stewart, who runs the AI Whispers community in Buenos Aires and hosts the Crazy Wisdom podcast (with over 660 interviews), shared how he went from teaching people prompt engineering to building his own video conferencing software as a Riverside.fm replacement, while Michael opened up about his year-long journey creating Genrupt Inc, an AI-powered content generation tool for e-commerce sellers. The conversation covered everything from the decline in quality of Claude's reasoning capabilities and how Chinese companies used distillation attacks to copy Anthropic's models, to the importance of spaced repetition systems for managing knowledge in the age of LLMs, with both sharing battle-tested prompting strategies like asking AI to "explain it to me in genius terms" and using deep research queries to reverse engineer how competitors build their products.Show Notes:- Dan Martell's book "Buy Back Your Time" was mentioned as one of the best business books for thinking about life and business- Check out John Vervaeke's "Awakening from the Meaning Crisis" for understanding relevance realization and why AI fundamentally cannot determine what's relevant to humans without being toldTimestamps00:00 Michael discusses being exhausted from getting his app ready for launch, working nonstop with AI to prepare landing page for podcast traffic driving beta signups05:00 Stewart explains starting AI Whispers in Buenos Aires after leaving OpenAI vendor company, meeting early adopters like Torin who was building mind-reading EEG technology10:00 Discussion of how corporations resist AI adoption due to political games and job security fears while some companies use AI as excuse for pandemic-era layoffs15:00 Stewart describes teaching workshops on using LLMs as linguistic tools rather than coding tools, noting technical people often lack humanities background needed for prompting20:00 Explaining chatbot wrappers, API calls, and how Anthropic's reasoning quality declined after Chinese distillation attacks copied their secret sauce developed with philosophers25:00 Technical discussion of model training, fine-tuning versus RAG for new information, and different approaches to updating AI knowledge beyond initial training30:00 Stewart describes building podcast recording software to replace expensive Riverside, struggling with syncing audio and video files across different computer clocks35:00 Discussion of critical factors in vibe coding, discovering unknown technical requirements, and how AIs don't automatically reveal missing information40:00 Stewart's reverse engineering process using deep research function to study competitors' hiring and technology stacks, separating planning agents from coding agents45:00 Prompting techniques including "explain like I know everything" and using spaced repetition systems to capture valuable prompts and technical knowledge50:00 Michael explains his Generux app for generating ecommerce content using Amazon review data analysis to inform high-converting listing images and videos55:00 Discussion of founder mentality involving self-delusion about project timelines, Michael working nine-plus hours daily for nine months on app development60:00 Comparing Amazon's expert software to prosumer software approach, discussing distribution challenges and future robotics applications for customized products65:00 Stewart demonstrates spaced repetition app for memory improvement and knowledge retention, explaining relevance realization problem that AI agents cannot solve without embodimentKey Insights1. Stewart Alsop started AI Whisperers in Buenos Aires after leaving his role at Invisible Technologies, which was OpenAI's largest vendor for RLHF work. He noticed that machine learning engineers at tech companies lacked the humanities background needed to properly interact with large language models, which are fundamentally linguistic tools. This led him to create weekly workshops teaching non-technical people how to use AI effectively, running events every Thursday for two years straight. The group attracted intense geeks from the start and eventually led to Stewart speaking right after Vitalik Buterin at DevConnect, marking a significant milestone for the community.2. Large corporations are resistant to AI adoption due to multiple factors including political dynamics within organizations and employees fearing job loss. Many companies that grew during the pandemic are now using AI as an excuse to downsize when the real issue is inefficiency from rapid expansion. Stewart observed that even technical people in machine learning often don't understand how to properly use AI tools because they lack linguistic and humanities training. The fundamental problem is educational, requiring companies to train people how to use these new tools while those same people resist learning them.3. Vibe coding has evolved significantly with Claude Code being a game changer that reduced the technical barrier to entry. Before Claude Code, developers needed substantial technical knowledge to work through constant doom loops and debugging cycles. The success of coding AI tools stems from thirty years of testing infrastructure that provides clear yes or no feedback on whether code works. This infrastructure doesn't exist in the same way for manufacturing, science, and other fields, which is why software became the dominant area for AI assistance initially.4. Claude's quality degradation over recent months resulted from multiple factors including distillation attacks by Chinese companies who reverse engineered Anthropic's reasoning capabilities. Anthropic had hired philosophers, sociologists, and psychologists to develop exceptional reasoning in Claude 4.5, but this was expensive to run. When Chinese models like Kimi copied these capabilities at one tenth the cost, and when mainstream users flooded the platform before Anthropic's planned IPO, the company had to reduce quality to manage computational costs. This represents a significant loss for power users who relied on Claude's superior reasoning abilities.5. Stewart built a podcast recording application to replace Riverside because he needed API access to automate workflows, which Riverside wanted one thousand dollars monthly to provide. The technical challenge involves syncing audio and video from local recordings on multiple computers with different clocks through a server, then merging them so voices match lip movements. This problem requires understanding complex timing issues across different network conditions and file formats. Stewart has been working through AI psychosis for months on this FFMPEG pipeline problem, illustrating how vibe coding still requires building intuition about technical problems even without traditional coding knowledge.6. The transition from expert software to prosumer software represents a major opportunity for AI-enabled tools. Expert software like Photoshop, Blender, and terminal interfaces have extreme complexity that intimidates beginners, but AI is making these capabilities accessible through natural language. The reign of specialists is ending as generalists with broad knowledge and curiosity can now build complete applications by leveraging AI to fill technical gaps. This shift particularly benefits entrepreneurs and founders who specialize in getting into difficult situations and figuring them out, even when they originally thought tasks would be easier than they turned out to be.7. Building applications with AI requires accepting massive time investments beyond initial estimates and developing strategies for overcoming knowledge gaps. Michael estimated his ecommerce content generation app would take months but spent nearly a year working over nine hours daily, while Stewart spent months solving audio-video sync issues. Success requires using tools like deep research to understand how competitors solve problems, maintaining separate planning and coding agents, and learning to ask the right questions. The key insight is that vibe coders can achieve ninety percent of functionality independently, but the final ten percent often requires understanding specific technical concepts that AI cannot intuit without proper context and domain knowledge.

The OKC Thunder have become the NBA's favorite villain, Pope Leo publishes an AI manifesto, and The Mandalorian and Grogu had a disappointing first weekend. → Help us improve our podcast! Click here to fill out this three-minute survey. Song of the Week - "the cure" by Olivia Rodrigo → Click here to read the lyrics → Click here to listen to the song (language) In Other News: Small "dot cakes," baked in cups, and covered in frosting and rainbow nonpareil sprinkles, are going viral. The colorful aesthetic of these cakes is just half of the appeal, with the other part being the satisfying scrape of a spoon being dragged across the top.  A new YPulse report found that 87% of 13- to 24-year-old guys agree with the statement, "I am a gamer," suggesting that online gaming continues to be one of the fastest-growing social spaces for boys and young men. A newly published report from the American Bible Society found that 38% of parents are regularly engaged with the Bible, as opposed to 23% of nonparents. A ton of other interesting statistics are included in the latest chapter of their State of the Bible report, linked here. DIY "cyberdecks" are the latest tech trend on TikTok. Creators are using Raspberry Pi mini computers to build whimsical homemade devices inside of retro purses, Game Boys, or briefcases. Off Campus has become Gen Z's latest #BookTok-adapted TV obsession, landing as Prime Video's biggest debut ever among viewers aged 18-34. Common Sense Media flagged the series for extreme explicit sexual content.

This Week In Startups is made possible by:Render - render.com/twistDeel - deel.com/twistNorthwest Registered Agent - northwestregisteredagent.com/twistToday's show:The "Ryanair of drone delivery" just raised $50 million and plans to bring its technology from Europe to the United States. Manna founder Bobby Healy explains to TWiST how his Dublin-based company completed 300,000 deliveries while some rivals are still publishing blog posts, and why low-cost airline economics will decide who wins the autonomous skies.Sticking to the drone theme, TWiST welcomed Theseus co-founder Ian Laffey, who called in from Kyiv to tell us about his company's drone guidance system. It runs off a simple camera and Google Maps. The technology could rewrite the modern, GPS-jammed battlefield, and bring more firepower to smaller nations fending off larger foes.Guest Links:Manna https://www.manna.aeroBobby Healy https://www.linkedin.com/in/bhealy/Manna funding announcement https://www.manna.aero/blog/series-bTheseus https://www.theseus.us/Ian Laffey https://www.linkedin.com/in/ilaffey2/Most recent Theseus funding announcement https://techcrunch.com/2025/04/17/defense-tech-theseus-landed-y-combinator-the-us-special-forces-and-4-3m-from-a-tweet/The tweet that kickstarted Theseus: https://x.com/ilaffey2/status/1759353732075294766Timestamps:0:00 Bobby Healy of Manna joins TWiST1:41 How a Manna base works: drones migrate around the city like Waymos7:18 Battle-hardened in Irish weather: 97% uptime in wind and rain8:52 Margin-positive economics & the path to $0.20 per delivery9:25 Northwest Registered Agent: Get more when you start your business with Northwest. In 10 clicks and 10 minutes, you can form your company and walk away with a real business identity — Learn more at https://northwestregisteredagent.com/twist12:32 $50M Series B vs competitors raising $600–800M19:51 Deel - Founders scale faster on Deel. Set up payroll for any country in minutes, hire anyone anywhere, get visas handled fast, and get back to building. Visit https://deel.com/twist to learn more.22:53 The peer-to-peer drone future and hyper-local commerce25:46 Growing from 170 to 570 people and moving manufacturing to Oklahoma28:43 Ian Laffey of Theseus joins TWIST29:57 Render: Find out why 5 million developers are already using the all-in-one cloud platform, Render. Go to https://render.com/twist and apply for the Render Startup Program to get $500-$100,000 in free credits, depending on your stage and backers.30:58 Inside Ukraine's drone industry: front-line iteration and free-market speed33:55 How GPS gets jammed across the spectrum35:10 Theseus's approach: cameras + satellite maps + ML37:04 The product: Raspberry Pi, SD card, camera — pretending to be GPS49:02 Ukraine: 6–8M drones a year. The US: 300K over two years.51:17 Are US drone primes actually reconstituting the supply chain?58:22 Y Combinator as a defense tech accelerator59:40 "Pick an issue and start working as hard as you can towards it"Subscribe to the TWiST500 newsletter: https://ticker.thisweekinstartups.comCheck out the TWIST500: https://www.twist500.comSubscribe to This Week in Startups on Apple: https://rb.gy/v19fcpFollow Lon:X: https://x.com/lonsFollow Alex:X: https://x.com/alexLinkedIn: ⁠https://www.linkedin.com/in/alexwilhelmFollow Jason:X: https://twitter.com/JasonLinkedIn: https://www.linkedin.com/in/jasoncalacanisCheck out all our partner offers: https://partners.launch.co/Great TWIST interviews: Will Guidara, Eoghan McCabe, Steve Huffman, Brian Chesky, Bob Moesta, Aaron Levie, Sophia Amoruso, Reid Hoffman, Frank Slootman, Billy McFarlandCheck out Jason's suite of newsletters: https://substack.com/@calacanisFollow TWiST:Twitter: https://twitter.com/TWiStartupsYouTube: https://www.youtube.com/thisweekinInstagram: https://www.instagram.com/thisweekinstartupsTikTok: https://www.tiktok.com/@thisweekinstartupsSubstack: https://twistartups.substack.com

Get ready for another unforgettable episode of the Wise_N_Nerdy podcast as Charles and Joe welcome back returning guest Todd Sarner for a conversation packed with gaming debates, parenting wisdom, music industry stories, anime discussions, and the kind of chaotic humor fans have come to love. The episode kicks off with the Question of the Week: “Do you like that games do cosmetic-only purchases, or would you prefer game-changing content?” The hosts quickly find common ground, passionately agreeing that games should never allow players to buy a competitive advantage. From battle passes to microtransactions, the discussion dives into the modern gaming landscape and why cosmetic-only monetization feels far more fair to players who value skill and balance over pay-to-win mechanics. With the traditional roll of the dice, the episode launches into a barrage of Bad Dad Jokes, courtesy of Joe's middle child, Bob. The jokes come fast, the groans come faster, and the entire segment perfectly captures the wholesome chaos that defines Wise_N_Nerdy humor. Next comes the heartfelt “How Do I…?” segment, where the hosts discuss an important topic for parents everywhere: not letting pride get in the way of being a good parent. Through honest conversation and personal insight, Charles, Joe, and Todd explore how humility, communication, and admitting mistakes can strengthen relationships with your kids and help families grow together. The dice then guide the show into the thoughtful “Parliament of Papas” segment, featuring a question from community member MithrilBiata about fostering independence for a cousin with AuDHD. The hosts approach the discussion with empathy and care, sharing perspectives on encouragement, patience, and creating supportive environments that empower neurodivergent individuals while still respecting their unique challenges and strengths. From there, the episode shifts into the fan-favorite “Daddy, Tell Me A Story” segment, where Todd Sarner shares incredible memories from his time working as a roadie for Metallica. From behind-the-scenes chaos to unforgettable concert experiences, Todd's stories offer a rare glimpse into life on the road with one of the biggest bands in music history. Finally, the episode wraps up with the always entertaining “What Are You Nerding Out About?” segment. Joe shares his excitement about setting up a Raspberry Pi project to host a bot he created for the Digital Media Track Discord server. The bot, hilariously named Quasar—short for Questionably Useful Automated Scheduling Assistant Robot—perfectly embodies the nerdy creativity at the heart of the show. Meanwhile, Todd talks about using manga as a tool to improve his Japanese language skills, specifically mentioning Erased. In a perfect moment of synchronicity, Charles reveals that he had just finished watching the Erased adaptation that same week. Charles also shares exciting updates about how things are finally coming together between his six-month contract work and his Sunday morning gig, bringing the episode to a hopeful and uplifting conclusion. This episode is a perfect blend of gaming culture, fatherhood, fandom, humor, and heartfelt conversation. Whether you're here for the nerdy discussions, the parenting insights, or Todd's incredible stories from the music world, there's something for everyone. So settle in, share a laugh, and don't forget to Find your FAMdom. Learn more about Todd Sarner over at http://transformativeparenting.com Wise_N_Nerdy: Where Fatherhood Meets Fandom Learn more about your ad choices. Visit megaphone.fm/adchoices

Sam Altman took the stand this week to defend himself and his company against a lawsuit by Elon Musk. The three-week long trial has featured some of the biggest names in Silicon Valley, including Microsoft's CEO Satya Nadella and OpenAI cofounder and former chief scientist Ilya Sutskever. As the trial nears its end, Danny Fortson and Katie Prescott talk about why the stakes are so high and debate whether this is a case of sour grapes, or if OpenAI did actually “steal a charity” from Musk. Plus, the founder of Raspberry Pi on the future of AI and how he feels about his microcomputer being used to power AI agents such as OpenClaw.Get in touch: techpod@thetimes.co.ukProducer: Marnie DukeExecutive Producer: Priyanka DeladiaImage: Getty Hosted on Acast. See acast.com/privacy for more information.