๐Ÿก
  • โ†”
  • โ†’

to read (pdf)

  1. Neobrutalism components - Start making neobrutalism layouts today
  2. Debunking zswap and zram myths
  3. Building a Pipeline for Agentic Malware Analysis | Tim Blazytko
  4. Study of Binaries Created with Rust through Reverse Engineering - JPCERT/CC Eyes | JPCERT Coordination Center official Blog
  5. Letting AI Actively Manage Its Own Context | ๆ˜Žๅคฉ็š„ไนŒไบ‘

generated: March 31, 2026 at 09:31:53

  1. March 31, 2026
    1. ๐Ÿ”— MetaBrainz MerchBrainz rss

      We have added a range of great new MetaBrainz designs to our merch store: https://www.redbubble.com/people/metabrainz/shop

      These designs by Monkey, previously only available to MetaBrainz summit attendees, have been lightly modified (summit-specific text removed) for everyday wear. Are many people going to know what you're repping? No. Are the ones that do going to go " DAAAAAAAAAAAAMN IT'S THE BRAINZ YO"? Most definitely!

      Note: We don 't print 'em, so these mockups may differ from the final product.

      Choose your fighter: synth, bollywood, psychedelic, vaporwave or black metal, as well as the classic logo and unicorn designs. We also dropped a couple of additional designs today. As well as a 'new notes!?' sticker/magnet there is a new "I made 1,ooo edits and all I got was this lousy T-shirt" design, and a 100,000 edit version. Rumour has it there are secret versions of this shirt available for super high-scorersโ€ฆ

      Do you have great/fun/stupid ideas for MetaBrainz-themed shirts or other merch? Let us know!

    2. ๐Ÿ”— r/reverseengineering Introducing the Rootkit Techniques Matrix and updates to the Guide rss

      submitted by /u/rkhunter_
      [link] [comments]

    3. ๐Ÿ”— mhx/dwarfs dwarfs-0.15.2 release

      32-bit glibc Build Fixes and FUSE Driver Cleanup

      32-bit native build fixes

      (#354)

      This release fixes a set of issues that showed up in native 32-bit builds, most notably on openSUSE Tumbleweed with glibc. The most important one was related to sparse file tests that create files larger than 4 GiB: glibc requires _FILE_OFFSET_BITS=64 for 64-bit file operations in that environment, and without it those tests would fail. This was not just a test bug, all the binaries simply could not deal with files larger than 4 GiB in this scenario.

      However, this was only an issue for glibc-based 32-bit builds. It did not affect musl-libc-based builds, which is why it went unnoticed for some time. This did not affect the statically linked release binaries, which are using musl-libc.

      A few additional 32-bit related issues were also fixed: the formatting code for times and ratios relied too heavily on floating-point arithmetic and turned out not to be deterministic across platforms and compilers. That code has now been rewritten to use integer arithmetic instead, avoiding platform- specific behavior. A bug in the test code itself, which surfaced only with GCC, has been fixed as well.

      FUSE driver refactoring

      The FUSE drivers (dwarfs, dwarfs2) have gone through a substantial internal cleanup and refactoring pass in this release. This fixes a number of subtle startup and option-handling issues and makes the behavior of the different driver variants much more consistent.

      One visible improvement is error reporting for invalid options. For example, if -o image_size=1234 was used instead of the correct -o imagesize=1234, older versions would end up reporting a misleading filesystem loading failure rather than flagging the unknown option directly. That kind of behavior has now been fixed.

      Internally, this also removes a great deal of preprocessor-heavy startup logic that had diverged over time across the various FUSE implementations and modes (high-level, low-level, Windows, FUSE v2, and FUSE v3). The resulting code is much easier to follow, more consistent across platforms, and better covered by tests.

      Bug fixes

      • The image size was not passed correctly to one instance of the filesystem parser, which caused errors when loading a DwarFS image embedded inside a larger file (for example, a multi-layer file). Thanks to Ruan Formigoni for the pull request fixing this issue.

      • The performance monitor timer for op_lseek in the FUSE driver was not initialized correctly. This could lead to segmentation faults or bus errors due to an uninitialized index into a std::deque. The issue has been fixed, and an additional check has been added to catch similar errors in the future.

      • Native 32-bit glibc builds could fail in tests involving sparse files larger than 4 GiB because _FILE_OFFSET_BITS=64 was required for 64-bit file operations. Additional non-deterministic test failures related to time and ratio formatting were also fixed by rewriting that code to use integer arithmetic instead of floating-point arithmetic. A separate test bug that surfaced only with GCC was fixed as well. Addresses #354.

      • The FUSE drivers (dwarfs, dwarfs2) were refactored to eliminate a number of subtle startup and option-handling issues and to make behavior much more consistent across the various supported FUSE variants.

      • The manual pages shown with --man for all tools unintentionally included the license header from XML comments at the top of the source files. The renderer now ignores those comments.

      Build

      • After benchmarking the latest mimalloc allocator, it turns out to perform mostly on par with jemalloc. It is still less configurable, but it is clearly usable when that extra configurability is not needed.

      • The small universal release binaries are now built with mimalloc instead of jemalloc, reducing their size by about 10%.

      • Older Clang versions, such as those shipped with Ubuntu 22.04, are no longer supported because they cannot use libstdc++'s std::expected implementation. DwarFS can still be built on Ubuntu 22.04 with GCC.

      Test

      • A few particularly slow tests were identified through profiling and have been reworked to run faster while still covering most of the same code paths.

      New Contributors

      Full Changelog : v0.15.1...v0.15.2

      SHA-256 Checksums

      f81290d5c4890a274a60a82b801e62110975ca466799e4408ad046bc70695aef  dwarfs-0.15.2-Linux-aarch64.tar.xz
2466659a4e783d1bc794e17215dcdf093fae8e9493ffaa03091a85c8c11369f2  dwarfs-0.15.2-Linux-arm.tar.xz
fd6ed59b7805539c6fc6e6e508344d10479f6587abe1040a1e86997f19b52fa0  dwarfs-0.15.2-Linux-i386.tar.xz
62f5f2bac65232184cb14e7bb7921a38b34440dcd688080eebdcdc512915d3ba  dwarfs-0.15.2-Linux-loongarch64.tar.xz
08e556adeb248a20aec04bf70886146f5e56bd0efc0bbe225aae69d20b25d33e  dwarfs-0.15.2-Linux-ppc64le.tar.xz
1668eca05412c2bd848ad4aa606a61fb2bf48f3cf92aac556149778a713885f2  dwarfs-0.15.2-Linux-ppc64.tar.xz
3110c8f630a4ae65fe16e4e3280f74d34b2c7a8224630e03361ed799819eeb9f  dwarfs-0.15.2-Linux-riscv64.tar.xz
5879d6d1e406a5ddf4dc68d8179540bd797af5d58abe7def9e62c6841221eb95  dwarfs-0.15.2-Linux-s390x.tar.xz
ad9ef4edf2d124b5c8d4540b2298a9b520e15841c68b921192d9bcb83eb69455  dwarfs-0.15.2-Linux-x86_64.tar.xz
6b7edcb2121347e273753d949f72913f006ec12477248384b24c48989ec34995  dwarfs-0.15.2.tar.xz
c34c05e7f65edcfd5f21bc3fed2de90d3f4b8c5b311d3b5ae302ae3ec6fc7161  dwarfs-0.15.2-Windows-AMD64.7z
46d690ecf546539d3229df9e3ad2412a806e4dee95e22c9ea843d934003f21bb  dwarfs-fuse-extract-0.15.2-Linux-aarch64
3d49d59416bcb989504b70bc63ebcbbb5be5c9a049bd432cefeb4620aa0fc3ae  dwarfs-fuse-extract-0.15.2-Linux-aarch64.upx
d6b4f4fc498e48031f7e7bb5ed3297a1272a68465f1803ad599ee486b0d49799  dwarfs-fuse-extract-0.15.2-Linux-arm
c5214353ad9de53a7fbff6aa5adfa65a9b830b694be839d5de1dbec9ff6a12f0  dwarfs-fuse-extract-0.15.2-Linux-arm.upx
5056562a6e12bcb20e7e07aeff0fa31113bae52f6feefd1a79f87d412c8bcd6d  dwarfs-fuse-extract-0.15.2-Linux-i386
92ac91f59581663985250cc0bcad02742c5cf1a5b009925212f97c1a424f69c3  dwarfs-fuse-extract-0.15.2-Linux-i386.upx
ede37a302b6e038f25dc4a35f25d8c9378fb2ae35600ec445a1eec0bf8b9d64c  dwarfs-fuse-extract-0.15.2-Linux-loongarch64
eec1b96f2d19c04aeda2099914e0b905cec6dec98be439f1bfc4f8f31c447554  dwarfs-fuse-extract-0.15.2-Linux-ppc64
983ee30f114bbafdeefc7ca8a79eecffa33c6314b9c516e7183424ec1d75802c  dwarfs-fuse-extract-0.15.2-Linux-ppc64le
fba9d984f3258f5c35e441b2eb468e25baa9f339e6100013c5a2fbb1c6bfcc1e  dwarfs-fuse-extract-0.15.2-Linux-riscv64
a3210163095b118407f6b8bd174d60bdb92a9d3fa70b9cdcb761d39570bd2bbb  dwarfs-fuse-extract-0.15.2-Linux-riscv64.upx
28f9ca8b2c9ccfc3c7e5949ed89b33a24aade539b3e0de40d5d364e0d06b0065  dwarfs-fuse-extract-0.15.2-Linux-s390x
85084aae43406fa8892df1cc24bd6df96948d99e8a35ca4c2873518fef0fa41c  dwarfs-fuse-extract-0.15.2-Linux-x86_64
40d027c79c7be4a5f7701433477f832390c3aaab437ca3bb2e3f0aa0a007d557  dwarfs-fuse-extract-0.15.2-Linux-x86_64.upx
b9c25399e1e4672601c0afbcb44e522af71698ea41691384555abe09776c113e  dwarfs-universal-0.15.2-Linux-aarch64
432a460080765f52b2b6e51ef99ca87bc4ba1cdf8fa9257155cd89d1b20edbc8  dwarfs-universal-0.15.2-Linux-aarch64.upx
114496a88f27af058481d09e4c75a5079ff9567317745fd50ca4ae79eec30070  dwarfs-universal-0.15.2-Linux-arm
23703b2ce7de3a3ed52f1441759f91a10ab654243678a050e98e5fda0d821c05  dwarfs-universal-0.15.2-Linux-arm.upx
35771934f6dc34038624cf99179bcfb4fe707c533e294d4a75cebdc56785cf08  dwarfs-universal-0.15.2-Linux-i386
24d6ae52dc7166d667cabb47b77233f3a2e87848fb7ffc71a1d230aeb54dd5f7  dwarfs-universal-0.15.2-Linux-i386.upx
a3d97d40a2cc1baf70efe5e5509f9537826b13ee27bdf3bf95a2914361d31181  dwarfs-universal-0.15.2-Linux-loongarch64
547650e46dde48abdd5824115e3c39cb66d551e4647383716591ea5bbcfb7f2e  dwarfs-universal-0.15.2-Linux-ppc64
9712e02402f2a2094a565d39ec2bad2a3a43dbc042a18c93035726de4b133c24  dwarfs-universal-0.15.2-Linux-ppc64le
24f53482d4992797b178e9d63156519569168d2ad469c998451670c44362c418  dwarfs-universal-0.15.2-Linux-riscv64
912b7c0205df9c3a3af61e9b5816fd7b83219259db3ecbe9d0761be97335d0c1  dwarfs-universal-0.15.2-Linux-riscv64.upx
13719648b094adf2c86df6dcc1c34f6b414d01f2032ab1c035bcc95e97f7d135  dwarfs-universal-0.15.2-Linux-s390x
7e4d7ed1b4c8d3f1db01d6914e5b8bcba1d1eb69dfaafe06d32214797fb0dd55  dwarfs-universal-0.15.2-Linux-x86_64
3f073cf225f975415da316aacee1825497a981ff7dad654bf50adb9b2592f7bb  dwarfs-universal-0.15.2-Linux-x86_64.upx
af985a17f080dd708f4fe8c6993adfa0a9f2545f96322e86dd4464ec2bcc0838  dwarfs-universal-0.15.2-Windows-AMD64.exe
feb6e82cd37eba74540c20ab4b73f82c5698f37bada15c7869ab976e04792c46  dwarfs-universal-small-0.15.2-Linux-aarch64
622c917795af04b045d070846ef8492f1c033f5722aa2c02549e218bcaaeace3  dwarfs-universal-small-0.15.2-Linux-aarch64.upx
759c66628b384769e9a3bcd5f98feadec3faa5334910e865c57551a44258f817  dwarfs-universal-small-0.15.2-Linux-arm
2b2fb1d586d79eff8024f69ffc805a341323358ef96ea7cbaf06b41fb76e9628  dwarfs-universal-small-0.15.2-Linux-arm.upx
041cd1200eeac5cf6bdd0c8dc922d119390959a4881b70eddf82d7ac79ae8d89  dwarfs-universal-small-0.15.2-Linux-i386
1dee9fc1846b902f544d8fcfaf7299b0381fa5d8345c2e9eb5d581ce73350b86  dwarfs-universal-small-0.15.2-Linux-i386.upx
c41cc39c690bba884077f995233eeeef968e6de20b2814fc4c1836281892ce70  dwarfs-universal-small-0.15.2-Linux-loongarch64
9f45a53288ac79192454aa5c96d90c92d47206a6162516b5d8f7efa6b85128a4  dwarfs-universal-small-0.15.2-Linux-ppc64
8a6d16cc922ba48b17c78964388cd04f5fa39593340a1721453ed3ebc766862c  dwarfs-universal-small-0.15.2-Linux-ppc64le
5f05442e1426ce962a0f319f0e27167943024758f5dd508053683a8cefa261a7  dwarfs-universal-small-0.15.2-Linux-riscv64
b84b860adee190cadd0d54a643d9eb787366320371d67944e3e0aff035a4acb5  dwarfs-universal-small-0.15.2-Linux-riscv64.upx
49cc48c441feb0a96b1685a6919ae361a8ae27e060e7a0ff1d92b8611091edaa  dwarfs-universal-small-0.15.2-Linux-s390x
85f0a2a95c8438a06e1177936ae1e4d9e45cec7876824037776b7866cb19973c  dwarfs-universal-small-0.15.2-Linux-x86_64
ff16901aa36b692a98bacfda58c68c5868ff4dd72babe61b33571165730cf477  dwarfs-universal-small-0.15.2-Linux-x86_64.upx
    4. ๐Ÿ”— r/reverseengineering hCAPTCHA Reverse Engineered rss

      submitted by /u/Electrical-Flight570
      [link] [comments]

    5. ๐Ÿ”— r/reverseengineering hCAPTCHA Reverse Engineered rss

      submitted by /u/Electrical-Flight570
      [link] [comments]

    6. ๐Ÿ”— backnotprop/plannotator v0.16.2 release

      Follow @plannotator on X for updates

      Missed recent releases? Release | Highlights
      ---|---
      v0.16.1 | SSE stream idle timeout fix for external annotations API
      v0.16.0 | GitHub Copilot CLI, external annotations API, bot callback URLs, interactive checkboxes, print support, diff display options
      v0.15.5 | Custom display names, GitHub viewed file sync, expand/collapse all in file tree, search performance, WSL fix
      v0.15.2 | Compound Planning skill, folder annotation, /plannotator-archive slash command, skill installation via platform installers
      v0.15.0 | Live AI chat in code review, plan archive browser, folder file viewer, resizable split pane, Pi full feature parity
      v0.14.5 | GitLab merge request review, login page image fix, Windows install path fix
      v0.14.4 | GitHub review submission, repo identifier in tab title, nested code fence parser fix, Pi paste URL wiring
      v0.14.3 | PR context panel, diff search in code review, OpenCode permission normalization, landing page redesign
      v0.14.2 | OpenCode plan mode prompt replacement, Windows non-ASCII path fix, Pi link fix
      v0.14.1 | Single submit_plan with auto-detect, viewed-file draft persistence, Bear nested tag fix
      v0.14.0 | PR review via GitHub URL, /plannotator-last for annotating agent messages, OpenCode plan mode permissions fix, VS Code SSH proxy fix

      What's New in v0.16.2

      v0.16.2 focuses on annotation UX. Comment popovers are now draggable, annotation counts surface across sidebar tabs, and the code review diff viewer supports custom fonts. 4 PRs.

      Draggable Comment Popovers

      Comment popovers in both plan review and code review can now be repositioned by dragging their header bar. Previously, popovers near viewport edges or at the bottom of long documents would clip or overlap content, forcing users to scroll to work around them. A shared useDraggable hook handles the drag mechanics with a 3px movement threshold that prevents interfering with header button clicks. Once dragged, auto-positioning pauses so the popover stays where you put it. Position resets when a new annotation is selected.

      The same drag behavior applies to the annotation toolbar in code review line comments.

      Cross-File Annotation Visibility

      Annotations are now visible across sidebar tabs. The Files and Vault browsers show per-file annotation count badges, with folders displaying aggregate counts from descendants. A summary header reports "N annotations in M files" when any file has annotations. Dot indicators appear on the Files and Vault tab icons when annotated files exist, even when the sidebar is collapsed.

      The table of contents badge was redesigned from a heavy accent circle to a lighter muted rounded badge, and the same component is reused across all sidebar trees. Navigation back buttons now adapt based on context, returning to the correct sidebar tab when navigating between files.

      Custom Diff Fonts

      The code review diff viewer now supports custom monospace fonts and font size adjustments. A Code Font dropdown and font size slider appear in the Display settings tab. Nine fonts are available: Fira Code, Hack, IBM Plex Mono, Inconsolata, JetBrains Mono, Red Hat Mono, Roboto Mono, Source Code Pro, and Atkinson Hyperlegible Mono. Fonts load on demand from Google Fonts and jsDelivr CDN. The overrides apply to the diff shadow DOM, annotations, suggestions, and AI chat code blocks. Settings persist via the ConfigStore system.

      Additional Changes

      • OpenCode verbose log fix. Removed writeRemoteShareLink stderr output that flooded the TUI on remote sessions, and stripped leftover debug logs from the PR viewed files feature (#440, closing #435 reported by @h4rvey-g)

      Install / Update

      macOS / Linux:

      curl -fsSL https://plannotator.ai/install.sh | bash

      Windows:

      irm https://plannotator.ai/install.ps1 | iex

      Claude Code Plugin: Run /plugin in Claude Code, find plannotator , and click "Update now".

      Copilot CLI:

      /plugin marketplace add backnotprop/plannotator
/plugin install plannotator-copilot@plannotator

      OpenCode: Clear cache and restart:

      rm -rf ~/.bun/install/cache/@plannotator

      Then in opencode.json:

      {
  "plugin": ["@plannotator/opencode@latest"]
}

      Pi: Install or update the extension:

      pi install npm:@plannotator/pi-extension

      What's Changed

      • fix(opencode): remove verbose logs that flood the TUI by @backnotprop in #440
      • feat(review): custom diff font family and size overrides by @backnotprop in #441
      • feat(ui): draggable comment popover and annotation toolbar by @backnotprop in #442
      • feat(ui): cross-file annotation visibility and adaptive navigation by @backnotprop in #444

      Community

      @h4rvey-g reported the OpenCode TUI flooding issue in #435, which led to the verbose log cleanup in #440.

      Full Changelog : v0.16.1...v0.16.2

    7. ๐Ÿ”— r/Yorkshire Gresley Society announces major exhibition celebrating Sir Nigel Gresleyโ€™s 150th anniversary at The Danum Gallery in Doncaster. 04/04/2026 to 30/05/2026 rss

      Gresley Society announces major exhibition celebrating Sir Nigel Gresleyโ€™s 150th anniversary at The Danum Gallery in Doncaster. 04/04/2026 to 30/05/2026 | submitted by /u/CaptainYorkie1
      [link] [comments]
      ---|---

  2. March 30, 2026
    1. ๐Ÿ”— r/reverseengineering RE//verse 2026: Hacking the Xbox One by Markus 'doom' Gaasedelen rss

      submitted by /u/scottyMo221
      [link] [comments]

    2. ๐Ÿ”— r/reverseengineering The Webs Digital Locks have Never had a Stronger Opponent rss

      submitted by /u/Electrical_Date_8707
      [link] [comments]

    3. ๐Ÿ”— r/reverseengineering Quero conseguir achar uma senha pra acessar um menu debbug de um jogo, o menu aparece qdo aperto varias vezes na logo,mais pede uma senha,ja tentei descompilar o app e procurar a senha mais nao consigo, talvez esteja criptografada,e nรฃo tenho computador,alguem poderia me ajudar? rss

      submitted by /u/Neither-Cream3287
      [link] [comments]

    4. ๐Ÿ”— r/LocalLLaMA Qwen 3.6 spotted! rss

      Qwen 3.6 spotted! | https://openrouter.ai/qwen/qwen3.6-plus-preview submitted by /u/Namra_7
      [link] [comments]
      ---|---

    5. ๐Ÿ”— r/LocalLLaMA llama.cpp at 100k stars rss

      llama.cpp at 100k stars | https://x.com/ggerganov/status/2038632534414680223 https://github.com/ggml-org/llama.cpp submitted by /u/jacek2023
      [link] [comments]
      ---|---

    6. ๐Ÿ”— r/york looking for friends! rss

      Iโ€™m a 2nd year international student (f) at uni & have struggled to find people i really connect with. iโ€™m neurodiverse and havenโ€™t really met many other nd people as I work a lot and often canโ€™t make it to scheduled events, but Iโ€™d particularly really like to make more ND friends!

      Iโ€™m queer, love cinema, david lynch, charity shopping + vintage clothes, art, feminism, reading (esp classics), alternative music, gigs, and going to leeds gay bars lol.

      send me a message if u want to chat/plan something! :)

      submitted by /u/LocksmithVast8025
      [link] [comments]

    7. ๐Ÿ”— r/Harrogate Rudys 3000 free pizzas - yeah right rss

      A right first world grumble.

      Rudys announced with some fanfare they are giving 3000 pizzas away to celebrate opening in town.

      The email dropped today whilst I was in my inbox looking at something else. Within 2 mins of landing every slot to book for the next six weeks were fully booked.

      My spider senses suggest there were no free pizzas.

      submitted by /u/Similar-Actuator-338
      [link] [comments]

    8. ๐Ÿ”— r/reverseengineering Windows x86 Stack Overflow Breakdown + Hand-Assembled Shellcode (Educational VM Lab) rss

      submitted by /u/Medical-Health-9377
      [link] [comments]

    9. ๐Ÿ”— HexRaysSA/plugin-repository commits sync repo: +4 releases rss 
      sync repo: +4 releases

## New releases
- [DeepExtract](https://github.com/marcosd4h/DeepExtractIDA): 0.9.12
- [IDAssist](https://github.com/symgraph/IDAssist): 1.5.0
- [IDAssistMCP](https://github.com/symgraph/IDAssistMCP): 1.4.0
- [Suture](https://github.com/libtero/suture): 1.2.5
    10. ๐Ÿ”— r/LocalLLaMA Stanford and Harvard just dropped the most disturbing AI paper of the year rss

      https://arxiv.org/abs/2602.20021

      submitted by /u/Fun-Yogurt-89
      [link] [comments]

    11. ๐Ÿ”— backnotprop/plannotator v0.16.1 release

      Follow @plannotator on X for updates

      Missed recent releases? Release | Highlights
      ---|---
      v0.16.0 | GitHub Copilot CLI, external annotations API, bot callback URLs, interactive checkboxes, print support, diff display options
      v0.15.5 | Custom display names, GitHub viewed file sync, expand/collapse all in file tree, search performance, WSL fix
      v0.15.2 | Compound Planning skill, folder annotation, /plannotator-archive slash command, skill installation via platform installers
      v0.15.0 | Live AI chat in code review, plan archive browser, folder file viewer, resizable split pane, Pi full feature parity
      v0.14.5 | GitLab merge request review, login page image fix, Windows install path fix
      v0.14.4 | GitHub review submission, repo identifier in tab title, nested code fence parser fix, Pi paste URL wiring
      v0.14.3 | PR context panel, diff search in code review, OpenCode permission normalization, landing page redesign
      v0.14.2 | OpenCode plan mode prompt replacement, Windows non-ASCII path fix, Pi link fix
      v0.14.1 | Single submit_plan with auto-detect, viewed-file draft persistence, Bear nested tag fix
      v0.14.0 | PR review via GitHub URL, /plannotator-last for annotating agent messages, OpenCode plan mode permissions fix, VS Code SSH proxy fix
      v0.13.1 | OpenCode plan mode rewrite, Obsidian save fix

      What's New in v0.16.1

      v0.16.1 fixes SSE connection stability for the external annotations API introduced in v0.16.0. 1 PR from an external contributor, 1 first-timer.

      SSE Stream Idle Timeout Fix

      Bun's default idle timeout of 10 seconds was killing the external annotations SSE stream (/api/external-annotations/stream) before the first 30-second heartbeat could fire. The browser's EventSource auto-reconnected, but each reconnect triggered a full snapshot resend and produced a [Bun.serve]: request timed out after 10 seconds warning in the console.

      The fix uses Bun's per-request server.timeout(req, 0) to disable the idle timeout only on SSE stream requests. Normal HTTP requests keep the default 10-second safety net. The change applies to all three server types (plan, review, annotate).

      Install / Update

      macOS / Linux:

      curl -fsSL https://plannotator.ai/install.sh | bash

      Windows:

      irm https://plannotator.ai/install.ps1 | iex

      Claude Code Plugin: Run /plugin in Claude Code, find plannotator , and click "Update now".

      Copilot CLI:

      /plugin marketplace add backnotprop/plannotator
/plugin install plannotator-copilot@plannotator

      OpenCode: Clear cache and restart:

      rm -rf ~/.bun/install/cache/@plannotator

      Then in opencode.json:

      {
  "plugin": ["@plannotator/opencode@latest"]
}

      Pi: Install or update the extension:

      pi install npm:@plannotator/pi-extension

      What's Changed

      • fix(server): keep external annotation SSE streams alive by @foxytanuki in #439

      New Contributors

      Community

      @foxytanuki filed #438 with a thorough root cause analysis identifying the mismatch between Bun's 10-second idle timeout and the 30-second heartbeat interval, then followed up with the fix in #439.

      @j-huang-rj independently identified the same issue and submitted a fix in #433. The targeted per- request approach from #439 was chosen, but both contributors spotted the problem within hours of v0.16.0 shipping.

      Full Changelog : v0.16.0...v0.16.1

    12. ๐Ÿ”— r/reverseengineering Reverse Engineering Crazy Taxi, Part 2 rss

      submitted by /u/ifnspifn
      [link] [comments]

    13. ๐Ÿ”— r/reverseengineering I built pycdc-studio, a Qt desktop UI for exploring Python bytecode with pycdc/pycdas rss

      submitted by /u/Commercial_Rip_1827
      [link] [comments]

    14. ๐Ÿ”— r/Leeds Royal Armouries International Jousting Tournament Tickets rss

      Hi, everyone!

      I hope this is okay to ask on here / realise this is a long shot, but would anyone happen to have a spare ticket / or two for the upcoming jousting tournament, if you perhaps can't go for any reason, or know someone that can't?

      Full disclosure, I left it too long to buy my own because my partner was deliberating whether or not they could come with me, and I didn't realise the demand. ๐Ÿ˜… My mistake! But, I thought it was worth asking. Thank for you reading if you've come this far!

      submitted by /u/FigureO9
      [link] [comments]

    15. ๐Ÿ”— Simon Willison Mr. Chatterbox is a (weak) Victorian-era ethically trained model you can run on your own computer rss

      Trip Venturella released Mr. Chatterbox, a language model trained entirely on out-of-copyright text from the British Library. Here's how he describes it:

      Mr. Chatterbox is a language model trained entirely from scratch on a corpus of over 28,000 Victorian-era British texts published between 1837 and 1899, drawn from a dataset made available by the British Library. The model has absolutely no training inputs from after 1899 โ€” the vocabulary and ideas are formed exclusively from nineteenth-century literature.

      Mr. Chatterbox's training corpus was 28,035 books, with an estimated 2.93 billion input tokens after filtering. The model has roughly 340 million paramaters, roughly the same size as GPT-2-Medium. The difference is, of course, that unlike GPT-2, Mr. Chatterbox is trained entirely on historical data.

      Given how hard it is to train a useful LLM without using vast amounts of scraped, unlicensed data I've been dreaming of a model like this for a couple of years now. What would a model trained on out-of-copyright text be like to chat with?

      Thanks to Trip we can now find out for ourselves!

      The model itself is tiny, at least by Large Language Model standards - just 2.05GB on disk. You can try it out using Trip's HuggingFace Spaces demo:

      Screenshot of a Victorian-themed chatbot interface titled "๐ŸŽฉ Mr. Chatterbox (Beta)" with subtitle "The Victorian Gentleman Chatbot". The conversation shows a user asking "How should I behave at dinner?" with the bot replying "My good fellow, one might presume that such trivialities could not engage your attention during an evening's discourse!" The user then asks "What are good topics?" and the bot responds "The most pressing subjects of our societyโ€” Indeed, a gentleman must endeavor to engage the conversation with grace and vivacity. Such pursuits serve as vital antidotes against ennui when engaged in agreeable company." A text input field at the bottom reads "Say hello..." with a send button. The interface uses a dark maroon and cream color scheme.

      Honestly, it's pretty terrible. Talking with it feels more like chatting with a Markov chain than an LLM - the responses may have a delightfully Victorian flavor to them but it's hard to get a response that usefully answers a question.

      The 2022 Chinchilla paper suggests a ratio of 20x the parameter count to training tokens. For a 340m model that would suggest around 7 billion tokens, more than twice the British Library corpus used here. The smallest Qwen 3.5 model is 600m parameters and that model family starts to get interesting at 2b - so my hunch is we would need 4x or more the training data to get something that starts to feel like a useful conversational partner.

      But what a fun project!

      Running it locally with LLM

      I decided to see if I could run the model on my own machine using my LLM framework.

      I got Claude Code to do most of the work - here's the transcript.

      Trip trained the model using Andrej Karpathy's nanochat, so I cloned that project, pulled the model weights and told Claude to build a Python script to run the model. Once we had that working (which ended up needing some extra details from the Space demo source code) I had Claude read the LLM plugin tutorial and build the rest of the plugin.

      llm-mrchatterbox is the result. Install the plugin like this:

      llm install llm-mrchatterbox

      The first time you run a prompt it will fetch the 2.05GB model file from Hugging Face. Try that like this:

      llm -m mrchatterbox "Good day, sir"

      Or start an ongoing chat session like this:

      llm chat -m mrchatterbox

      If you don't have LLM installed you can still get a chat session started from scratch using uvx like this:

      uvx --with llm-mrchatterbox llm chat -m mrchatterbox

      When you are finished with the model you can delete the cached file using:

      llm mrchatterbox delete-model

      This is the first time I've had Claude Code build a full LLM model plugin from scratch and it worked really well. I expect I'll be using this method again in the future.

      I continue to hope we can get a useful model from entirely public domain data. The fact that Trip was able to get this far using nanochat and 2.93 billion training tokens is a promising start.

      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.

    16. ๐Ÿ”— sacha chua :: living an awesome life 2026-03-30 Emacs news rss

      It's not too late to write about mistakes and misconceptions as part of the Emacs Carnival for March and not too early to think about the theme of "Newbies/Starter Kits" which Cena will be hosting for April. Who knows, maybe those ideas can become part of the newcomers presets. It could be fun to explore something like notes for Emacs beginners and see where you end up.

      Also, I'm looking forward to seeing if these tips for reloading Emacs Lisp code can help me avoid little bugs from leftover code.

      Enjoy!

      Links from reddit.com/r/emacs, r/orgmode, r/spacemacs, Mastodon #emacs, Bluesky #emacs, Hacker News, lobste.rs, programming.dev, lemmy.world, lemmy.ml, planet.emacslife.com, YouTube, the Emacs NEWS file, Emacs Calendar, and emacs-devel. Thanks to Andrรฉs Ramรญrez for emacs-devel links. Do you have an Emacs-related link or announcement? Please e-mail me at sacha@sachachua.com. Thank you!

      You can e-mail me at sacha@sachachua.com.

    17. ๐Ÿ”— r/york Where to find Wild Gralic in York? rss

      I'm looking for wild garlic and I normally go to knavesmire woods but there isn't really any this year! If anyone knows some good spots that are within a walking/cycling distance of the city centre let me know!!

      submitted by /u/FewEntrepreneur7226
      [link] [comments]

    18. ๐Ÿ”— r/Leeds 3 cycling incidents on Stanningley Road in 10 minutes. I hate cycling in this city. rss

      With the weather getting better, fuel getting expensive, and the trains remaining rubbish, I thought I'd get my fat arse back on my bike to work this morning, from Farsley to the LGI/university precinct. I guess that was a stupid idea.

      All of these things happened while riding on the segregated bike path (Leeds- Bradford "Superhighway"), specifically the Stanningley Road stretch. I'm an experienced cyclists and I genuinely obey the rules, including stopping at all traffic lights - just to preempt any silly responses. I drive as well.

      First one - the stretch just before Bramley station. Driver turns left straight across me as I'm going along the bike path. Comes from behind me so I don't see her till the last second and have to slam on the brakes. Hadn't seen me even though she had just passed me.

      Second one, 5 minutes later - riding down the long downhill stretch just by the tennis club. Going quite quickly. Driver pulls into the segregated bike lane and tries to park dead in front of me. Again hasn't even bothered to check mirrors for cyclists before trying to park in the fucking bike lane.

      Third one, only a couple of minutes afterwards - again a quick stretch because of the downhill, just before Armley park. A pedestrian and her young daughter , not at a crossing, have been jumping the motor traffic to get across the road. I don't see them until the very last second because they pop out from behind cars, straight into the bike lane, without looking. Full on emergency stop, thankfully I changed brake pads lately and have my wits about me, I pull up to a stop maybe a foot or two (maximum) in front of the little girl. If I had hit her and knocked her over and she'd hit her head, she could have been killed. Terrifying experience.

      These all happen on quick, straight, downhill stretches of the path. I'm a strong enough cyclist but not a racer, so I'm not hooning it at all, just going at a fair clip coasting downhill. I suppose it's a reminder to expect the unexpected at any moment. And to get a helmet cam.

      But JFC. First time back on the bike in months and three incidents like this straight away. Stuff like this always happens too - at least one incident per week if I'm riding every day. Insane drivers with no business anywhere on the public highway nearly killing you with their cars. Pedestrian incidents are rarer but they still happen.

      Cycling here is shit. Even in places like Stanningley Road where the infrastructure is relatively good, it's just totally ignored by other road users. Because the overall state of cycle provision across the city is poor, there aren't enough cyclists for people to learn to look out for them when driving, and the vicious cycle (!) continues.

      Mind you, if you don't habitually look out for cyclists when driving your car anyway, you shouldn't have a licence. The roads around here are full of psychos and maniacs.

      Rant over. I think I will be back on the train for a while even though it's overcrowded and always late. Just adding to the complaints about the standard of transport provision in Leeds which is completely laughable for a city of this size and (professed) ambition. I'd also love to hear whether anybody else using this stretch of cycle lane also experiences incidents like this regularly or whether it's just me being an idiot.

      EDIT: Thanks everyone, appreciate all the responses. I've calmed down now, this post was a bit of a rant. I'm sorry so many other people have had a crap time.

      I don't want to discourage anyone cycling. I'll still do it, even if not every day. It can be safe and healthy if you take precautions and ride very defensively. I think I had forgotten over the last few months now careful you have to be.

      Some tips on defensive riding here: https://www.edinburghbicycle.com/info/blog/what-is-defensive-cycling

      And please everyone if you are cycling on the road, take your lane when you need to! Don't be intimidated into squeezing right into the side of the road, it's an invitation to bellends to try and pass you on a blind corner or smoosh you into a bus stop.

      submitted by /u/Jazzlike-Machine-222
      [link] [comments]

    19. ๐Ÿ”— r/LocalLLaMA Technical clarification on TurboQuant / RaBitQ for people following the recent TurboQuant discussion rss

      I am Jianyang Gao, first author of the RaBitQ papers. I am posting this here because TurboQuant is now being discussed in [r/LocalLLaMA](/r/LocalLLaMA) in the context of local inference / KV-cache compression, and I think the community should have a technically precise comparison on the public record.

      We are posting this comment to create a public record because the public discussion and promotion of TurboQuant have already created substantial confusion about its relationship to our RaBitQ line of work [1, 2]. These issues and explanations were not raised for the first time. In January 2025, Majid Daliri, the second author of the paper, contacted us to debug his Python translation of our RaBitQ implementation. In May 2025, after we came across their TurboQuant paper on arXiv, we raised the concerns below directly with him in detail. Despite that notice, the authors retained the inaccurate statements in their ICLR submission. Recently, on March 26, 2026, we formally notified all authors again. However, they agreed to fix only part of these issues and only after the ICLR 2026 conference takes place, which we believe is insufficient to dispel the widespread misunderstanding created by their recent promotion and may instead create further confusion at the ICLR meeting itself.

      Our concern has three parts.

      1. Method-level description of RaBitQ is materially incomplete. TurboQuant repeatedly describes random rotation as a key step of its method, yet its description of RaBitQ reduces mainly to a grid-based PQ framing while omitting the Johnson-Lindenstrauss transformation / random rotation, which is one of the most important linkage between the two methods. Moreover, even after two reviewers asked for clarification and discussion of the Johnson-Lindenstrauss transformation / random rotation, the ICLR camera-ready version of TurboQuant still did not add such a discussion; instead, the original description of RaBitQ in the main body was moved to the appendix.
      2. The theoretical description is not supported. TurboQuant described RaBitQ's guarantees as "suboptimal" and attributed this to "loose analysis" without any explanations, although our paper [2] posted in September 2024 had already clearly claimed asymptotic optimality, which matches the optimal bound by Alon and Klartag [3]. Even after this issue was explicitly raised and clarified in emails in May 2025, the authors still do not provide a systematic explanation of how TurboQuant's guarantees compare to the RaBitQ line in their ICLR submission.
      3. The empirical comparison also lacks full disclosure. Majid's January 2025 emails show that he had translated our C++ implementation of RaBitQ into Python and asked us to help debug it. In May 2025, he further acknowledged that, in the reported runtime setting, the RaBitQ baseline was run on a single CPU with multiprocessing disabled. The TurboQuant method itself is run on an A100 GPU. Yet the public paper makes efficiency claims without clearly disclosing that experimental setup. This issue was also raised in our private emails in May 2025.

      In May 2025, our emails directly raised the theoretical and empirical issues; Majid wrote that he had informed his co-authors. During ICLR review, reviewers also asked for clarification about random rotation and the relation to RaBitQ. On March 26, 2026, we formally raised these concerns again to all authors and were told that corrections would wait until after the ICLR 2026 conference takes place; we were also told that they would not acknowledge the structural similarity regarding the Johnson-Lindenstrauss transformation. We do not consider that acceptable given the present level of public promotion and community confusion.

      We are posting this comment so that the community has an accurate public record. We request that the authors publicly and promptly clarify the method- level relationship between TurboQuant and RaBitQ, the theory comparison, and the exact experimental conditions underlying the reported RaBitQ baseline. Given that these concerns were known before ICLR submission and before the current round of public promotion of TurboQuant, we believe it is necessary to bring these issues into the public discussion.

      Public OpenReview thread: https://openreview.net/forum?id=tO3ASKZlok

      References

      [1] Jianyang Gao and Cheng Long, "RaBitQ: Quantizing High-Dimensional Vectors with a Theoretical Error Bound for Approximate Nearest Neighbor Search," Proceedings of the ACM International Conference on Management of Data (SIGMOD), 2024.

      [2] Jianyang Gao, Yutong Gou, Yuexuan Xu, Yongyi Yang, Cheng Long, and Raymond Chi-Wing Wong, "Practical and Asymptotically Optimal Quantization of High- Dimensional Vectors in Euclidean Space for Approximate Nearest Neighbor Search," arXiv:2409.09913, Sep. 2024; later published in SIGMOD 2025.

      [3] Noga Alon and Bo'az Klartag, "Optimal compression of approximate inner products and dimension reduction," 2017 IEEE 58th Annual Symposium on Foundations of Computer Science (FOCS), IEEE, 2017.

      submitted by /u/gaoj0017
      [link] [comments]

    20. ๐Ÿ”— r/Harrogate Roofer recommendations please rss

      Looking for reliable roofers in or around Harrogate please as we've had a nightmare with who did our front and rear flat dormer roofs, initially replaced in October and it's almost April now and they're still not 100% sorted.

      Cheers

      submitted by /u/OkNeighborhood7482
      [link] [comments]

    21. ๐Ÿ”— r/wiesbaden Worin unterscheiden sich Mainz und Wiesbaden am meisten? Wรผrde es irgendwann Sinn machen die Doppelstรคdte in einer zusammenzufรผhren? rss

      submitted by /u/Klarsichtbeton
      [link] [comments]

    22. ๐Ÿ”— r/Yorkshire I think this might be the best garden in North Yorks I've ever seen! Love that Monty Don seems to be such a fan rss

      I think this might be the best garden in North Yorks I've ever seen! Love that Monty Don seems to be such a fan | submitted by /u/Terrible_Passion6178
      [link] [comments]
      ---|---

    23. ๐Ÿ”— r/reverseengineering /r/ReverseEngineering's Weekly Questions Thread rss

      To reduce the amount of noise from questions, we have disabled self-posts in favor of a unified questions thread every week. Feel free to ask any question about reverse engineering here. If your question is about how to use a specific tool, or is specific to some particular target, you will have better luck on the Reverse Engineering StackExchange. See also /r/AskReverseEngineering.

      submitted by /u/AutoModerator
      [link] [comments]

    24. ๐Ÿ”— MetaBrainz python-discid 1.4.0 rss

      A new version of python-discid, a Python wrapper library for libdiscid, is now available. Version 1.4.0 focuses on modernizing the code base and updating the documentation.

      The public API is now fully type-hinted and the type hints are also used in the documentation. A Disc.pregap property was added for convenient access to the first track's pregap. For the full list of changes see the changelog in the documentation.

      The new version is available on PyPI. See also the install instructions for more options. Please note that the new minimal Python version supported is now Python 3.10.

    25. ๐Ÿ”— backnotprop/plannotator v0.16.0 release

      Follow @plannotator on X for updates

      Missed recent releases? Release | Highlights
      ---|---
      v0.15.5 | Custom display names, GitHub viewed file sync, expand/collapse all in file tree, search performance, WSL fix
      v0.15.2 | Compound Planning skill, folder annotation, /plannotator-archive slash command, skill installation via platform installers
      v0.15.0 | Live AI chat in code review, plan archive browser, folder file viewer, resizable split pane, Pi full feature parity
      v0.14.5 | GitLab merge request review, login page image fix, Windows install path fix
      v0.14.4 | GitHub review submission, repo identifier in tab title, nested code fence parser fix, Pi paste URL wiring
      v0.14.3 | PR context panel, diff search in code review, OpenCode permission normalization, landing page redesign
      v0.14.2 | OpenCode plan mode prompt replacement, Windows non-ASCII path fix, Pi link fix
      v0.14.1 | Single submit_plan with auto-detect, viewed-file draft persistence, Bear nested tag fix
      v0.14.0 | PR review via GitHub URL, /plannotator-last for annotating agent messages, OpenCode plan mode permissions fix, VS Code SSH proxy fix
      v0.13.1 | OpenCode plan mode rewrite, Obsidian save fix
      v0.13.0 | Built-in themes, annotatable plan diffs, file-scoped code review comments, Octarine integration, unified review core, Pi remote sessions

      What's New in v0.16.0

      v0.16.0 adds GitHub Copilot CLI as Plannotator's fifth runtime, an external annotations API for integration (stay tuned...), bot callback URLs for Slack- style approval workflows, interactive plan checkboxes, print support, and configurable diff display options. 11 PRs, 3 from external contributors, 2 first-timers.

      GitHub Copilot CLI Integration

      Plannotator now works with GitHub Copilot CLI, contributed by @Yecats. Plan review, code review, and markdown annotation all function the same way they do in Claude Code. The Copilot plugin hooks into exit_plan_mode to intercept plans, and the same /plannotator-review, /plannotator-annotate, and /plannotator-last commands are available.

      Install the binary, then in Copilot CLI:

      /plugin marketplace add backnotprop/plannotator
/plugin install plannotator-copilot@plannotator

      A follow-up PR added environment-variable-based agent detection so the UI correctly identifies which agent launched Plannotator, fixing the badge display that was previously hardcoded to Claude Code.

      External Annotations API

      Any external program can now push annotations into a live Plannotator session. Linters, AI tools, or custom scripts send annotations via HTTP POST to /api/external-annotations, and they appear in the browser UI in real-time through Server-Sent Events. The API supports single and batch annotation creation, field updates via PATCH, deletion by ID or source, and version-gated polling as a fallback for environments where SSE isn't practical.

      This is the foundation for integrating Plannotator with external toolchains. A linter could annotate code review diffs with warnings. A CI pipeline could push review comments. An AI assistant could highlight sections of a plan it has questions about.

      All three server types (plan, review, annotate) expose the same endpoints, and the Pi extension has full parity.

      Interactive Checkboxes

      Task checkboxes in rendered plans are now clickable. Checking or unchecking a box creates a COMMENT annotation that captures the action, the section context, and the task text. Toggling back to the original state removes the override and deletes the annotation. This means your checkbox interactions become part of the feedback sent to the agent.

      Print Support

      Plans can now be printed directly from the review UI. An export dropdown menu in the toolbar offers a print option, and Ctrl+P / Cmd+P works as a keyboard shortcut. A dedicated print stylesheet produces clean white-paper output with A4 formatting, hiding the toolbar, sidebar, and interactive elements.

      Diff Display Options

      The code review diff viewer now exposes display settings that were previously locked to defaults. You can configure overflow behavior (scroll vs word wrap), toggle diff indicators and line numbers, control inline diff granularity, and show or hide diff backgrounds. All settings are persisted via the ConfigStore system (cookies + ~/.plannotator/config.json) and accessible from a new Display tab in the review Settings dialog.

      Bot Callback URL Parameters

      Plannotator share URLs now support callback parameters for bot integrations. When a bot (e.g., a Slack bot) generates a plan and posts the Plannotator URL, it can embed ?cb=<callback_url>&ct=<auth_token> so the approval decision is sent back to the bot automatically. The user reviews and approves in Plannotator, and the bot receives the result without any copy-paste.

      Additional Changes

      • OpenCode startup performance. Replaced compile-time HTML embedding with lazy readFileSync getters and background preloading. Bundle size drops from 21.25 MB to 0.81 MB (96% reduction), cold-start module load from ~160ms to ~35ms (#411, closing #410 reported by @DRBragg)
      • Markdown parser fixes. Indented closing fences (inside list items), trailing text after fence closers, and false table detection on lines with pipes are all fixed (#429, closing #427 reported by @jhillyerd)
      • PR/MR platform test coverage. Regression tests for URL parsing, labels, display helpers, and CLI selection across GitHub and GitLab, including self-hosted GitLab (#426 by @sudorest)
      • Compound skill description fix. Trimmed to fit Claude Code 2.1.86's 250-character limit and added disable-model-invocation frontmatter (#430, closing #412 reported by @arogulin)
      • Copilot on marketing site. The landing page harness selector now includes a Copilot button with install instructions, in alphabetical order alongside the other five runtimes.

      Install / Update

      macOS / Linux:

      curl -fsSL https://plannotator.ai/install.sh | bash

      Windows:

      irm https://plannotator.ai/install.ps1 | iex

      Claude Code Plugin: Run /plugin in Claude Code, find plannotator , and click "Update now".

      Copilot CLI:

      /plugin marketplace add backnotprop/plannotator
/plugin install plannotator-copilot@plannotator

      OpenCode: Clear cache and restart:

      rm -rf ~/.bun/install/cache/@plannotator

      Then in opencode.json:

      {
  "plugin": ["@plannotator/opencode@latest"]
}

      Pi: Install or update the extension:

      pi install npm:@plannotator/pi-extension

      What's Changed

      • feat: GitHub Copilot CLI integration by @Yecats in #409
      • perf(opencode): lazy-load HTML to fix plugin startup time by @backnotprop in #411
      • feat: bot callback URL params for seamless plan review by @aviadshiber in #416
      • fix: detect calling agent via env vars and centralize agent config by @Yecats in #418
      • feat: print support with export menu integration and keyboard shortcut by @Yecats in #420
      • feat: interactive checkboxes with annotation tracking by @Yecats in #423
      • test: cover PR/MR platform helpers by @sudorest in #426
      • feat(review): diff display options with ConfigStore integration by @backnotprop in #428
      • fix(parser): indented fences, trailing text, table detection, and escaped pipes by @backnotprop in #429
      • fix(skill): trim compound skill description under 250-char limit by @backnotprop in #430
      • feat: external annotations API with real-time SSE by @backnotprop in #400

      New Contributors

      Contributors

      @Yecats authored four PRs in this release: GitHub Copilot CLI integration (#409), agent detection fix (#418), print support (#420), and interactive checkboxes (#423). First contribution to the project, and immediately one of the most prolific single- release contributors.

      @aviadshiber authored the bot callback URL system (#416), enabling Plannotator integration with external bot workflows. First contribution.

      @sudorest added PR/MR platform test coverage (#426), protecting the multi-platform review routing.

      Community members who reported issues that drove changes in this release:

      Full Changelog : v0.15.5...v0.16.0

    26. ๐Ÿ”— Szymon Kaliski Q1 2026 rss

      Home Server on NixOS, Sandboxing in MicroVMs, and Feedback Loops for LLMs

    27. ๐Ÿ”— Ampcode News Amp Free Is Ad-Free rss

      When you use Amp Free, you won't see ads anymore.

      We know many of you loved the ads, advertisers were happy, and we quickly grew ad sales to a $10M+ USD annual run rate, but the world has changed since we introduced ads in October 2025.

      The launches of Gemini 3 Pro, Opus 4.5, and GPT-5.2 Codex starting in late November 2025 changed the world, and in this new world, ads don't make sense. Ads just don't pay for enough frontier tokens to make a difference, and token consumption is only going up from here.

      Along with this, OpenAI now offers subscription plans with even more aggressive discounts than what Anthropic offered before. You can pay OpenAI $20/month to get (seemingly) $1000+/month in tokens. This gives you a lot more "free" usage than Amp's ad-supported free tier and is a better choice if cost is your top concern.

      What about the $10 daily free usage of Amp? Most who have it will keep getting it, now without ads. We'll be pausing it for some less-active users. As we ship updates to Amp, you can expect the free daily grant to be more available and more generous for people using Amp in the recommended ways, and less so for people using older Amp versions and workflows. We'll let you know before we make that change. Think of it as a bonus for staying on the frontier with us.

  3. March 29, 2026
    1. ๐Ÿ”— IDA Plugin Updates IDA Plugin Updates on 2026-03-29 rss

      IDA Plugin Updates on 2026-03-29

      New Releases:

      Activity:

    2. ๐Ÿ”— r/wiesbaden Gefunden an der Ecke Adelheid/Schiersteiner Str. rss

      Hoffe der Person geht es mittlerweile besser. Dennoch irgendwo auch schรถne Worte die einem sehr nahe gehen. Ein Reminder dass sehr viele Menschen solche Gefรผhle mit sich herum tragen ohne jemanden zum sprechen zu haben. In dieser schรถnen Stadt sollten wir alle mehr zusammenhalten <3

      submitted by /u/pomelokriger
      [link] [comments]

    3. ๐Ÿ”— r/reverseengineering io_uring from Userland blog (drop a review guys!) rss

      submitted by /u/Outrageous_Egg7579
      [link] [comments]

    4. ๐Ÿ”— r/Leeds Things to do in Leeds rss

      Hello. Iโ€™m coming to Leeds on Wednesday for 2 nights with my husband and 2 boys (20 and 17). Iโ€™m looking for suggestions for what we could do? We have an apartment which is very central. We are working our way through cities in the UK and weโ€™ve never been to Leeds. We would definitely like to go to a few pubs in the evening but any suggestions for the days would be very welcome. We love a bit of culture. I have finished work today so not had time to research anything, but I definitely will do and any recommendations would be very helpful in the meantime. Thanks in advance โ˜บ๏ธ

      submitted by /u/jogon365
      [link] [comments]

    5. ๐Ÿ”— r/reverseengineering The ECMAScript spec forces V8 to leak whether DevTools is open rss

      submitted by /u/LongFaithlessness59
      [link] [comments]

    6. ๐Ÿ”— r/Yorkshire Do you think thereโ€™s a demand for women only gym/fitness & wellness (all in one) centres? rss

      submitted by /u/Powerful-Duck-5193
      [link] [comments]

    7. ๐Ÿ”— r/reverseengineering Decompiling an Android Application Written in .NET MAUI 9 (Xamarin) rss

      submitted by /u/igor_sk
      [link] [comments]

    8. ๐Ÿ”— r/reverseengineering ChatGPT Won't Let You Type Until Cloudflare Reads Your React State. I Decrypted the SDK That Does It. rss

      submitted by /u/AdTemporary2475
      [link] [comments]

    9. ๐Ÿ”— r/Leeds Am I the only one who heard thunder strike??? rss

      Heard thunder strike in city centre for the first time in 2 years!!! Did u guys heard it too?

      submitted by /u/CraftyCompetition860
      [link] [comments]

    10. ๐Ÿ”— r/reverseengineering [Project] Noctyra - A modular, AST-based Python deobfuscator rss

      submitted by /u/lululepuoff
      [link] [comments]

    11. ๐Ÿ”— r/Leeds Finding L&P - A New Zealand Drink - in Leeds or there abouts rss

      My mate, who is from NZ, hasnโ€™t been back to NZ in about 5 years, keeps on nattering on about L&P, a drink. Does anyone know where I can find this in Leeds? Iโ€™d rather find it in the city than pay postage.

      Thanks!

      submitted by /u/Jacob_Ack
      [link] [comments]

    12. ๐Ÿ”— r/Leeds Anxious but authentically trying to make friends rss

      Hey โ€” 35M here. I recently came out of a 9-year relationship, and itโ€™s put me in a place I didnโ€™t expect: a full reset. Not just in terms of dating, but in how I see myself overall. Right now, Iโ€™m trying to rebuild my confidence, figure out what I actually want from life, andโ€”if Iโ€™m being honestโ€”understand parts of myself I may have ignored for a long time. One of those things is my sexuality. Iโ€™ve always had a somewhat ambiguous relationship with it, but lately Iโ€™ve found myself questioning things more. Not in a rushed or panicked wayโ€”more like a quiet curiosity I never really gave space to before. Being in a long-term relationship, I think I just stayed on a path without really stopping to examine it. Now that Iโ€™m on my own, I feel like I owe it to myself to explore that side of who I amโ€”without judgment, labels, or pressure to have immediate answers.

      To cut a long story short, what Iโ€™d really value right now is building genuine, platonic friendshipsโ€”meeting people, having good conversations, and reconnecting in a low-pressure way.

      If anything I've said resonates with you feel free to give me a shout, but also if you're (like me) trying to be more social and make friends then also give me a shout.

      submitted by /u/Antique_Payment2492
      [link] [comments]

    13. ๐Ÿ”— r/york WATCH - Crowds gather for Palm Sunday procession at York Minster rss

      WATCH - Crowds gather for Palm Sunday procession at York Minster | submitted by /u/Due_Ad_3200
      [link] [comments]
      ---|---

    14. ๐Ÿ”— r/Yorkshire Famous Grouse - Red Grouse, Yorkshire Dales rss

      Famous Grouse - Red Grouse, Yorkshire Dales | submitted by /u/aspiranthighlander
      [link] [comments]
      ---|---

    15. ๐Ÿ”— sacha chua :: living an awesome life Emacs Carnival March 2026: Mistakes and learning to reach out rss

      Mostly-similar versions follow: I started with French, translated it to English, and then tweaked some details. Thanks to Philip Kaludercic for hosting this month's carnival!

      In English

      The theme for this month's Emacs Carnival is Mistakes and Misconceptions. Itโ€™s difficult to pinpoint one thing that is clearly a mistake, but there are certainly things I could do more effectively.

      My configuration is very large because I assume my little modifications are only useful to me. They feel too specific, too idiosyncratic. I think people who create libraries or even packages used by lots of other people are awesome. I don't know if I could quite do that myself, though! Even submitting patches upstream and participating in the ensuing discussions sometimes requires more persistence than I have.

      The advantage of keeping my changes in my config is that even if I'm unsure, I can try something out, develop a rough prototype, and change my mind if necessary. When I publish them in a library or a package, I feel like I have to polish my ideas. It's hard to stick to just one idea long enough to refine it.

      My favorite situation is when I write about my attempt in a post, and it inspires someone else to implement their own version (or even a new library or package). On the other hand, if I learn to share my code, I can help more people, and I can also learn from more people and more conversations.

      Many of my modifications are short and easy to copy from my posts, but there are a few collections that depend on other functions, making them difficult to copy. These functions are scattered across several posts on my blog. For example, my functions for learning a language (I'm learning French at the moment) and for controlling Emacs by voice are becoming quite complex. The functions are also exported to my configuration, but the Emacs Lisp file is difficult to navigate if someone wants to copy them. I can extract the code into a file now that Org Mode can tangle to multiple files, but if I spend a little time replacing the "my-" prefix with a library prefix and move them to a repository, people could clone it and download updates. Even if no one uses it, the act of polishing and documenting it will probably be useful to me one day.

      So, it's possible that this is a mistake I often make in Emacs: thinking my functions are too idiosyncratic and too rough, so I leave them in my config. If I dedicate time to extracting the code into a library, I might benefit in the long run. I know lots of people are interested in using Emacs for language learning or by voice. There have been so many other libraries and workflows over the years, so I'm sure people are out there. I want to practice learning more with others. To start, I can make sure interested people can follow my progress through RSS feeds or Mastodon, I can respond when people send me messages, and I can collect contact info and send them a message when I post about the subject.

      I can write more if I reread the changes in my configuration each week, or if I reread my complete configuration for sections which I haven't yet written about. If I participate in virtual meetups or even livestream, I can find out what interests other people. If I submit patches and create tasks in my Org Mode inbox to track the discussions, I can practice refining my work.

      Prot has lowered his coaching prices to โ‚ฌ10 /hour. He's quite prolific when it comes to package development, so he can probably help me figure out how to get stuff out of my config and into a form that other people might be able to use. I've been enjoying learning with my French tutor. It might be worth experimenting with spending some money and time to improve my Emacs skills as well. Sure, it's totally just for fun, but I think it's valuable to practice learning with the help of others instead of stumbling around on my own.

      There's always more to learn, which is wonderful. So this is not really a mistake, just something that could be good to work on. Onward and upward!

      Check out Emacs Carnival March 2026: Mistakes and Misconceptions to see other people's takes on the topic.

      En franรงais

      Le thรจme du Carnaval d'Emacs ce mois-ci est ยซ les erreurs et les idรฉes reรงues ยป. C'est difficile d'identifier une chose qui soit clairement une erreur, mais il y a certainement des choses que je ne fais pas efficacement.

      Ma configuration est trรจs volumineuse car je pense que mes petites modifications ne sont utiles que pour moi. Elles sont trop spรฉcifiques, trop particuliรจres. J'apprรฉcie ceux qui crรฉent des bibliothรจques ou mรชme des paquets que beaucoup d'autres utilisent, mais de mon cรดtรฉ, je ne me sens pas capable de le faire pour l'instant. Mรชme soumettre des correctifs en amont et participer ร  la discussion qui s'ensuit parfois demande plus de persรฉvรฉrance que je n'en ai.

      L'avantage de garder mes modifications dans ma configuration est que, mรชme si je ne suis pas sรปre, je peux essayer quelque chose, dรฉvelopper un prototype prรฉliminaire, et changer d'avis si nรฉcessaire. Quand je les publie dans une bibliothรจque ou un paquet, j'ai l'impression que je dois peaufiner mes idรฉes. C'est difficile de s'en tenir ร  une seule idรฉe assez longtemps.

      Ma situation prรฉfรฉrรฉe est quand je partage mes essais sur mon blog, et qu'ils inspirent une autre personne qui implรฉmentera sa propre version, voire une nouvelle bibliothรจque ou un nouveau paquet.

      En revanche, si j'apprends ร  partager mon code, je peux aider plus de personnes, et je peux aussi apprendre de plus de personnes et de plus de conversations.

      Beaucoup de mes modifications sont brรจves et faciles ร  copier de mes articles, mais il y a quelques collections qui dรฉpendent d'autres fonctions, ce qui les rend difficiles ร  copier. Les fonctions sont dispersรฉes dans plusieurs articles sur mon blog. Par exemple, mes fonctions pour apprendre une langue (particuliรจrement le franรงais) et pour contrรดler Emacs par commande vocale deviennent plutรดt complexes. Elles sont aussi exportรฉes vers ma configuration, mais le fichier Emacs Lisp est difficile ร  parcourir si on veut les copier. Je peux extraire le code dans un fichier maintenant que Org Mode peut le tangler vers plusieurs fichiers, mais si je consacre un peu de temps ร  remplacer le prรฉfixe ยซ my- ยป par celui de la bibliothรจque et ร  le pousser sur le dรฉpรดt, les gens pourraient le cloner et rรฉcupรฉrer les mises ร  jour. Mรชme si personne ne l'utilise, le fait de les peaufiner et de le documenter me sera utile un jour.

      Donc il est possible que ce soit une erreur que je commets souvent dans Emacs : je pense que mes fonctions sont trop idiosyncratiques et trop brutes, je les laisse donc dans ma configuration. Mais si je consacre du temps ร  extraire le code vers une bibliothรจque, j'en bรฉnรฉficierai peut-รชtre ร  long terme. Je sais que beaucoup de gens sont intรฉressรฉs par l'utilisation d'Emacs pour apprendre une langue ou pour la commande vocale. Il y a eu de nombreuses autres bibliothรจques et flux de travail au fil des ans, donc je suis sรปre qu'il y a du monde. Je veux m'entraรฎner ร  apprendre auprรจs de plus de personnes. Pour commencer, je peux m'assurer que les gens intรฉressรฉs peuvent suivre mon progrรจs via les flux RSS ou sur Mastodon, je peux rรฉpondre quand on m'envoie des messages, et je peux recueillir les coordonnรฉes et leur envoyer un message lorsque je publie un article ร  ce sujet.

      Je peux รฉcrire davantage si je relis les modifications dans ma configuration chaque semaine, ou si je relis ma configuration entiรจre pour les sections dont je n'ai pas encore parlรฉ. Si je participe ร  des rรฉunions virtuelles ou mรชme si je diffuse en direct, je vais voir ce qui intรฉresse les autres. Si je soumets des correctifs et crรฉe des tรขches dans ma boรฎte de rรฉception Org Mode pour suivre les discussions, je m'entraรฎne ร  affiner mon travail.

      Prot a baissรฉ ses tarifs de coaching ร  10 euros de l'heure. Il est trรจs prolifique en matiรจre de dรฉveloppement de paquets. J'apprends bien avec mon tuteur en franรงais, donc cela vaut peut-รชtre la peine de consacrer de l'argent et du temps ร  amรฉliorer mes compรฉtences sur Emacs. Certes, c'est juste pour le plaisir, mais c'est aussi important pour moi de m'entraรฎner ร  apprendre avec l'aide des autres au lieu de trรฉbucher toute seule.

      J'ai toujours plus de choses ร  apprendre, ce qui est merveilleux. Ce n'est pas vraiment une erreur, mais plutรดt un point ร  amรฉliorer. En avant !

      Consultez Emacs Carnival March 2026: Mistakes and Misconceptions pour d'autres perspectives sur le sujet.

      You can e-mail me at sacha@sachachua.com.

    16. ๐Ÿ”— r/york York city photos rss

      York city photos | Absolutely stunning ๐Ÿ˜ submitted by /u/AdAccomplished3733
      [link] [comments]
      ---|---

    17. ๐Ÿ”— r/LocalLLaMA LocalLLaMA 2026 rss

      LocalLLaMA 2026 | we are doomed submitted by /u/jacek2023
      [link] [comments]
      ---|---

    18. ๐Ÿ”— r/Harrogate Local area opinions rss

      Looking at houses on Greenfields Road/Greenfields Drive.

      Anyone able to give me insight on what itโ€™s like? I know itโ€™s a bit of a cut through road, but think the houses are set back enough for traffic noise not to bother.

      I know Harrogate/Starbeck/Knaresborough are all lovely places and anti social behaviour and crimes are a lot less than Leeds where Iโ€™m coming from. Just trying to get a feel for the area thatโ€™s all.

      submitted by /u/GemzH
      [link] [comments]

    19. ๐Ÿ”— r/Harrogate Recycling at large supermarket in Harrogate? rss

      I have some empty liquid soap refills that I'm looking to recycle. Unfortunately I can't recycle them normally, according to the instructions I need to take them to a 'large supermarket' to be recycled.

      Does anybody know where I might be able to take them? Thanks

      submitted by /u/leaftreefrog
      [link] [comments]

    20. ๐Ÿ”— Register Spill Joy & Curiosity #80 rss

      Do you know how it should work? Does the agent? Or does the codebase?

      Lately I've been thinking a lot about why sometimes using an agent leads to great results and other times it doesn't. My current theory: it depends on what knowledge about the task at hand is encoded where.

      If all the knowledge required to solve the task to your satisfaction is available either in your prompt, or in the codebase, or in the training data of the model, then things go fine.

      Things go badly if there's a gap. That is, if you wrongly assume the agent will know how to do something but it won't because that knowledge is neither in the codebase nor in the training data.

      If I ask the agent to fix a bug that has a very obvious solution, say: a button's hover state doesn't activate on hover, then everything you need to know to fix it is available. The problem is in the prompt, the code should explain what the button is, and what a hover state is is in the training data.

      But what if there's a bug and you don't know even how to explain what the bug is or what the desired state is? Not good.

      Or what if you tell the agent to build you a feature and you assume it does so by going over here and adding that and then going over there and adding this, but the codebase allows fifteen other ways, and the training data doesn't say those fifteen other ways are bad? Not good.

      Sometimes the codebase and its documentation contains that information through types or tests or conventions. Other times the training data tells the agent that there's only one way to add a new endpoint in Rails or Next.js or SvelteKit. But if it's neither in the codebase nor in the training data, then you have to put it in the prompt.

      Theory is too big a word for these thoughts, yes, but I've been asking myself "where is the knowledge?" a lot when working with Amp this week and found it useful, so there you go, maybe you get something out of it too.

      • Last week I asked whether software is turning into a liquid and David Soria Parra, Member of Technical Staff at Anthropic and creator of MCP (meaning: someone who's seen things up close), replied: "I think people don't run the AI maximalist simulation of what this actually means and how far it will go just yet. Most code will just be ephemeral one time use"

      • John Regehr: Zero-Degree-of-Freedom LLM Coding using Executable Oracles. This is excellent and resonated with my thoughts from above. "When an LLM has the option of doing something poorly, we simply can't trust it to make the right choices. The solution, then, is clear: we need to take away the freedom to do the job badly. The software tools that can help us accomplish this are executable oracles. The simplest executable oracle is a test case--but test cases, even when there are a lot of them, are weak. [โ€ฆ] When I look at the best software testing efforts out there, there's invariably something creative and interesting hiding inside. I feel like a lot of projects leave easy testing wins sitting on the floor because nobody has carefully thought about what test oracles might be used. Finding executable oracles for LLMs feels the same to me: with a little effort and critical thinking, we can often find a programmatic way to pin down some degree of freedom that would otherwise be available to the LLM to screw up." I also want to quote that lovely last paragraph, but I won't, because I want you to read everything else that leads up to it too. This is good stuff.

      • And here's Mary Rose Cook, singing harmonies on top of Regehr's lines when talking about freedom of expression and constraints for agents: Code generation that just works.

      • Cheng Lou has "crawled through depths of hell to bring you, for the foreseeable years, one of the more important foundational pieces of UI engineering (if not in implementation then certainly at least in concept): Fast, accurate and comprehensive userland text measurement algorithm in pure TypeScript, usable for laying out entire web pages without CSS, bypassing DOM measurements and reflow." It's called Pretext and it's impressive. I mean, look at this demo! Move the orbs around! Or the ASCII one or click on the logos in this one. According to Lou, this was "achieved through showing Claude Code and Codex the browsers ground truth, and have them measure & iterate against those at every significant container width, running over weeks." And yet the README doesn't mention that at all. That tells me we're past a big milestone.

      • If you're on desktop, see also this dragon that's built with Pretext.

      • Marc Brooker is asking: What about juniors? This is one of the most inspiring and motivating pieces of writing I've read in the past few months. I love the Wellington quote on engineering: "to define it rudely but not inaptly, it is the art of doing that well with one dollar, which any bungler can do with two after a fashion." And I love Marc's very own definition: "I believe that this is the core work of engineering: deeply understanding the problem to be solved, the constraints, the tools available, and the environment in which it operates, and coming up with an optimal solution. This requires real creativity, because the constraints are typically over constrained, and real empathy because many of the constraints come directly from human irrationality. It also requires a deep understanding of the tools available, and what those tools can and can't do." I also think his answer to the question is interesting and the question itself is very important. (I said similar things on last year's You've Been A Bad Agent episode.)

      • Marc's previous post is also great: "Over the next couple of years, the most valuable people to have on a software team are going to be experienced folks who're actively working to keep their heuristics fresh. Who can combine curiosity with experience. Among the least valuable people to have on a software team are experienced folks who aren't willing to change their thinking. Beyond that, it's hard to see."

      • If you read both of Marc's posts, you'll enjoy Pieter Hintjens' A Tale of Two Bridges. Engineering is the art of making the tradeoffs, not building the perfect thing.

      • Michael Nielsen: Which Future? I'm very glad I read this. Bikini Atoll and fire safety will stay with me.

      • Sad news: Tracy Kidder, author of The Soul of a New Machine, has died. I highly recommend reading this book. I last did so in March of last year. And here I am again, telling you: read it, it's fantastic. And then read Bryan Cantrill's reflections on it.

      • Rands has been bitten by the agent bug: "I've never built more interesting, random, and useless scripts, tools, and services than I have in the last six months. The cost to go from 'Random Thought' to 'Working Something' has never been lower"

      • Linear: Issue tracking is dead. Look up to the sky, there's me, in a tiny plane that's pulling a banner saying in big red letters: told you.

      • This is very, very on the nose and I wouldn't sign it without making some big changes, but there is something here that I've felt before, maybe not to this extent, maybe not in this exact shape, but something here resonates and makes parts of it feel true: "'Collaboration' is bullshit." I don't think Big Tech the Boogeyman is to blame (my 8-year-old had to do her first group project in school a few weeks ago -- creating a stop-motion movie -- and nearly lost her mind), but this this much, I think, is true: "most complex, high-quality work is done by individuals or very small groups operating with clear authority and sharp accountability, then rationalized into the language of teamwork afterward. Dostoevsky wrote The Brothers Karamazov alone. The Apollo Guidance Computer came from a team at MIT small enough to have real ownership [โ€ฆ] Communication matters, and shared context matters. But there's a huge difference between communication and collaboration as infrastructure to support individual, high-agency ownership, and communication and collaboration as the primary activity of an organisation."

      • Eoghan McCabe, CEO of Intercom, is saying the "age of vertical models is here." I'm skeptical, because it all hinges on this idea of verticals and domain knowledge and I don't know if that won't be washed away by bigger models, but it is interesting: "the labs are in an interesting position where on one hand the horizontal, general purpose models are actually over-serving the market for specific use cases. E.g. their models are more generally intelligent than is needed for customer service. And on the other hand, the open-weight models are more than good enough where high quality domain specific post-training can make the resulting models superior at the special purpose jobs, and in the ways that matter to that particular job. E.g. in service, the soft factors really matter, like judgement, pleasantness, attentiveness (as well as the hard factors mentioned prior, like the ability to effectively resolve problems, quickly and cheaply)."

      • meow.camera

      • Google published TurboQuant, a "set of advanced theoretically grounded quantization algorithms that enable massive compression for large language models and vector search engines." I won't claim here to understand all of it, but I do think I understand the bit about how "PolarQuant converts the vector into polar coordinates using a Cartesian coordinate system" and that's very cool. Also goes to show that if AI progress wasn'tt a race towards AGI and they'd all stop building bigger and bigger models, there'd be so many optimizations to make.

      • Systems Thinking is Brain Rot for Analysts. Refreshing.

      • This is the Gruber I love: "And the fucking autoplay videos, jesus. You read two paragraphs and there's a box that interrupts you. You read another two paragraphs and there's another interruption. All the way until the end of the article. We're visiting their website to read a fucking article. If we wanted to watch videos, we'd be on YouTube. It's like going to a restaurant, ordering a cheeseburger, and they send a marching band to your table to play trumpets right in your ear and squirt you with a water pistol while trying to sell you towels."

      • And this is the Internet I love: 25 Years of Eggs. "Everyone needs a rewarding hobby. I've been scanning all of my receipts since 2001. I never typed in a single price - just kept the images. I figured someday the technology to read them would catch up, and the data would be interesting. This year I tested it. Two AI coding agents, 11,345 receipts. I started with eggs."

      • Cursor's crossroads: "It's a story distinctly of the AI era: Cursor is four years old but already has an innovator's dilemma, arguably outgunned by newer products in the market it popularized. Every AI startup fears OpenAI or Anthropic releasing a product directly in competition with theirs. It's the nightmare scenario, and Cursor is living it, more quickly than Truell and his team ever expected. [โ€ฆ] As Truell and I get ready to end our Zoom call, I notice the picture of Caro again. I think about how it took Caro six months to edit a single chapter of The Power Broker. Truell has less time than that before the next change."

      • Great brain massage: Let's see Paul Allen's SIMD CSV parser.

      • Okay, now before you click the next link and close the tab right away, let me tell you: yes, I thought so too. I also thought that it's not for me, doesn't contain anything I didn't know, that it's boring old stuff, but it's not! There's some real whoa-moments in there: Google Has a Secret Reference Desk. Here's How to Use It. The title is weird though, yes, but, hot damn, the intitle: "index of" /pdfthing alone is worth it.

      • Satisfyingly meta: Joel Meyerowitz on Photographing Giorgio Morandi's Studio.

      • Stripe launched projects.dev which "lets you or your agents provision multiple services, generate and store credentials, and manage usage and billing from the CLI." Makes total sense when you want to increase the GDP of the Internet.

      • Finally! Edward, Nick, Rasmus, and Julia shared the "first iteration of the Playbit runtime, our vision for building playful personal-scale software": playbit.app.

      • Dappled light: "Growing up, I loved this mix of shade and sun I called 'shun.' Sunlight slipped through the leaves, and its tiny gaps turned into pinholes that project little dancing suns. It felt like magic."

      • McCartney's creativity in 3 photographs.

      Note from the producer: no newsletter next week. One weekend of vacation.

      Collected 25 years of egg receipts? You should subscribe:

  4. March 28, 2026
    1. ๐Ÿ”— IDA Plugin Updates IDA Plugin Updates on 2026-03-28 rss

      IDA Plugin Updates on 2026-03-28

      New Releases:

      Activity:

    2. ๐Ÿ”— r/reverseengineering Blog: Decompiling the White House's New App rss

      submitted by /u/ScottContini
      [link] [comments]

    3. ๐Ÿ”— r/reverseengineering Agent reverse-engineers website APIs from inside your browser rss

      submitted by /u/BodybuilderLost328
      [link] [comments]

    4. ๐Ÿ”— r/Leeds Attitudes of Leeds private hire drivers rss

      Ey up!

      Been living in Leeds for over a decade, have had an amazing time in here so far, in terms of social attitudes and values in general. Public life here is truly pleasant. But when it comes to the taxi / private hire scene it's a different story, unfortunately.

      On the rare occasion when I've needed a ride, I've been met with appalling attitudes on behalf of the driver more often than not. These can be summed up as the following:

      Driver deliberately ignoring social cues that I don't want any chat, big or small, being way too insistent in knowing where I'm going and for how long, etc (airport rides).

      Driver asking me to justify my reproductive choices (this one, I reported to the company with no feedback whatsoever from them).

      Driver ranting about "British riders having weak vision at night... don't know how they are allowed to drive" and "women drivers" - I am a woman, so this felt way too boundary pushing, trolling-like behaviour during what should have been a peaceful ride home after a flight.

      Yes, I've had the occasional amazing friendly driver. But I am lost for words at how often seemingly I've had the ones that seem to take advantage of the 'captive situation' so to speak. The last one was truly disgusting, and made me want to opt out from using their services ever again, as I don't feel safe.

      Would report to the licensing enforcement team, but I'm not sure I really trust the potential outcome.

      Have any of you ever experienced this over here? I'm trying to get a sense of the scale of this problem, how common this is, or have I just had a back luck... many times?

      How is this behaviour tolerated?

      Please, tell me your stories, I'm all ears.

      submitted by /u/MeaningLegitimate782
      [link] [comments]

    5. ๐Ÿ”— r/Yorkshire Palm Sunday Eve. Battle of Towton rss

      Palm Sunday Eve. Battle of Towton | Palm Sunday Eve. Itโ€™s strange to think that on this night in 1461, the men at Towton would have been preparing themselvesโ€ฆ knowing what was coming with the dawn. No certainty. No escape. Only the knowledge that morning would bring a fight to the death with no prisoners taken. The losing side were stripped naked in the snow, had their ears and noses cut off by daggers, then butchered with Halberds, swords, war hammers and axes. After visiting Towton and Saxton, that thought sits differently with me. Those fields donโ€™t feel empty โ€” they feel remembered. Tonight, I give my utmost respect to all those men who foughtโ€ฆ and to those who endured what came after. See my films on Towton and John Clifford here Towton : https://www.youtube.com/watch?v=TU2ojFL-oIU John Clifford : https://www.youtube.com/watch?v=aBPtGYYnyWI submitted by /u/The_Black_Banner_UK
      [link] [comments]
      ---|---

    6. ๐Ÿ”— r/york I HATE THE NO 11 BUS rss

      just wanted to scream it into the void.

      thanks

      submitted by /u/Smart_Apricot_9735
      [link] [comments]

    7. ๐Ÿ”— r/LocalLLaMA Turbo3 + gfx906 + 4 mi50 16gb running qwen3.5 122b ๐Ÿคฏ rss

      Turbo3 + gfx906 + 4 mi50 16gb running qwen3.5 122b ๐Ÿคฏ | Today I merged gfx906 and Turbo3 forks in a fresh fork of llamacpp and it went well. submitted by /u/Exact-Cupcake-2603
      [link] [comments]
      ---|---

    8. ๐Ÿ”— r/wiesbaden Vorfall RB10 Wiesbaden Hbf rss

      Hat jemand mitbekommen, was gestern Abend, ca. 21:50, in der RB10 nach Neuwied am Hbf Wiesbaden los war?

      Scheinbar hat jemand Reizgas (?) versprรผht. Ich saรŸ ziemlich am Ende und habe nur schmerzverzerrte Schreie aus der Zugmitte gehรถrt.

      Ich hatte dann zwei Polizisten am Gleis informiert, habe mir dann aber ein Uber genommen und dementsprechend auch nichts mehr mitbekommen.

      Hoffe es war nichts schlimmeres.

      submitted by /u/blenderbender_
      [link] [comments]

    9. ๐Ÿ”— r/LocalLLaMA Gemma 4 rss

      Gemma 4 | Sharing this after seeing these tweets(1 , 2). Someone mentioned this exact details on twitter 2 days back. submitted by /u/pmttyji
      [link] [comments]
      ---|---

    10. ๐Ÿ”— r/Leeds Does anyone have any tickets they don't need for the hyde park LOTR Marathon on april 6th? rss

      submitted by /u/231923
      [link] [comments]

    11. ๐Ÿ”— r/Leeds Leeds at night photos rss

      Thanks for your kind words on my first uploads. I took some photos at night in the same locations and thought I'd share. Still learning but enjoying it so far.

      submitted by /u/Phil-pot
      [link] [comments]

    12. ๐Ÿ”— r/LocalLLaMA A simple explanation of the key idea behind TurboQuant rss

      TurboQuant (Zandieh et al. 2025) has been all the rage in the past two days, and I've seen lots of comments here attempting to explain the magic behind it. Many of those comments boil down to "dude, it's polar coordinates!!!", and that's really misleading. The most important part has nothing to do with polar coordinates (although they are emphasized in Google's blog post, so the confusion is understandable).

      TurboQuant is a vector quantization algorithm. It turns a vector of numbers into another vector of numbers that takes up less memory.

      Quantization is a fairly basic operation. If you have an n -dimensional vector that looks like this:

      0.2374623 0.7237428 0.5434738 0.1001233 ...

      Then a quantized version of that vector may look like this:

      0.237 0.723 0.543 0.100 ...

      Notice how I simply shaved off the last four digits of each number? That's already an example of a crude quantization process. Obviously, there are far more sophisticated schemes, including grouping coefficients in blocks, adaptive thresholds, calibrated precision based on experimental data etc., but at its core, quantization always involves reducing coefficient precision.

      Here is the key idea behind TurboQuant: Before quantizing a vector, we randomly rotate it in the n -dimensional space it resides in. The corresponding counter-rotation is applied during dequantization.

      That's it.

      Now you probably feel that I must have left out an important detail. Surely the rotation can't be completely random? Maybe it's sampled from a particular distribution, or somehow input-dependent? Or perhaps there is another operation that goes hand in hand with it?

      Nope. I didn't leave anything out. Just applying a random rotation to the vector dramatically improves quantization performance.

      But why?

      Because the magnitudes of the coefficients of state vectors in language models aren't distributed uniformly among the vector dimensions. It's very common to see vectors that look like this:

      0.0000023 0.9999428 <-- !!! 0.0000738 0.0000003 ...

      This phenomenon has many names, and it shows up everywhere in transformer research. You can read about "massive activations" (Sun et al. 2024) and "attention sinks" (e.g. Gu et al. 2024) for a deeper analysis.

      What matters for the purposes of this explanation is: Vectors with this type of quasi-sparse structure are terrible targets for component quantization. Reducing precision in such a vector effectively turns the massive component into 1 (assuming the vector is normalized), and all other components into 0. That is, quantization "snaps" the vector to its nearest cardinal direction. This collapses the information content of the vector, as identifying a cardinal direction takes only log2(2n) bits, whereas the quantized vector can hold kn bits (assuming k bits per component).

      And that's where the random rotation comes in! Since most directions aren't near a cardinal direction (and this only becomes more true as the number of dimensions increases), a random rotation almost surely results in a vector that distributes the coefficient weight evenly across all components, meaning that quantization doesn't cause information loss beyond that expected from precision reduction.

      The TurboQuant paper proves this mathematically, and gives an exact description of the distribution behavior, but the intuitive understanding is much more straightforward than that.

      This idea isn't new (RaBitQ employs the same trick, and QuIP a similar one), but TurboQuant combines it with a second step that eliminates biases that arise when quantized vectors that are optimal in a certain sense (MSE) are used to compute inner products, which is what happens in attention blocks. See the paper if you're interested in the details.

      submitted by /u/-p-e-w-
      [link] [comments]

    13. ๐Ÿ”— r/LocalLLaMA Bought RTX4080 32GB Triple Fan from China rss

      Bought RTX4080 32GB Triple Fan from China | Got me 32GB RTX 4080 from China for around 1300โ‚ฌ. (+ extra shipping)
      I think for the current market the price it is reasonable for 32GB of VRAM.
      It runs smooth and works quiet because of triple fan which was important for me What is first thing I should try to do? https://www.reddit.com/r/LocalLLaMA/comments/1s62b23/comment/od9z1q3/?utm_source=share&utm_medium=web3x&utm_name=web3xcss&utm_term=1&utm_content=share_button submitted by /u/Sanubo
      [link] [comments]
      ---|---

    14. ๐Ÿ”— r/LocalLLaMA Me waiting for TurboQuant be like rss

      Me waiting for TurboQuant be like | submitted by /u/Altruistic_Heat_9531
      [link] [comments]
      ---|---

    15. ๐Ÿ”— r/Leeds Worth Opening a Sauna in Leeds? rss

      I have now been to over 40 saunas across the UK and was introduced to contrast therapy during my time in Helsinki. Since then, this has helped my mental and physical well-being significantly.

      Professionally, I am a Data Scientist but have always wanted to build something which might make a difference to the local community in Leeds especially given that so many people are into running and fitness.

      This is a long shot but thought I had ask if people even enjoy the idea of cold plunges and sauna?

      submitted by /u/BondBagri
      [link] [comments]

    16. ๐Ÿ”— r/Yorkshire Living in the Pennine hills is the gift that keeps giving rss

      Living in the Pennine hills is the gift that keeps giving | What a sight to open the curtains to, have a great weekend everyone ๐Ÿ˜ submitted by /u/Gh0styD0g
      [link] [comments]
      ---|---

    17. ๐Ÿ”— r/york York GPs rss

      Hey,

      Anyone living in york know/have experience with GPs that do shared care?

      I need it for my testosterone and adhd medication!

      Thanks in advance

      submitted by /u/Total_Bed_3882
      [link] [comments]

    18. ๐Ÿ”— r/Yorkshire Amos the Donkey, Barnsley, 1910 rss

      Amos the Donkey, Barnsley, 1910 | submitted by /u/Del_213
      [link] [comments]
      ---|---

    19. ๐Ÿ”— r/Harrogate Where to buy Casio watches in Harrogate? rss

      Does anybody know where I can buy Casio digital watches in Harrogate? Not G-Shock, just regular old cheap Casio's. All I know are the big luxury jewelry shops. Any smaller outlets around?

      submitted by /u/RetroBreezeYT
      [link] [comments]

    20. ๐Ÿ”— r/wiesbaden Schlossplatz, 13:00 - Rain or shine rss

      submitted by /u/ramona_rox
      [link] [comments]

    21. ๐Ÿ”— r/Yorkshire Places to go ? rss

      Hey everyone

      Stopping up in York town centre next weekend and would greatly appreciate some visit ideas. I've seen Robin Hood bay on here so that's already pencilled in, and I saw a YouTuber go to a chippy called the Scrap Box. I've never been to the Viking museum, but last time we were up there were did Whitby so we don't want to go twice.

      Are there any other day trip visits within an hours ish drive from the city centre ?

      Cheers

      submitted by /u/michaeljcox24
      [link] [comments]

    22. ๐Ÿ”— r/LocalLLaMA The AI releases hype cycle in a nutshell rss

      The AI releases hype cycle in a nutshell | This might look like a shitpost but beyond the meme lies the truth. Pay attention to my point: every new AI feature announcement now follows the exact same script: Week one : is pure exuberance (VEO 3 generating two elderly men speaking in Portuguese at the top of Everest, nano banana editing images so convincingly that ppl talk about photoshop's death, GPT-5.4 picking up on subtle context. Then week two hits. The model starts answering nonsense stuffed with em dashes, videos turn into surrealist art that ignores the prompt, etc. The companies don't announce anything about degradation, errors, etc. they don't have to. They simply announce more features (music maker?) feed the hype, and the cycle resets with a new week of exuberance. submitted by /u/GreenBird-ee
      [link] [comments]
      ---|---

    23. ๐Ÿ”— r/Harrogate Best dentist in Harrogate?? Need suggestions rss

      Need to switch dentist and not sure whereโ€™s actually good.

      Had a couple rushed appointments before so just want somewhere decent that takes their time. Happy to go private if itโ€™s worth it.

      Any reco?

      submitted by /u/Purplemoon_1988
      [link] [comments]

    24. ๐Ÿ”— r/Yorkshire Man who was 'front and centre' of far-right Hull riots jailed for six years rss

      submitted by /u/johnsmithoncemore
      [link] [comments]

    25. ๐Ÿ”— HexRaysSA/plugin-repository commits sync repo: +2 releases, ~1 changed rss 
      sync repo: +2 releases, ~1 changed

## New releases
- [drop-all-the-files](https://github.com/milankovo/ida-drop-all-the-files): 1.4.0
- [global-struct-dissector](https://github.com/williballenthin/idawilli): 0.1.1

## Changes
- [oplog](https://github.com/williballenthin/idawilli):
  - 0.3.0: archive contents changed, download URL changed
    26. ๐Ÿ”— r/york rail replacement buses, sunday 29/03 rss

      hi, iโ€™m travelling tomorrow on one of the rail replacement buses to newcastle. where is the bus stop for this? is it leeman road next to the memorial gardens?

      submitted by /u/aster0idzz
      [link] [comments]

    27. ๐Ÿ”— Drew DeVault's blog tar: a slop-free alternative to rsync rss

      So apparently rsync is slop now. When I heard, I wanted to drop a quick note on my blog to give an alternative: tar. It doesnโ€™t do everything that rsync does, in particular identifying and skipping up-to-date files, but tar + ssh can definitely accomodate the use case of โ€œtransmit all of these files over an SSH connection to another hostโ€.

      Consider the following:

      tar -cz public | ssh example.org tar -C /var/www -xz

      This will transfer the contents of ./public/ to example.org:/var/www/public/, preserving file ownership and permissions and so on, with gzip compression. This is roughly the equivalent of:

      rsync -a public example.org:/var/www/

      Hereโ€™s the same thing with a lightweight progress display thanks to pv:

      tar -cz public | pv | ssh example.org tar -C /var/www -xz

      I know tar is infamously difficult to remember how to use. Honestly, I kind of feel that way about rsync, too. But, hereโ€™s a refresher on the most important options for this use-case. To use tar, pick one of the following modes with the command line flags:

      • -c: create an archive
      • -x: extract an archive

      Use -f <filename> to read from or write to a file. Without this option, tar uses stdin and stdout, which is what the pipelines above rely on. Use -C <path> to change directories before archiving or extracting files. Use -z to compress or decompress the tarball with gzip. Thatโ€™s basically everything you need to know about tar to use it for this purpose (and for most purposes, really).

      With rsync, to control where the files end up you have to memorize some rules about things like whether or not each path has a trailing slash. With tar, the rules are, in my opinion, a bit easier to reason about. The paths which appear on the command line of tar -c are the paths that tar -x will open to create those files. So if you run this:

      tar -c public/index.html public/index.css

      You get a tarball which has public/index.html and public/index.css in it.

      When tar -x opens this tarball, it will call fopen("public/index.html", "w"). So, whatever tarโ€™s working directory is, it will extract this file into ./public/index.html. You can change the working directory before tar does this, on either end, by passing tar -C <path>.

      Of course, you could just use scp, but this fits into my brain better.

      I hope thatโ€™s useful to you!

      Update: As a fun little challenge I wrapped up this concept in a small program that makes it easier to use:

      https://git.sr.ht/~sircmpwn/xtar

      Example:

      xtar -R /var/www me@example.org public/*

generated: March 31, 2026 at 09:34:12