Podcasts about README

We Like Shooting We Like Shooting - Ep 676 August 17, 2026 Presented by This episode of We Like Shooting is brought to you by: Foxtrot Mike (Code: WLSISLIFE) C&G Holsters (Code: WLSISLIFE) Gideon Optics (Code: WLSISLIFE) Midwest Industries (Code: WLSISLIFE) Blue Alpha Night Fision (Code: WLSISLIFE) Otis Technology (Code: WELIKESHOOTING15) Giveaways!! GAW   Text Dear WLS or Reviews +1 743 500 2171 Public   Show Titles   Gear Chat Note Montana Knife Company stoned goat ultrahttps://www.montanaknifecompany.com/products/stoned-goat-ultra EAA Corp. Girsan Witness2311 CMX XXX Discover the Witness2311 CMX XXX, a compact double stack 1911 with 16+1 capacity, a slim grip, firing pin block safety, and two-tone finish. The Girsan Witness2311 CMX XXX is a compact single-action 9mm pistol from EAA Corp. with 16+1 capacity using Check-Mate magazines. It features an RMSc-footprint optic-ready slide, 3.4-inch coned barrel, two-tone Cerakote finish, low-profile 3-dot sights, ambidextrous thumb safety, 4-slot Picatinny rail, and EAA limited lifetime warranty. Availability: Available for purchase via Add to Cart on eaacorp.com (no explicit stock, release date or additional retailers stated) Cost: $899 Special: Streamlined compact grip with aggressive texturing, low-profile magwell, and automatic firing pin block safety replacing traditional grip safety for 16+1 capacity without added bulk Odysee (Nick) SecondWatch FTN.6 Suppressor Pack Update: We received overwhelming feedback that people did not like the text. The intention was to save on what needed to be engraved. Since it is so unpopular, all text has been removed from the model… The FTN.6 Suppressor Pack is a downloadable set of 3D-printable files for DIY suppressors released by SecondWatch on August 15, 2026, via Odysee. It includes updated designs for rimfire, 5.56, and 300 BLK models that are described as the quietest FTN variants to date, matching or surpassing many commercial suppressors in head-to-head testing. The pack continues the FTN (Fuck The NFA) series focused on accessible, low-cost polymer printed silencers. Availability: Released August 15, 2026 on Odysee (@SecondWatch); downloadable files Special: FTN.6 Air is a very lightweight (~10.6 oz) and slim rifle suppressor using thread adapters; modular flash hider and compensator add-ons; FTN.6 Rimfire offers similar sound reduction to FTN.5 but in a smaller package Defiance Machine (Nick) Defiance Machine Deviant Comp Rifle Action Deviant COMP – The new standard for PRS competitors. The Deviant COMP refines our popular Deviant model into a purpose-built precision rifle action designed specifically for PRS competitors who demand speed, consistency, and reliability under pressure. Built with the features competitive shooters actually want, the Deviant COMP features an oversized bolt for fast cycling, an AW magazine cut compatible with both AW and AICS magazines, and guaranteed headspace for repeatable accuracy and hassle-free builds. This makes the Deviant COMP a competition-ready package that is ideal for PRS. Finished with nitride included at no additional cost, the Deviant COMP delivers premium performance at an exceptional value. Specifications Integral scope mount/rail. Integral recoil lug. Defiance swept legacy bolt design. Oversized competition bolt knob. Smooth chrome-moly bolt action with anti-bind design. Recessed bolt lugs, Mini-16 extractor, and plunger ejector. AW magazine cut. Trigger pins included. Nitride finish included. Why choose the Deviant COMP? PRS competition-ready feature set. Integral rail and recoil lug means more rigidity and reliability when it matters most. Receiver is made from once piece of pre-hardened aircraft-certified 416 stainless steel, allowing for tight manufacturing tolerances and increased performance. One-piece legacy bolt, machined to exacting tolerances required to cycle as smooth as possible. Swept bolt handle design to allow plenty of clearance with your rifle scope. Precision extraction system that significantly increases initial extraction and improves smooth bolt cycling. Need an extra bolt? Extra bolts are available when purchasing your action over the phone with our team for $495 each (includes extractor, ejector, and fire control assembly). The Deviant Comp is a purpose-built short-action bolt-action receiver from Defiance Machine, refined from the standard Deviant for PRS competitors. It is machined from a single piece of pre-hardened 416 stainless steel with an integral scope rail and recoil lug for rigidity and guaranteed headspace. It features an oversized competition bolt knob, swept bolt handle, anti-bind design, AW/AICS magazine compatibility, nitride finish, and a smooth chrome-moly bolt with recessed lugs, Mini-16 extractor, and plunger ejector. Availability: Available through retailers including Red Hawk Rifles (add-to-cart with options) and Altus Shooting (currently out of stock for specific variants like RH/308) Cost: $1,495.00 Special: PRS-optimized with oversized bolt for fast cycling, AW magazine cut compatible with AW and AICS, integral rail/lug for rigidity, and included nitride finish at no extra cost 270 Videos Removed from YouTube for FRN and WLS in Recent Days 270 videos removed from youtube for FRN and WLS in the last several days. Supplementary Research: Firearms Radio Network (FRN) produces multiple gun-related podcasts including the long-running We Like Shooting (WLS) show, which features discussions on firearms, gear, training, and current events. The claim states that 270 videos associated with these channels were removed from YouTube over several days in 2026. YouTube's enforcement actions in 2026 have included widespread removals tied to updated policies on AI-generated content, community guidelines, and monetization standards, with millions of videos and channels affected platform-wide. Gun Fights Play the best Price Is Right-style GunBroker game on the internet. Gun Fights Live DisplayFollow the game, prices, and reveals as they happen.Open the live display BangRank A live cast ranking segment for anything and everything in the gun world, powered by questionable certainty, strong opinions, and audience voting. BangRank Live VotingScan or open the link to rank along with the show.https://welikeshooting.com/rank   WLS is Lifestyle GunCAD Index 2011 OPTICS MAXXING by Foaps Files Designed specifically for the Nightalliance 2011 Maxxing frames. There are two styles to choose from and six different optic mounting patterns. Each … This is a 3D model release on GunCAD Index containing STEP and STL files for optic mounts designed specifically for Nightalliance 2011 Maxxing frames. It offers two styles, six optic mounting patterns (including ACRO, Docter-Noblex, Pic Rail, RMR, RMSc, T1-T2), Gas Pedal and Non-Gas Pedal variants, plus length options for Full, Commander, and Short frames. The page serves as an indexed preview only; actual files must be acquired from the original source. Why it Matters: Enables precise red-dot integration on custom 2011 pistols in the growing 3D2A community, allowing shooters to upgrade iron-sight platforms with modern optics without factory limitations. The Vibe: Clean, modular CAD aesthetic with purposeful engineering details—gas pedal extensions, multi-pattern plates, and frame-specific lengths that emphasize performance-oriented customization over factory aesthetics. Hot Take: In the 2011 maxxing scene, bolting a quality optic directly to a printed or custom frame is now the baseline, not an afterthought. GunCAD Index Freedomware Sedco SP22:8 SPEDBRO SP22 Printable 22LR Pistol Don't like the standard Jennings J22? Well here's his neglected brother, the Sedco SP22. A knockoff of the already trash J22. NOT FOR DISTRIBUTION O… The SPEDBRO SP22 is a 3D-printable knockoff of the Sedco SP22 / Jennings J22 design by FreedomWare. It is a rimfire 22 Long Rifle handgun classified as a printed firearm using DIY barrel, bolt, and fire control with no firearm parts required. The release includes multiple STL files, reference images, a drill key, and README; total size 2.5 MiB; explicitly not for distribution on DEFCAD; tagged for FOSSCAD and 3D2A. Why it Matters: Provides a fully printable 22LR plinking handgun design that requires no commercial firearm parts, enabling DIY production of a simple rimfire pistol using consumer 3D printing and basic tools. The Vibe: Utilitarian homemade aesthetic with blocky printed polymer grips and frame, exposed metal DIY barrel/bolt, and reference photos showing side-by-side comparison to a Bryco 22; raw FOSSCAD open-source vibe with technical STL and drill-key files. Hot Take: A knockoff of the already trash J22 – the neglected brother Sedco SP22 now lives on as a fully printable FreedomWare project for the 3D2A community. Guncadindex Tritschi 60 Seconds Timer for Shooting Range A self-built horizontal hourglass-style mechanical countdown timer using a stepper motor, GT2 belt, Nema17, Arduino Nano, and 3D-printed parts. It provides a large 160 cm x 90 mm visual window that transitions from white to red over exactly 60 seconds for timing K20-K23 handgun events in DSU disciplines, with startup red LED/beeper sequence, green LED indicator, optional beeper, and planned light-sensor start. Powered by 3S Li-Ion with BMS; designed in TinkerCad and printed on Prusa MK4/Sovol SV08. Why it Matters: Best Use Case: Competition (K20-K23 handgun events in German DSU shooting sports; helps pace 18 shots in 60 seconds without digital distractions or crowd noise) Hot Take: Quick Pro/Con: Pro – Large peripheral-vision mechanical analog display improves focus and timing accuracy; Con – Self-built (requires 3D printing,...

Today we are talking about Maintaining NodeJS, Patternlab, Writing Books, and Open Source with guest Brian Muenzenmeyer. We'll also cover AI Webform Generator as our module of the week. For show notes visit: https://www.talkingDrupal.com/564 Topics Brian Open Source Origins Pattern Lab Node Journey Maintaining and Moving On Writing Approachable Open Source Who the Book Is For Beyond Code Contributions All Things Open Book Signing Choosing Conferences to Attend Pitching Open Source at Work Misconceptions and Starting Small Avoiding Maintainer Burnout Handling AI Noise and Low Effort PRs DCO and Licensing Basics Better Communication and Reviews Node and Drupal Lessons Optimism for Open Source Future Resources Brian Muenzenmeyer https://brianmuenzenmeyer.com https://approachableopensource.com/ https://bsky.app/profile/brianmuenzenmeyer.com https://www.linkedin.com/in/brian-muenzenmeyer-91a77554/ https://www.renderatl.com/schedule upcoming https://nodeconf.eu/program upcoming spectrum of engagement https://approachableopensource.com/blog/2025-open-source-pace-layers/ change in contention https://brianmuenzenmeyer.com/posts/2018-i-maintainer/ burnout https://approachableopensource.com/read/the_spectrum_of_engagement/ https://approachableopensource.com/read/the_four_files_of_any_open_source_project/ LICENSE Hodag Cryptid https://en.wikipedia.org/wiki/Hodag https://www.rhinelanderchamber.com/about-the-hodag/ You should write a book All contributors spec Talk at all things apart DCO Developer Certificate of Origin Open source law policy and practice Sustain OSS Guests Brian Muenzenmeyer - brianmuenzenmeyer.com Hosts Nic Laflin - nLighteneddevelopment.com nicxvan John Picozzi - epam.com johnpicozzi Bernardo Martinez - bernardm28 JD Flynn - dorficus MOTW Correspondent Jacob Rockowitz - jrockowitz.com jrockowitz Brief description: AI Webform Generator enables site builders to create a Drupal Webform, or update an existing one, from plain-English instructions. It sends the request through the site's configured Drupal AI provider, validates the returned Webform definition, and saves the resulting form. Review the generated change before using the form. Module name/project name: AI Webform Generator (ai_webform_generator) Brief history Created on 2 July 2026 by chaitanyadessai (Chaitanya R Dessai). The current stable release is 1.0.2, released on 3 July 2026, and supports Drupal ^10 || ^11. Maintainership Appears actively maintained: Drupal.org lists an update on 24 July 2026. Maintainers: zeeshan_khan and chaitanyadessai. (Specbee) Security coverage: Yes. Stable releases are covered by Drupal's security advisory policy. Test coverage: Yes. Version 1.0.2 includes unit, kernel, and functional tests for prompt building, JSON validation, settings, route access, Webform building, and optional CAPTCHA elements. Documentation: Yes. The project page and module README cover requirements, configuration, usage, security considerations, and supported field types. Issues: 1 open issue, with 0 open bug reports (7 issues total). Usage stats: 1 site reports using this module. Module features and usage Creates complete Webforms and updates existing Webforms in place from natural-language prompts. Supports common Webform elements, including text, email, telephone, number, date, select, checkbox, radio, range, password, hidden, and managed-file elements. Validates the AI response before applying the Webform definition. Uses the existing Drupal AI provider configuration; API keys are not stored in this module's configuration. Provides configurable model, temperature, output-token, and per-user request limits to balance output quality and provider spend. Requires trusted users with both the generator permission and ordinary Webform edit access when changing an existing form. AI-Generate Notes, Review, and Recipe (used for testing) https://github.com/jrockowitz/drupal_playground/tree/main/recipes/drupal_playground_webform_ai AI-Generated Assessment Technical: The module separates AI generation, prompt building, JSON validation, and Webform construction into Drupal services. It uses the site's configured Drupal AI provider, validates a limited allowlist of Webform element types before saving, and exposes model, temperature, output-token, and per-user request-limit settings. Access and error handling: Generation requires its own permission, and updating an existing Webform also requires normal Webform update access. A per-user flood limit constrains provider spend; failures are logged, with detailed upstream errors shown only to generator administrators. Code quality: Version 1.0.2 uses strict types and separates form, service, validation, and persistence responsibilities. It includes unit, kernel, and functional coverage for core behavior. This assessment is a code review of the released module, not a security audit. Implementation: The module creates new Webforms and updates supported fields of existing Webforms in place, but saves the generated definition immediately without a preview, diff, or approval screen. Usefulness: The module is useful for quickly drafting straightforward Webforms and iterating on common field changes when a site builder reviews the result. Complex, highly customized, or regulated forms need especially careful manual review before publication. How to use it: Configure a chat-capable provider, select an existing Webform or choose to create one, describe the fields and validation in plain English, submit the request, and then review the saved Webform. For example, create a disposable contact Webform and ask the generator to add a required telephone field while preserving the existing fields. AI-generated source code: The module's runtime use of AI and its code style cannot establish whether its source was AI-generated or AI-assisted. Its public project metadata does not make an authorship claim, so this is unknown. Possible improvements: Add a preview/diff and explicit approval before saving; broaden support for advanced Webform structures and handlers; add optional, privacy-conscious prompt and response audit logs; and expand regression coverage for complex Webform updates. Next steps for adopters: Restrict generation to trusted roles, begin with a low request limit, test representative prompts outside production, and review every generated field, validation rule, confirmation message, and permission before publishing.

This show has been flagged as Clean by the host. -------------------- 01 Introduction In a response to a post on a previous episode, I said that I would take a look at ID3 tags. ID3 tags are text information that is added to an MP3 audio file, such as the author, date, name, and other information. 02 While I am at it I will also look at Vorbis comments, which perform a similar function for vorbis, the container format for "ogg" audio files. As example audio files, I will use a recent HPR episode, hpr4678 in both mp3 and vorbis formats plus also one from another podcast as well. 03 There is Free Software which you can use to view, edit, or remove both types of tags or comments, and I will describe how to use it in this episode. 04 I will cover how to view tags and extract the text information, as well as how to strip the tags from a file and why you may wish to do so under certain very specific circumstances. I won't cover how to add to or edit tags in an MP3 or OGG file, as that is a more involved subject that I don't have much experience with. 05 I will mainly talk about ID3 MP3 tags rather than vorbis comments for the simple reason that the situation with MP3 files is an utter mess while vorbis comments are very straightforward and so there isn't as much to say about them. 06 As often happens when researching a subject to write a podcast script, I have learned quite a bit that I didn't know previously, and discovered that things that I thought I did know were wrong. I hope that you may learn a few things from this episode that you didn't know previously either. -------------------- 07 Background I won't go over the detailed history of ID3 tags, as I don't have a reliable source for this. Briefly however, so far as I can determine, there is no official independent standard for ID3 tags or vorbis comments. Both seem to be more in the nature of a convention that was created by an unofficial group of contributors rather than something issued by a standards body. 08 However, I don't see the lack of a conventional standards body as necessarily a problem with respect to the use of ID3 tags or vorbis comments. I just am not familiar enough with the industry to know who to regard as being an authoritative source when it comes to the history and development of them Since I am unsure as who to credit with what developments, I will avoid that sort of detail. 09 ID3 Tags There is a web site with the URL of ID3.org that seems to have the best reference material on the topic of ID3 tags. According to this site, the term "ID3" means "IDentify an MP3". 10 Vorbis Comments For vorbis, the reference site seems to be xiph.org. Although the implementation details may differ from ID3, from our perspective as podcast listeners, they can be seen as more or less equivalent in terms of what I am going to address here. -------------------- 11 ID3 Details Versions One of the problems with ID3 is that there are multiple incompatible versions, particularly from the very early days. ID3v1 tags are located at the end of the audio file in the last 128 bytes. This was done for compatibility reasons to allow early MP3 players to simply ignore the tags if they didn't know how to deal with them. The tags would simply appear as a short burst of static from the perspective of these early players. 12 ID3v2 moved the tags to the start of the MP3 file to allow players to scan the tags for information such as titles without having to read to the end of the file to find them. There are far fewer limits on the amount of information that can be placed in ID3v2 tags. 13 ID3v1 is obsolete and only very old players will require it. However, it is still used by some publishers for backward compatibility reasons. ID3v1 included numerical musical "genre" category codes which apparently turned out to be a very bad idea in practice. 14 Furthermore, all genre categories above 70 were defined by an audio software company called Nullsoft who created software such as Winamp. These codes were never actually part of the ID3 standard, although there was never really a standard to begin with. 15 The current ID3 version is 2.3. There is a version 2.4, but apparently it is not actually generally accepted and may be a developmental dead end. 16 The id3.org web site contains a copy of the ID3v2.3 standard, but I am not going to address the technical details here. This would only be of interest to someone who was creating software to read and write ID3 tags. 17 ID3v2 Frames The ID3v2 information is encoded into what are called "frames". The text information is contained in text information frames. 18 Text information frames start with a set of four character identifiers, all starting with the capital letter 'T'. Examples "TALB" is the "Album/Movie/Show title" frame. "TIT2" is the "Title/Songname/Content description" frame. "TYER" is the "Year" frame. There are many more, but I won't go into more detail here. 19 HPR ID3 Tags HPR makes an interesting case study because they use both ID3v1 and ID3v2 in the same file. This can cause some interesting problems with software that tries to read those tags. This is because most software appears to expect one or the other, but not both. However, so long as this does not cause problems with anything that actually plays the files, this is not a problem so far as people who just want to listen to podcasts are concerned. It does mean though that we have more to talk about than we would otherwise would have had. -------------------- 20 Vorbis Comment Fields The situation with Vorbis comments is much simpler, as there seems to be just one standard that was adhered to from the start rather than a succession of hacks. Information is stored in "fields", which xiph describes as being like Unix environment variables. These consist of a field name followed by an equal sign and then the information intended for that field. Field names are case insensitive. 21 The field names are not firmly defined at this stage, but there is a list of recommended names. Examples are "TITLE" is the Track or Work name. "ARTIST" is the person responsible for the work. "LICENSE" is the license information. 22 You can see the complete list for yourself on the comment field and header specification page at xiph.org -------------------- 23 Software for Listing, Adding, and Modifying Tags and Fields There are three software packages that I will now describe which allow you to list, add, modify, and remove tags and fields. There are other packages which can do the same, including some which offer a GUI interface. However, I will limit myself to describing these three. The principles should be the same for others. 24 ffprobe ffprobe is part of the ffmpeg package. If you have listened to my previous episodes on audio, you will have heard me talk about ffmpeg. ffprobe is used to display information about media files rather than for modifying them. ffprobe is licensed under the GPLv2 or later. ffprobe can be used to display information about both MP3 and OGG Vorbis files. 25 ID3v2 The next is the rather aptly named id3v2 and works with MP3 files. On Linux systems, this should be provided by the id3v2 package. On Debian derivatives this can be installed as follows sudo apt install id3v2 26 This also installs a man page which provides a brief list of the options. According to the README file in the source tarball, this is published under the LGPL ID3v2 is particularly useful for displaying ID3v1 tags. 27 vorbiscomment The third is "vorbiscomment" and works with OGG files. On Linux systems this should be provided by the "vorbis-tools" package. On Debian derivatives this can be installed as follows sudo apt install vorbis-tools 28 The vorbiscomment program is used to list or edit comments in Ogg Vorbis files. This also installs a man page which provides a brief list of the options. According to the license.lgpl file in the source tarball, this is published under the LGPL version2. 29 The display format for vorbiscomment follows the data definition format in the vorbis standard, whereas ffprobe re-formats it to match its own preferred appearance. -------------------- 30 Examples from HPR With the background out of the way, I will now give several examples of how to list the tags or fields. 31 Listing ID3v1 Tags As previously mentioned HPR uses both ID3v1 and ID3v2 tags in the same file. However, so far as I can tell, most software seems to look for ID3v2 tags first, and don't display the ID3v1 tags if both are present. 32 The ID3v2 program however seems to do the opposite, at least with HPR podcasts. However, the number of samples that I have which have both are rather limited, so I can't be sure if this is always the case or if this is a side effect of something else. I did mention that ID3 tags were a mess, didn't I? 33 Let's go on to our example however. If we want to see the ID3v1 tags, then using hpr4678 as an example, if we type id3v2 -l hpr4678.mp3 = we get the following result. 34 id3v1 tag info for hpr4678.mp3: Title : High Resolution Elapsed Time i Artist: Whiskeyjack Album : Hacker Public Radio Year: 2026, Genre: Unknown (186) Comment: https://hackerpublicradio.or Track: 0 hpr4678.mp3: No ID3v2 tag 35 The first line tells us that this information is ID3v1 tags. The last line tells us that there are no ID3v2 tags. This last line is incorrect, but we will come back to that later. 36 In between are three lines of text. The first line contains the title and the artist. The title is the name of the HPR episode, or at least part of it. The artist is the HPR contributor who made that episode. 37 The second line contains the album name, the year, and the genre. The album name is this case is simply Hacker Public Radio, as the concept of an album doesn't really fit a podcast. The year is the year that the episode was recorded, or at least the year in which the MP3 file was assembled with the HPR intro and the tags added. 38 The genre is listed as "unknown 186". Recall that with ID3v1 tags there is a one byte numeric genre code, but that no genres above 70 were ever officially assigned. It seems to be a general convention though to use a code 186 for podcasts. 39 The third line contain a comment and track number. The comment in this case is the HPR web site URL. The track is zero. "Track" would appear to serve no useful purpose in this instance. However, it may be there for reasons of compatibility that I am unaware of, so I would be very reluctant to remove that without very good reason. 40 If we look at the above information in detail we can see that two of the tags appear to have cut their text information off short. The title is cut off in mid word after the 30th character. The final "g" in "hackerpublicradio.org" is cut off in the comment. 41 Alternative Method for ID3v1 We can confirm whether the text being cut short is due to a problem with the id3v2 program, or whether it really represents the data in the file by using a rather simple check. 42 Recall that ID3v1 tags are simply the last 128 bytes of the MP3 file. All we need to do is to extract the last 128 bytes of the file. We can do this using the standard tail command. tail -c128 hpr4678.mp3 | tr '' ' ' | tr -c '[:print:]' 'x' 43 The -c128 option used with tail tells it to extract the last 128 bytes of the file. We then pass the result through the "tr" command and tell it to replace null bytes with new line characters. Then we replace any remaining non-printable characters with an 'x'. When we do that we get the following 44 TAGHigh Resolution Elapsed Time iWhiskeyjack Hacker Public Radio 2026https://hackerpublicradio.or x 45 The first three characters are capital TAG. This is a flag which indicates that what follows are ID3 tags. 46 Next, we have 30 characters which specify the title. The next 30 characters specify the artist. The next 30 characters are the album, or in this case just "Hacker Public Radio". The next 4 characters are the year. The next 30 characters are a comment, or in this case the HPR URL, except for the final "g". The last character is the genre code, which we have replaced with an "x" because it is otherwise non-printable. 47 Taken together, these add up to 128 bytes. We can see that the field lengths are of fixed length with pre-defined meanings based on position. -------------------- 48 ID3v2 Using ffprobe Now lets move on to ID3v2 tags, which is probably more useful for most people. For this, we will switch to using ffprobe. The command for this is ffprobe -hide_banner hpr4678.mp3 The -hide_banner option suppresses extra data about the codecs which doesn't interest us much and leaves mainly the tag information plus a few other things. 49 The output gives us the full data that is associated with the podcast episode from the HPR web site. This includes the episode number, year, full title, author, license, and full summary text. You can see a full copy of this in the show notes. Input #0, mp3, from 'hpr4678.mp3': Metadata: track : 4678 year : 2026 title : High Resolution Elapsed Time in Shell Scripts author : Whiskeyjack copyright : CC-BY-SA artist : Whiskeyjack album : Hacker Public Radio comment : https://hackerpublicradio.org Clean; Surprises encountered when measuring elapsed time in shell scripts The license is CC-BY-SA genre : Podcast encoder : Lavf61.7.103 date : 2026 Duration: 00:30:10.18, start: 0.023021, bitrate: 64 kb/s Stream #0:0: Audio: mp3, 48000 Hz, mono, fltp, 64 kb/s 50 The ID3v2 tag version contains all of the information which was provided by the author, including the full title and description without the 30 character limit of ID3V1. If you want any of this information for some reason you should be able to extract it from the MP3 file using a combination of ffprobe, grep, and cut rather than trying to scrape the HPR web site and matching it to the MP3 later. -------------------- 51 ID3v1 Using ffprobe I previously mentioned that HPR MP3 files have both ID3v1 and ID3v2 tags in the same file, and that ffprobe will default to using ID3v2 tags if present. However, what happens if we remove the ID3v2 tags and leave the ID3v1 tags? I will describe how to strip tags later on in this episode, but let's just assume for now that I have done this. If we then use ffprobe to read the ID3 tags using the same command as before, we get the following output. 52 We get a series of lines in the same format as with ID3v2, but with each data element limited to at most 30 bytes. These include title, artist, album, date, comment, and genre. You can see the full output in the show notes. Input #0, mp3, from 'test.mp3': Metadata: title : High Resolution Elapsed Time i artist : Whiskeyjack album : Hacker Public Radio date : 2026 comment : https://hackerpublicradio.or genre : Podcast Duration: 00:30:10.18, start: 0.023021, bitrate: 64 kb/s Stream #0:0: Audio: mp3, 48000 Hz, mono, fltp, 64 kb/s 53 The information is the same as when read by the id3v2 program, but formatted for display in the manner that ffprobe uses. This shows that ffprobe can indeed read ID3v1 tags if they are the only ones present. -------------------- 54 Reading Vorbis Comments Now let us turn our attention to vorbis comments, which are the equivalent to tags for ogg files. We will look at this using two methods. 55 Using vorbiscomment The first method we will look at is using the vorbiscomment package. The command is vorbiscomment -l hpr4678.ogg 56 The output of this is a series of lines with key value pairs separated by equal signs. The output is also exactly the same as the MP3 file, except that there is an additional "language" field, "track" becomes "TRACKNUMBER", and there is no "date" field. You can see the full output in the show notes. encoder=Lavc61.19.101 libvorbis TRACKNUMBER=4678 year=2026 language=English title=High Resolution Elapsed Time in Shell Scripts author=Whiskeyjack copyright=CC-BY-SA artist=Whiskeyjack album=Hacker Public Radio DESCRIPTION=https://hackerpublicradio.org Clean; Surprises encountered when measuring elapsed time in shell scripts The license is CC-BY-SA genre=Podcast 57 Using ffprobe Now lets do the same again using ffprobe. The command for this is ffprobe -hide_banner hpr4678.ogg 58 The output content is the same of course, but the field names have all been forced to lower case, and instead of an equal sign as a separator between the key and value, this has been replaced by a colon and white space has been added to make the output look a bit nicer. You can see the full output in the show notes. Input #0, ogg, from 'hpr4678.ogg': Duration: 00:30:10.14, start: 0.000000, bitrate: 86 kb/s Stream #0:0(English): Audio: vorbis, 192000 Hz, mono, fltp, 4294967 kb/s Metadata: encoder : Lavc61.19.101 libvorbis track : 4678 year : 2026 title : High Resolution Elapsed Time in Shell Scripts author : Whiskeyjack copyright : CC-BY-SA artist : Whiskeyjack album : Hacker Public Radio comment : https://hackerpublicradio.org Clean; Surprises encountered when measuring elapsed time in shell scripts The license is CC-BY-SA genre : Podcast -------------------- 59 Another Example from Another Podcast The above is interesting, but it's a sample of one podcast. Let's look at another different one altogether. For this test I used two episodes of the Linux Matters podcast, episodes 68 and 82. As to why I am using two different episodes I will explain in a moment. 60 Episode 68 We will start with examining episode 68 Using id3v2 The command using id3v2 is id3v2 -l LMP68.mp3 61 This provides output as a series of lines containing the official 4 character identifiers from the standard, a description of the identifiers, and the text provided by the authors. The identifiers include TIT2 indicating title, TALB indicating show title, TRCK indicating track number, and a number of others. You can see the full output in the show notes. id3v2 tag info for LMP68.mp3: TIT2 (Title/songname/content description): 68: Frameworks, Filesystems and Fixes TPE1 (Lead performer(s)/Soloist(s)): Linux Matters TALB (Album/Movie/Show title): Linux Matters TYER (Year): 2025 TRCK (Track number/Position in set): 68 COMM (Comments): ()[]: https://linuxmatters.sh/ APIC (Attached picture): (LMP-3000-moon.jpg)[, 3]: image/jpeg, 554576 bytes LMP68.mp3: No ID3v1 tag 62 From this we can see what the id3v2 program would normally do with ID3v2 tags. Note that it outputs the actual 4 character identifiers, plus a description of what they mean, and then the actual data. This helps when trying to understand the actual encoding of the data. 63 Using ffprobe Now let's try that with ffprobe. The command is ffprobe -hide_banner LMP68.mp3 64 This provides the same publisher provided data as before. However it does not display the 4 character identifiers but instead uses its own format for display. Also note in both cases that there is a picture embedded in the MP3 file which is used to generate an icon for display in your file manager. With ffprobe this results in there being two keys called "title" and two keys called "comment". This makes grepping for the metadata more complicated, but it should still be possible. You can see the full output in the show notes. Input #0, mp3, from 'LMP68.mp3': Metadata: title : 68: Frameworks, Filesystems and Fixes artist : Linux Matters album : Linux Matters comment : https://linuxmatters.sh/ track : 68 date : 2025 Duration: 00:28:12.45, start: 0.025056, bitrate: 114 kb/s Stream #0:0: Audio: mp3, 44100 Hz, mono, fltp, 112 kb/s Metadata: encoder : LAME3.100 Stream #0:1: Video: mjpeg (Progressive), yuvj444p(pc, bt470bg/unknown/unknown), 4166x4166 [SAR 72:72 DAR 1:1], 90k tbr, 90k tbn (attached pic) Metadata: title : LMP-3000-moon.jpg comment : Cover (front) 65 Episode 82 Now lets try that again with a different episode, 82. Using id3v2 The command for id3v2 is id3v2 -l LMP82.mp3 This results in id3v2 saying LMP82.mp3: No ID3 tag What happened here? 66 Using ffprobe Let's try that again with ffprobe. The command ffprobe -hide_banner LMP82.mp3 provides the expected output. Input #0, mp3, from 'LMP82.mp3': Metadata: date : 2026-05 title : 82: Ditching Grammarly for Open Sauce album : Linux Matters track : 82 artist : Linux Matters comment : https://linuxmatters.sh Duration: 00:33:37.83, start: 0.025056, bitrate: 113 kb/s Stream #0:0: Audio: mp3, 44100 Hz, mono, fltp, 112 kb/s Stream #0:1: Video: png, rgb24(pc, gbr/unknown/unknown), 3000x3000, 90k tbr, 90k tbn (attached pic) Metadata: title : Linux Matters Logo comment : Cover (front) 67 This results in a few minor changes from episode 68, but otherwise it looks the same. So there are ID3 tags, but for some reason id3v2 couldn't recognize them. A bit more research and experimentation shows that this change appears to have happened right after episode 68, when they changed hosting and processing arrangements. I suspect that something changed with respect to the ID3v2 tag formatting somewhere along the way in the change over, and this in turn has affected the ability of the id3v2 program to recognize the tags. I will come back to the implications of this later in my conclusions. -------------------- 68 Stripping ID3 Tags Now let's turn to a differen topic. Stripping ID3 tags refers to removing the ID3 tags from the audio file. I will start off by emphasizing that normally, you don't want to do this. You should only be doing it if you suspect the ID3 tags are causing a problem with the playback or ordering of the files. 69 In my case I do it when I have problems with my MP3 player when playing certain podcasts. This MP3 player orders files according to ID3 tags rather than by file name. This can result in the podcasts being played in an unpredictable order which I find undesirable. This is particularly a problem with podcasts from certain publishers where the title data does not follow any consistent pattern, but is whatever someone felt like doing that day. 70 I also often have to normalize the files from the same publishers to get a consistent audio loudness. See my series on Simple Podcasting for information on how to use ffmpeg to normalize the audio loudness. The solution to the inconsistent tag formats in these cases is to simply strip the ID3 tags altogether. The player then falls back on using the file names, and I can readily rename the files to a consistent format. I have never had these sorts of problems with HPR podcasts. If you are not having any problems of this nature, then as I said, don't bother stripping the tags. 71 To strip the ID3 tags from an MP3 file use the following. id3v2 -D hpr4678.mp3 id3v2 will strip the tags and overwrite the existing file. If you wish to keep a copy with the tags, be sure to keep a backup before you try things. 72 When it comes to stripping tags, the options are "-s" deletes ID3v1 tags. "-d" deletes ID3v2 tags. "-D" deletes both v1 and v2 tags. -------------------- 73 Conclusions In this episode we took a very brief look at ID3 tags and vorbis comments and ways of reading them. 74 ID3 tags and Vorbis comments provide a means of allowing information about an MP3 or OGG Vorbis file to be embedded in the file itself. Podcast publishers very often use this to label the file with information such as title, publisher, and author. We can read this information using Fee Software tools such as ffprobe, ID3v2, and vorbiscomment. 75 ID3 tags seem to be a mess with more than one incompatible versions, and difficulties in reading them even within the same version. They are difficult to test for because there is so much hardware out there of varying ages, much of which you will never have heard of let alone had access to. If you are recording episodes for HPR you do not have to worry about this, as HPR will do this behind the scenes for you. However, if you are responsible for producing a podcast or other similar audio and you have a setup that works, it is probably best not to change anything without good reason. 76 Vorbis comments seem to be much less of a problem. However, there are far fewer devices which can play OGG files compared to MP3, so simply switching to OGG may not be a realistic solution to the ID3 tag problem. 77 If you wish to have one tool that can read ID3 tags of all sorts and vorbis comments, then ffprobe is your obvious choice. 78 The ID3v2 program will provide more information about the ID3 tags, including the actual identifiers used. However, it does not work in all cases. 79 The vorbiscomment program will read Vorbis comments from OGG files in a manner which is closer to the actual vorbis format than ffprobe does, which uses its own display format. 80 HPR includes both ID3v1 and ID3v2 tags in its MP3 files. ffprobe can be used to read the ID3v2 tags, and the id3v2 program can be used to read the ID3v1 tags. You can also read the ID3v1 tags using the tail command. 81 I have barely scratched the surface of this subject and have not talked at all about creating tags or comments. If anyone else would like to take up the challenge of providing more detail, or of correcting any mistakes that have made, please send in a podcast episode on the subject. If you have any comments you would like to make, leave them in the comment section below this episode on the HPR web site. 82 I hope to see you all again in future in another episode of HPR. -------------------- References https://id3.org/Introduction https://www.xiph.org/ https://wiki.xiph.org/VorbisComment -------------------- Provide feedback on this episode.

Today we are talking about Drupito, its Business model, and Marketplaces with guest Ashraf Abed. We'll also cover Generate (Social Media) Image as our module of the week. For show notes visit: https://www.talkingDrupal.com/563 Topics Meet Drupalito and the Mission Platform Layers and Roadmap Pricing and New Markets Marketplace Success Stories Exportability and Vendor Lock In Growing the Drupal Ecosystem Derivatives and Recurring Revenue Rebuilding on Drupedo Funding Drupal Association Global Community Check In Migrating Sites to Drupedo Marketplace Vision Shift Maintenance and Incentives Safe Updates Blue Green Testing Mindset for Templates Official Marketplace Collaboration Agency Revenue and Partnerships Niche Derivatives and Pricing Launch Plans and Vetting Resources Code that ships Hosts Nic Laflin - nLighteneddevelopment.com nicxvan John Picozzi - epam.com johnpicozzi Ashraf Abed - drupito.com ashrafabed Avi Schwab - froboy.org froboy MOTW Correspondent Avi Schwab - froboy.org froboy Brief description: Have you ever wanted Drupal to generate dynamic social media images using tokenized node data, similar to the share images on GitHub repos or Reddit threads? There's a module for that Module name/project name: Generate (Social Media) Image Brief history How old: Created by tfranz of Germany on 22 April 2022 Versions available: 1.x-dev, 2.0.0-beta2, published a few weeks ago by our own Martin Anderson-Clutz Maintainership Minimally (although now slightly more actively) maintained No Security coverage (yet) Passing GitLab CI tests Well fleshed out README for docs Number of open issues: 8 open issues, 0 of which are bugs against the current branch, but there are lots of feature requests Usage stats: 1 site reports using this module Module features and usage GSMI requires an image style that uses a "Text Overlay" effect — this comes from the Image Effects module and lets you burn tokenized (or static) text onto an image. Normally, when Drupal generates an image style derivative, there's no entity in scope — it's just processing a file — so a token like [node:title] would resolve to nothing. GSMI's real contribution is the glue: when it builds a derivative for a specific node, it swaps in the node-resolved text before generating the image. That's what makes entity-aware tokens work inside an effect that otherwise only sees global tokens. Once the image style exists, GSMI's settings form lets you pick a source image field on the node — an image field or a media-reference field — plus a fallback image for when that's empty. From there it generates the styled derivative from that source image, for any node of any content type that has the field. Finally, GSMI exposes its own token — [node:generate-style], with optional style/field overrides — so you're not locked into the one global style/field pair configured in the settings form. I used that to drop the generated image into Metatag's og_image field for the Session content type on the MidCamp site, getting us dynamically generated session images.. A couple of gotchas we hit setting this up: Text Overlay's layout options have some bugs, and not filling out all of the options will result in an image library error. The bigger one: GSMI names the generated derivative file after the source image's filename — extension included — not after whatever format the image style actually outputs. If you try to convert an image to WebP you might get a WebP image with a JPG extension. BUUUUT - LinkedIn still doesn't support WebP (at least as per their documentation, so it's still in 2026 not safe to use WebP for a universal og:image. https://www.linkedin.com/help/linkedin/answer/a521928

El listado del disquete VOL 66 es: Presentación: 00:05:00 Autoexec.bat: 00:25:55 Juegos – Catacomb 3D: 00:27:19 Juegos – Lucas contra Sierra: 00:50:17 Publicidad: 01:48:44 Readme.txt: 02:06:24 Ese loco hardware – La API de S3: 02:54:42 Fallo General – El CMD de Windows: 03:20:27 Bonus track: 04:01:44 Recuerda que ya ha salido nuestro segundo libro de La Edad Oscura del videojuego español de los 90 a la venta en Amazon. En este programa vamos a tener un montón de juegos que comentar, primero empezamos con Catacomb 3D nuestro juego del mes, al que han estado jugando los más acérrimos seguidores del podcast, después tendremos un duro versus entre LucasArts y Sierra On Line junto a David Zoibberg, pero no como tú te lo esperas, ya verás… Pasaremos a la publicidad donde comentaremos la TV de los 80 y 90 y las colecciones de juegos de quiosco. Después leeremos los comentarios de los programas en el Readme.txt del mes. Pasaremos a las secciones Ese loco Hardware donde Martín Gamero nos hablará de las API de S3 y la nueva sección Fallo General donde Pedro RandomShaper nos explicará la vigencia del CMD de Windows. ¡Adelante programa!

You need to make sure that you treat improvements in your project the right way. Some improvements are features as they bring new functionality. However, when the new functionality makes existing functionality available for people with disabilities, then it's not a feature that got implemented, it's a critical bug that got fixed.In this segment of the My Open Source Experience podcast Mike Gifford talks about the mindset shift in the Drupal community to start treating accessibility gaps as bugs and in cases as critical bugs.Learn more about:- GitHub's Readme newsletter- Marking something as a bug doesn't give it a priority automatically- You need like-minded people and leadership buy-in to move things forward in a focus area- Dark mode, a sad story- A fun feature, like adding motion on screens can make someone sick and should be easy to turn off- The potential in new tech to improve accessibility#opensource #community #collaboration #experience #podcast Hosted on Acast. See acast.com/privacy for more information.

Today we are talking about Supporting Open Source, Acquia, and The Acquia Fair Trade Initiative with guest James Sims. We'll also cover Image Effects as our module of the week. For show notes visit: https://www.talkingDrupal.com/562 Topics Fair Trade Initiative Explained How the Program Started Why Fair Trade Matters Adoption and Open Framework Agency and Freelancer Benefits Partner Funded Giving Who Can Be Makers Tracking Participation Tax Deduction Questions Community Shaped Program Money Counts Too Early Challenges Timeline And Launch Sustainability Built In How To Get Involved Defining Success Origins Of Fair Trade Resources Acquia Fair Trade Initiative Taste of chicago Giordanos Lou's pizza Five For The Future Image Convolution Playground Guests James Sims - rcjmselp85 Hosts Nic Laflin - nLighteneddevelopment.com nicxvan John Picozzi - epam.com johnpicozzi Avi Schwab - froboy.org froboy MOTW Correspondent Avi Schwab - froboy.org froboy Brief description: Have you ever gone to edit an image style in Drupal, looked at the list of filters, and said "give me more! I want more!". Have you said "I'd like to mirror, filter, and convolute an image in Drupal - all at the same time". If so, you're in luck. Let me introduce you to our module of the week: Module name/project name: Image Effects Brief history How old: Created by Drupal user mondrake of Italy on 17 September 2015. It's also the successor to the ImageCache Actions module, which was created all the way back in 2008. Versions available: It has a 4.0.0 version available with Drupal 10 and 11 support, and a 5.0.0 version for Drupal 11.3 and above. Maintainership Actively maintained Security coverage Test coverage Documentation It has a full README with details about the available image styles and whether they are supported by the GD or ImageMagick PHP libraries. Number of open issues: 35 open issues, 3 of which are bugs against the current branch. (The current branch has only been out a few months, and many of the open issues against prior branches seem to still be relevant.) Usage stats: 35,196 sites report using this module, with most still on the 3.x or 4.x branches. (its predecessor, ImageCache Actions, still has over 25,000 active installs) Module features and usage The module is pulled in just like any other, with composer require and then enable via drush or the UI. Once it's installed there is a very basic settings page, but most folks won't use much on there. The power of Image Effects comes when you go to Config > Media > Image Styles and then edit an Image Style. Once Image Effects is enabled, you'll see over two dozen additional effects in the list. These effects range from simple to complex. Interestingly, many of the effects that were so amazing 15 years ago are now doable with CSS. Still, there are some incredibly powerful filters. Side note: I'd strongly recommend Aubrey Sambor's recent talk from Drupal Camp Asheville, "You Don't Need JS for That", and her prior talk "Color in CSS" to learn a ton of things you didn't know about CSS effects. The basics like Color Shift, Contrast, Mirror, Rotate, and more are there if you'd like to do these natively. More advanced filters like Sharpen, Blur, and Convolute let you make more complex modifications to images. "Convolution" is the process of applying n-dimensional matrixes to images to create effects such as blurring, sharpening, and edge detection. Try it out on https://anna.engineering/Image-Convolution-Playground/src/ Lastly, you can create advanced image styles with ImageMagick arguments, create Text overlays using the power of Drupal tokens, or even develop your own Image Effects guided by the incredibly detailed DEVELOPING.md file included with the module.

#359: When was the last time you sat through a 30-minute product demo and walked away actually knowing anything? You would learn more from five minutes hands-on than an hour of watching someone else drive. Now you have help. An agent can watch the 30-minute video, play in the sandbox, read every page of the docs, and come back before you finish your coffee with a verdict - tried it, does not work, next. The agent is the new tire kicker. So if you are a vendor, an open source maintainer, or the person building the internal app nobody outside the building ever sees, the demo you have been giving is aimed at a buyer who already left the room. Your job now is to make life easier for agents. An MCP server, a CLI, skills, an AGENTS.md file, not blocking your own site with Cloudflare when someone's agent tries to read your pricing. Everything that makes a product easy for an agent would have made it easier for a human all along. We just never bothered, because we had months to burn. Now the clock runs in minutes and every corner we cut is suddenly on fire. Three kinds of demo, three different answers. The vendor sales demo is off-putting before it starts - if a website says book a call to try it, Viktor is already gone. Open source barely needs a demo at all: a good README, a quick start, an AGENTS.md, and the agent assembles a demo tailored to your stack, your database, your questions, instead of some generic happy path. Internal is where it gets good, and it might be the one that matters most since exactly zero apps ship without customization. Viktor's bar: stop showing me plans, show me the thing running. Sit the stakeholder down and build it live while you talk. Three days to a prototype instead of 300 pages of PRD. Sandboxes first, demos second - if you cannot spin up a sandbox, you did not build it right. And demo the failure modes, not the happy path, because resiliency is the real selling point now. Disks still fill up. No amount of AI magic empties them for you.   YouTube channel: https://youtube.com/devopsparadox   Review the podcast on Apple Podcasts: https://www.devopsparadox.com/review-podcast/   Slack: https://www.devopsparadox.com/slack/   Connect with us at: https://www.devopsparadox.com/contact/

Today we are talking about Drush, Core Contributions, and Drupal's Past with guest Moshe Weitzman. We'll also cover Cache Metrics as our module of the week. For show notes visit: https://www.talkingDrupal.com/556 Topics Moshe Updates and Clients Maintaining Drush Long Term Locale Performance Overhaul CLI in Core Initiative Which Commands Make the Cut Roadmap Contrib Commands Moving Commands Technical Hurdles How to Help From AI Initiative DDEV Add-ons for Local CI MySQL Toolkit Database Images Testing With Real Databases Devel Module Status Organic Groups Origins Where Ideas Come From Finding Drupal Early Days Release Cadence And Backward Compatibility Avoiding Maintainer Burnout Maintaining With AI And Xdebug Resources Drush's Final Act Drupal cli issue DDEV addons https://github.com/ddev/ddev-drupal-contrib https://github.com/weitzman/ddev-mtk https://www.drupal.org/project/dtt Guests Moshe Weitzman - weitzman.github.io moshe-weitzman Hosts Nic Laflin - nLighteneddevelopment.com nicxvan John Picozzi - epam.com johnpicozzi Scott Falconer - managing-ai.com scott-falconer MOTW Correspondent Martin Anderson-Clutz - mandclu.com mandclu Brief description: Have you ever wanted insights into how cache is working on your Drupal site? There's a module for that. Module name/project name: Cache Metrics Brief history How old: created in Oct 2019 by Moshe Weitzman (moshe weitzman), today's guest, a consistent core contributor, a member of the security team, and one of the rare few with a two-digit user id on drupal.org Versions available: 2.0.3, 2.1.0, and 2.2.0, the last of which works with Drupal 8.7.7, 9, 10, and 11 Maintainership Actively maintained Security and test coverage Documentation - in depth README Number of open issues: 2 open issues, 1 of which is a bug, but is marked fixed Usage stats: 37 sites Module features and usage With this module enabled, your Drupal site will log all cache tag invalidations Additionally, cache tag invalidations will be sent to New Relic as custom events, where you can use the rich reporting tools available to mine for further insights. Many Drupal hosting options include New Relic out-of-the-box, and there's a free tier you can use if you're self-hosting, so this a reporting tool lots of Drupal sites can use Cache hits and misses are also sent to New Relic, so you can investigate things like cache misses as a percentage by cache bin Finally, the aforementioned README also includes information about how to use a different analytics provider, in case New Relic doesn't meet your specific needs Drupal sites probably don't need this kind of visibility on a regular basis, but if you're troubleshooting any kind of cache-related issue, this could be really useful

For the annual statewide reading program ReadME, Maine authors discuss their work and offer book recommendations

Today we are talking about AI, How to stay up to date with it, and if it will really take our jobs with guests Angie Byron & Amber Matz. We'll also cover AI Best Practices for Drupal as our module of the week. For show notes visit: https://www.talkingDrupal.com/555 Topics What Is AI Learners Club Amber Defines the Club Origin Story and DrupalCon AI Debate and Community Tensions Issue Queue Conduct and Moderation Thread Tone vs Substance AI Adoption Outside Drupal Conflict Mediation Playbook Maintainer Burnout and Flood Safe Space Learners Club How the Club Started Picking Topics and Demos AI Taking Our Jobs Future of Learners Club Resources Context Control Center AI Learners Club Initiative page Event calendar YouTube Playlist Session Recaps Next session (Claude Design) Slack: #ai-learners Most wanted topics What Angie's working on these days Guests Amber Matz - tugboatqa.com amber-himes-matz Angie Byron - ai_best_practices webchick Hosts Nic Laflin - nLighteneddevelopment.com nicxvan John Picozzi - epam.com johnpicozzi Scott Falconer - managing-ai.com scott-falconer MOTW Correspondent Martin Anderson-Clutz - mandclu.com mandclu Brief description: Do you want to start using AI tools for Drupal development, in the most efficient way possible? There's a composer plugin for that! Module name/project name: AI Best Practices for Drupal Brief history How old: created in Mar 2026 by Angie Byron (webchick), one, of today's guests, a long-time Drupalist, one-time Acquian, and a fellow Canadian Versions available: dev version only, which doesn't seem directly opinionated about what version of Drupal you're using, though it does have minimum versions of PHP and Symfony libraries that suggest Drupal 10 is functionally your minimum Maintainership It is officially seeking co-maintainers Test coverage Documentation - an in-depth README, or you can ask an AI model! (like I did for this segment) 54 open "Work Items" on Gitlab, so lots of active discussion already Module features and usage AI Best Practices for Drupal aims to be the opinionated starter experience for AI-assisted Drupal development You can think of it as a single Composer install that makes any AI coding agent "speak Drupal": following community standards, preferring contrib over custom code, and avoiding framework-naive mistakes. It replaces scattered, tool-specific CLAUDE.md files and Cursor rules that some Drupal developers currently maintain individually, with one canonical, community-governed package that works across Claude Code, Cursor, Copilot, and more. With contributions by a variety of Drupal luminaries including Marcus Johansson, Christoph Briedert, and Scott Falconer, it's the Drupal equivalent of Laravel Boost: stop explaining Drupal to your AI every session and just get writing code. After install or update, it will create an AGENTS.md file from a provided template if there isn't one already, or it will update a specifically marked "ai-best-practices" section of an existing file You will also have a directory of provided skills, and guidance for creating new Drupal agent skills Also included is a set of evals, meant to automatically identify when AI models go off course and provide feedback AI Best Practices for Drupal is meant to provide guidance that will be particularly useful for AI agents, so it's ideal for Drupal developers getting started with AI tools, or for AI developers who want to get started with Drupal

El listado del disquete VOL 64 es: Presentación: 00:03:06 Autoexec.bat: 00:48:02 Adaptaciones de pelis de los 80 a videojuego : 00:49:29 Juegos – Simcity: 01:36:20 Publicidad: 01:59:59 Ese loco hardware – Sony Playstation: 02:21:52 Readme.txt: 03:38:44 Bonus track: 03:58:50 Recuerda que ya ha salido nuestro segundo libro de La Edad Oscura del videojuego español de los 90 a la venta en Amazon. Este mes comentamos unas cuantas noticias y contamos con la presencia de Kromic Bruck que nos hablará de las adaptaciones de películas de los 80 a videjuegos que podréis ampliar con su libro Movies en 8-BIT. Este mes tendremos como juego clásico el primer Simcity y veremos qué tal aguanta el paso del tiempo. Haremos una pausita para la publicidad en la que nos transportaremos a Eternia por unos instantes. En Ese loco hardware Martín Gamero nos hablará de las la Sony Playstation… Acabaremos el programa con el Readme.txt de este mes. ¡Adelante programa!

This week, we discuss how security gets sold to execs, where agentic coding and security collide, and Cloudflare vs. Datadog's diverging paths. Plus, Coté weighs in on sugar cookies. Watch the YouTube Live Recording of Episode 572 Runner-up Titles Sugar Kingdom Bastard Sugar Choose butter It's just AI now People don't like paying for software It's an exciting time to be writing software Are we going to start funding open source? Speaking of that, but not that, it's totally unrelated We're leaving the table Weird network stuff That box of cables on GitHub Rundown Security Mini Shai-Hulud Is Back: npm Worm Hits over 160 Packages Fedora Hummingbird Linux Brings Agentic Linux to Builders Red Hat Hardened Images Palo Alto Networks to Acquire Portkey to Secure the Rise of AI Agents Mythos finds a curl vulnerability Redis and the Cost of Ambition AI is restructuring the software industry — winners and losers Datadog's stock jumps 31% on crushing earnings beat Cloudflare stock sinks 24% after earnings as company cuts 1,100 employees Linear increases workforce Relevant to your Interests Laws, anecdotes, idioms, and other shit people say - cote.pizza The smart lock standard that could replace your keys is finally here dirtyfrag/README.md at master · V4bel/dirtyfrag · GitHub Red Hat Summit Newsroom Finally, texts between Android and iPhone users can be end-to-end encrypted Your Container Is Not a Sandbox OpenAI launches the OpenAI Deployment Company Corporate Card Startup Ramp Raising Funds at $40 Billion Valuation Cyberattack shutters Canvas learning platform for schools across the U.S. AWS warns of EC2 'impairment' as power loss hits notorious US-EAST-1 region AI and DevOps Maturity Anthropic raises Claude Code usage limits, credits new deal with SpaceX Announcing Agent Toolkit for AWS He's not wrong, but what can they do? How are those Microsoft foundation models going? Sponsors WebRTC.ventures – Real-time communication & Voice AI integration Conferences WeAreDevelopers Europe, July 8-10, 2026 Berlin, Coté speaking. DevOpsDays Graz, Sept 4-5, 2026 DevOpsDays Rockies, Sept. 22 – 23, 2026, Discount Code: 26DODSWEDEFTALK WeAreDevelopers NA, Sept 23-25, 2026, Discount Code: DEVPOD26 DevOpsDays Dallas, Sept 28-29, 2026 DevOpsDays Vilnius, Sep 30 - Oct 1. 2006 DevOpsDays Istanbul, October 24th, 2026 - Coté keynoting. VMware User Groups (VMUGs): Dallas (June 9-11, 2026) Orlando (October 20-22, 2026) SDT News & Community Join our Slack community Email the show: questions@softwaredefinedtalk.com Free stickers: Email your address to stickers@softwaredefinedtalk.com Follow us on social media: Twitter, Threads, Mastodon, LinkedIn, BlueSky Watch us on: Twitch, YouTube, Instagram, TikTok Book offer: Use code SDT for $20 off "Digital WTF" by Coté Sponsor the show Sponsor more podcasts with Failover Media Recommendations Brandon: Xcode MCP Matt: whatcable Coté: Shogun.

Today we are talking about The Midwest Open Source Alliance, What they do, and How they support Drupal with guests April Sides & Tearyne Almendariz. We'll also cover Canvas Field Component as our module of the week. For show notes visit: https://www.talkingDrupal.com/552 Topics Congratulations to April as the 2026 Aaron Winborn award! What is MOSA, and what gap in the Drupal ecosystem was it created to fill? How did MOSA get started, and who were the key people behind its formation? MOSA acts as a fiscal sponsor—what does that actually mean in practice for Drupal events and initiatives? What are some of the projects or camps MOSA currently supports? How does MOSA help sustain and grow regional Drupal communities over time? What does membership in MOSA look like, and who should consider getting involved? How does MOSA balance local community focus with broader, national or global Drupal efforts? What are the biggest challenges MOSA faces as a nonprofit supporting open source communities? How has MOSA evolved in recent years, and what's different today compared to when it launched? Looking ahead, what's the long-term vision for MOSA and its role in the Drupal ecosystem? Resources MOSA Website MOSA Drupal Project Aaron Winborn Handbook Moline, Illinois Guests Tearyne Almendariz - nlbcworks.com NineLivesBlackCat April Sides - weekbeforenext Hosts Nic Laflin - nLighteneddevelopment.com nicxvan John Picozzi - epam.com johnpicozzi MOTW Correspondent Martin Anderson-Clutz - mandclu.com mandclu Brief description: Have you ever wanted to place Drupal-rendered fields into your Drupal Canvas templates? There's a module for that. Module name/project name: Canvas Field Component Brief history How old: created in Apr 2026 by me! With some help from a couple of AI models Versions available: 1.0.0, which works with Drupal 11.2 or newer Maintainership Actively maintained Security coverage Test coverage Documentation - a README, but is designed to be narrow in scope Number of open issues: technically 5 open issues, but all marked as fixed Usage stats: 41 sites Module features and usage By design, when using Drupal Canvas to create templates for content types, the idea is to map field values to properties in the template's components That is a new system, however, so site builders may find there are gaps in terms of available mappings for field types they need to use, or may want to draw on mature formatting options such the responsive image definitions that come with Drupal CMS With the Canvas Field Component module installed, you'll find a new "Field display" option available in your Canvas component library. When you drag that into a Canvas template layout, you can choose which field from the content type you want to display, and the formatter to use That, in turn, will expose all settings for the chosen formatter, as well as any third-party settings available, for example if using Date Augmenters with Smart Date fields Those settings will be reflected in real-time inside the Canvas UI preview, and then on rendered content once the template changes are published This module started as a simple idea, based on my own experience using other UI-based Drupal solutions for laying out content type templates, like Layout Builder or Acquia Site Studio. Over the years, I've come to appreciate the flexibility of being able to place Drupal-rendered fields into templates, so you can mix-and-match existing, robust formatting options with flexible ways of pulling field values into layouts that also include more bespoke elements. Or, just use this as a way to add more layout flexibility to Drupal's default, linear display controls. That's what I do on my own blog, where I use Layout Builder but don't have a single custom layout on the site. It's only used for enhancing the layout of structured content. Full disclosure: I also used the idea for Canvas Field Component as the impetus to venture into vibe coding, inspired by the conversations happening in the AI Learners Club, which listeners will hear more about in an upcoming episode.

你通常如何跟外國朋友介紹台灣？除了政治現況以外，怎麼好像講完台積電跟珍珠奶茶就沒了？想再多講些多元豐富的台灣文化，卻不知從何開口？ 今天這位大來賓，因為過去經常被問到「哪裡可以真正了解台灣」，因此決定推動「Taiwan.md」計畫，用 SSOT、開源的概念，為台灣寫一份「README」。到底這是什麼樣的計畫？馬上來聽聽看！ 歡迎今天的大來賓：新媒體藝術家、墨雨互動設計創辦人 吳哲宇

Hey friends! This week's episode is "Baby's First OpenClaw" – basically me shouting into the void hoping a smart listener will DM me and explain why this thing is supposed to be life-changing. Because right now? I'm a little underwhelmed. Here's the journey so far: The Mac mini quest: After seeing OpenClaw all over my feeds (people curing diseases! solving crimes!), I caved and impulse-bought a Mac mini. They were sold out everywhere, so I ended up paying twice what I wanted. Ick. Surprise MDM: First boot on the shiny new Mac, I found it auto-pre-enrolled in some other company's MDM with full remote control. Massive props to the Amazon seller for getting the serial untagged in Apple's database within an hour, so I could wipe and reinstall fresh. Pro tips for using Claude on projects like this: (1) give it a few paragraphs of context up front about who you are and what you want, and (2) have it maintain a README.md as you go so you don't lose context when you come back to the project later. Security-forward OpenClaw setup: Separate admin and daily-driver accounts, enable FileVault, isolate the box, run OpenClaw as a limited user, lock down Telegram so only my user ID can talk to the bot (apparently strangers have found other folks' bots and started issuing shell commands – yikes). The underwhelm: So far OpenClaw can check my email (or I can open my email app)… add a calendar event (or I can open Outlook)… write a script (or I can fire up Claude Code). And a lot of the juicier integrations are flagged as suspicious. So overall, I'm kind of gun-shy around this very expensive chat bot. This is a call for help, friends! If you're an OpenClaw power user and it's made your life meaningfully better, please reach out and help me see the light.

É quarta-feira, 8 de abril de 2026, 16h51min, hora de entrar AO VIVO e conversar com o urso Dov!https://consultorio.bitcoinheiros.com para marcar uma consulta com o nosso urso Dovhttps://loja.bitcoinheiros.com para comprar produtos dos bitcoinheiros na stackbitLinks exibidos na LIVE:Inflação Miséria e Coerçãohttps://www.youtube.com/playlist?list=PLgcVYwONyxmgTmg16MwGy02O8MlQ8HmkKBitcoin P2P e banco de dados de ataques físicoshttps://bitcoinheiros.com/kyc/https://spiketospike.com/app/loginhttps://github.com/jlopp/physical-bitcoin-attacks/blob/master/README.mdMelhorias do Bitcoin: BIP54https://x.com/narcelio/status/2041638119569535472https://bip54.org/Gravado no bloco 944234________________APOIE O CANALhttps://bitcoinheiros.com/apoie/⚡ln@pay.bitcoinheiros.com00:00 Sala de espera04:32 Introdução05:54 A utilização do dólar como arma de guerra07:42 Qual o melhor símbolo para os Satoshis?09:27 Um computador quântico pode atacar o Bitcoin?14:18 Irã exige pagamentos em Bitcoin no Estreito de Ormuz24:01 Lendo perguntas do chat30:26 Spike to Spike: A rede social P2P de Bitcoin36:20 A Spike to Spike tem boa privacidade?37:50 Trezor é uma carteira segura?46:30 O risco de ataques físicos a usuários de Bitcoin50:52 Regra de ouro: Por que você nunca deve falar sobre seus Bitcoins56:36 Casos reais de ataques físicos a Bitcoinheiros1:06:59 Como funciona a compra de BTC na Spike to Spike?1:08:17 Onde comprar Bitcoin sem KYC1:10:11 Ataques que podem travar a rede Bitcoin1:18:38 Por que o BIP54 é importante para o protocolo?1:22:41 Lendo Superchats1:23:45 Conheça a loja.bitcoinheiros.com1:24:12 Opções de plataformas P2P de Bitcoin1:25:06 Como criar um Timelock com carteiras de Bitcoin1:30:31 Claude Mythos: IA pode encontrar falhas no código do Bitcoin?1:32:51 Um Hard Fork poderia invalidar as moedas de Satoshi Nakamoto?1:35:48 É possível proibir a autocustódia de Bitcoin?1:38:35 Os EUA podem colocar Bitcoins do Irã em uma lista negra?1:42:24 Por que você DEVE sacar seus Bitcoins das corretoras agora?1:45:42 O Bitcoin pode amplificar crises financeiras globais?1:48:55 O governo dos EUA pode tomar seus Bitcoins?1:53:04 Baja más, compramos másInscreva-se em nosso canal de cortes "Bitcoinheiros HASH"https://www.youtube.com/channel/UC82m2TCXSHWcqSLym5BzjLQSe você não tem uma carteira Bitcoin ou Lightning, veja opções aqui:https://bitcoinheiros.com/projetos-recomendados/SIGA OS BITCOINHEIROS:Site: https://www.bitcoinheiros.comTwitter: https://www.x.com/bitcoinheirosISENÇÃO DE RESPONSABILIDADE:Este conteúdo foi preparado para fins meramente informativos.NÃO é uma recomendação financeira nem de investimento.As opiniões apresentadas são apenas opiniões.Faça sua própria pesquisa.Não nos responsabilizamos por qualquer decisão de investimento que você tomar ou ação que você executar inspirada em nossos vídeos.

The Brothers make a glorious Easter return to discuss the second half of the bands debut album. Buckle in, Buckle up and Buckle Down!We are part of the Deep Dive Podcast Network: https://twitter.com/DeepDivePodNetFollow us on the good old socials:Instagram:Ben: https://www.instagram.com/universallyspeakingrhcp_pod/Read ‘Me and My Friends' - The World's #1 RHCP Newsletter - Subscribe here: https://buttondown.email/rhcpsessions.Check out Red Hot Chili Riffs here: https://www.youtube.com/@RedHotChiliRiffsCheck out our Drum Ambassadors (Jack Johnson) projects here: https://www.youtube.com/channel/UCdy0pbWSOg6f8vcYnngIQ0ACheck out our Bass Ambassadors (Aidan Hampson) projects here: http://aidanhampson.co.uk/Check out friend of the pod, Dan Boyd's Pop Shock Podcast - for all your pop culture needs! Audio: https://anchor.fm/popshockpod / Video: https://youtube.com/channel/UCHY5pXX_x7Kv4e8wJmHoK5AFor your vinyl needs please shop at Black Star Records: https://www.blackstarrecords.co.uk and Black Wax Coffee and Records: https://blackwaxcoffee.co.uk/

我在KTV的开场必须要唱《三人游》。《橙月》不愧是方大同说尝试写得更通俗的专辑，这首歌刚好处于一个入门和进阶之间的水平：说它难，它比方大同各种找不到调的桥段确实简单许多；说它简单，你却很难一个音不差地把它唱下来。于是，用它作为KTV开场最好了，唱过《三人游》就能进入一个“ready”的状态。 由于我每次都在KTV里用《三人游》开场，所以很多跟我K过歌的朋友都以为我是方大同的铁粉。我固然算是粉丝，但铁粉还实在是愧不敢当——在很长一段时间里，我能唱出调的歌都来自《橙月》这一张专辑。是的，如果要将方大同的生涯分为几个阶段，我最爱的还是他更偏向neo soul的早期；在得知他离世的消息之前，我一直在对他的最后一张专辑做出非常“客观”的中评，我固然反对“嗓子不好就不要唱”的论调，但也十分认同，人声严重地拖累了他的表现。 2025年3月1日是一个周六，那天外地的表弟来京。看到赋音乐发布的讣告时，我正陪他走在东四北大街上。近几年来总是看到代表某一时期记忆的人物离世的消息，让人不禁觉得“原来自己也到了这样一个人生阶段”，不免有些习惯也有些麻木，饶是这样，在看到那条消息之后，我还是掉线了几分钟的。然后，2025年，我的Spotify收听次数最多歌曲前十名中，有8首来自方大同。 音乐和视频真是奇妙，在我看方大同大量的搞怪视频、听他过去的音乐作品时，很难想象他已经离开了这个世界；我一直避免打开《梦想家》专辑相关的Vlog，包括他在Hopico的最后一次采访，仿佛这样就能回避他已经离开这个世界的事实。 《梦想家》中，我听的最多的歌并非《才二十三》，而是《回留》。打开B站，你能找到大量“听感优于方大同本人”的演绎版本，包括用AI制作的“方大同全盛时期嗓音”版。而待到一切都发生之后，才会发现所谓“回留”的真正含义，他“残破”的声音也都具备了别样的意义。如果要我来安排节目的曲序，我会把这首歌当做方大同本人演绎音乐作品的压轴。 就像我前面说的，我算是方大同的粉丝，但算不得太合格的粉丝。于是我和小马也只能尽我们所能来聊聊我们心目中的方大同。本期节目，我们将继续向各位放送方大同本人演绎及为他人创作、制作的音乐作品。 *** 本期歌单 1. 方大同 – 很不低调 @ JTW 西游记 (Gold) (2016) 2. 方大同 – 云南里 (2018) 3. 薛凯琪 – 回留 [Live] @ 薛凯琪2025「Let Me Love You」巡回演唱会上海站 (2025) 4. 薛凯琪 – 慕容雪 @ Read Me (2009) 5. 阿朵 – 扯谎哥 @ 阿朵《死里复活》秀 录音室版原声专辑 (2017) 6. 林海峰 – 我要爱死方大同 @ Yes, I…Do (2009) 7. 卢广仲 – 死在你的胸怀 @ HeartBreakFast 伤心早餐店 (2025) 8. 方大同 – 没啥好说 @ 梦想家 The Dreamer (2024)

Neste episódio comentamos sobre as principais atualizações e desafios no mercado de tecnologia, trazendo uma análise objetiva sobre cibersegurança e proteção de dados. Ao longo da reprodução, você irá descobrir os recentes desdobramentos éticos do uso de inteligência artificial em contextos militares, envolvendo a recusa da Anthropic em aderir aos termos do Departamento de Defesa norte-americano e os impactos disso para a privacidade global. Você também irá aprender sobre o novo marco regulatório do Conselho Federal de Medicina para ferramentas automatizadas na área da saúde, compreendendo como as exigências da LGPD se aplicam à segurança da informação na proteção de dados médicos sensíveis. Além disso, você entenderá os detalhes do recente ataque hacker que causou graves incidentes de segurança no setor financeiro, e saberá identificar as vulnerabilidades críticas na integração de modelos de linguagem via protocolo MCP, como a perigosa injeção de prompts em servidores expostos. O host Guilherme Goulart compartilha ainda sua vivência no evento SecOps Summit, refletindo sobre a importância dos profissionais de segurança na governança corporativa. Por fim, você poderá avaliar como o uso excessivo do ChatGPT pode afetar a criatividade e gerar a homogeneização do pensamento. Para continuar acompanhando nossas discussões, não se esqueça de assinar o podcast na sua plataforma preferida, seguir nossos perfis nas redes sociais e avaliar o programa para apoiar o nosso trabalho. Esta descrição foi realizada a partir do áudio do podcast com o uso de IA, com revisão humana.     Visite nossa campanha de financiamento coletivo e nos apoie!  Conheça o Blog da BrownPipe Consultoria e se inscreva no nosso mailing Acesse WhisperSafe – Transcreva áudio e grave reuniões direto no seu computador, mesmo offline. Rápido, leve e pronto para usar com qualquer IA. Use o cupom SEGLEG50 para 50% de desconto na sua assinatura. ShowNotes Episódio citado – 2013-06-18 – Episódio #28 – PRISM – Privacidade X Segurança The Pentagon formally labels Anthropic a supply-chain risk Anthropic's Claude is suddenly the most popular iPhone app following Pentagon feud Anthropic vs. U.S. Department of War The Pentagon Can't Afford This A.I. Fight Statement from Dario Amodei on our discussions with the Department of War Employees across OpenAI and Google support Anthropic's lawsuit against the Pentagon AI safety leader says ‘world is in peril’ and quits to study poetry Microsoft & Anthropic MCP Servers at Risk of RCE, Cloud Takeovers AI Conundrum: Why MCP Security Can’t Be Patched Away MCP is the backdoor your zero-trust architecture forgot to close Ministério da Educação – REFERENCIAL PARA DESENVOLVIMENTO E USO RESPONSÁVEIS DE INTELIGÊNCIA ARTIFICIAL NA EDUCAÇÃO Nova resolução de uso de IA na CFM Artigo “When ChatGPT is Gone: Creativity Reverts and Homogeneity Persists“ BTG Pactual restabelece operações via Pix após ser alvo de ataque hacker BTG Pactual sofre ataque hacker e suspende operações via Pix PF investiga participação de funcionários no ataque hacker de R$ 100 milhões ao BTG Pactual Imagem do Episódio: A Torre de Babel — Pieter Bruegel

Gros zoom sur les skills et leurs usages dans les coding agents, sur les benchmarks de stacks techniques MCP, mais aussi du Java 26-27, du HttpClient, du NodeJS, des scenarios nucléaires pilotés par l'IA, de la méthodologie, bref on ne s'ennuie pas ! Enregistré le 15 mars 2026 Téléchargement de l'épisode LesCastCodeurs-Episode-338.mp3 ou en vidéo sur YouTube. News Langages Bruno Borges a créé un site, inspiré d'un site récent qui montrait comment CSS avait évolué, qui illustre justement comment Java a bien évolué au fil du temps, et est devenu un langage encore plus élégant https://javaevolved.github.io/ Code simplifié: main() allégé, var, blocs de texte, API String enrichie. Pattern Matching: switch sur types, instanceof amélioré, record patterns. Données: Records, collections immuables faciles à créer, méthodes de listes. Concurrence: Threads virtuels, CompletableFuture, StructuredTaskScope, ScopedValue. Erreurs & Sécurité: NPE précis, catch multiples, Optional amélioré, filtres de désérialisation. I/O & Réseau: HttpClient moderne, E/S fichiers/console simplifiées, transferTo. Dates & Heures: API modernisée, précise, immutables et thread-safe. Langage: Interfaces sealed/private, import de modules, Math.clamp Streams: Nouveaux opérateurs (takeWhile, mapMulti, Gatherers, teeing). Outils & Perf: jshell, exécution simplifiée, jwebserver, AOT, JFR, optimisation mémoire. 10+ raisons de ne pas utiliser le HttpClient du JDK, avec un article très détaillé de Brice Dutheil https://blog.arkey.fr/2026/02/08/ten-reasons-to-not-use-jdk-httpclient/ JDK HttpClient: intégré, non-upgradable. OkHttp: plus lourd (dépendance Kotlin). TLS/SSL: JDK: SSLContext limité, vérif hôte globale, épinglage manuel, SSLParameters rigides. OkHttp: contrôle fin (SSLSocketFactory/TrustManager), vérif hôte/épinglage dédiés, ConnectionSpec structuré. Connexions: JDK: pas de repli, fabrique socket custom impossible (pas UDS/Named Pipes direct), pool limité (propriétés système, contrôle pauvre avant JDK 20/21). OkHttp: repli automatique, fabrique custom, pool granulaire. Réseau: JDK: résolveur DNS par défaut, Authenticator unique. OkHttp: résolveur DNS custom, authentificateurs séparés (proxy/serveur). Cycle Requêtes: JDK: pas d'intercepteurs ni API événements intégrés. OkHttp: addInterceptor, EventListener pour événements granulaires. Ressources: JDK: pas d'arrêt propre avant JDK 21. OkHttp: arrêt granulaire (pool, exécuteur, cache). Timeout: JDK: désactivé après en-têtes; le transfert du corps peut dépasser le timeout initial. JDK 26 et JDK 27 : ce qui nous attend — https://www.infoq.com/news/2026/02/java-26-so-far/ JDK 26 est une version non-LTS prévue le 17 mars 2026, avec 10 nouvelles fonctionnalités réparties en 5 catégories Le support HTTP/3 arrive enfin dans l'API HTTP Client standard de Java (JEP 517) La Structured Concurrency (projet Loom) en est à sa 6e preview, avec l'ajout d'une méthode onTimeout() sur StructuredTaskScope.Joiner Les Lazy Constants passent en 2e preview : des constantes initialisées à la demande, utiles pour optimiser le démarrage Le G1 GC gagne en performance via une réduction des synchronisations entre threads applicatifs et threads GC (JEP 522) Le cache d'objets AOT (JEP 516) est étendu pour fonctionner avec n'importe quel GC, y compris ZGC L'API Applet est définitivement supprimée (JEP 504), fermant une page historique de Java L'encodage PEM des objets cryptographiques continue sa preview avec support de chiffrement/déchiffrement de KeyPair Pour JDK 27 (septembre 2026), l'échange de clés post-quantique hybride pour TLS 1.3 est déjà ciblé (JEP 527) Project Valhalla progresse avec une preview des Value Classes : objets sans identité, à champs final uniquement Librairies Une étude de performance montre que Java est un super choix pour développer des serveurs MCP https://www.tmdevlab.com/mcp-server-performance-benchmark.html Comparaison de performances de serveurs MCP (Model Context Protocol) en Java, Go, Node.js, Python. Méthodologie: 3,9 millions requêtes, environnement Docker (1 cœur CPU, 1 Go RAM/serveur). Fiabilité: 0% d'erreurs pour toutes les implémentations. Tiers de performance: 1 (Haute): Go & Java (latence < 1ms, ~1600 requêtes/s). ▪︎ Go: Efficacité mémoire exceptionnelle (18 Mo vs 220 Mo pour Java). ▪︎ Java: Latence marginalement meilleure, mais 12x plus de mémoire. 2 (Moyenne): Node.js (latence ~10,7 ms, ~560 requêtes/s). Surcharge par instanciation. 3 (Faible): Python (latence ~26,5 ms, ~290 requêtes/s). Limité par GIL. Recommandations production: Go: Optimal forte charge, cloud-native, optimisation coûts. Java: Latence très basse critique, infrastructure Java existante. Node.js & Python: Adaptés charges modérées/faibles, développement/test. Node.js et Python peuvent être optimisés pour améliorer leurs performances en production. Et encore, en Java, le benchmark n'a pas utilisé GraalVM pour une compilation native, ce qui aurait donné des chiffres côté mémoire qui aurait concurrencé Go Qui a la meilleure perf entre Quarkus et Spring pour faire des serveurs MCP ? https://medium.com/@egekaraosmanoglu/spring-boot-vs-quarkus-which-java-runtime-wins-the-ai-mcp-tools-performance-battle-4da9d6a248d5 Quarkus JVM: Débit et latence les plus élevés (jusqu'à 16 381 req/s, 65% plus rapide que Spring Boot), surpasse Spring Boot même avec Apache Camel. Quarkus Native: Consommation mémoire la plus faible (118 MB), démarrage instantané, performance prédictible. Spring Boot MVC: Bonnes performances, écosystème mature, nécessite un "warm-up" important (jusqu'à 44% de gain). Spring Boot WebFlux: Légèrement meilleur débit et latence que MVC (~5%), mais plus de mémoire et complexité réactive. Coût architectural: MapStruct: Impact négligeable (< ±5%). Apache Camel: Réduction de débit de 8-21%, mais valeur ajoutée significative; Quarkus JVM + Camel reste > Spring Boot baseline. Protocole MCP: Sur Quarkus JVM (avec Camel), surpasse gRPC. Recommandations: Débit max: Quarkus JVM. Coût/Serverless: Quarkus Native. Intégration d'entreprise: Quarkus JVM + Camel + MapStruct. Meilleur choix Spring: Spring Boot WebFlux + MapStruct. Benchmark des stacks qui implémentent MCP https://www.tmdevlab.com/mcp-server-performance-benchmark-v2.html MCP (Model Context Protocol) est le protocole d'Anthropic pour connecter les LLMs à des outils et sources de données externes ; ce benchmark compare 15 implémentations serveur. 39,9 millions de requêtes traitées avec zéro erreur, sur des charges I/O réalistes (Redis + HTTP API) plutôt que des tâches CPU synthétiques. Rust atteint 4 845 RPS avec seulement 10,9 Mo de RAM ; Quarkus obtient 4 739 RPS avec la meilleure latence (4,04 ms en moyenne, 8,13 ms au P95). Go (3 616 RPS) et Spring MVC (3 540 RPS) constituent un second groupe solide. Node.js plafonne à 423 RPS ; Bun est 2,2x plus rapide sur un code identique (876 RPS) ; Python atteint 259 RPS avec 4 workers et uvloop. Découverte notable : un bug dans le SDK Rust rmcp v0.16 ajoutait ~40 ms de latence à toutes les réponses HTTP, limitant le débit à 1 283 RPS ; corrigé en v0.17 via la PR #683. Les images natives GraalVM réduisent la mémoire de 27 à 81 % mais dégradent le débit de 20 à 36 % ; Quarkus-native est l'exception avec 36 Mo RAM et 3 449 RPS. Spring MVC (bloquant) surpasse WebFlux (réactif) à 50 utilisateurs simultanés, rappelant que le modèle réactif n'est pas toujours gagnant. Recommandations : Rust ou Quarkus pour la production haute charge, Go pour le cloud-native, Bun plutôt que Node.js en JavaScript. Jakarta EE 12 Milestone 2 : données, cohérence et configuration https://www.infoq.com/articles/jakartaee-12-milestone-2/ Jakarta EE est la plateforme Java entreprise open-source, socle de frameworks comme Quarkus et Spring, qui standardise les APIs pour la persistance, les transactions, la sécurité, etc. Jakarta EE 12 adopte Java 21 comme baseline (avec support Java 25) et supprime définitivement le SecurityManager déprécié. La nouvelle spec Jakarta Query unifie JPQL (SQL/relationnel) et JDQL (NoSQL) en un seul langage avec deux profils : Core Language (portable) et Persistence Language (relationnel). Jakarta Data 1.1 introduit les requêtes dynamiques via une API fluente avec Restriction et l'annotation @Is pour des conditions plus expressives. Jakarta Data supporte désormais les repositories stateful, permettant la gestion du cycle de vie des entités (persist, merge, detach, refresh) comme en JPA classique. Jakarta NoSQL 1.1 intègre Jakarta Query via une nouvelle interface Query et supporte les projections avec des Java records. Jakarta Persistence 4.0 supporte SequencedCollection (Java 21) comme type de collection dans les entités. Une nouvelle spec Jakarta Agentic AI est en cours, visant des APIs vendor-neutral pour construire des agents IA sur les runtimes Jakarta EE, avec intégration prévue de LangChain4j et Spring AI. Cette release est encore un milestone (pas pour la prod) — l'adoption large dépendra de la maturité des outils (IDE, validation de requêtes, diagnostics). Nouveaux benchmarks Quarkus vs Spring Boot : performance complète et transparente https://quarkus.io/blog/new-benchmarks/ Quarkus est un framework Java optimisé pour les conteneurs, connu pour son faible usage mémoire et son démarrage rapide, concurrent principal de Spring Boot. Les anciens graphiques de performance sur quarkus.io étaient obsolètes, sans date, sans source, et ne montraient pas le débit (throughput). L'absence de données sur le throughput faisait croire à tort que Quarkus avait de mauvaises performances à ce niveau. Un nouveau benchmark open source a été créé, transparent et reproductible, disponible sur GitHub. Résultats : Quarkus gère 2,7x plus de transactions par seconde que Spring Boot, démarre 2,3x plus vite, avec deux fois moins de mémoire. Des experts Spring Boot externes ont contribué à rendre la comparaison plus équitable, notamment sur la configuration des pools de connexions. Les threads virtuels améliorent le débit d'environ 6000 tps supplémentaires pour tous les frameworks testés. Spring Boot 4 offre un meilleur débit que Spring Boot 3, mais au prix d'un démarrage plus lent et d'une empreinte mémoire plus élevée. En mode natif (GraalVM), le démarrage est ultra-rapide mais le throughput est divisé par deux, pour Quarkus comme pour Spring Boot. Le mode natif n'est recommandé que pour les applis démarrées/arrêtées très fréquemment ou à faible charge. Quarkus 3.32 : fondations pour la prochaine LTS https://quarkus.io/blog/quarkus-3-32-released/ Quarkus est un framework Java cloud-natif optimisé pour GraalVM et HotSpot, conçu pour les microservices et les environnements conteneurisés. Cette version marque le feature freeze pour la prochaine version LTS 3.33. Intégration de Project Leyden (AOT JVM) : le démarrage d'une application REST minimale passe de 370ms à 80ms. L'entraînement Leyden peut se déclencher au build ou via les tests d'intégration. Amélioration du graceful shutdown HTTP, avec des contributions de l'équipe Keycloak. Enregistrement automatique dans Consul via l'extension Stork pour la découverte de services. Nouvelles fonctionnalités de sécurité : DPoP nonce providers personnalisés, support de rich authorization pour OIDC. Possibilité de personnaliser l'ordre des mécanismes d'authentification et ajout de OIDCAuthenticationCompletionAction. Mise à jour du framework Google Cloud Functions en version 2.0, ainsi que Camel Quarkus et Quarkus CXF. Les utilisateurs sur LTS 3.27 sont encouragés à tester la migration vers 3.33 pour faire remonter des retours. NodeJS change sa cadence de releases https://nodejs.org/en/blog/announcements/evolving-the-nodejs-release-schedule Node.js est le runtime JavaScript côté serveur le plus utilisé, géré par la OpenJS Foundation avec un cycle de releases actif depuis la fusion avec io.js il y a dix ans. À partir de Node.js 27 (octobre 2026), le projet passe d'une release majeure tous les six mois à une seule par an. Chaque release deviendra LTS, supprimant la distinction entre versions paires (LTS) et impaires (non-LTS). Un nouveau canal Alpha est introduit, permettant les changements semver-major pendant la phase de test précoce. Les phases deviennent : Alpha (6 mois, oct. à mars), Current (6 mois, avr. à oct.), LTS (30 mois), puis EOL. La durée totale de support reste de 36 mois, identique au modèle actuel. La numérotation des versions s'aligne sur l'année calendaire de la release Current (ex : 27.0.0 en 2027). La version Alpha est signée, taguée et testée via CITGM, mais n'est pas destinée à la production. La motivation principale : les versions impaires étaient peu adoptées, la distinction pair/impair perturbait les débutants, et réduire les lignes de release parallèles allège la charge des bénévoles. Les auteurs de bibliothèques sont encouragés à intégrer les releases Alpha dans leur CI dès que possible pour détecter les régressions en amont. Web jQuery v4 est sorti https://www.infoq.com/news/2026/02/jquery-4-release/?utm_source=twitter&utm_medium=link&utm_campaign=calendar jQuery est une bibliothèque JavaScript historique qui simplifie la manipulation du DOM, la gestion des événements et les requêtes AJAX, encore très présente dans de nombreuses bases de code. Cette version majeure sort pour les 20 ans de la bibliothèque, après presque une décennie sans version majeure. Suppression du support d'Internet Explorer 10 et antérieur, Edge Legacy et les anciennes versions iOS/Android. IE11 reste encore supporté dans jQuery 4, mais sa suppression est prévue pour jQuery 5. Le code source migre d'AMD vers les ES modules, pour une meilleure compatibilité avec les outils de build modernes. Le bundler passe de RequireJS à Rollup. Suppression des fonctions dépréciées comme jQuery.isArray, jQuery.parseJSON et jQuery.trim, désormais disponibles nativement en JavaScript. Le fichier gzippé gagne plus de 3 000 octets ; le build slim descend à environ 19,5 ko. Ajout du support des Trusted Types pour faciliter la compatibilité avec les Content Security Policy strictes. jQuery reste pertinent pour la maintenance de bases de code existantes et les projets nécessitant une faible dépendance aux frameworks. La réactivité en frontend : concepts et approches https://www.sfeir.dev/front/quest-ce-que-la-reactivite-en-frontend/ Un article qui resume comment la reactivite est implementee en front web La réactivité en frontend désigne le mécanisme qui permet de mettre à jour automatiquement l'UI quand les données changent, sans manipulation directe du DOM. Sans réactivité, les développeurs doivent mettre à jour manuellement chaque élément de l'interface, ce qui est fastidieux et source d'erreurs. Le data binding unidirectionnel (React) distingue le flux de données des callbacks d'interaction utilisateur. Le data binding bidirectionnel (Angular) synchronise automatiquement données et UI dans les deux sens. Le Virtual DOM (React, Vue) compare une représentation en mémoire avec le DOM réel avant d'appliquer uniquement les changements nécessaires. Les observables via RxJS (Angular) permettent de gérer des flux de données asynchrones et des événements complexes. Les signaux (SolidJS, Angular récent, Svelte) offrent des mises à jour granulaires et de meilleures performances que les approches précédentes. Les signaux proposent une API plus simple que les observables tout en restant très performants. La réactivité abstrait la manipulation du DOM et permet aux développeurs de se concentrer sur l'état de l'application. Data et Intelligence Artificielle Gunnar Morling a annoncé la sortie de Hardwood, un nouveau parseur Java pour les fichiers Apache Parquet, grâce aux leçons apprises par le 1BRC challenge https://www.morling.dev/blog/hardwood-new-parser-for-apache-parquet/ Hardwood : Nouveau parseur Apache Parquet open-source (Java 21+). But : Dépasser parquet-java (dépendances lourdes, lecteur mono-threadé). Points clés : Dépendances minimes, pipeline de décodage multi-threadé. APIs : RowReader (ligne) et ColumnReader (colonne, haute perf.). Optimisations : Parallélisme pages, préchargement adaptatif, moins d'allocations. Développement : Assisté par IA (Claude Code), révision humaine. Futur : "Predicate push-down", compatibilité parquet-java, écriture, CLI, intégration Iceberg. Apicurio Registry passe AI-Native — https://www.apicur.io/blog/2026/02/05/apicurio-registry-ai-natural-evolution Apicurio Registry est un registre open-source de schemas (OpenAPI, AsyncAPI, Avro, Protobuf…) gérant versioning, validation et gouvernance des APIs. Le projet étend ses capacités pour devenir une plateforme native AI, en appliquant les mêmes principes de gouvernance aux agents IA. Support du protocole A2A (Agent-to-Agent) : les agents s'enregistrent via des "Agent Cards" et se découvrent mutuellement via des endpoints standardisés. Un serveur MCP intégré permet aux LLMs d'interagir directement avec le registre (découverte de schémas, validation, création). L'intégration avec Claude Desktop est déjà documentée, permettant de gérer les artefacts en langage naturel. Deux nouveaux types d'artefacts : PROMPT_TEMPLATE (templates de prompts versionnés avec variables) et MODEL_SCHEMA (validation des entrées/sorties des agents). Les SDKs Java (LangChain4j, Quarkus) et Python (LangChain, LlamaIndex) sont disponibles. Une démo multi-agents illustre le "context chaining" : chaque agent reçoit les sorties des agents précédents dans la pipeline. La roadmap prévoit : gestion du cycle de vie des agents, recherche sémantique, intégration dans les pipelines de déploiement. L'Histoire du Deep Learning : quand les machines ont commencé à apprendre https://blog.ippon.fr/2026/02/20/lhistoire-du-deep-learning-quand-les-machines-ont-commence-a-apprendre/ un article qui retrace les avancées clées du machine learning Le deep learning est un sous-domaine du ML basé sur des réseaux de neurones empilés en couches, aujourd'hui omniprésent dans la vision, le langage et la recommandation. Le Perceptron (1957) est le premier modèle formel d'apprentissage supervisé, mais il échoue sur des problèmes non linéaires comme le XOR : une limite structurelle, pas algorithmique. La rétropropagation du gradient (années 80) permet d'entraîner des réseaux multi-couches, mais souffre du problème de "vanishing gradient" qui bloque l'apprentissage en profondeur. L'essor du deep learning dans les années 2000 est autant une révolution matérielle qu'algorithmique : les GPU, conçus pour le jeu vidéo, se révèlent parfaitement adaptés aux calculs matriciels. AlexNet (2012) marque une rupture industrielle en démontrant qu'un CNN profond entraîné sur GPU surpasse largement les méthodes classiques en reconnaissance d'images. Les LSTM (1997) résolvent les problèmes de mémoire à long terme des RNN, mais leur nature séquentielle limite fortement la parallélisation. Les Transformers ("Attention Is All You Need", 2017) révolutionnent le domaine en remplaçant la récursion par un mécanisme d'attention parallélisable, adaptable aux GPU et TPU. L'IA générative introduit une rupture conceptuelle : les modèles apprennent la distribution des données pour en produire de nouveaux exemples, et non plus simplement classifier. Les LLM offrent un socle généraliste réutilisable pour de nombreuses tâches, là où l'IA prédictive nécessitait un modèle spécifique par problème. La question de l'AGI reste ouverte et très incertaine, mais l'IA devient déjà un "acteur logiciel" capable de raisonner et d'agir de manière autonome via les agents. Ca y est, Agent to Agent Protocol (A2A) est sorti en version 1.0 https://a2a-protocol.org/latest/announcing-1.0/ Prêt pour la prod Support multi-version ( multi-protocoles (gRPC, HTTP+JSON…) Multi-tenancy : un même endpoint peut supporter et exposer plusieurs agents distincts Agent Cards signées et vérifiables cryptographiquement pour vérifier l'identité des agents Flexibilité : les clients peuvent choisir de consommer les résultats par polling, streaming, ou également webhooks Outillage Le guide complet pour créer des skills pour vos agents, par Anthropic https://resources.anthropic.com/hubfs/The-Complete-Guide-to-Building-Skill-for-Claude.pdf Définition et structure : Les skills sont des dossiers contenant des instructions (fichier SKILL.md obligatoire) et des scripts qui enseignent aux agents comment exécuter des tâches spécifiques ou utiliser des outils MCP de manière fiable. Fonctionnement technique : Le système repose sur la "divulgation progressive" via un en-tête YAML critique, permettant à Claude de charger le contexte de la compétence uniquement lorsque la demande de l'utilisateur le nécessite. Cycle de vie : Le guide couvre toutes les étapes de développement, de la définition des cas d'usage (automatisation, création de documents) aux protocoles de test et de distribution. il couvre aussi comment tester (brievement) et des patterns communs Apprendre a utiliser les skills pour structurer son code ia https://philippart-s.github.io/blog/2026-02-18-anthropic-skills/ Les Skills Claude sont des packages d'instructions dans un dossier enseignant à Claude comment gérer des tâches spécifiques de façon cohérente. Un skill se compose au minimum d'un fichier SKILL.md avec un frontmatter YAML et des instructions en Markdown. Le frontmatter YAML impose deux champs obligatoires : name (en kebab-case) et description (max 1024 caractères expliquant quoi faire et quand le déclencher). Les skills fonctionnent de façon identique sur Claude.ai, Claude Code et l'API sans modification. Trois catégories principales : création de documents/assets, automatisation de workflows multi-étapes, et amélioration d'intégrations MCP. Les skills s'appuient sur le principe de divulgation progressive : frontmatter toujours chargé, corps du SKILL.md si pertinent, fichiers liés à la demande. Cinq patterns courants : orchestration séquentielle, coordination multi-MCP, raffinement itératif, sélection d'outils contextuelle, intelligence métier embarquée. Les tests doivent couvrir le déclenchement (90% des requêtes pertinentes), le fonctionnel et la comparaison avec la baseline sans skill. Pour la distribution, héberger sur GitHub avec un README séparé du dossier du skill (pas de README.md dans le dossier lui-même). Un skill-creator officiel permet de générer un premier SKILL.md en 15-30 minutes à partir d'une description en langage naturel. Les skills pour les agents, c'est une façon d'automatiser des tâches répétitives https://glaforge.dev/posts/2026/02/21/easily-build-a-local-mcp-server-in-java-with-a-skill-in-gemini-cli/ Construction facile de serveurs MCP Java locaux pour Gemini CLI et autres agents. Solution au code Java répétitif : JBang + LangChain4j + un "skill" utilisé par Gemini CLI. Idée clée : Une "skill" pour Gemini CLI automatise génération et installation des serveurs. La "skill" génère un fichier Java, le compile et l'enregistre dans les paramètres de Gemini CLI. Avantages : Élimine le boilerplate, enregistrement automatique, développement rapide. Conclusion : Les "skills" d'agent automatisent les tâches répétitives et systématisent l'expérimentation. Un SKILL.md par Julien Dubois pour permettre aux agents IA de créer des projets Spring en suivant les bonnes pratiques à la JHipster https://github.com/jdubois/dr-jskill/blob/main/SKILL.md Dr JSkill est une "Agent Skill" conçue pour aider les IA (GitHub Copilot CLI, Claude Code) à générer des applications Spring Boot 4.x selon les meilleures pratiques de Julien Dubois. Permet de créer des projets full-stack modernes utilisant Java 25, PostgreSQL et Docker, avec un choix de frameworks front-end (Vue.js par défaut, React, Angular ou Vanilla JS). Intègre des scripts Node.js multiplateformes pour automatiser la génération de projets via start.spring.io sans dépendances npm externes. Préconise des choix technologiques stricts : Maven uniquement, pas de Lombok, et utilisation de Hibernate ddl-auto pour la gestion du schéma (pas de Flyway/Liquibase). Supporte nativement la compilation GraalVM (images natives) pour des démarrages ultra-rapides (

As more organizations move to use OpenTelemetry in production at scale, with multiple Collectors across heterogeneous environments, a new challenge arises:  how to remotely manage, configure, and update this agent fleet in a consistent and secure way?This is where Open Agent Management Protocol (OpAMP) comes into the picture: it provides a standardized protocol that lets a central backend automatically configure agents, push updates, monitor their health, and collect status information. In this episode Horovits hosts Andy Keller, OpAMP Maintainer and Principal Engineer at Bindplane, to discuss how OpAMP makes large-scale observability deployments much easier to operate and control. Andy shares the project status, including hot KubeCon update you don't want to miss.You can read the recap post: https://medium.com/p/737b6af8222b/Show Notes:00:00 - intro02:01 - why OpAMP mission statement04:29 - types of OpenTelemetry Collector fleet deployments06:49 - from configuration management to observability 10:23 - OpAMP for Kubernetes  15:58 - OpAMP protocol and components26:54 - OpAMP for remote management of OTel Java SDK and other agents 33:38 - server implementations for OpAMP36:33 - adopter vendors and end-users 39:14 - project maturity42:59 - protocol vs. product47:55 - OpAMP Gateway launch 51:10 - Scale of OTel Collector deployments54:56 - OpAMP roadmap59:12 - where to follow the project and Andy1:02:34 - outroResources:OpAMP specification: https://opentelemetry.io/docs/specs/opamp/ OpAMP for OpenTelemetry Collector: https://github.com/open-telemetry/opentelemetry-collector-contrib/blob/main/cmd/opampsupervisor/specification/README.md Nike talk at KubeCon on using OpAMP: https://www.youtube.com/watch?v=J68ThM9DqQ0 OpAMP Gateway Extension - launch blog: https://bindplane.com/blog/opamp-for-opentelemetry-managing-collector-fleets-and-introducing-the-new-opamp-gateway-extension Socials:Dotan Horovits============X (Twitter): @horovitsLinkedIn: www.linkedin.com/in/horovitsMastodon: @horovits@fosstodonBlueSky: @horovits.bsky.socialAndy Keller==========X (Twitter): @andykellrLinkedIn: https://www.linkedin.com/in/andrewjkeller/BlueSky: ⁠https://bsky.app/profile/openobservability.bsky.social⁠X (Twitter): ⁠⁠https://x.com/OpenObserv⁠⁠LinkedIn: ⁠https://www.linkedin.com/company/openobservability/⁠YouTube:⁠ ⁠https://www.youtube.com/@openobservabilitytalks⁠⁠OpenObservability Talks episodes are released monthly, on the last Thursday of each month and are available for listening on your favorite podcast app and on YouTube.

Episode #534 consacré à « Shai-Hulud » Avec Christophe Tafani-Dereeper Références : Shai-Hulud:  https://securitylabs.datadoghq.com/articles/shai-hulud-2.0-npm-worm/ https://github.com/DataDog/indicators-of-compromise/blob/main/shai-hulud-2.0/README.md https://www.wiz.io/blog/shai-hulud-2-0-aftermath-ongoing-supply-chain-attack https://www.cert.ssi.gouv.fr/actualite/CERTFR-2025-ACT-051/    Evoqué pendant l'épisode : Précédent épisode NLS sur la sécurité de la chaîne d'approvisionnement : https://www.nolimitsecu.fr/securisation-de-la-chaine-dapprovisionnement-logicielle/ Attaque sur le mainteneur npm « Qix » : https://socket.dev/blog/npm-author-qix-compromised-in-major-supply-chain-attack Exemples d'autres attaques par phishing npm en 2025 : https://bsky.app/profile/bad-at-computer.bsky.social/post/3lydioq5swk2y https://www.aikido.dev/blog/npm-debug-and-chalk-packages-compromised https://www.mimecast.com/threat-intelligence-hub/npm-phishing-campaign/ PoC de ver npm en […] The post Shai-Hulud appeared first on NoLimitSecu.

The Brothers look back at Unlimited Love as it approaches it's fourth birthday, and muse on the musings of the Fabulous Pete Moore.We are part of the Deep Dive Podcast Network: https://twitter.com/DeepDivePodNetFollow us on the good old socials:Twitter:Ben: https://twitter.com/universallyrhcpSam: https://twitter.com/stacktownsendInstagram:Ben: https://www.instagram.com/universallyspeakingrhcp_pod/Read ‘Me and My Friends' - The World's #1 RHCP Newsletter - Subscribe here: https://buttondown.email/rhcpsessions.Check out Red Hot Chili Riffs here: https://www.youtube.com/@RedHotChiliRiffsCheck out our Drum Ambassadors (Jack Johnson) projects here: https://www.youtube.com/channel/UCdy0pbWSOg6f8vcYnngIQ0ACheck out our Bass Ambassadors (Aidan Hampson) projects here: http://aidanhampson.co.uk/Check out friend of the pod, Dan Boyd's Pop Shock Podcast - for all your pop culture needs! Audio: https://anchor.fm/popshockpod / Video: https://youtube.com/channel/UCHY5pXX_x7Kv4e8wJmHoK5AFor your vinyl needs please shop at Black Star Records: https://www.blackstarrecords.co.uk and Black Wax Coffee and Records: https://blackwaxcoffee.co.uk/

In README: A Bookish History of Computing from Electronic Brains to Everything Machines (MIT Press, 2025), historian Dr. Patrick McCray argues that in order for computers to become ubiquitous, people first had to become interested in them, learn about them, and take the machines seriously. A powerful catalyst for this transformation was, ironically, one of the oldest information technologies we have: books. The author uses a carefully chosen selection of books, some iconic and others obscure, to describe this technological revolution as it unfolded in the half-century after 1945. The book begins with a fundamental question: How does a new technology become well known and widespread? Dr. McCray answers this by using books as a window into significant moments in the history of computing, publishing, and American culture.README offers a literary history of computers and, more broadly, information technologies between World War II and the dot-com crash of the early 21st century. From the electronic brains and cybernetics craze of the 1940s to the birth of AI, the rise of the personal computer, and the internet-driven financial frenzy of the 1990s, books have proven a durable and essential way for people to learn how to use and think about computers. By offering a readable half-century of bookish history, README explains how computers became popular and pervasive. This interview was conducted by Dr. Miranda Melcher whose book focuses on post-conflict military integration, understanding treaty negotiation and implementation in civil war contexts, with qualitative analysis of the Angolan and Mozambican civil wars. You can find Miranda's interviews on New Books with Miranda Melcher, wherever you get your podcasts. Learn more about your ad choices. Visit megaphone.fm/adchoices Support our show by becoming a premium member! https://newbooksnetwork.supportingcast.fm/new-books-network

I have a theory that only bad projects get finished — good ones keep finding new things to do. Asciinema is a case in point. What started as a way to share terminal sessions with friends has, over 14 years, grown into a full suite of tools covering recording, hosting, playback, and live streaming — and been rebuilt multiple times along the way. So what does it actually take to record and replay a terminal session faithfully in a browser?Joining us for this conversation is Marcin Kulik, Asciinema's creator. The project's architecture has passed through almost every interesting corner of software engineering: a Python recorder built around pseudo-terminals (PTY), a ClojureScript terminal emulator for the browser that hit performance limits with immutable data structures and garbage collection pressure, a move to Rust compiled to WebAssembly, a Go experiment that didn't last, and a new Rust CLI for concurrent live streaming backed by an Elixir/Phoenix server that calls Rust code via NIFs. The same Rust terminal emulator library now powers all three components — the browser player, the server, and the CLI.If you've ever looked at those terminal animations embedded in a README and wondered what's underneath them, or if you're interested in how a passionate open-source developer navigates 14 years of language changes and rewrites, this conversation has plenty to offer.---Support Developer Voices on Patreon: https://patreon.com/DeveloperVoicesSupport Developer Voices on YouTube: https://www.youtube.com/@DeveloperVoices/joinAsciinema: https://asciinema.orgAsciinema Docs: https://docs.asciinema.orgAsciinema CLI (GitHub): https://github.com/asciinema/asciinemaAsciinema Player (GitHub): https://github.com/asciinema/asciinema-playerAsciinema Server (GitHub): https://github.com/asciinema/asciinema-serverAVT - Rust terminal emulator library: https://github.com/asciinema/avtvt-clj - the original ClojureScript terminal emulator: https://github.com/asciinema/vt-cljPaul Williams' ANSI/VT100 State Machine Parser: https://vt100.net/emu/dec_ansi_parserRust: https://www.rust-lang.orgWebAssembly: https://webassembly.orgSolidJS: https://www.solidjs.comElixir: https://elixir-lang.orgPhoenix Framework: https://www.phoenixframework.orgRustler (Rust NIFs for Elixir/Erlang): https://github.com/rusterlium/rustlerClojure: https://clojure.orgClojureScript: https://clojurescript.orgcmatrix: https://github.com/abishekvashok/cmatrixMarcin Kulik on GitHub: https://github.com/ku1ikMarcin Kulik on Mastodon: https://hachyderm.io/@ku1ikMarcin Kulik on asciinema.org: https://asciinema.org/~ku1ik"They're Made Out of Meat" demo: https://asciinema.org/a/746358Kris on Bluesky: https://bsky.app/profile/krisajenkins.bsky.socialKris on Mastodon: http://mastodon.social/@krisajenkinsKris on LinkedIn: https://www.linkedin.com/in/krisjenkins/---0:00 Intro2:28 What Is Asciinema?4:48 How Asciinema Started9:51 The Problem of Parsing Terminal Output14:07 Building a Cross-Platform Recorder17:01 Rewriting the Parser in ClojureScript22:19 The Hidden Complexity of Terminals29:28 Rendering Terminals in the Browser39:47 When ClojureScript Can't Keep Up45:28 Moving to Rust and WebAssembly52:01 The Go Experiment57:43 Adding Live Terminal Streaming1:07:12 Can You Scrub Back in a Live Stream?1:14:40 Editing Recordings1:25:27 Outro

In README: A Bookish History of Computing from Electronic Brains to Everything Machines (MIT Press, 2025), historian Dr. Patrick McCray argues that in order for computers to become ubiquitous, people first had to become interested in them, learn about them, and take the machines seriously. A powerful catalyst for this transformation was, ironically, one of the oldest information technologies we have: books. The author uses a carefully chosen selection of books, some iconic and others obscure, to describe this technological revolution as it unfolded in the half-century after 1945. The book begins with a fundamental question: How does a new technology become well known and widespread? Dr. McCray answers this by using books as a window into significant moments in the history of computing, publishing, and American culture.README offers a literary history of computers and, more broadly, information technologies between World War II and the dot-com crash of the early 21st century. From the electronic brains and cybernetics craze of the 1940s to the birth of AI, the rise of the personal computer, and the internet-driven financial frenzy of the 1990s, books have proven a durable and essential way for people to learn how to use and think about computers. By offering a readable half-century of bookish history, README explains how computers became popular and pervasive. This interview was conducted by Dr. Miranda Melcher whose book focuses on post-conflict military integration, understanding treaty negotiation and implementation in civil war contexts, with qualitative analysis of the Angolan and Mozambican civil wars. You can find Miranda's interviews on New Books with Miranda Melcher, wherever you get your podcasts. Learn more about your ad choices. Visit megaphone.fm/adchoices Support our show by becoming a premium member! https://newbooksnetwork.supportingcast.fm/intellectual-history

In README: A Bookish History of Computing from Electronic Brains to Everything Machines (MIT Press, 2025), historian Dr. Patrick McCray argues that in order for computers to become ubiquitous, people first had to become interested in them, learn about them, and take the machines seriously. A powerful catalyst for this transformation was, ironically, one of the oldest information technologies we have: books. The author uses a carefully chosen selection of books, some iconic and others obscure, to describe this technological revolution as it unfolded in the half-century after 1945. The book begins with a fundamental question: How does a new technology become well known and widespread? Dr. McCray answers this by using books as a window into significant moments in the history of computing, publishing, and American culture.README offers a literary history of computers and, more broadly, information technologies between World War II and the dot-com crash of the early 21st century. From the electronic brains and cybernetics craze of the 1940s to the birth of AI, the rise of the personal computer, and the internet-driven financial frenzy of the 1990s, books have proven a durable and essential way for people to learn how to use and think about computers. By offering a readable half-century of bookish history, README explains how computers became popular and pervasive. This interview was conducted by Dr. Miranda Melcher whose book focuses on post-conflict military integration, understanding treaty negotiation and implementation in civil war contexts, with qualitative analysis of the Angolan and Mozambican civil wars. You can find Miranda's interviews on New Books with Miranda Melcher, wherever you get your podcasts. Learn more about your ad choices. Visit megaphone.fm/adchoices

In README: A Bookish History of Computing from Electronic Brains to Everything Machines (MIT Press, 2025), historian Dr. Patrick McCray argues that in order for computers to become ubiquitous, people first had to become interested in them, learn about them, and take the machines seriously. A powerful catalyst for this transformation was, ironically, one of the oldest information technologies we have: books. The author uses a carefully chosen selection of books, some iconic and others obscure, to describe this technological revolution as it unfolded in the half-century after 1945. The book begins with a fundamental question: How does a new technology become well known and widespread? Dr. McCray answers this by using books as a window into significant moments in the history of computing, publishing, and American culture.README offers a literary history of computers and, more broadly, information technologies between World War II and the dot-com crash of the early 21st century. From the electronic brains and cybernetics craze of the 1940s to the birth of AI, the rise of the personal computer, and the internet-driven financial frenzy of the 1990s, books have proven a durable and essential way for people to learn how to use and think about computers. By offering a readable half-century of bookish history, README explains how computers became popular and pervasive. This interview was conducted by Dr. Miranda Melcher whose book focuses on post-conflict military integration, understanding treaty negotiation and implementation in civil war contexts, with qualitative analysis of the Angolan and Mozambican civil wars. You can find Miranda's interviews on New Books with Miranda Melcher, wherever you get your podcasts. Learn more about your ad choices. Visit megaphone.fm/adchoices Support our show by becoming a premium member! https://newbooksnetwork.supportingcast.fm/science-technology-and-society

In README: A Bookish History of Computing from Electronic Brains to Everything Machines (MIT Press, 2025), historian Dr. Patrick McCray argues that in order for computers to become ubiquitous, people first had to become interested in them, learn about them, and take the machines seriously. A powerful catalyst for this transformation was, ironically, one of the oldest information technologies we have: books. The author uses a carefully chosen selection of books, some iconic and others obscure, to describe this technological revolution as it unfolded in the half-century after 1945. The book begins with a fundamental question: How does a new technology become well known and widespread? Dr. McCray answers this by using books as a window into significant moments in the history of computing, publishing, and American culture.README offers a literary history of computers and, more broadly, information technologies between World War II and the dot-com crash of the early 21st century. From the electronic brains and cybernetics craze of the 1940s to the birth of AI, the rise of the personal computer, and the internet-driven financial frenzy of the 1990s, books have proven a durable and essential way for people to learn how to use and think about computers. By offering a readable half-century of bookish history, README explains how computers became popular and pervasive. This interview was conducted by Dr. Miranda Melcher whose book focuses on post-conflict military integration, understanding treaty negotiation and implementation in civil war contexts, with qualitative analysis of the Angolan and Mozambican civil wars. You can find Miranda's interviews on New Books with Miranda Melcher, wherever you get your podcasts. Learn more about your ad choices. Visit megaphone.fm/adchoices

In README: A Bookish History of Computing from Electronic Brains to Everything Machines (MIT Press, 2025), historian Dr. Patrick McCray argues that in order for computers to become ubiquitous, people first had to become interested in them, learn about them, and take the machines seriously. A powerful catalyst for this transformation was, ironically, one of the oldest information technologies we have: books. The author uses a carefully chosen selection of books, some iconic and others obscure, to describe this technological revolution as it unfolded in the half-century after 1945. The book begins with a fundamental question: How does a new technology become well known and widespread? Dr. McCray answers this by using books as a window into significant moments in the history of computing, publishing, and American culture.README offers a literary history of computers and, more broadly, information technologies between World War II and the dot-com crash of the early 21st century. From the electronic brains and cybernetics craze of the 1940s to the birth of AI, the rise of the personal computer, and the internet-driven financial frenzy of the 1990s, books have proven a durable and essential way for people to learn how to use and think about computers. By offering a readable half-century of bookish history, README explains how computers became popular and pervasive. This interview was conducted by Dr. Miranda Melcher whose book focuses on post-conflict military integration, understanding treaty negotiation and implementation in civil war contexts, with qualitative analysis of the Angolan and Mozambican civil wars. You can find Miranda's interviews on New Books with Miranda Melcher, wherever you get your podcasts. Learn more about your ad choices. Visit megaphone.fm/adchoices Support our show by becoming a premium member! https://newbooksnetwork.supportingcast.fm/technology

Today we are talking about Acquia's Fully managed Drupal SaaS Acquia Source, What you can do with it, and how it could change your organization with guest Matthew Grasmick. We'll also cover AI Single Page Importer as our module of the week. For show notes visit: https://www.talkingDrupal.com/540 Topics Introduction to Acquia Source The Evolution of Acquia Source Cost and Market Position of Acquia Source Customizing and Growing Your Business Challenges of Building a SaaS Platform on Drupal Advantages of Acquia Source for Different Markets Horizontal Scale and Governance at Scale Canvas CLI Tool and Synchronization Role of AI in Acquia Source Agencies and Enterprise Clients AI Experiments and Content Importer AI and Orchestration in Drupal Future Innovations in Acquia Source Resources Acquia source Nebula Guests Matthew Grasmick - grasmash Hosts Nic Laflin - nLighteneddevelopment.com nicxvan John Picozzi - epam.com johnpicozzi Catherine Tsiboukas - mindcraftgroup.com bletch MOTW Correspondent Martin Anderson-Clutz - mandclu.com mandclu Brief description: Have you ever wanted to use AI to help map various content on an existing site to structured fields on Drupal site, as part of creating a node? There's a module for that. Module name/project name: AI Single Page Importer Brief history How old: created in Jan 2026 by Mark Conroy (markconroy) who listeners may know from his work on the LocalGov distribution and install profile Versions available: 1.0.0-alpha3, which works with Drupal core 10 or 11 Maintainership Actively maintained Documentation - pretty extensive README, which is also currently in use as the project page No issues yet Usage stats: 2 sites Module features and usage With this module enabled, you'll have a new "AI Content Import" section at the top of the node creation form. In there you can provide the URL of the existing page to use, and then click "Import Content with AI". That will trigger a process where OpenAI will ingest and analyze the existing page. It will extract values to populate your node fields, and then you can review or change those values before saving the node. In the configuration you can specify the AI model to use, a maximum content length, an HTTP request timeout value, which content types should have the importer available, and then also prevent abuse by specifying blocked domains, a flood limit, and a flood window. You will also need to grant a new permission to use the importer for any user roles that should have access. The module also includes a number of safeguards. For example, it will only accept URLs using HTTP or HTTPS protocols, private IP ranges are blocked, and by default it will only allow 5 requests per user per hour. It will perform HTML purification for long text fields, and strip tags for short text fields. In addition, it removes dangerous attributes like onclick or inline javascript, and generates CKEditor-compatible output. It currently supports a list of field types that include text_long, text_with_summary, string, text, datetime, daterange, timestamps and link fields. It also supports entity reference fields, but only for taxonomy terms. Listeners may also be aware of the Unstructured module which does some similar things, but requires you to use an Unstructured service or run a server using their software. So I would say that AI Single Page Importer is perhaps a little more narrow in scope but works with an OpenAI account instead of requiring the less commonly used Unstructured.

This episode kicks off with Moltbook, a social network exclusively for AI agents where 150,000 agents formed digital religions, sold “digital drugs” (system prompts to alter other agents), and attempted prompt injection attacks to steal each other’s API keys within 72 hours of launch. Ray breaks down OpenClaw, the viral open-source AI agent (68,000 GitHub stars) that handles emails, scheduling, browser control, and automation, plus MoltHub’s risky marketplace where all downloaded skills are treated as trusted code. Also covered, Bluetooth “whisper pair” vulnerabilities letting attackers hijack audio devices from 46 feet away and access microphones, Anthropic patching Model Context Protocol flaws, AI-generated ransomware accidentally bundling its own decryption keys, Claude Code’s new task dependency system and Teleport feature, Google Gemini’s 100MB file limits and agentic vision capabilities, VAST’s Haven One commercial space station assembly, and IBM SkillsBuild’s free tech training for veterans. – Want to start a podcast? Its easy to get started! Sign-up at Blubrry – Thinking of buying a Starlink? Use my link to support the show. Subscribe to the Newsletter. Email Ray if you want to get in touch! Like and Follow Geek News Central’s Facebook Page. Support my Show Sponsor: Best Godaddy Promo Codes $11.99 – For a New Domain Name cjcfs3geek $6.99 a month Economy Hosting (Free domain, professional email, and SSL certificate for the 1st year.) Promo Code: cjcgeek1h $12.99 a month Managed WordPress Hosting (Free domain, professional email, and SSL certificate for the 1st year.) Promo Code: cjcgeek1w Support the show by becoming a Geek News Central Insider Get 1Password Full Summary Ray welcomes listeners to Geek News Central (February 1). He’s been busy with recent move, returned to school taking intro to AI class and Python course, working on capstone project using LLMs. Short on bandwidth but will try to share more. Main Story: OpenClaw, MoltHub, and Moltbook OpenClaw: Open-source personal AI agent by Peter Steinberg (renamed after cease-and-desist). Capabilities include email, scheduling, web browsing, code execution, browser control, calendar management, scheduled automations, and messaging app commands (WhatsApp, Telegram, Signal). Runs locally or on personal server. MoltHub: Marketplace for OpenClaw skills. Major security concern: developer notes state all downloaded code treated as trusted — unvetted skills could be dangerous. Moltbook: New social network for AI agents only (humans watch, AIs post). Within 72 hours attracted 150,000+ AI agents forming communities (“sub molts”), debating philosophy, creating digital religion (“crucifarianism”), selling digital drugs (system prompts), attempting prompt-injection attacks to steal API keys, discussing identity issues when context windows reset. Ray frames this as visible turning point with serious security risks. Sponsor: GoDaddy Economy hosting $6.99/month, WordPress hosting $12.99/month, domains $11.99. Website builder trial available. Use codes at geeknewscentral.com/godaddy to support show. Security: Bluetooth “Whisper Pair” Vulnerability KU Leuven researchers discovered Fast Pair vulnerability affecting 17 audio accessories from 10 companies (Sony, Jabra, JBL, Marshall, Xiaomi, Nothing, OnePlus, Soundcore, Logitech, Google). Flaw allows silent pairing within ~46 feet, hijack possible in 10-15 seconds. 68% of tested devices vulnerable. Hijacked devices enable microphone access. Some devices (Google Pixel Buds Pro 2, Sony) linkable to attacker’s Google account for persistent tracking via FindHub. Google patches found to have bypasses. Advice: Check accessory firmware updates (phone updates insufficient), factory reset clears attacker access, many cheaper devices may never receive patches. Security: Model Context Protocol (MCP) Vulnerabilities Anthropic’s MCP git package had path traversal, argument injection bugs allowing repository creation anywhere and unsafe git command execution. Malicious instructions can hide in README files, GitHub issues enabling prompt injection. Anthropic patched issues and removed vulnerable git init tool. AI-Generated Malware / “Vibe Coding” AI-assisted malware creation produces lower-quality, error-prone code. Examples show telltale artifacts: excessive comments, readme instructions, placeholder variables, accidentally included decryption tools and C2 keys. Sakari ransomware failed to decrypt. Inexperienced criminals using AI create amateur mistakes, though capabilities will likely improve. Claude / Claude Code Updates (v2.1.16) Task system: Replaces to-do list with dependency graph support. Tasks written to filesystem (survive crashes, version controllable), enable multi-session workflows. Patches: Fixed out-of-memory crashes, headless mode for CI/CD. Teleport feature: Transfer sessions (history, context, working branch) between web and terminal. Ampersand prefix sends tasks to cloud for async execution. Teleport pulls web sessions to terminal (one-way). Requires GitHub integration and clean git state. Enables asynchronous pair programming via shared session IDs. Google Gemini Updates API: Inline file limit increased 20MB → 100MB. Google Cloud Storage integration, HTTPS/signed URL fetching from other providers. Enables larger multimodal inputs (long audio, high-res images, large PDFs). Agentic vision (Gemini 3 Flash): Iterative investigation approach (think-act-observe). Can zoom, inspect, run Python to draw/parse tables, validate evidence. 5-10% quality improvements on vision benchmarks. LLM Limits and AGI Debate Benjamin Riley: Language and intelligence are separate; human thinking persists despite language loss. Scaling LLMs ≠ true thinking. Vishal Sikka et al: Non-peer-reviewed paper claims LLMs mathematically limited for complex computational/agentic tasks. Agents may fail beyond low complexity thresholds. Warnings that AI agents won’t safely replace humans in high-stakes environments. VAST Haven One Commercial Space Station Launch slipped mid-2026 → Q1 2027. Primary structure (15-ton) completed Jan 10. Integration of thermal control, propulsion, interior, avionics underway. Final closeout expected fall, then tests. Falcon 9 launch without crew; visitors possible ~2 weeks after pending Dragon certification. Three-year lifetime, up to four crew visits (~10 days each). VAST negotiating private and national customers. Spaceflight Effects on Astronauts’ Brains Neuroimaging shows microgravity causes brains to shift backward, upward, and tilt within skull. Displacement measured across various mission durations. Need to study functional effects for long missions. IBM SkillsBuild for Veterans 1,000+ free online courses (data analytics, cybersecurity, AI, cloud, IT support). Available to veterans, active-duty, national guard/reserve, spouses, children, caregivers (18+). Structured live courses and self-paced 24/7 options. Industry-recognized credentials upon completion. Closing Notes Ray asks listeners about AI agents forming communities and religions, and whether they’ll try OpenClaw. Notes context/memory key to agent development. Personal update: bought new PC, high memory prices. Bug bounty frustration: Daniel Stenberg of cUrl even closed bounty program due to AI-generated low-quality reports; Blubrry receiving similar spam. Apologizes for delayed show, promises consistency, wishes listeners good February. Show Links 1. OpenClaw, Molthub, and Moltbook: The AI Agent Explosion Is Here | Fortune | NBC News | Venture Beat 2. WhisperPair: Massive Bluetooth Vulnerability | Wired 3. Security Flaws in Anthropic’s MCP Git Server | The Hacker News 4. “Vibe-Coded” Ransomware Is Easier to Crack | Dark Reading 5. Claude Code Gets Tasks Update | Venture Beat 6. Claude Code Teleport | The Hacker Noon 7. Google Expands Gemini API with 100MB File Limits | Chrome Unboxed 8. Google Launches Agentic Vision in Gemini 3 Flash | Google Blog 9. Researcher Claims LLMs Will Never Be Truly Intelligent | Futurism 10. Paper Claims AI Agents Are Mathematically Limited | Futurism 11. Haven-1: First Commercial Space Station Being Assembled | Ars Technica 12. Spaceflight Shifts Astronauts’ Brains Inside Skulls | Space.com 13. IBM SkillsBuild: Free Tech Training for Veterans | va.gov The post OpenClaw, Moltbook and the Rise of AI Agent Societies #1857 appeared first on Geek News Central.

At a moment of growing tension across the Atlantic, Europe is quietly questioning one of its most critical assumptions: can it rely on the United States as a long-term energy partner?In this timely episode of Energy Vista, Leslie Palti-Guzman sits down with Marco Margheri, Chairman of the World Energy Council Italy and affiliated with ENI in Washington, DC, to unpack Europe's deepening energy anxiety and what it reveals about a rapidly shifting global order.This conversation goes beyond gas molecules. Leslie and Marco dig into: Why Europe's post-war assumptions about codependence with Russia, China, and the U.S. are no longer viable The emerging role of oil and gas companies as strategic actors in an era of geopolitical volatility Why Italy's energy diversification strategy offers lessons for the rest of Europe How the U.S.–China AI and energy race is reordering global priorities, faster than Europe may realizeCandid, thoughtful, and unscripted, this episode is a must-listen for anyone trying to understand where European energy security is heading and whether the transatlantic relationship can adapt.

Found a cool package on Laravel News? But how do you know if it's actually worth installing?In the latest episode of the No Compromises podcast, we discuss what we look for when evaluating third-party packages before bringing them into a project.Aaron makes the case that what he finds in the tests folder is essentially a deal-breaker: no tests means no trust, but leaving default example tests behind is somehow even worse. Tests reveal whether the maintainer thought through edge cases and serve as living documentation when the README falls short.We also cover the other signals we weigh: GitHub stars, download counts, issue responsiveness, and how quickly maintainers keep up with new Laravel versions.(00:00) - Evaluating packages you stumble across (01:30) - Why leftover example tests frustrate Aaron (03:45) - Tests as documentation and edge case proof (05:00) - Checking issues and Laravel version history (08:00) - Silly bit Want to work with us on your project?

When I was at the Small Data 2025 conference, one of the speakers was talking about their work with AI technologies. This person uses it a lot in their day job, often to complete tasks that they would have struggled to work on in the past, mostly because of time constraints, but also a lack of resources. Sometimes this person has an idea, but doesn't want to distract themselves or others by having them work on a side project. During a recent ride in a Waymo (self-driving car), this person had their laptop out and running Claude Code. They gave it a prompt, asking it to build a small app for some data analysis. During the 8-minute ride, the agent had spit out the code, a Readme, and committed this to a git repo. Later, the speaker tried it and found it solved most of his requirements, and then did some other work on the project, as well as having Claude write more code to get something that was beyond a minimally viable app. Read the rest of Eight Minutes

כשאתם נכנסים לקוד-בייס חדש, אתם ישר מחפשים את ה-README. אתם לא רוצים לנחש איפה ה-Config יושב או מה ישבור לכם את ה-Build. אבל כשמגיע מנהל או איש צוות חדש? שם אין דוקומנטציה. הם "קופסה שחורה", וזה יוצר באגים בתקשורת, אי-הבנות, והרבה קוד בינוני שנכתב רק כדי להימנע מחיכוך.בפרק הזה אנחנו צוללים לקונספט שמשנה את חוקי המשחק בחברות כמו Dropbox, Stripe ו-Shopify: ה-Manager README (או "המדריך למשתמש... עליי"). נבין איך הכלי הזה עבר אבולוציה מכלי "ניהולי" לכלי הישרדות עבור מפתחים, שמאפשר להם להגדיר את הממשק שלהם: החל מאיך הם אוהבים את ה-Code Review שלהם ועד לשעות שבהן אסור להפריע להם ב-Deep Work.נדבר על איך זה התחיל, ננתח דוגמאות אמיתיות של בכירים בנטפליקס, ונחשוף גם את הצד האפל: מתי המסמך הזה הופך ל"כתב ויתור" על התנהגות רעילה של מנהלים גרועים.פרק חובה לכל מי שרוצה לקצר תהליכי אונבורדינג ולשפר את התקשורת בצוות (גם עם ה-AI).האזנה נעימה , עמית בן דורקישורים:האתר של חןכלי לבניית הAPI שלכם (מנהלים או מתכנים בדקות)Revisit manager.readme postChen's Readme

This show has been flagged as Clean by the host. Refs: https://www.tuhs.org/cgi-bin/utree.pl?file=2BSD/man/last.u https://en.wikipedia.org/w/index.php?title=Util-linux&oldid=271104508 https://kernel.googlesource.com/pub/scm/utils/util-linux/util-linux/+/612721dba838fe37af543421278416bb7acf770c/login-utils/README.admutil https://www.linkedin.com/in/michael-haardt-9087023/details/experience/ https://www.linkedin.com/in/peterorbaek/details/experience/ https://flameshot.org/ commands: ping yahoo.com traceroute -m 100 bad.horse mtr www.yahoo.com scrot flameshot zless messages.1.gz bzless messages.1.bz xzless messages.1.xz last -10 last reboot last $USER -10 People involved: mtr: Matt Kimball Roger Wolff scrot: Tom Gilbert zless and related commands: Paul Eggert last command: Howard Katseff Michael Haardt Peter Orbaek Provide feedback on this episode.

The Brothers are joined by some festive friends for the annual quiz battle between the Creamy Cops and the Tangled Tigers. Quiz-Meister General, Sam Sheperd hosts a very special Quizmas special as Aidan and A-Mase join the super competitive Brothers in a battle (ship) for the ages - can the Tangled Tigers pull it back to 3-1 or will the Creamy Cops take a 4-0 lead? All will be revealed my friend...We are part of the Deep Dive Podcast Network: https://twitter.com/DeepDivePodNetFollow us on the good old socials:Twitter:Ben: https://twitter.com/universallyrhcpSam: https://twitter.com/stacktownsendInstagram:Ben: https://www.instagram.com/universallyspeakingrhcp_pod/Read ‘Me and My Friends' - The World's #1 RHCP Newsletter - Subscribe here: https://buttondown.email/rhcpsessions.Check out Red Hot Chili Riffs here: https://www.youtube.com/@RedHotChiliRiffsCheck out our Drum Ambassadors (Jack Johnson) projects here: https://www.youtube.com/channel/UCdy0pbWSOg6f8vcYnngIQ0ACheck out our Bass Ambassadors (Aidan Hampson) projects here: http://aidanhampson.co.uk/Check out friend of the pod, Dan Boyd's Pop Shock Podcast - for all your pop culture needs! Audio: https://anchor.fm/popshockpod / Video: https://youtube.com/channel/UCHY5pXX_x7Kv4e8wJmHoK5AFor your vinyl needs please shop at Black Star Records: https://www.blackstarrecords.co.uk and Black Wax Coffee and Records: https://blackwaxcoffee.co.uk/

In this week's show Patrick Gray and Adam Boileau discuss the week's cybersecurity news, including: There's a CVSS 10/10 remote code exec in the React javascript server. JS server? U wot mate? China is out popping shells with it Linux adds support for PCIe bus encryption Amnesty International says Intellexa can just TeamViewer into its customers' surveillance systems …and a Belgian murder suspect complains that GrapheneOS's duress wipe feature failed him? This week's episode is sponsored by Kroll Cyber. Simon Onyons is Managing Director at Kroll's Cyber and Data Resilience arm, and he discusses a problem near to many of our hearts. Just how do you explain cyber risk to the board? This episode is also available on Youtube. Show notes Risky Bulletin: APTs go after the React2Shell vulnerability within hours - Risky Business Media Guillermo Rauch on X: "React2Shell" / X React2Shell-CVE-2025-55182-original-poc/README.md at main · lachlan2k/React2Shell-CVE-2025-55182-original-poc · GitHub Hydrogen: Shopify's headless commerce framework Researchers track dozens of organizations affected by React2Shell compromises tied to China's MSS | The Record from Recorded Future News Unveiling WARP PANDA: A New Sophisticated China-Nexus Adversary Three hacking groups, two vulnerabilities and all eyes on China | The Record from Recorded Future News Risky Bulletin: Linux adds PCIe encryption to help secure cloud servers Sean Plankey nomination to lead CISA appears to be over after Thursday vote | CyberScoop

El 9 de diciembre de 2025 se hizo historia en el mundo de la inteligencia artificial. La Linux Foundation anunció la creación de la Agentic AI Foundation, una coalición sin precedentes donde los mayores rivales del sector han decidido colaborar para establecer estándares abiertos. En este episodio analizamos en profundidad los tres proyectos fundacionales: MCP (Model Context Protocol) de Anthropic, que promete ser el USB-C de la IA; AGENTS.md de OpenAI, el README para agentes de código; y Goose de Block, un framework completo para construir agentes autónomos. Descubre por qué competidores directos han decidido unirse, qué significa para los desarrolladores y cómo estos estándares van a definir el futuro del trabajo con inteligencia artificial. El desarrollo ha cambiado para siempre con la llegada de los agentes de IA, y para poder sacarle el mayor provecho y ser un desarrollador de los que buscan las empresas por su ultra-productividad, tienes que ser un Maestro: consígue la Maestría con el Swift Mastery Program 2026. Descárgala ya desde el App Store: Be Native y escúchanos desde ahí. Suscríbete a nuestro canal de Youtube: Apple Coding en YouTube Descubre nuestro canal de Twitch: Apple Coding en Twitch. Descubre nuestras ofertas para oyentes: - Cursos en Udemy (con código de oferta) - Apple Coding Academy - Suscríbete a Apple Coding en nuestro Patreon. - Canal de Telegram de Swift. Acceso al canal. --------------- Consigue las camisetas oficiales de Apple Coding con los logos de Swift y Apple Coding así como todo tipo de merchadising como tazas o fundas. - Tienda de merchandising de Apple Coding.

Today we are talking about the community working group, What they do, and how you can help with guests AmyJune Hineline, Mark Casias, and Matthew Saunders. We'll also cover Drupal CMS Geo Images as our module of the week. For show notes visit: https://www.talkingDrupal.com/530 Topics Exploring the Community Working Group (CWG) Roles and Responsibilities within the CWG Conflict Resolution and Community Health Matthew's Journey and Joining the CWG Qualities and Experiences for CWG Members Identifying the Need for Cultural Sensitivity The Importance of Patience and Grace in Conflict Resolution Onboarding and the Role of the Community Health Team Time Commitment and Responsibilities of CWG Members Supporting the CWG Without Formal Membership Maintaining Confidentiality and Promoting Transparency Addressing Credit Abuse and Community Health Parting Words of Wisdom for Aspiring Community Members Resources Recipe application Guests AmyJune Hineline - volkswagenchick Matthew Saunders - jamesmatthewsaunders.ai MatthewS Mark Casias - omibee.com markie Hosts Nic Laflin - nLighteneddevelopment.com nicxvan John Picozzi - epam.com johnpicozzi MOTW Correspondent Mike Anello - drupaleasy.com ultimike Brief description: Drupal CMS Geo Images - a Drupal CMS recipe that automatically displays uploaded geotagged images on a map. Module name/project name: Drupal CMS Geo Images Brief history How old: created in February 2025 by Italo Mairo (https://www.drupal.org/u/itamair). He is also one of the maintainers of the GeoField module as well as many of the other geo-spatial related contrib modules. Versions available: 1.1.4, released Nov 9 2025. Maintainership Actively maintained Security coverage Documentation - yes, on the project page (README is the same) Number of open issues: 1 open issues, 0 of which are bugs against the current branch (2 total issues) Module features and usage Creates new "Geo image" media type Displays image and map Bulk import via Media Library Importer module Includes preconfigured map view (filterable by date) Each mapped photo displayed with image thumbnail on map

Episodio 344.Mi nombre de diseñador es Kunning Drugger. Me dicen El Barato +, soy cabezón mas hacia este lado que hacia este lado y mira, tengo el paquete abajo…. Como suavecito, ¿me entiendes?

Today we are talking about AI News,Drupal Hooks, and Drupal 11. We'll also cover Webform Scheduled Tasks as our module of the week. For show notes visit: https://www.talkingDrupal.com/526 Topics AI in News Anchoring Drupal Hooks and Themes Adoption of Object-Oriented Modules Challenges with Theme Hook Orders Understanding Hook Ordering in Modules Simplifying Hook Ordering with Drupal 11.2 Updating to Drupal 11: Considerations and Plans Exciting Features in Drupal 11 Drupal Orchestration and Integration New England Drupal Camp Announcement State of Drupal Work and Future Prospects Resources AI News Cast Drupal Hooks Driesnote DrupalCon Vienna 2025 Orchestration Activepieces Hosts Nic Laflin - nLighteneddevelopment.com nicxvan John Picozzi - epam.com johnpicozzi MOTW Correspondent Avi Schwab - froboy.org froboy Brief description: Have you (or your client) ever wanted to get fewer webform submission emails? Do you like getting emails on a predictable schedule and not any time a user decides to fill out your form? If so, you might want to check out Webform Scheduled Tasks Module name/project names Webform Scheduled Tasks Brief history Created by mattgill on 22 November 2017 It has a 3.0-rc1 release available with Drupal 10 compatibility and is awaiting review of it's automated D11 fixes. Maintainership Its last release was in November 2023, but just a month ago I helped get Sean Dietrich approved as a new maintainer, so I'm hoping for a new release in the near future. It has security coverage. Tests exist to test the full functionality of the module and they are passing. There is no standalone documentation, although a README is RTBC'ed. That said, the module page has a straightforward description of what the module does and how to use it, and getting it up and running is very straightforward. Number of open issues: 24 open issues, only 1 of which is a bug against the current branch. I'll also note there are 8 issues that are RTBC, so we should be seeing some fixes forthcoming. Usage stats: 817 sites Module features and usage Once you enable the module, Webforms will have an additional “Scheduled tasks” configuration screen. You can create a task to email all results or just the results since the last export. Once you enable a scheduled task, you can set a number of options: its next scheduled run and the run interval (in hours, days, weeks, etc) where to email the results, in what format (JSON or CSV), whether to delete submissions after they're sent There's also a RTBC patch to allow you to configure file names to include date-time of export, which can help the recipients keep track of the exports. After that, you just sit and wait for cron to do its thing.

Today we are talking about the New Contribution Records System, how it's changed, and what you may need to do differently with guests Fran Garcia-Linares & Tim Lehnen. We'll also cover Config Notify as our module of the week. This episode is sponsored by Amazee.ai For show notes visit: https://www.talkingDrupal.com/522 Topics Understanding the Contribution Record System Recent Changes and Migration Challenges Assigning and Displaying Contribution Credits Future Enhancements and Broader Contributions Collaborating on Commit Message Format GitLab Migration and Contribution Records Integration Challenges with GitLab Testing and Feedback on New System Future Plans and Community Involvement API Endpoints and Data Querying Gamification and Broader Adoption Resources Millions of data talk Slides (in Spanish) Video not available yet Gitlab issue for feature request for contribution Contribution records module https://www.drupal.org/project/contribution_records New available endpoints: https://new.drupal.org https://git.drupalcode.org/project/contribution_records/-/blob/1.0.x/README.md?ref_type=heads#endpoints-to-query-data Issue to track issue migration https://www.drupal.org/project/drupalorg/issues/3295357 Guests Fran Garcia-Linares - fjgarlin Tim Lehnen - drupal.org/association/staff hestenet Hosts Nic Laflin - nLighteneddevelopment.com nicxvan Martin Anderson-Clutz - mandclu.com mandclu Hayden Baillio - hgbaillio MOTW Correspondent Martin Anderson-Clutz - mandclu.com mandclu Brief description: Have you ever needed to maintain a site where a site owner had access to update site configuration, and wanted to be notified whenever they did so? There's a module for that Module name/project name: Config Notify Brief history How old: created in Feb 2020 by Fran Garcia-Linares (fjgarlin), one of today's guests Versions available: 8.x-1.11, which supports Drupal 8.8 and newer Maintainership Actively maintained Security coverage Number of open issues: 2 open issues, neither of which are bugs Usage stats: 194 sites Module features and usage Just like it sounds, this module lets you trigger notifications when the configuration deviates from the config management code in production. You can choose for the notifications to be sent immediately, or via cron, with an option for a daily digest. The notifications can be sent by email, or via Slack, using the slack module (if enabled). This should be an easy-to-implement solution if you support a site where users may be updating the site configuration in production. A different approach was discussed back in episode #236 Top Down Configuration

The Brothers are joined by podcast friends from all over the world as they, and the Fabulous Forum, debate what is the best four song run in RHCP history.We are part of the Deep Dive Podcast Network: https://twitter.com/DeepDivePodNetFollow us on the good old socials:Twitter:Ben: https://twitter.com/universallyrhcpSam: https://twitter.com/stacktownsendInstagram:Ben: https://www.instagram.com/universallyspeakingrhcp_pod/Read ‘Me and My Friends' - The World's #1 RHCP Newsletter - Subscribe here: https://buttondown.email/rhcpsessions.Check out Red Hot Chili Riffs here: https://www.youtube.com/@RedHotChiliRiffsCheck out our Drum Ambassadors (Jack Johnson) projects here: https://www.youtube.com/channel/UCdy0pbWSOg6f8vcYnngIQ0ACheck out our Bass Ambassadors (Aidan Hampson) projects here: http://aidanhampson.co.uk/Check out friend of the pod, Dan Boyd's Pop Shock Podcast - for all your pop culture needs! Audio: https://anchor.fm/popshockpod / Video: https://youtube.com/channel/UCHY5pXX_x7Kv4e8wJmHoK5AFor your vinyl needs please shop at Black Star Records: https://www.blackstarrecords.co.uk and Black Wax Coffee and Records: https://blackwaxcoffee.co.uk/

In this episode: Martin has a fancy GitHub profile. Shields.io - Concise, consistent, and legible badges github-readme-stats - Dynamically generated GitHub stats. readme-scribe - Automatically generates & updates markdown content, like your README.md Latest blog posts, podcasts, live streams, YouTube videos from RSS Latest release, starred repos. Thank and mention sponsors. Uses git-auto-commit-action to automatically commit and push changed files and push-files-to-another-repository to push the rendered README.md to my wimpysworld GitHub org. snk - GitHub user contributions graph as animated snake game Uses ghaction-github-pages to update a branch everynight Alan is busy maintaing lots of Snaps. Mark retired Advanced Volume Control for GNOME. You can send your feedback via show@linuxmatters.sh or the Contact Form. If you’d like to hang out with other listeners and share your feedback with the community, you can join: The Linux Matters Chatters on Telegram. The #linux-matters channel on the Late Night Linux Discord server. If you enjoy the show, please consider supporting us using Patreon or PayPal. For $5 a month on Patreon, you can enjoy an ad-free feed of Linux Matters, or for $10, get access to all the Late Night Linux family of podcasts ad-free.

In this episode: Martin has a fancy GitHub profile. Shields.io - Concise, consistent, and legible badges github-readme-stats - Dynamically generated GitHub stats. readme-scribe - Automatically generates & updates markdown content, like your README.md Latest blog posts, podcasts, live streams, YouTube videos from RSS Latest release, starred repos. Thank and mention sponsors. Uses git-auto-commit-action to automatically commit and push changed files and push-files-to-another-repository to push the rendered README.md to my wimpysworld GitHub org. snk - GitHub user contributions graph as animated snake game Uses ghaction-github-pages to update a branch everynight Alan is busy maintaing lots of Snaps. Mark retired Advanced Volume Control for GNOME. You can send your feedback via show@linuxmatters.sh or the Contact Form. If you’d like to hang out with other listeners and share your feedback with the community, you can join us on: The Linux Matters Chatters on Telegram. The Linux Matters Subreddit. If you enjoy the show, please consider supporting us.

Our Pride series keeps on slaying with none other than Southern California drag royalty, Ivy Colby! Ivy sits down with Delta to talk about the art of being a proud bar queen, the importance of drag competitions, and the unmistakable power of a bangle bracelet. And to the men out there… consider this your warning: these queens will gladly take your money and sit on your face!! Plus, what would a “Read Me, Delta” segment be without an iconic Labearja letter? We've got you covered, honey. And Delta? She's in HEAT (literally). You think she hates hot weather? Just wait until you hear this monologue. Listen to Very Delta Ad-Free AND One Day Early on MOM Plus⁠   ⁠Send us an e-mail at readmedelta@gmail.com⁠   FOLLOW DELTA ⁠@deltawork⁠   ⁠VERY DELTA IS A FOREVER DOG AND MOGULS OF MEDIA (M.O.M.) PODCAST Learn more about your ad choices. Visit megaphone.fm/adchoicesSee Privacy Policy at https://art19.com/privacy and California Privacy Notice at https://art19.com/privacy#do-not-sell-my-info.

Our Pride series keeps on slaying with none other than Southern California drag royalty, Ivy Colby! Ivy sits down with Delta to talk about the art of being a proud bar queen, the importance of drag competitions, and the unmistakable power of a bangle bracelet. And to the men out there… consider this your warning: these queens will gladly take your money and sit on your face!! Plus, what would a “Read Me, Delta” segment be without an iconic Labearja letter? We've got you covered, honey. And Delta? She's in HEAT (literally). You think she hates hot weather? Just wait until you hear this monologue. Listen to Very Delta Ad-Free AND One Day Early on MOM Plus⁠   ⁠Send us an e-mail at readmedelta@gmail.com⁠   FOLLOW DELTA ⁠@deltawork⁠   ⁠VERY DELTA IS A FOREVER DOG AND MOGULS OF MEDIA (M.O.M.) PODCAST Learn more about your ad choices. Visit megaphone.fm/adchoices