🏡

October 06, 2026
1. 🔗 syncthing/syncthing v2.1.6 release
  Major changes in 2.1
  - Devices and folders can now be grouped in the GUI by setting the new
    group attribute.
  - HTTP and HTTPS proxies with support for CONNECT can now be used, in
    addition to the existing support for SOCKS proxies (the environment
    variable all_proxy=https://...).
  - Block indexing can be turned off for folders where it's more desirable to
    optimise for reduced database size and overhead than minimal transfer
    size (the blockIndexing attribute on folder configuration).
  - GUI login session duration can be configured to be longer or shorter than
    the default one week, or set to infinitely long. The cookie path can also
    be adjusted. (The sessionCookieDurationS and sessionCookiePath
    attributes in the GUI configuration.)
  This release is also available as:
  - APT repository: https://apt.syncthing.net/
  - Docker image: docker.io/syncthing/syncthing:2.1.6 or ghcr.io/syncthing/syncthing:2.1.6
    ({docker,ghcr}.io/syncthing/syncthing:2 to follow just the major version)
  What's Changed
  
  Fixes
  - fix(model): introducers should not be able to add themselves to folders by @calmh in #10880
  - fix(gui): add accessible labels to buttons in Edit Device modal (fixes #10873) by @tomasz1986 in #10874
  - fix(model): properly error out when a temp file can't be created by @calmh in #10883
  - fix: disable keepalive on most outgoing HTTP connections by @calmh in #10891
  - fix(monitor): continue log writes when stdout is unavailable on detached Windows consoles (fixes #10882) by @Shablone in #10889
  - fix(gui): improve header and button color contrast (fixes #10488) by @giri256 in #10815
  - fix: use global short lived HTTP client with proper HTTP/2 support by @calmh in #10901
  - fix: remove unnecessary delay in index transmission by @calmh in #10908
  - fix(watchaggregator): properly convert floating-point time duration (fixes #10899) by @calmh in #10900
  New Contributors
  - @giri256 made their first contribution in #10815
  Full Changelog : v2.1.5...v2.1.6
2. 🔗 HexRaysSA/plugin-repository commits sync repo: +1 release rss
```
sync repo: +1 release

## New releases
- [ida-settings-editor](https://github.com/williballenthin/ida-settings): 1.3.1
```
October 05, 2026
1. 🔗 earendil-works/pi v1.0.4 release
  New Features
  - Tool patterns and--no-mcp: --tools and --exclude-tools accept * patterns, for example --tools read,codemode,'mcp__radius__*' keeps only one MCP server's tools. --tools now keeps MCP tools unless an entry starts with mcp__, and --no-mcp turns off MCP for one run. See Tools and MCP tools.
  - Codemode persists images : tools.read() on an image file now gives back an image block that image() can show. See Call tools.
  Added
  - Added * patterns to --tools and --exclude-tools, for example --tools read,codemode,'mcp__radius__*'
  - Added --no-mcp to disable the built-in MCP support for one run
  Fixed
  - Fixed syntax highlighting losing colors after the first line of multiline strings and comments in fenced code blocks (#10143)
  - Fixed codemode scripts not receiving images from read: tools.read() now resolves to an image block for image files, which image() shows (#10251)
  - Fixed MCP OAuth sign-in failing with invalid_redirect_uri on servers with OpenID Connect client registration, such as mcp.modem.dev: pi now registers as a native client (#10493)
  - Fixed --tools removing MCP tools, which left pi --tools codemode without any MCP servers. --tools now keeps MCP tools unless an entry starts with mcp__
  - Fixed MCP session shutdown returning while a server was still connecting, leaving its transport open until the server answered or timed out (#10249)
  - Fixed system prompt rules and the skills hint naming tools hidden by prepareLoadout. Hidden tools are left out of the rules, the skills hint names no tool when the file reader is hidden, and codemode shows each tool's prompt guidelines with its declaration; ToolLoadout gains getPromptGuidelines() (#10343)
  - Fixed Bedrock requests that fail with The pending stream has been canceled after a stalled HTTP/2 connection not being retried automatically (#10379)
  - Fixed codemode scripts that patch built-ins (for example Array.prototype.toJSON = ...) crashing pi and leaving the tool call unsettled. Built-ins are now frozen before the script runs, so such patches have no effect (#10444)
2. 🔗 r/Harrogate Stolen Bike rss
  
  Unfortunately a long shot…
  Bike stolen from Hornbeam Park Train Station bike shed last Thursday 1st October.
  It was parked up from 8:30 I got back at 5:15 to a lock on the floor 🫠
  
  Anyone saw anything or seen anything at all.. long shot I know
  
  It’s a Specized Allez - Black logo on black frame..
  
  Looks like this in the link https://c02.purpledshub.com/uploads/sites/39/2019/03/specialized\_allez\_roadbike-1497505835774-ql7rfro3fj68-a84f63a.jpg?webp=1&w=1200
  
  How do I add a picture to a post 😅
  
  submitted by /u/shrekwhocooks
  [link] [comments]
3. 🔗 exe.dev The Hardest Working Header on the Internet rss
  
  When your browser reads this blog, it looks up blog.exe.dev using DNS, and sends an HTTP request with a Host: blog.exe.dev header to our servers. Our anycast network receives the request and uses Host: blog.exe.dev to figure out which of all the exe VMs to proxy your request to. Load balancers, CDNs, web servers… the modern web works because of the humble Host header. (SSH does not have such a header, alas.)
  
  exe.dev lets you bring your own custom domain to point to your VM. Thanks to Let’s Encrypt, we're able to provision the certificate on your behalf. And, now, we also let you provision a wildcard certificate, so you can have, for example, *.example.com all point to the same VM, and you can route accordingly. domain add vm-name *.example.com in our lobby is the place to get started, and it'll walk you through it.
  
  An earlier version of this blog post falsely accused Certificate Transparency of delaying how quickly custom domains started working. This is no longer a problem! (DNS time-to-live configuration remains an occasional stumbling block, though.)
4. 🔗 smol-machines/smolvm smolvm v1.23.6 release
  What's Changed
  - Mark a machine initialized once an API start pulled its image by @LoganGrasby in #1572
  - Boot pack machines with a 512 MiB packed-layer DAX window by @LoganGrasby in #1506
  - Size the server's checkpoint caches for its disk and drop an extraction's marker before removing it by @BinSquare in #1573
  - Bump the workspace to 1.23.6 by @BinSquare in #1574
  Full Changelog : v1.23.5...v1.23.6
5. 🔗 smol-machines/smolvm smolvm v1.23.5 release
  What's Changed
  - Run the clone re-mint as a plain shell so it never leaves an orphan for the guest's init to reap by @BinSquare in #1570
  - Bump the workspace to 1.23.5 by @BinSquare in #1571
  Full Changelog : v1.23.4...v1.23.5
6. 🔗 MetaBrainz Happening NOW: AMA with Silona Bonewald, MetaBrainz Foundation Executive Director rss
  
  Silona Bonewald, our new Executive Director, is NOW _hosting an AMA (Ask Me Anything)_ in this forum thread.
  
  Please respect the code of conduct, as you always do!
  
  You are welcome to post questions in the thread later, and Silona will do her best to answer them when she has the time. We will close the thread after a couple of days - though of course the door remains open to chat with the MetaBrainz team any time in the future!
  
  You can find more information about Silona on our Executive Director announcement post.
7. 🔗 sharkdp/hyperfine v1.21.0 release
  Features
  - Add support for minutes and hours in --time-unit, as well as short and plural aliases such as ms, seconds, and min, see #960 (@sharkdp)
  - Expose $HYPERFINE_ITERATION to --prepare and --conclude commands, see #781 and #807 (@willcl-ark)
  - Show elapsed time during the initial benchmark run, see #416 and #581 (@devonhollowood)
  - Add colors to --help output, see #841 (@starsep)
  Changes
  - With --parameter-scan or --parameter-list, --reference now selects an existing benchmark by its full displayed name instead of running a separate reference command. The name must match exactly one benchmark; use --command-name instead of --reference-name in this mode, see #847 and #979 (@sharkdp)
  - Format times in CSV exports with six decimal places, see #966 and #972 (@sharkdp)
  - Update dependencies and raise the minimum supported Rust version to 1.97, see #934 (@sharkdp)
  Bugfixes
  - Make Markdown, AsciiDoc, and Org-mode exports compare against the specified reference, and label faster and slower results in command-sorted comparisons with --reference, see #811 and #979 (@sharkdp)
  - Reject zero values for --runs, --min-runs, and --max-runs instead of allowing invalid run counts, see #923 (@VXNCXNX, @sharkdp)
  - Reject negative parameter-scan steps before expanding ranges, avoiding hangs and excessive memory use, see #951 (@Likio3000)
  - Preserve existing export files when command options are invalid, see #950 (@Likio3000)
  - Truncate export files when rewriting results to avoid leaving trailing bytes, see #970 (@sharkdp)
  - Preserve backticks in command names in Markdown exports, see #947 (@Likio3000)
  - Handle broken output pipes gracefully instead of panicking, see #932 (@Mathjk)
  - Collect peak memory usage separately for each command on Unix, so commands no longer inherit the peak memory usage of earlier commands, see #965 (@sharkdp)
  - Preserve 100-nanosecond precision in Windows CPU times, see #964 (@sharkdp)
  - Python scripts: Correct the interpretation of Welch's t-test results, see #943 (@sharkdp)
  Other
  - Build binaries for Windows ARM64 and Linux ARM64 musl, see #922 and #924 (@meop)
  - Refactor measurement, statistics, and formatting code to use typed quantities, see #954, #958, #961, #967, #969, #971, and #976 (@sharkdp)
  - Improve documentation and examples, including comparisons across Git branches, iteration variables, reference commands, and selective failure handling, see #899, #900, #929, and #940 (@xfocus3, @ded-furby, @Likio3000, @sharkdp)
8. 🔗 smol-machines/smolvm smolvm v1.23.4 release
  What's Changed
  - Let the first machine start create the default machine's disks by @BinSquare in #1566
  - Bump the workspace to 1.23.3 by @BinSquare in #1563
  - Keep the shared extraction trim running when a machine leases a pre-digest or vanished extraction by @BinSquare in #1568
  - Bump the workspace to 1.23.4 by @BinSquare in #1569
  Full Changelog : v1.23.3...v1.23.4
9. 🔗 smol-machines/smolvm smolvm v1.23.3 release
  What's Changed
  - Make cold checkpoint restores stop re-reading the artifact and waiting on RAM fsync by @BinSquare in #1552
  - Keep a request queued behind a start from stopping the VM that start booted by @BinSquare in #1555
  - Stop the systemd scope a refused start created by @BinSquare in #1556
  - Make checkpoint capture fast for restored machines and multi-GB state by @BinSquare in #1558
  - Reclaim shared checkpoint extractions no machine leases beyond the restore cache bound by @BinSquare in #1557
  - Remove the unpublished smolvm-embedded and smolvm-rollout SDKs by @BinSquare in #1559
  - Flatten only a branch source's immutable disk layers, in place, so the chain stays short without copying a layer the VMM can write by @BinSquare in #1550
  - Never let an implicit start restart a machine that is up, and log why a VM is restarted by @BinSquare in #1565
  - Keep a shared extraction while its RAM is still being written back by @BinSquare in #1560
  - Bump the workspace to 1.23.3 by @BinSquare in #1567
  Full Changelog : v1.23.2...v1.23.3
10. 🔗 earendil-works/pi v1.0.3 release
  New Features
  - Azure Foundry Chat Completions — The azure provider (renamed from azure-openai-responses) now also serves Foundry Chat Completions deployments, starting with azure/deepseek-v4-pro. See Azure OpenAI.
  - Codemode images saved to files — image() also writes each image to a temp file and names the path in the result, so later turns can copy or move generated images. See Generate images.
  Breaking Changes
  - Renamed the Azure provider from azure-openai-responses to azure. Rename the provider key in auth.json (or run /login again), in models.json, and in settings.json (defaultProvider, enabledModels patterns, and modelThinkingLevels keys). Sessions that used the old provider fall back to another model when resumed, and their prompt cache is not reused. The AZURE_OPENAI_* environment variables are unchanged (#9714 by @jsanter27)
  Added
  - Added Azure Foundry Chat Completions deployments, starting with azure/deepseek-v4-pro (#9645, #9714 by @jsanter27)
  Changed
  - Codemode image() now also saves each image to a temp file and names the path in the result, so later turns can copy or move generated images (#10310)
  - Output files (full text of truncated tool output, binary MCP resources, codemode images) are now readable only by the user
  - Home/End now always move the editor cursor to the line start/end; fullscreen transcript top/bottom moved to Ctrl+Home/Ctrl+End, which no longer move the editor cursor (#10314)
  Fixed
  - Fixed subscription logins such as Sign in with ChatGPT failing with refresh_token_invalidated after a request was cancelled during an OAuth token refresh
  - Fixed codemode failing for the rest of a session after a pnpm global update removed the running install, and added a restart hint when errors occur after pi was updated or removed on disk (#10439)
  - Fixed interactive sessions reporting a read EIO or setRawMode EIO crash (and asking to run /bug) when the terminal went away, e.g. after closing the window or resuming a suspended pi in a closed terminal
11. 🔗 smol-machines/smolvm smolvm v1.23.2 release
  What's Changed
  - Show the Homebrew install in the README by @BinSquare in #1551
  - Finish a restore instead of relaunching the workload when exec wakes a restored machine by @BinSquare in #1553
  - Bump the workspace to 1.23.2 by @BinSquare in #1554
  Full Changelog : v1.23.1...v1.23.2
12. 🔗 matklad Benchmark In Milliseconds rss
  Benchmark In Milliseconds
  
  Oct 5, 2026
  
  How long should a micro benchmark run? My rule of thumb is to tweak the input size until the benchmark takes about 300ms, for the following reasons:
  - Milliseconds are integers ranging from 1 to 999. Enough precision to notice even a small improvement, and easy to scan visually. No need for different units or floating points (compare 1.31s with 239ms).
  - Anything faster than, say, 10ms risks being skewed by fixed costs (e.g, interpreter startup). Hundreds of milliseconds is an eternity for a computer, usually enough to make one-off overheads irrelevant without using fancier (= less robust) techniques to explicitly account for them.
  - For a human, hundreds of milliseconds is fast, but noticeable. Pushing numbers into human-perceptible range allows me to use my intuitive sense of time and speed, it doesn’t rely exclusively on numeracy. It’s plain fun to see, as a result of optimization work, how a previously lagging CLI command becomes “instant”.
  - But anything longer than a second makes iterating on the benchmark slower than it needs to be. Running a benchmark 10 times in a row to eyeball variance should be fast!
  The imminently-to-be-stated assumption here is that the purpose of benchmarking isn’t so much a precise measurement of performance, but rather providing the author with enough intuition to make a correct decision.
13. 🔗 Filip Filmar Linux boots to a shell on Vreteno rss
  
  Mainline Linux now boots to a shell on Vreteno, the RISC-V core written in TxHDL. It runs on the Alinx AX7A200B board, an Artix-7 FPGA with 1 GiB of DDR3 memory, at 100 MHz. The kernel runs in supervisor mode with virtual memory turned on. OpenSBI runs in machine mode below it, and a BusyBox shell runs in user mode above it. This post describes what the core needed for that, how the boot was brought up, and what is still missing.
October 04, 2026
1. 🔗 smol-machines/smolvm smolvm v1.23.1 release
  What's Changed
  - Stop live disk-chain merges and fix the merge claim deadlock by @BinSquare in #1546
  - Let a no-network machine whose registry image the host fetched be checkpointed by @BinSquare in #1545
  - Report in-flight requests on loopback and exit promptly after the shutdown grace by @BinSquare in #1544
  - Accept an image reference with both a tag and a digest by @BinSquare in #1549
  - Keep restored machines branching and log server error reasons. by @BinSquare in #1548
  - Bump the workspace to 1.23.1 by @BinSquare in #1547
  Full Changelog : v1.23.0...v1.23.1
2. 🔗 MetaBrainz Picard 3.0 released rss
  The Picard team is happy to announce the new major version 3.0 of MusicBrainz Picard, now available to download. MusicBrainz Picard is the official tag editor for the MusicBrainz database and helps you get your music collection sorted and cleaned up with data from MusicBrainz.
  
  ![An image of a mock software cardboard box, showing "MusicBrainz Picard" as the title. There are two worn-out looking stickers visible on the box, one saying "Complete Tagging Solution", one "Community Support".
  
  Beside the box there is a pink / orange circle with the text "Version 3".](https://blog.metabrainz.org/wp-content/uploads/2026/10/Picard- Update-3-edited-1024x889.png)
  
  This release brings many changes, including an upgrade to Qt6, a completely new plugin system, several improvements to the user interface, cover art processing, ISRC submission and many more. More details below.
  
  What's new? User interface improvements Qt is the application framework Picard is built upon. Qt simplifies the implementation of cross-platform desktop applications as it abstracts away many of the differences between various operating systems. Picard 2 was based on Qt5. With Picard 3 we have updated to Qt6. Besides ensuring that Picard stays up-to-date and available on modern desktops, this version change also brings some advantages like much improved support for screen scaling and better support for a dark mode. Specifically on Windows the old issues of having fonts scale inconsistently are now resolved. The UI now also supports a dark mode across all operating systems and switching between light and dark mode does no longer require a restart of the application. Picard already supported customizing the file and album list views by selecting the columns to display. In previous versions this was limited to a couple of pre-defined columns, though. New contributor knguyen1 implemented full custom column support. You can now define your own columns, where you can define the actual column content using scripting. This gives a lot of flexibility showing exactly the information you need. There is also a new pre- defined “Match” column that allows to sort releases by match quality. For more details see the chapter Custom Columns in the documentation. The columns context menu, allowing you to customize the columns being shown in the main list views. Another new feature, implemented by jpmsousa03, is the ability to filter the list views. You can select the fields to search and enter a search term. Only items matching this filter will be shown. It is now possible to select and copy multiple tags in the metadata view and paste them on e.g. another tag, updating all corresponding tags. It is also possible to paste multiple copied values into a spreadsheet tool. This feature was provided by StevilKnevil. The metadata view now also shows the actual differences between existing tags and the new tags being written. On a first start Picard now shows a setup wizard, that guides new users through some essential configuration. !Setup Wizard showing the File Organization settings. Also some essential functionality, such as loading files and clustering, gets explained by a tutorial mode when a feature is first used. Both the wizard and tutorial can be disabled or re-enabled in the user interface options. The tutorial being shown when a release is loaded for the first time. New plugin system
  
  Apart from the Qt6 migration the new plugin system is the most significant change in Picard 3. While the previous plugin system enabled a lot of flexibility in Picard, it has a couple of limitations. For example, Picard would load, and partially run, the code of each installed plugin on every start, whether the plugin was enabled or not. This could lead to unwanted side effects and unexpected behavior. On the development side it proved also difficult for third-party developers, especially for more complex plugins, as all code had to be checked into the central picard-plugins Git repository.
  
  The new plugin system provides:
  - Separation of plugin metadata and code: MANIFEST.toml is mandatory
  - A defined plugin API with typing support
  - Git based versioning and updating of plugins
  - Plugins can be installed and updated from a central plugin registry, from third-party Git repositories, or from a local directory
  - Several trust levels (official, trusted, community, untrusted)
  - The ability to blacklist plugins centrally allows us to react on security issues
  - A picard-cli command line tool to manage (install, uninstall, update…) plugins
  - Plugins now support their own translation system (optionally manageable via Weblate), so their user interface texts can be translated
  - Plugins have their own configuration namespace
  All the extension points known from Picard 2 to register metadata processors, context menu actions, cover art providers, file formats, option pages etc. are still available. But there are several new extension points; plugins can now register cover art filters and processors, custom variables, actions in a global "Plugin Tools" menu and CD ripping log file formats.
  
  As a user, the new plugin management under Options → Plugins now clearly separates installed plugins from plugins available for installation. Both the list of installed and available plugins can be searched, and it is possible to install plugins from third-party developers. See the Plugins Options documentation for a more in- depth description.
  
  The new Plugins option page, showing a list of currently installed plugins.
  
  This also means that Picard v2 plugins are not compatible and need to be migrated to the new system. There are already 30 plugins available, both plugins migrated from v2 and brand new ones. Have a look at the plugins v3 list on the Picard website.
  
  If you are a developer and want to update your plugins to Picard 3 or maybe write a new one, please see the Plugin overview in the Picard User Guide and the detailed Picard Plugin v3 Documentation.
  
  Cover art processing It is now possible to both filter and process cover art loaded from cover art providers. The new options in Cover Art / Processing allow you to ignore images below a certain size or automatically resize loaded images or convert them to a specific file format. Cover art processing can be extended by Plugins, which can register their own cover art filters and processors. Filters can restrict what cover art gets loaded, while processors can perform image processing on the loaded cover art. Cover art processing was implemented as part of Google Summer of Code 2024 by twodoorcoupe. You can read more about this in twodoorcoupe’s blog post GSoC 2024: Picard image processing. New tags and scripting enhancements As full support for synced lyrics was added, there is now a new %syncedlyrics% tag. The MuicBrainz Artist ID of a composer is available as a new tag %musicbrainz_composerid%. There are also several new variables, that provide data for tagging and naming scripts, but are not written as tags to the files by default. The new %_genres% and %_folksonomy_tags% variables give you access to the raw list of genres or folksonomy tags as loaded from MusicBrainz. For recordings with a broadcasted relationship the broadcasting date is available as %_broadcast_date%. If a recording has a linked work with a ISWC, the ISWC is now available as %_iswc%. The variables %_albumartists_countries% and %_artists_countries% contain all country codes for all credited album artists / track artists. Likewise the disambiguation comments for artists and album artists are available as %_artistcomment% and %_albumartistcomment%. The %_filesize% variable contains the file size in bytes (if the script is running in a context where a file is available, i.e. on tracks with a matched file or in a file naming script). There are now two new functions and [$get_original()](https://picard- docs.musicbrainz.org/en/latest/functions/func_get_original.html), which allow to explicitly request the original or new value of a variable. The $rsearch scripting function gained a new optional parameter, which can be used to specify the capture group inside the regular expression to be returned. Please see the documentation of the $rsearch function for an example. Improved built-in player
  
  The built-in player received several improvements. As before the player is based on QtMultimedia. With Qt6 this component brings better cross-platform support for various audio formats and pitch-adjustment if playback speed changes (requires Qt 6.10).
  
  The player has also been internally refactored to better separate the player and UI. This allows better integration with the OS. The player now supports macOS “Now Playing” and on Linux can be controlled by MPRIS2 compatible tools. It can also submit listens to ListenBrainz. Both OS integration and ListenBrainz support can be configured in the new Audio Player Options.
  
  Save and restore user session
  
  Picard can save and restore your current workspace state as a session file under the main File menu. Sessions preserve file placement (unclustered, clusters, albums, specific tracks, and standalone recordings), your manual metadata edits, and selected configuration options so you can resume work later. Thanks to knguyen1 for this feature. See the chapter Sessions Management in the documentation for more details.
  
  Export / import option profiles
  
  Option profile support was already available in Picard 2. Option profiles allow you to create multiple different set of configuration options and quickly switch between them. With Picard 3 such option profiles now also can be exported and imported, both as a backup or to share them with others. If an option profile is exported in order to share it, the export will exclude any configuration options that are considered secret or private (such as authentication data). For details see the User Guide under Backing Up and Sharing Profiles.
  
  Exporting and importing option profiles can also be done using the new picard-cli command line utility, see below.
  
  We are excited to see how this feature will be used by the community.
  
  Operating system support
  
  Picard is now available for macOS ARM64 aka Apple silicon. While it was previously possible to run Picard on such systems using Apples Rosetta 2 emulation layer, the native builds offer better performance. Please note that there are separate downloads for the ARM64 and Intel versions of Picard. Please make sure to download the file appropriate for your hardware.
  
  Due to the updated dependencies, in particular Picard now using PyQt6 / Qt6 and the minimum supported Python version being 3.10, support for older operating systems had to be dropped.
  Picard 3 requires Windows 10 or later or macOS 13 or later. Linux users should have Qt 6.6 or later and at least Python 3.10 available.
  
  CD disc lookup from tags and more log file import options
  
  The existing functionality to lookup disc IDs from CD ripping log files was extended to support raw SCSI TOC data files as written by redumper.
  
  For files ripped with iTunes / Apple Music and which contain the CD TOC as a iTunes_CDDB_1 tag it is now possible to perform a disc ID lookup directly from the tag. This is explained in detail in the User Guide under Lookup iTunes Tag.
  
  Synchronized lyrics
  
  Picard 3 provides initial support for synchronized lyrics. It can load and save a syncedlyrics tag from ID3 and WMA tags. The synchronized lyrics are using the LRC format to describe the timings. We plan to extend support for synchronized lyrics with future updates to support more tagging formats and lyrics features.
  
  Translation of artist, release and track titles by aliases
  
  The existing system to translate artist names using aliases has been extended to also provide translations of album and track titles. Also the old behavior of always falling back to using the sort name as translation has been made optional and is now disabled by default. See the Metadata Options documentation for details.
  
  The new metadata translation options, which allow to translate artist names as well as album and track titles.
  
  Improved release matching
  
  The algorithm for matching files to releases and recordings after a Lookup was totally reworked and greatly improved.
  Overall we expect the new algorithm to give better results. There is now also an extensive test framework in-place that allows us to detect regressions in the matching performance in the future.
  
  ISRC lookup and submission
  
  Picard now supports extracting ISRCs from CDs and adding them to loaded releases. It can also submit ISRCs loaded from disc or already present in the tags back to MusicBrainz. If new ISRCs are present for matched files, the ISRC submission dialog can be opened from the menu in File → Submit ISRCs. For details see the documentation on Submitting ISRCs.
  
  The new ISRC submission dialog. It will show which new ISRCs are available for a recording and can submit those ISRCs back to MusicBrainz.
  
  Individual files with an existing ISRC tag can also be looked up by ISRC using Lookup by… → Lookup by ISRC from the file's context menu.
  
  Command line utility "picard-cli"
  
  Picard 3 comes with a new command line utility "picard-cli". Currently this allows managing plugins and exporting/importing option profiles from the command line. Run picard-cli --help for more details.
  
  Updated Picard User Guide
  
  The online documentation available at https://picard-docs.musicbrainz.org has been updated for all of the changes in Picard 3. It is now hosted on ReadTheDocs and available in English, French and Dutch. When opening documentation pages from inside Picard the links will use the language matching Picard's user interface language, if available. You can help translate the Picard User Guide into your language, see the instructions for Picard, Picard Website and Picard User Guide Internationalization.
  
  Performance and memory optimizations
  
  This release includes several optimizations to improve the speed and responsiveness of Picard during certain operations and to reduce memory use.
  
  And more…
  
  There have been many more improvements and bug fixes: Picard 3 is the product of roughly three years of work that began in late 2023 with the move to PyQt6: 687 merged pull requests, nearly 6,800 commits from over 100 contributors (including 40-ish translators), and almost 400 resolved tickets.
  
  A good part of the code was rewritten, to ease maintenance and future evolution. Static typing is now used (but covering the whole code will take some time, we focused on important parts).
  Test coverage is also much larger.
  
  Please see the change log for a complete list of changes.
  
  Download
  
  Picard 3.0 is available for download from the download page of the Picard website.
  
  Please note: For Windows users installing from the Windows Store the update to version 3.0 is not yet available. We will provide a Windows Store release with an update shortly. The Linux Flatpak package is maintained separately and will be updated soon.
  
  Picard is free software and the source code is available on GitHub.
  
  Acknowledgements
  
  Getting this new major version of Picard ready was a huge effort, one that wouldn't have been possible without the many contributors. Thanks to everyone who helped with code, translation or reporting issues and feature requests.
  
  Code contributions by Adela Chang, Akshat Khatri, Anton Kesy, Arnab Chakraborty, Bob Swift, Bryan Roessler, David Kellner, Deepak Kumar, Francisco Lisboa, FRC, Goldmaster, Greg Myers, Deepak Tiwari, James Le Cuirot, joncrall, João Sousa , Julian Anderson, Kajal Soni, knguyen, krotka, Laurent Monin, Lctrs, leo60228, Marethyun, Martin, Martin Natano, metaisfacil, OscarL, Philipp Wolfer, pranavsource1, Rakim, ripstream, Sanskar Mittal, Alex, ShubhamBhut, soniikajal, Sophist, StevilKnevil, nullHawk, thekiefs, Thuna, Giorgio Fontanive, x11x and Yohay.
  
  Translations were updated by:
  
  Albanian: Besnik
  Arabic: alaishaq
  Catalan: Marc Riera
  Chinese (Simplified Han script): imgradeone, KenParker_CN and Nebulain
  Chinese (Traditional Han script): BestSteve, Iceman1415 and silentbird
  Czech: Fjuro
  Dutch: mfmeulenbelt, RandomMushroom128 and toineenzo
  English (United Kingdom): glawie
  Estonian: Priit Jõerüüt
  Finnish: Jaakko Perttilä
  French: Laurent Monin and rez00
  Galician: ninjum
  Georgian: NorwayFun
  German: bababasti, chaban, Gsam3, janrieger, Philipp Wolfer and st.esser
  Greek: Theo Asimakopoulos
  Hungarian: hildgyorgy and pXF
  Italian: GABG and salo.rock
  Japanese: marudosurdo, RT2231, shuuji3 and zatto13
  Korean: coldified_
  Lithuanian: Vaclovas Intas
  Malay: Jeluang
  Norwegian Bokmål: "ApeKattQuest, MonkeyPython" and Metafono
  Polish: ankhedonic, Echelon and Michal77
  Portuguese: evarfino and joaodtx
  Portuguese (Brazil): cristian_emanuel and vitortle
  Russian: Dimlbur, wileyfoxyx and Wonordel
  Spanish: deusdagon, Dino RTX, jaimeMF and Nicolás Tamargo
  Spanish (Latin America): MichTheOcelot
  Swedish: blueday
  Turkish: brtc and dirt3009
  Ukrainian: Arhidimon, emptybrainz, Nerten and oleh_hishak
  
  Get in touch
  
  Please use the MetaBrainz community forums and the ticket system to give feedback, suggest new features or report bugs.
  
  Breaking changes
  - Support for older operating system versions was dropped due to the update to Qt6 and newer Python versions. That means the minimum supported Windows version is now Windows 10, while for macOS you need macOS 13 "Ventura" or later. Users on older operating systems, who cannot or do not want to update their OS, should continue to use Picard 2. We plan to do at least one final Picard 2 release with important fixes to allow this version to be continued to be used.
  - Not all plugins from Picard 2 are available. Several important ones have been ported, but some old plugins were unmaintained or do not meet the quality standards expected. If you miss a specific plugin you rely on please let us know in the community forums.
  - The artist sort name by default is no longer used as a fallback to provide a "translated" name. The previous behavior resulted in several bugs being reported with wrong artist names after translation. If you relied on the old behavior you can restore it by enabling "Use artist sort name for translation" in the Metadata Options.
  - Passing a parameter to the $matchedtracks() scripting function now is an error. Previously it was possible to pass a parameter to this function (e.g. $matchedtracks(%artist%)), but it had no effect.
  - The lyrics and comments tags now always support a language, which is used when the tag is being loaded from or saved to ID3. The format is lyrics:lang:description / comment:lang:description, where lang is a 3 letter ISO code and description an additional descriptive text. If the language is being omitted, the separating colons are still mandatory, e.g. comment::description.
  Known issues
  - On macOS, in some setups, the global menu is not showing check marks for checkable menu items. It is currently unclear which exact setups are affected by this. If you experience this issue, please reach out with details on your macOS version (see PICARD-2509).
  - Restoring a large session takes a significant amount of time and causes the UI to become unresponsive. We plan to improve this in future releases (see PICARD-3460).
  - The picard-cli command line tool is not available on macOS when being installed as an app. However, it can be installed by installing Picard from PyPI.
  Change log
  
  Since the last stable Picard release 2.13.3 there have been 14 pre-releases for Picard 3. During the development we addressed 393 tickets to fix bugs, add features and improve existing functionality. Please see the detailed change log on the website for a full list of changes.
3. 🔗 smol-machines/smolvm smolvm v1.23.0 release
  What's Changed
  - Explain published ports whose guest server listens only on loopback by @BinSquare in #1514
  - Bump the workspace to 1.22.3 by @BinSquare in #1515
  - Bump the Nix package to 1.22.2 and refresh the flake inputs by @BinSquare in #1517
  - perf: cut the per-run registry tax on seeded starts by @BABTUNA in #1511
  - agent: expedite RCU before the shutdown freeze by @BABTUNA in #1520
  - Let x86_64 machines attach devices on IRQs 16-23 so more volumes boot by @BinSquare in #1521
  - Resume a live checkpoint's source before its saved RAM reaches disk by @BinSquare in #1519
  - Branch a running machine without limit and remove the disk layers no branch reads by @BinSquare in #1526
  - Let smolvm serve run nested-virtualization machines only when started with --allow-nested-virt by @BinSquare in #1528
  - Let a checkpoint taken on an arm64 Mac restore on arm64 Linux by @BinSquare in #1531
  - Add an operator-supplied egress watchlist to smolvm serve by @BinSquare in #1530
  - Bump libkrun and libkrunfw so a Mac checkpoint restores on arm64 Linux by @BinSquare in #1532
  - Enforce the VMM syscall filter by default on arm64 serve, as on x86_64 by @BinSquare in #1533
  - Let a machine with no network boot a registry image by @BinSquare in #1536
  - Share and keep one cache take per checkpoint so restores stop re-hashing it by @BinSquare in #1535
  - Let a paused machine's saved execution upload to the object store in parallel parts by @BinSquare in #1534
  - agent: observe workload exit through a pidfd by @BABTUNA in #1525
  - Bump the workspace to 1.23.0 by @BinSquare in #1541
  Full Changelog : v1.22.2...v1.23.0
4. 🔗 r/Harrogate Party venue rss
  
  Hi,
  
  I’m going to be hosting a party for around 70 people so looking for some recommendations in and around Harrogate.
  Criteria would be that I can arrange my own food and DJ, but there’s a bar.
  
  Anywhere good that you have personally used?
  I’ve thought of a couple of places but open to other suggestions.
  
  TIA!
  
  submitted by /u/eldaja7
  [link] [comments]
5. 🔗 roboflow/supervision supervision-0.30.7 release
  v0.30.7 — Fewer hangs, truer mAP
  
  Eight bug fixes: video processing, dataset export, mAP and Transformers loading no longer fail or hang silently.
  - process_video raises on a failed write instead of hanging.
  - MeanAveragePrecision matches pycocotools where recall lands on a threshold.
  - Dataset export can write back into the folder the images came from.
  - from_transformers reads semantic output that includes per-pixel scores.
  Drop-in upgrade, no code changes. Stored mAP baselines may shift slightly.
  
  ✨ Spotlights / highlights
  
  sv.process_video stops hanging (#2636)
  
  A frame the writer rejects, or a callback that returns None, now raises instead of blocking forever.
```
import supervision as sv

def callback(frame, index):
    sv.BoxAnnotator().annotate(frame.copy(), detections)  # forgot `return`

sv.process_video("in.mp4", "out.mp4", callback)
# before: hangs after `writer_buffer` frames
# now:    TypeError naming the frame
```
  sv.metrics.MeanAveragePrecision matches pycocotools (#2638)
  
  Recall thresholds and recall are float64, as in COCOeval. A class whose recall lands exactly on a threshold used to score slightly high: mAP@50 0.7470 instead of 0.7415 in one case.
  
  Datasets re-export in place (#2637)
```
ds = sv.DetectionDataset.from_coco(
    images_directory_path="data",
    annotations_path="data/_annotations.coco.json",
)
ds.as_coco(
    images_directory_path="data",
    annotations_path="data/_annotations.coco.json",
)
# before: shutil.SameFileError
# now:    annotations rewritten, images left in place
```
  Transformers semantic output with scores (#2643)
  
  sv.Detections.from_transformers accepts results from return_segmentation_scores=True instead of raising KeyError: 'segments_info'.
  
  🔄 Migration guide
  
  No migration required for this release.
  
  📝 Notable changes
  
  🔧 Fixed
  - sv.process_video raises RuntimeError("Writer thread raised: ...") or TypeError instead of hanging when a frame cannot be written or a callback returns None. (#2636)
  - sv.metrics.MeanAveragePrecision computes IoU and recall thresholds, IoUs and recall in float64, matching pycocotools. mAP changes only for classes whose recall lands exactly on one of the 101 thresholds, by up to about 0.007 mAP@50. (#2638)
  - sv.DetectionDataset.as_yolo, as_pascal_voc, as_coco, as_createml and as_labelme export into the folder the images were loaded from instead of failing with shutil.SameFileError. (#2637)
  - sv.Detections.from_transformers accepts semantic segmentation output with segmentation_scores; per-pixel scores stay out of per-detection confidence. (#2643)
  - sv.crop_image clips finite crop coordinates outside the 32-bit integer range to the image bounds, instead of wrapping to an empty crop. (#2642)
  - sv.DetectionDataset.as_labelme gives disconnected components of one mask a shared group ID, so from_labelme rebuilds one detection. (#2640)
  - sv.DetectionDataset.as_labelme, as_yolo and as_pascal_voc export in-memory grayscale (height, width) images. (#2641)
  - sv.KeyPoints.with_nms keeps skeletons with zero joints instead of raising a zero-size reduction error. (#2639)
  🏆 Contributors
  - kevin (@kevin9327) — stopped process_video hangs, made mAP match pycocotools, and fixed in-place dataset export.
  - Marvel Harisson (@INo-xious, LinkedIn) — fixed LabelMe grouping, grayscale dataset export and keypoint NMS.
  - NIKHIL (@Nikhi00718) — fixed crop_image clipping and Transformers semantic output loading.
  Full changelog : 0.30.6...0.30.7
6. 🔗 streamyfin/streamyfin v0.55.0 release
  What's Changed
  
  This is the biggest Streamyfin release so far. The headline is a fully native video player on every platform: SwiftUI on iPhone, iPad and Apple TV, Jetpack Compose on Android and Android TV. It brings new gestures, a sleep timer, dialogue boost and in-player subtitle search, and it is the default on iPhone, iPad and Apple TV (tvOS 26+). On Android and Android TV it is opt-in for now
  
  Around the player, subtitles got a full overhaul, media segments can be skipped everywhere, transcoded downloads finally play offline with multiple subtitles, and the home screen has a new hero carousel and redesigned cards. Android TV gains an ExoPlayer engine with real HDR output, Dolby Vision and Atmos passthrough, plus a proper TV menu
  
  As usual, thanks to everyone filing issues, testing builds, translating strings, and helping move the project forward!
  
  ✨ Highlights
  - Fully native video player on iPhone and iPad (#1929), Apple TV (#1930, #1935), Android (#1958) and Android TV (#1968)
  - New player gestures and tools , double tap to seek (#1933), hold for 2x speed, pinch to zoom-to-fill, sleep timer, dialogue boost and in-player subtitle search and download
  - HDR on Android TV , opt-in ExoPlayer engine with HDR10/HDR10+ (#1783), Dolby Vision Profile 5 direct play and Dolby Atmos passthrough (#2002)
  - Skip intros, credits, recaps, previews and commercials on every player (#1367)
  - Subtitle styling , font, colour, background and opacity (#1543), and subtitles shown automatically while muted (#1900)
  - Transcoded downloads with offline subtitles (#1889), with download progress as a Live Activity on iOS (#1924)
  - New home screen , native hero carousel on iOS (#1979) and Android (#1983), and media rows redrawn as artwork-backed cards (#1984)
  - Seerr sign-in with Quick Connect , no more retyping your password (#2008, #1908)
  - Custom auth headers for servers behind Cloudflare Zero Trust or an authenticating reverse proxy (#1961)
  - Award and Oscar status on movie and series pages (#1911)
  🎬 Player
  - Play resumes right where you left off by default, with a setting to be asked instead (#1998)
  - Audio and subtitle choices are remembered per series, plus a mono downmix option
  - Original audio language setting (#1938)
  - Subtitle and audio tracks are selected by identity instead of list position, fixing wrong tracks with duplicate languages and burned-in subtitles (#1781, #1944)
  - Subtitle menus are ordered like Jellyfin Web, and keep that order on iOS (#1781, #1847)
  - Bundled fallback fonts so subtitles render in more languages on iOS and tvOS (#1993, #2019)
  - AV1 transcoding (#2052), and AV1 direct play only when the device can hardware-decode it (#1923)
  - Hold-to-speed with a configurable rate (#1931) and hardware keyboard support (#1773) in the standard player
  - Source file bitrate in the technical info overlay (#1829)
  - Watch state is reported reliably on exit, on transitions and for downloaded items (#1662, #1823, #1872, #1873, #1879, #1890, #2003, #2017)
  - The "still watching" prompt only appears at the end of an episode and pauses playback while it waits (#1956)
  - Picture-in-picture fixes on iOS (#1667, #1870, #1918, #2094) and Android (#1778)
  - Chromecast delivers text subtitles as selectable tracks instead of burning them in, and H265 casting works again (#1972, #1910)
  - Other apps resume their audio after you leave the player (#1651)
  - Correct punctuation placement in right-to-left subtitles (#1932)
  - Previous and next episode buttons at season boundaries and with missing episodes (#1649)
  📺 TV
  - Android TV now uses a proper TV menu instead of the mobile layout (#1709)
  - TV interface scales to the display resolution, with reworked focus styling (#1987)
  - Quality selector in the TV player controls (#1824)
  - Shuffle episodes from the series page
  - Scrubbing on tvOS shows an episode poster preview (#1941)
  - Subtitle search in the native tvOS player (#1936)
  - Fixed silent audio on tvOS with Atmos and Continuous Audio Output (#1970, #1990)
  - Playback pauses when the tvOS app is backgrounded (#1934)
  - Apple TV Top Shelf images are no longer cropped (#1726, #1825)
  - Home screen episodes show their series name, with the backdrop as a fallback image (#1888, #1887, #1999)
  - "See All" opens the library, and Back returns to the library list (#1782)
  - Changing audio track while transcoding re-negotiates the stream (#1791)
  - Seerr posters and search tabs match the rest of the TV interface (#1898)
  - Assorted Android TV fixes (#1672)
  ⬇️ Downloads
  - More accurate size estimates for transcoded downloads (#2084)
  - Downloads survive the screen turning off on Android (#1546, #2000)
  - Faster with large download libraries, and no more crash when moving to the next downloaded episode (#1547)
  - Delete-all confirmation and live storage usage (#1808)
  - Items deleted on the server no longer break playback sync (#1845)
  - Posters show for downloaded content (#1652), and direct downloads use the right media source (#1666)
  🐛 Fixes
  - Jellyfin 12 compatibility (#1801, #2085)
  - Continue Watching updates instantly, including changes made on other devices (#1439)
  - Recently Added on mobile matches Jellyfin Web (#2128)
  - Unwatched episode count on series and box sets (#1787)
  - Option to use episode images in Next Up and Continue Watching (#1817), and no more black thumbnails there (#1815)
  - The app opens on Home after a cold boot instead of Libraries (#1945)
  - Each library remembers its own filters, and reset clears the sort too (#1814)
  - Quick Connect code opens in a sheet that closes itself once you are signed in (#1809)
  - Expired sessions are cleaned up properly, and the app no longer hangs on the splash screen when offline (#1809)
  - Server addresses with http:// are honoured, and server probes time out instead of hanging (#1977, #2013)
  - Tapping a notification opens what it is about, even when the app was closed (#2078)
  - Live TV streams are released, so channels stop failing on the tuner stream limit (#1799)
  - Seerr requests seasons the same way Seerr does, and servers with non-semver versions are accepted (#2125, #1980)
  - Admin-locked settings are enforced, and plugin defaults apply correctly (#1807)
  - The music queue no longer follows you to another account (#1854)
  - Tapping a poster twice no longer opens the same screen twice (#1806)
  - The series page selects the season of the current episode (#2109)
  - Network location settings (#1800)
  ⚡ Performance
  - Worklets are precompiled in production builds, roughly halving native memory use on Android (#1848)
  - General playback performance fixes (#1765)
  🔧 Build & Infra
  - Expo SDK 56 → 57 and React Native 0.86 (#1838, #2097)
  - TypeScript 6, with scripts, app config and config plugins migrated to TypeScript (#1717, #1718, #1719)
  - Android targets API 36 (#2096), and iOS scene lifecycle support (#2108)
  - MPVKit 0.41.0-av5 (#1995, #2029)
  - Anonymous crash and error reporting through Sentry, with an opt-out in settings (#1976, #1978, #1994)
  - Test suite moved to jest-expo and React Native Testing Library (#2006)
  - Dropped the third-party IP location lookup (#2014)
  🌍 Translations
  - Ongoing Crowdin sync (#1699, #1758, #1810, #1821, #1925, #1967, #2069)
  - German translations completed and corrected (#1843), and remaining hardcoded strings made translatable (#1818)
  - Want to help translate Streamyfin? Join us at translate.streamyfin.app
  🛟 Support & Reporting Bugs
  
  The player was rewritten on every platform, so some rough edges are expected. Real-device reports are the fastest way to get them fixed.
  - Bugs and feature requests: open an issue. Search existing issues first and add to a match if there is one.
  - Questions and help: Discord
  Include in bug reports: app version, platform and device, OS version, Jellyfin server version, direct play or transcoding, the media's codecs and subtitle format, which player you used (native or standard), steps to reproduce, and logs or a screen recording if possible.
  
  👋 New Contributors
  
  Full Changelog : v0.54.1...v0.55.0
7. 🔗 HexRaysSA/plugin-repository commits sync repo: +2 releases, -2 releases rss
```
sync repo: +2 releases, -2 releases

## New releases
- [ida-mcp](https://github.com/hexrayssa/ida-mcp): 20261003.0.1
- [ida-nexus](https://github.com/hexrayssa/ida-nexus): 0.13.3

## Changes
- [ida-mcp](https://github.com/hexrayssa/ida-mcp):
  - removed version(s): 0.8.0
- [ida-nexus](https://github.com/hexrayssa/ida-nexus):
  - removed version(s): 0.6.2
```
8. 🔗 Register Spill Joy & Curiosity #102 rss
  At the airport, on my way to New York to meet the rest of the Amp team, so no big intro this week. If you're around, you should come meet us.
  - The Next Feature Fallacy: "For people who love to build product, when something's not working, it's tempting to simply build more product. It leads to the launch-fail-relaunch cycle that I alluded to in a previous essay, Mobile app startups are failing like it's 1999. However, this rarely works, and when you look at the metrics, it's obvious why."
  - So, Google released Gemini 4 Argon. There's a whole bunch of numbers and percentages in that post and most of them I don't care about or trust, but this paragraph made me purse my lips as if to let out an impressed oooh : "A team of Argon agents analyzed fleet-wide profiling telemetry to autonomously identify and apply memory optimizations across Google's data centers, freeing up over 300 TiB of memory once rolled out, with an estimated 500 TiB to 1 PiB in total savings."
  - Daniel Lemire with a fascinating perspective: "There is a divergence in society. Some of us have been frustrated by the lack of progress. We don't like what has been happening to our civilization since 1970. We expected lunar bases, rejuvenation cures, cancer cures, space trips... and all we got was Twitter. […] I feel that the people who love stagnation got enough of what they wanted and I hope that we are at an inflexion point where we finally break free from the oppressive rule of stagnation." I've had similar thoughts before: if you walk through this small town in which I live, nearly everything looks like it did thirty years ago. One reason for that, of course, is that we now all spend many hours per day staring at screens and those screens contain large portions of our lives and no one has their screens sitting on the porch (although they sit with their screens there). Reading Lemire's post made me realize, again: for most of us the most positive vision of the future looks like the 90s. And that's… sad, isn't it?
  - "Several vulnerabilities have been discovered in the Linux kernel that
    may lead to a privilege escalation, denial of service or information
    leaks." Several, in this case, means 1597. Sign of the times.
  - I haven't read more than the first paragraph yet, but in a few seconds, once you've read it too, you'll agree that, yes, one can stop there and it would still be enough: "One warm spring night in 2011, a young man named Travis Hughes stood on the back deck of the Alpha Tau Omega fraternity house at Marshall University, in West Virginia, and was struck by what seemed to him--under the influence of powerful inebriants, not least among them the clear ether of youth itself--to be an excellent idea: he would shove a bottle rocket up his ass and blast it into the sweet night air. And perhaps it was an excellent idea. What was not an excellent idea, however, was to misjudge the relative tightness of a 20-year-old sphincter and the propulsive reliability of a 20-cent bottle rocket. What followed ignition was not the bright report of a successful blastoff, but the muffled thud of fire in the hole." But still, I want to read the whole thing now.
  - This was an amazing peek into a community I didn't even know existed: Pirating the Pirates.
  - So, rumor is that if you keep saying "there'll be a rug pull any time now, the prices will go up" they will roll you up in a rug , because look at this: "we found opus 5.5 to be 2X as efficient as gpt-6-sol in our internal cfo.ai evals so i was not expecting 6.1-sol to improve on that much but to see it 3X the efficiency of opus 5.5 and 2.5X against even sonnet 5.5 is actually [mindblowing]" GPT-6.1 Sol cost $2.72 vs. Sonnet 5.5's $7.60 on the same task, with the same score.
  - Anthropic on GLM-5.3: "Here, full credit is awarded for a full control-flow hijack. We evaluate several models on 100 tasks from the benchmark (selected at random), and find that GLM-5.3 develops full control flow hijacks in 4% of the trials; Claude Mythos Preview did so in 6%. Although GLM-5.3 performs below Claude Mythos Preview here, a meaningful threshold has clearly been crossed: earlier models, like Claude Opus 4.6 and GLM-5.2, do not succeed in any of them." That's wild, isn't it? Mythos, the model so dangerous that Anthropic only wants to give it to its highest-paying customers, got 6% and GLM-5.3, the Chinese model, gets 4%. And they managed to disable "GLM-5.3's safeguards between 64% and 100% of the time with simple techniques in our simulated tests." What I wonder now: doesn't that mean that Pandora's Box has been opened and that no "pacing" will help, that whatever Anthropic campaigned for when they got Mythos locked up by the U.S. government, is now in the past?
  - This is amazing and motivating and inspiring and I want every company and every organization and every government in the world to do this: "by the end of the ZBR cycle on July 1, 2026, Idaho had eliminated roughly half (49.1%) of its regulatory code. Regulatory volume fell in each of the eight annual code publications from 2019 to 2026 under ZBR. What Idaho has done, other states can achieve as well." ZBR refers to Zero-Based Regulation and that "borrows its central premise from zero-based budgeting: last year's baseline should not be presumed to be the right starting point. Traditional regulatory review generally asks what should be changed or repealed, if anything, from the existing code. ZBR begins with a more fundamental question: If the state were starting from scratch today, which rules would it adopt and in what form? The practical effect is to reverse regulatory inertia. Instead of requiring reformers to prove that an existing rule should be eliminated, the agency must justify why the rule should continue to exist."
  - Destroy Any Website. Awesome. More.
  - There have been many variations of the original motherfuckingwebsite.com and they never quite topped it, did they? But this newest one, the Modern Motherfucking Website, is quite good. I had Amp change my personal website to use that styling and… I think I might just push that up?
  - Jeffrey Katzenberg, co-founder and CEO of DreamWorks and, prior to that, CEO of Disney, on AI and Creativity and filmmaking: "The Disney archives held astonishing recordings of Walt explaining his creative process. His own writings. His notes and storyboards. Work product captured at every stage of his process. This was truly a gift. Listening, reading, sitting with the work itself, we heard him talk about character, about emotion, about how an audience feels when a character truly comes alive. He talked about making bold choices and refining a scene until it genuinely moved people. We didn't hear a word about pencils or paintbrushes. In fact, Walt was famous for being a technologist, forever hunting for state-of-the-art tools, often inventing them himself to achieve the images he saw in his head. But he never defined animation by the tools. He defined it by whether the audience believed the character. His principles were timeless. The tools were not. […] Tools are never the point. The instruments change with every generation. What endures is taste and imagination. The magical ability to make an audience feel. One of the greatest storytellers of our generation, George Lucas, succinctly captured the eternal essence of this issue: 'It's not the how, it's the why.'" The whole thing is very good.
  - Is Mathematics Over, or Just Graduating?: "Once airplanes get cheap, we will also discover satellites. We will map the whole terrain for mineral deposits and other valuable resources, and then extract them. It will be messy and dirty, and today's explorers will be deeply appalled at what it does to their beautiful jungle. They will long for the good old days. They will say this is no longer exploration but a commercial undertaking, large corporations wrecking the area they were so keen to explore. They will be right, but it won't change much, and large companies will find unimaginable riches there. […] Do not bet against the airplane. The skeptics who say AI can't conjecture, can't theorize, and can't explain are describing last spring's models. Within months, they will be describing nobody. The evidence is already on the table, and those with eyes can see it. Every "it can't do X" has a short shelf life now, and anyone building their identity on one of those sentences is building on sand."
  - Wilhelm is building a personal super app and it sounds like such a good idea. By now we've probably all experienced how easy it is to add more functionality once you have the skeleton of an app and deployment set up. This leans into that.
  - I'm not in need of one, but there are new Kindles and, man, they look good.
  - Jason Fried built his own writing application and there are a thousand things I could say here, but instead let me just say this: watch the demo video and think about how you would've built all of that three years ago. Also: god that guy is great at demos.
  - So there's been a bit of a kerfuffle because Figma doesn't allow any arbitrary MCP client to connect to their MCP server and the majority opinion seems to be that Figma should just allow that. Okay. But to me the most interesting thing that came out of the discussion was this post by Wes Bos and his reply further down: "Figma doesn't want you to use MCP. Amazon doesn't want you to shop with agents. Reddit won't let Claude access threads. X won't let ChatGPT read tweets. It's starting. This happened with APIs 8 years ago. […] I'd be willing to bet Amazon makes more money when you use the app. Grocery stores make more money when you walk the cash wrap. Airlines make more money when they scare you into buying insurance. Dark design patterns and consumer usage data make money. They don't want to give that up for some chat bot deciding what the cheapest red shoes are." It seems so obvious when put like that, doesn't it? He's exactly right of course: I remember many many years ago there were conference talks and excited conversations about how once everything is REST and everyone uses OAuth we can just pipe this into that and build our own client for that and have our cake and eat it too. Except that didn't happen. Not even close. So why would all the companies now allow anyone to bring their agent?
  - Jurassic Generation. I want to re-watch Jurassic Park now.
  - That being said: I think Sign in with ChatGPT might be one of the most interesting things launched this week. (Amp was a launch partner!)
  - Remember the Rippling vs. Deel corporate espionage drama? This isn't as good, but it's close: Factory kicked out a board member because (that's the accusation) he shared confidential information with Factory's competitor Cognition. But then the accused said he actually quit. But Keith Rabois said even that would be unethical and a lot of dirt was thrown. Very entertaining but I'm willing to bet that in a week no one will even talk about it anymore.
  - Made by mechanical means, by Felix Rieseberg, on how he used Claude to rebuild his personal website. What would you call this? Programming? Designing? Or just… building software?
  - Werner Herzog: "I only tell everyone out there: it will be a counterpoint against what you normally learn in film schools. Young people spend way too much time in film schools. It's way too expensive, way too long. And I don't like the kind of teaching there. So I said, 'Two things I really will teach you. Number one: lock picking. And number two: forging of documents,' like forging a shooting permit. And a film like Fitzcarraldo could not have been made without massive forgery, so you have to have the right criminal energy and the skills to learn."
  - Stewart Copeland playing the drums. YouTube says the video's been there for 19 years. I think I've watched it at least once in each one of those years.
  If you're in NYC you should definitely subscribe, but even if you're not you should:
9. 🔗 earendil-works/pi v1.0.2 release
  New Features
  - Sampling by thinking level — samplingParamsByThinkingLevel in models.json sets sampling parameters such as temperature and top_p for each thinking level on OpenAI-compatible APIs. See Configure sampling by thinking level.
  Added
  - Added samplingParamsByThinkingLevel to models.json for per-thinking-level sampling parameter overrides on OpenAI-compatible APIs. See Configure sampling by thinking level (#9776 by @mrexodia)
10. 🔗 Filip Filmar Thanklessly Maintaining Open Source Software: the book rss
  
  Thanklessly Maintaining Open Source Software started as a fake O’Reilly book cover, and it is now an actual book on Amazon. It has 95 pages, a year in the life of one unlucky maintainer, and a price of exactly one hexadecimal dollar. This post explains what is in it, and why you might want it anyway.
  
  Buy it on Amazon →
October 03, 2026
1. 🔗 Simon Willison We're going to need default hard budget caps on pretty much everything rss
  
  Here's a product feature which the world is going to need a whole lot more of over the coming months and years: default hard budget caps. I'm talking about the feature of pay-by-usage services and APIs that lets you say "after $X/month, cut this thing off and return errors". These need to be hard limits. Soft caps, "after $X/month, send me a warning email", will not cut it.
  
  Coding agents, and personal agents (coding agents wrapped in a less threatening UI), greatly reduce the friction of spinning up code that can do useful things. Sometimes those things cost money - calls to paid APIs, or hosted web applications, or systems that can bill for additional storage and compute.
  
  Nobody wants to wake up to an email sent at midnight warning about a budget limit and find that, while they slept, their rogue service had consumed several hundred (or several thousand) more dollars of usage.
  
  An argument against this is that businesses don't want their hosted applications to start throwing errors because some budget was exceeded. I expect that most businesses and individuals would prefer errors to a surprise $10,000+ bill.
  
  I think hard budget caps need to be the default. If someone wants to live dangerously they should be able to do that, but it needs to be on an opt-in basis. Have a nice, clear checkbox somewhere prominent:
  
  Remove the budget cap. My application will not be shut down if I exceed the configured budget limit, and I will be responsible for subsequent charges.
  
  The service I most want to see this from is AWS. I've heard plenty of stories from people who refuse to use AWS for personal projects out of (justified) fear that a runaway service might bankrupt them. I've also heard stories from people who didn't anticipate this and ended up seriously burned.
  
  ... and it turns out AWS finally launched spending limits a few weeks ago! From their announcement New AWS experience helps builders get started and ship faster on 16th September:
  
  When you're ready to upgrade to a paid plan, you can set a monthly spend limit for your project based on your usage patterns so that you stay within your budget. If a project's usage reaches its spend limit, your project is paused for that month.
  
  See also Create a spend limit in AWS Settings, though that page warns that "We're currently releasing our new experience to a limited number of customers." Here's hoping that hits general availability for existing accounts soon.
  
  Google Cloud launched a similar feature in July, called Spend Caps, which lets you "set a monthly financial cap on specific services within a project". Looks like this is becoming a trend!
  
  In an ideal world, our agents could help with this. It would be great if agents started biasing towards recommending providers with hard budget caps, and warning new and inexperienced builders against deploying applications using uncapped services that might get them into trouble.
  
  You are only seeing the long-form articles from my blog. Subscribe to /atom/everything/ to get all of my posts, or take a look at my other subscription options.
2. 🔗 HexRaysSA/ida-mcp v20261003.0.1 release
  What's Changed
  - Resolve Codex open_database paths from workspace by @thebabush in #30
  Full Changelog : v20260930.0.1...v20261003.0.1
3. 🔗 hacker news idalib references New comment by TuxSH in "Pop!_OS bans AI-generated code from much of its codebase" rss
  
  Vibe coding has always had and always will have one fundamental flaw: you didn't write the code it produced, therefore you don't have a good understanding/mental model of it.
  On the other hand asking these clankers "review the feature branch I wrote" and "review my entire codebase for bugs" or "help me debug this" has saved me months of prospective work.
  And more recently most major models have been getting _really_ good at RE, for example you can have OAI models (and maybe A/'s if they don't refuse) use idalib MCP and reverse-engineer stuff from start to finish, then follow up with GLM 5.3 for vuln assessment and exploit PoC.
  Stuff that used to take weeks or months now just takes a few hours, or less.
4. 🔗 r/Harrogate Good restaurants in the town centre? rss
  
  We’re in Harrogate next weekend and staying in the town centre.
  Any recommendations for decent non chain restaurants please.
  Budget is £150 for 2 including a bottle of wine.
  Thanking you in advance.
  
  submitted by /u/LoveHertford
  [link] [comments]
5. 🔗 r/Harrogate What’s going on with the town centre church blasting its bells Friday / Saturday evening for hours? rss
  
  It’s been going on for like 1.5hours straight. Can’t see any important religious ceremony? Yesterday too but don’t think there was even a service on, it was empty when it was happening lol
  
  Starting to think someone has left it on by mistake
  
  submitted by /u/FrontRaspberry5060
  [link] [comments]
6. 🔗 earendil-works/pi v1.0.1 release
  New Features
  - Nix flake — nix run github:earendil-works/pi/stable runs the latest release, and nix profile add github:earendil-works/pi/stable installs it. See Install pi.
  - Project overrides for MCP servers — .pi/mcp.json and /mcp can enable, disable, or change the exposure of a user-level server for one project. See Configure servers.
  - MCP Client ID Metadata Documents — oauth.clientRegistration: "cimd" lets authorization servers allow pi by its document URL instead of dynamic registration. See Authenticate with OAuth.
  - Tool renderers for any tool — pi.registerToolRenderer() draws calls to tools that are not registered yet, such as MCP tools in resumed sessions. See Tool rendering.
  - Cloudflare Clef classifiers — @cf/cloudflare/clef and @cf/cloudflare/clef-flash are usable from codemode scripts and extensions. See Use classifier models.
  Added
  - Added a copy key (app.message.copy, default ctrl+x) to OAuth sign-in screens in /login, /mcp, and /mcp login, which copies the sign-in URL when the browser cannot be opened or the wrapped link cannot be selected.
  - Added oauth.clientRegistration: "cimd" for MCP servers, which identifies pi with its Client ID Metadata Document on pi.dev instead of dynamic client registration, so authorization servers can allow pi by URL (#10302)
  - Added project overrides for user-level MCP servers: a .pi/mcp.json entry without command or url sets only enabled, exposure, and toolExposure of the user-level server, and /mcp can enable or disable a server for the current project (#10277)
  - Added Cloudflare's Clef and Clef Flash classifier models to cloudflare-workers-ai, usable from codemode scripts and extensions (#10316 by @ndisidore, #10322 by @RealAlexandreAI)
  - Added pi.registerToolRenderer(), which chooses how calls to a tool are drawn, including tools that are not registered (#10285)
  - Added a Nix flake for macOS and Linux: nix run github:earendil-works/pi/stable runs the latest release, and nix profile add github:earendil-works/pi/stable installs it. See Install pi (#9137)
  Changed
  - pi update on global npm installations now recommends migrating to the managed installation from the pi.dev installer, which pins all dependencies.
  - Anthropic tools added or redefined mid-conversation are now defined inline in the conversation, so redefining a tool under the same name keeps the prompt cache instead of resending the full tool list.
  Fixed
  - Fixed installations resolving vulnerable brace-expansion 5.0.9 by pinning brace-expansion 5.0.12 as a direct dependency (GHSA-q2hr-2g5m-vwhr, GHSA-qhr7-859c-m2p7, GHSA-6j4f-fj2g-mc7p) (#10288)
  - Fixed a trailing comma in --models adding an extra model to the model cycle (#10334)
  - Fixed a codemode script that prints in a loop crashing pi by running out of memory: a script fails once its output passes 16 Mi characters or 100000 items (#10283)
  - Fixed JPEG, GIF, and WebP images rendered by extensions through Image not appearing in Kitty, Ghostty, WezTerm, and Warp (#10292)
  - Fixed MCP tool calls in resumed sessions and HTML exports rendering fully expanded until their server connected, or for good if it never did (#10285)
  - Fixed fullscreen Kitty images collapsing to a one-row strip after scrolling in WezTerm (#10319)
  - Fixed "Selected model is at capacity" provider errors ending the turn instead of being retried (#10278)
  - Fixed Cloudflare AI Gateway Claude models failing with a 404 by using dashed model IDs (claude-opus-5-5 instead of claude-opus-5.5)
  - Fixed Sign in with ChatGPT continuing when its callback port is taken by another login, which made the browser show "OAuth state mismatch"; it now fails with a port-in-use error (#10265)
  - Fixed Amazon Bedrock OpenAI models costing requests above 272k input tokens at the short-context rate; Bedrock models now include the pricing tiers listed on models.dev (#10326)
  - Fixed Amazon Bedrock Claude requests failing with "Invalid signature in thinking block" after the system prompt or tools changed (#10324)
  - Fixed Together DeepSeek V4 Pro losing its thinking level controls after Together renamed it to deepseek-ai/DeepSeek-V4-Pro-0813 (#10336 by @cv)
  - Fixed the default NVIDIA model pointing at nvidia/nemotron-3-super-120b-a12b, which NVIDIA no longer serves; the default is now nvidia/nemotron-3-ultra-550b-a55b
  Removed
  - Removed npm-shrinkwrap.json from the published package. npm installations no longer pin transitive dependencies, and library consumers can now override them. Use the pi.dev installer for pinned installations (#5653)