🏡

to read (pdf)

generated: May 09, 2026 at 00:19:34

May 09, 2026
1. 🔗 anthropics/claude-code v2.1.137 release
  What's changed
  - [VSCode] Fixed extension failing to activate on Windows
2. 🔗 pydantic/pydantic-ai-harness v0.2.1 (2026-05-08) release
  What's Changed
  - fix(code_mode): Document monty's missing wall-clock and timing primitives in run_code description by @DouweM in #236
  - fix(code_mode): Filter builtin-tool local fallback tools (ToolDefinition.prefer_builtin=True) out of sandboxing by @DouweM in #234
  - Add codemode dependency group alias by @adtyavrdhn in #224
  Full Changelog : v0.2.0...v0.2.1
May 08, 2026
1. 🔗 r/reverseengineering [Update] QSLCL v2.0.2 - Universal SoC Framework with Encryption (A12-A17+, Qualcomm, MediaTek, Unisoc) rss
  
  submitted by /u/Axiic457
  [link] [comments]
2. 🔗 r/Yorkshire The Gannet, RSPB Bempton Cliffs, Yorkshire rss
  
  | submitted by /u/aspiranthighlander
  [link] [comments]
  ---|---
3. 🔗 r/Yorkshire A Yorkshire Street Scene From One County To The Next rss
  
  | submitted by /u/Curious_Strike_5379
  [link] [comments]
  ---|---
4. 🔗 Hex-Rays Blog Announcing the 2025 Plugin Contest Winners rss
  
  The 2025 Hex-Rays IDA Plugin Contest is officially wrapped up, and we are excited to announce this year's winners! This edition drew 25 submissions from both returning participants and newcomers, each bringing fresh ideas to extend and improve IDA Pro.
5. 🔗 anthropics/claude-code v2.1.136 release
  What's changed
  - Added CLAUDE_CODE_ENABLE_FEEDBACK_SURVEY_FOR_OTEL to re-enable the session quality survey for enterprises capturing responses through OpenTelemetry
  - Added settings.autoMode.hard_deny for auto mode classifier rules that block unconditionally regardless of user intent or allow exceptions
  - Fixed MCP servers configured in .mcp.json, plugins, and claude.ai connectors silently disappearing after /clear in the VS Code extension, JetBrains plugin, and Agent SDK
  - Fixed a rare login loop where a concurrent credential write could overwrite a freshly-rotated OAuth token and force re-login
  - Fixed MCP OAuth refresh tokens being lost when multiple servers refresh concurrently — users with several remote MCP servers should no longer need daily re-authentication
  - Fixed an API error (400) when extended thinking emitted a redacted thinking block after a tool call
  - Fixed --resume / --continue not finding sessions when the project path contains underscores
  - Fixed plan mode not blocking file writes when a matching Edit(...) allow rule exists
  - WSL2: image paste from Windows clipboard now works via a PowerShell fallback when xclip/wl-paste cannot read image data
  - Fixed plugin Stop/UserPromptSubmit hooks failing when cache cleanup deletes a version still in use by a running session
  - Improved visual consistency across slash command dialogs: standardized footer hints, dialog spacing, and arrow-key styling, and the dialog frame now appears immediately during loading instead of popping in after
  - Fixed colors appearing at wrong positions in bash command output and markdown code blocks
  - Fixed ReasonML diffs rendering corrupted "undefined" text artifacts at word-diff boundaries
  - Fixed worktree exit dialog warning about uncommitted files in the wrong directory after worktree removal
  - Fixed @ file picker not matching files created mid-session in small non-git directories
  - Fixed @-mention file picker not finding files in directories with more than 100 entries
  - Fixed failed tool calls not being click-to-expand in fullscreen mode when their output was truncated
  - Fixed Backspace and Ctrl+Backspace getting swapped after using Ctrl+G to open an external editor on terminals with persistent extended-key modes
  - Fixed /usage weekly reset showing time of day instead of the calendar date
  - Fixed welcome banner ellipsis causing column overflow on CJK terminals
  - Fixed /insights crash when session history contains tool calls with malformed input fields
  - Fixed a renderer crash when a tool's collapsibility classification changes mid-session
  - Fixed a skills entry in plugin.json hiding the plugin's default skills/ directory, and listing a file path now shows an error instead of failing silently
  - Fixed IDE shell-integration lock files not respecting CLAUDE_CONFIG_DIR
  - Fixed trailing whitespace in copied terminal output during streaming
  - Fixed plugin uninstall and enable/disable not matching slugs case-insensitively
  - Fixed tool error truncation marker showing a negative count for surrogate-pair strings
  - Fixed env vars from CLAUDE_ENV_FILE SessionStart hooks going stale after /resume or /clear
  - Fixed /branch saving a multi-line session title when given a pasted multi-line name
  - Fixed a stray leading space on the second line of wrapped text at the column boundary
  - Fixed Esc not dismissing dialogs in /install-github-app, /desktop, /resume, and /web-setup
  - Fixed /doctor MCP schema errors not naming the missing field or showing the source file path
  - Fixed Bash permission prompts showing an internal parser diagnostic instead of a user-readable explanation
  - Fixed plugin slash commands with spaces (e.g. /myplugin review) not resolving to their namespaced form
  - Fixed AskUserQuestion discarding multi-select answers when supplied as an array
  - Fixed /clear <name> not labeling the cleared session for /resume
  - Fixed CronList output missing qualifiers and the scheduled prompt
  - Fixed "Jump to bottom" overlay leaving color artifacts on CJK characters in fullscreen mode
  - Fixed wide markdown tables leaving a stale bordered render in terminal scrollback while streaming
  - Fixed pasted text being silently dropped when a long prompt with a pasted-text placeholder was auto-truncated
  - Fixed /release-notes getting stuck on an old version after a failed changelog refresh
  - Fixed /mcp server list not scrolling when there are more servers than fit in the terminal
  - Fixed mid-input slash command autocomplete not working after an initial slash command
  - Fixed scrolling to bottom re-engaging auto-follow with autoScrollEnabled: false
  - Fixed prompt suggestions being auto-submitted by Enter on an empty input instead of requiring Tab or arrow to accept
  - Fixed keyboard shortcut hints not reflecting rebound keys from keybindings.json
  - Fixed /settings language change being reverted on Escape after confirming
  - Fixed /terminal-setup only appearing in autocomplete on exact name match instead of partial prefixes
  - Fixed "Chat about this" on an AskUserQuestion dialog erasing the question text
  - Fixed MCP tool results being invisible when the server returns content blocks
  - Improved error message when --worktree collides with an existing or stale worktree
  - Changed plugin marketplace removal key to d (matching delete elsewhere) instead of r which collided with retry
6. 🔗 @HexRaysSA@infosec.exchange 🔦 PLUGIN SPOTLIGHT: ida-cyberchef mastodon
  
  🔦 PLUGIN SPOTLIGHT: ida-cyberchef
  
  This is a new open source plugin that embeds CyberChef's data transformation engine directly into IDA Pro, with a Qt interface that sits alongside your disassembly as a side panel.
  
  Data flows top to bottom through three panels for input, recipe, and output.
  
  https://hex-rays.com/blog/ida-pro-meet-cyberchef
7. 🔗 r/york Driving lessons rss
  
  I’m looking for driving lessons. I had about 6-12 months experience 2 years ago but I haven’t driven since. I was wondering if anyone knew any lessons I could take before my test that is somewhat cheap and good
  
  submitted by /u/sheetpost00
  [link] [comments]
8. 🔗 r/Yorkshire Hebden Bridge illustration rss
  
  | Hey folks! Thought you'd enjoy this new little illustration I just finished of Hebden Bridge. This took around 18 hours based on my own photos :) submitted by /u/zacrosso_art
  [link] [comments]
  ---|---
9. 🔗 r/wiesbaden In Germany soon rss
  
  Hi. I would like to ask if what are the things that I need to prepare? I will arrive in Hessen Germany this coming June and I am from the Philippines. Any answers/ suggestions will be a great help for me. Thank you.
  
  submitted by /u/No_Manner_2072
  [link] [comments]
10. 🔗 r/york Anyone looking for D&D groups or events in York? rss
  
  I've been working with some local communities recently in york and I'm trying to improve outreach involving a lot of upcoming Dungeons and Dragons related things
  
  submitted by /u/JunkDrawerTheatreCo
  [link] [comments]
11. 🔗 crosspoint-reader/crosspoint-reader SD Card Fonts (m1-b4) release
  
  Pre-built .cpfont font files for CrossPoint Reader.
  
  Download individual files or use Settings > System > Download Fonts on the device.
  
  See SD Card Fonts documentation for details.
12. 🔗 r/wiesbaden Outdoor Location gesucht rss
  
  Gude!
  
  Für eine Abschlussfeier suche ich nach einer Outdoor Location bestenfalls mit einem Zelt für maximal 50 Personen in Wiesbaden oder Umgebung.
  Bayleaf Events in Frankfurt Höchst ist eine sehr schöne Location mit Zelt und Deko und mein absoluter Favorit allerdings ist es nicht am 23. und 24. Mai verfügbar.
  Falls ihr sonst noch Ideen habt, würde ich mich auf jeden Fall freuen!
  
  submitted by /u/Levi_Ackermann_1304
  [link] [comments]
13. 🔗 r/reverseengineering Ghidra-SNES: A Ghidra extension for reverse engineering SNES ROMs (first public release, feedback welcome!) rss
  
  submitted by /u/JoshLeaves
  [link] [comments]
14. 🔗 tomasz-tomczyk/crit v0.11.0 release
  What's Changed
  
  Big milestone! Crit crossed more than 500 commits and 250 stars. You can now install it directly from homebrew and we released a Windows version!
  
  Thank you to everyone who contributed to get us here! I'd appreciate if you would share it with your colleagues or on Twitter! It helps a lot!
  
  crit is now in homebrew-core — no tap needed. If you installed from the tap, upgrade once with:
```
brew uninstall crit && brew untap tomasz-tomczyk/scratch && brew update && brew install crit
```
  Future updates will arrive via brew upgrade like any other formula.
  
  Windows + WSL support
  
  feat: add Windows + WSL support replaces Unix-only syscalls with cross- platform abstractions, adds rundll32 browser launch on native Windows, and keeps the existing WSL fallback chain. crit now works end-to-end on Windows natively.
  - feat: add Windows + WSL support by @tomasz-tomczyk in #459
  General
  - feat: add --file flag and better errors to crit comment --json by @tomasz-tomczyk in #480
  - fix: deny rather than silently auto-approve on daemon shutdown by @tomasz-tomczyk in #483 - Thank you @TalAmuyal for raising!
  - fix: remove daemon 1h idle timeout by @tomasz-tomczyk in #477 - Thank you @TalAmuyal for reporting!
  - fix: audit fixes — path safety, shared reads, dir pruning by @tomasz-tomczyk in #485
  - fix: chain reloadForScope when scope/commit changes mid-flight by @tomasz-tomczyk in #482
  - fix: scope unified diff comment highlight to commented side by @tomasz-tomczyk in #479
  - fix: header context chip colors and hidden unresolved count by @tomasz-tomczyk in #486
  - fix: preserve CLI argument order for files by @tomasz-tomczyk in #474
  - docs: switch primary brew install to homebrew-core by @tomasz-tomczyk in #481 - thanks @omervk for contributing to homebrew on our behalf!
  - docs: cleanup stale spec by @tomasz-tomczyk
  - refactor: drop auto-detection of stacked PRs / local stacks by @tomasz-tomczyk in #478
  Full Changelog : v0.10.5...v0.11.0
15. 🔗 r/Leeds Roundhay park warning rss
  
  Hi there!
  
  Just wanted to write that whilst walking my dog- I had a strange encounter with an older man.
  
  I was up the back of roundhay park lake (taking the pathway through the woods) at 11:30 this morning/ afternoon- he was in a very isolated part of the walking trail, and after staring at me walking past, I said ‘good afternoon’ and he replied by telling me he thought I was ‘very beautiful’ - I got a bad gut feeling and decided to leave straight away, he was saying more stuff as I was leaving but I didn’t hear him as he was very quiet.
  
  I just wanted to say to be cautious if you are in roundhay park and to stick to the main path by the lake if possible. Thanks!
  
  submitted by /u/SadEntertainment5259
  [link] [comments]
16. 🔗 r/reverseengineering Reverse-engineered DaVinci Resolve's activation check with Claude — Frida runtime tracing + radare2 rss
  
  submitted by /u/Hour-Dirt-4010
  [link] [comments]
17. 🔗 r/Yorkshire Richmond Castle in Yorkshire standing tall after nearly 1000 years. rss
  
  | submitted by /u/Still_Function_5428
  [link] [comments]
  ---|---
18. 🔗 r/york Policemen with assault rifles running around rss
  
  Does anyone know anything about the policemen running around with automatic weapons near Hungate apartments? Quite anxiety inducing to see that
  
  submitted by /u/Reduxtion
  [link] [comments]
19. 🔗 r/york Love the cobbled or setts, and the whole atmosphere of Shambles is just magical, really brings out the history and charm of the place! 🌺 rss
  
  | submitted by /u/Coffee000Oopss
  [link] [comments]
  ---|---
20. 🔗 tomasz-tomczyk/crit Spotify popup-relay preview (bb4d9fb) release
  
  WIP build of crit with share_flow: "popup" config support for SSO- protected crit-web instances.
  
  Setup instructions: SPOTIFY-PREVIEW.md
  
  Pair with crit-web: docker image ghcr.io/tomasz-tomczyk/crit-web:spotify- preview (release, built from branch share-receiver- elixir).
  
  Built from commit bb4d9fb of branch share- receiver.
  
  Feedback / issues: tomasz-tomczyk/crit-web#50
21. 🔗 r/Yorkshire There's no better place to drink a tea and reboot yourself than the Dales rss
  
  | Image by Dan Silcock submitted by /u/Seabeachlover10
  [link] [comments]
  ---|---
22. 🔗 backnotprop/plannotator v0.19.11 release
  Follow @plannotator on X for updates
  
  Missed recent releases? Release | Highlights
  ---|---
  v0.19.10 | Revert unreviewed bypass-clear-reminder permission mode
  v0.19.9 | OpenCode user-managed workflow, Pi model switch fix, Codex skill install, shimmer removal
  v0.19.8 | 49 themes with syntax highlighting, keyboard shortcut registry, smart code-file path validation, remote URL notifications
  v0.19.7 | Codex Stop-hook plan review, Codex skills, sidebar auto-close, file tree context menu
  v0.19.6 | Non-blocking Pi browser sessions, agent picker dropdown for OpenCode, annotate-last file resolution fix
  v0.19.5 | All-files diff view, clickable code file paths, server-side hide whitespace, non-ASCII path support
  v0.19.4 | All-files diff type, code file viewer, hide whitespace, quick-settings popover
  v0.19.3 | Configurable feedback messages, hide merged PRs in stacked PR selector
  v0.19.2 | Stacked PR review, source line numbers in feedback, diff type dialog re-show, ghost dot removal, docs cleanup
  v0.19.1 | Hook-native annotation, custom base branch, OpenCode workflow modes, quieter plan diffs, anchor navigation
  v0.19.0 | Code Tour agent, GitHub-flavored Markdown, copy table as Markdown/CSV, flexible Pi planning mode, session-log ancestor-PID walk
  
  What's New in v0.19.11
  
  v0.19.11 adds Jujutsu (jj) as a first-class VCS backend for code review and refines the review UI with slimmer separators, a cleaner header layout, and proper multi-line gutter selection. One of the two PRs in this release is from a first-time contributor.
  
  Jujutsu (jj) Code Review
  
  Plannotator's code review now works natively with Jujutsu, the Git-compatible VCS. When you run /plannotator-review in a jj workspace, the VCS is auto-detected and four jj-specific diff modes appear in the diff type picker:
  - Current (jj-current) shows the working-copy changes
  - Last (jj-last) shows the previous change
  - Line (jj-line) shows the full line of work from the current change back to the trunk bookmark
  - All (jj-all) shows all local changes not yet on the remote
  Compare-target selection adapts to jj's model. Instead of branch-based base selection, the picker offers remote bookmarks. The feedback exported to your agent includes jj-appropriate local diff instructions so it can reproduce the same view.
  
  Under the hood, this required a significant refactor. Diff collection, compare-target semantics, and file-content retrieval were pulled into a provider-based VCS abstraction in packages/shared/vcs-core.ts. Git, jj, and P4 each implement the same provider interface. The review server and UI consume provider-supplied metadata instead of branching on VCS-specific flags. This abstraction makes adding future VCS backends straightforward.
  
  For colocated repos (both .git and .jj present), jj takes priority. Pass --git to /plannotator-review to override.
  - Authored by @graemefolk in #675
  Review UI Refinements
  
  Several quality-of-life improvements to the code review interface:
  
  Slimmer hunk separators. The expand/collapse bars between diff hunks are now 24px (down from 32px), with semi-transparent theme-integrated backgrounds. Text and buttons fade with lower opacity for a subtler look that puts the focus on the code.
  
  Cleaner header layout. Sidebar toggles (Annotations, AI, Agents) moved to the far right of the header bar, with the options menu to their left. A visual divider separates the file tree button from the repo label.
  
  Collapse viewed files. Marking a file as viewed in all-files review mode now automatically collapses it, keeping only unreviewed files expanded.
  
  Multi-line gutter selection fix. Click-and-drag on the gutter annotation button now correctly selects a range of lines. The previous implementation used a deprecated Pierre API that never entered the selection mode, so dragging always reported a single line.
  - #683, closing #679 and #682
  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".
  
  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(review): add jj review workflows by @graemefolk in #675
  - Review UI refinements: separator styling and header layout by @backnotprop in #683
  New Contributors
  - @graemefolk made their first contribution in #675
  Community
  
  @graemefolk built full jj support from scratch, implementing the VCS provider, diff modes, compare-target picker, and feedback export in a single well-structured PR. The VCS abstraction layer they introduced benefits the entire codebase.
  
  @JohannesKlauss reported the multi-line gutter selection bug in #679, with a clear screen recording that made the root cause obvious.
  
  @festive-onion requested the collapse-on- viewed behavior in #682, a small change that meaningfully improves the review workflow for large diffs.
  
  Full Changelog : v0.19.10...v0.19.11
23. 🔗 r/reverseengineering SASS King Part 2: reverse-engineering ptxas heuristic decisions and what the compiled binary actually reveals rss
  
  submitted by /u/CurrentLawfulness358
  [link] [comments]
24. 🔗 r/reverseengineering I just released a C++ rewrite of **Minecraft rd-20090515** (May 15, 2009 — one of the earliest pre-Classic versions).If you find it interesting, a ⭐ on GitHub would mean a lot and help the project grow! rss
  
  submitted by /u/03D_DEV
  [link] [comments]
25. 🔗 r/LocalLLaMA Multi-Token Prediction (MTP) for LLaMA.cpp - Gemma 4 speedup by 40% rss
  
  | Implemented Multi-Token Prediction for LLaMA.cpp. Quantized Gemma 4 assistant models into GGUF format. Ran tests on a MacBook Pro M5Max. Gemma 26B with MTP drafts tokens 40% faster. Prompt: Write a Python program to find the nth Fibonacci number using recursion Outputs:
  LLaMA.cpp: 97 tokens/s
  LLaMA.cpp + MTP: 138 tokens/s Gemma4-assistant GGUF Quantized models: https://huggingface.co/collections/AtomicChat/gemma-4-assistant-gguf Local AI models app: http://atomic.chat Patched llama.cpp: https://github.com/AtomicBot-ai/atomic-llama-cpp-turboquant submitted by /u/gladkos
  [link] [comments]
  ---|---
26. 🔗 jank blog jank now has its own custom IR rss
  
  Good news, everyone! jank has a new custom intermediate representation (IR) and we're using it to optimize jank to compete with the JVM. We'll dive into more of that today, but first I want to say thank you to my Github sponsors and to Clojurists Together for sponsoring me this whole year. You all are helping a great deal. I am still searching for a way to continue working on jank full-time with an income which will cover rent and groceries, so if you've not yet chipped in a sponsorship, now's a great time!
27. 🔗 matklad Steering Zig Fmt rss
  Steering Zig Fmt
  
  May 8, 2026
  
  Two tips on using zig fmt effectively. Read this if you are writing Zig, or if you are implementing a code formatter.
  
  For me, zig fmt is better than any other formatter I used: rustfmt, the one in IntelliJ, deno fmt. zig fmt is steerable. For every syntactic construct, it has several variations for how it might be laid out. The variation used is selected by looking at what’s currently in a file.
  
  Easier to show a pair of examples:
```
    f(1, 2,
      3);

// -> zig fmt ->

    f(1, 2, 3);


    f(1, 2,
      3,);

// -> zig fmt ->

    f(
        1,
        2,
        3,
    );
```
  Depending on the trailing comma, function call is formatted on a single line, or with one argument per line.
  
  The way this plays out in practice is that you decide how you want to lay out the code, add a couple of ,, hit the reformat shortcut (, p is mine), and zig fmt does the rest. For me, this works better than the alternative of the formatter guessing. 90% of great formatting are blank lines between logical blocks and tasteful choice of intermediate variables, so you might as well lean into key choices, rather than eliminate them.
  
  I know of one non-trivial formatting customization point: columnar layout for arrays:
```
    .{ 1, 2, 3,
       4, 5, 6, 7, 8, 9, 10, 11,  };
```
  One would think that trailing comma would lead to a number-per-line layout, but, for arrays, zig fmt also takes note of the first line break. In this case, the line break comes after the first three items, so we get three numbers per line, aligned:
```
    .{
        1,  2,  3,
        4,  5,  6,
        7,  8,  9,
        10, 11,
    };
```
  How cool is that!
  
  Furthermore, with judicious use of ++, you can vary the number of items per line. When I need to pass --key value pairs to subprocess, I often go for formatting like this:
```
try run(&(.{ "aws", "s3", "sync", path, url } ++ .{
    "--include",            "*.html",
    "--include",            "*.xml",
    "--metadata-directive", "REPLACE",
    "--cache-control",      "max-age=0",
}));
```
28. 🔗 Armin Ronacher Pushing Local Models With Focus And Polish rss
  I really, really want local models to work.
  
  I want them to work in the very practical sense that I can open my coding agent, pick a local model, and get something that feels competitive enough that I do not immediately switch back to a hosted API after five minutes. There are a lot of reasons why I want this, but the biggest quite frankly is that we're so early with this stuff, and the thought of locking all the experimentation away from the average developer really upsets me.
  
  Frustratingly, right now that is still much harder than it should be but for reasons that have little to do with the complexity of the task or the quality of the models.
  
  We have an enormous amount of activity around local inference, which is great. We have good projects, fast kernels, and people are doing great quantization work. A lot of very smart people are making all of this better, and yet the experience for someone trying to make this work with a coding agent is worse than it has any right to be.
  
  Putting an API key into Pi and using a hosted model is a very boring operation. You select the provider, paste the key and then you are done thinking about how to get tokens. Doing the same thing locally, even when you have a high-end Mac with a lot of memory, is a completely different experience. You choose an inference engine, then a model, then a quantization, then a template, then a context size, then you've got to throw a bunch of JSON configs into different parts of the stack and then you discover that one of those choices quietly made the model worse or that something just does not work at all.
  
  That is the gap I am interested in.
  
  Runnable Is Not Finished
  
  A lot of local model work optimizes for making models runnable. That is necessary, but it is not the same thing as making them feel finished. I give you a very basic example here to illustrate this gap: tool parameter streaming.
  
  For whatever reason, most of the stuff you run locally does not support tool parameter streaming. I cannot quite explain it, but the consequences of that are actually surprisingly significant. If you are not familiar with how these APIs work, the simplest way to think about them is that they are emitting tokens as they become available. For text that is trivial, but for tool calls that is often not done, despite the completions API supporting this. As a result you only see what edits are being done on a file once the model has finished streaming the entire tool call.
  
  This is bad for a lot of reasons:
  - A dead connection is a weird connection: local models are slow, so when you don't get any tokens for 5 minutes then you can't tell if the connection died or just nothing came. This means you need to increase the inactivity timeouts to the point where they are pointless.
  - You won 't see what will happen: if you are somewhat hands-on, not seeing what bash invocation the system is concocting slowly in the background means potentially wasted tokens, and also means that you won't be able to interrupt it until way too late.
  - It 's just not SOTA. We can do better, and we should aim for having the best possible experience. Tool parameter streaming is as important as token streaming in other places.
  Having a model spit out tokens doesn't take long, but making the experience great end to end does take a lot more energy.
  
  Fragmentation
  
  The local stack is fragmented across many engines and layers. There is llama.cpp, Ollama, LM Studio, MLX, Transformers, vLLM, and many other pieces depending on hardware and taste. All of these are amazing projects! The problem is not that they exist or that there are that many of them (even though, quite frankly, I'm getting big old Python packaging vibes), the problem is that for a given model, the actual behavior you get depends on a long chain of small decisions that most users just don't have the energy for.
  
  Did the chat template render exactly right? Are the reasoning tokens handled in the intended way? Is the tool-call format translated correctly? Is the context window real? Are the KV caches actually working for a coding agent? Did I pick the right quantized model from Hugging Face? Are you accidentally leaving a lot of performance on the table because the model is just mismatched for your hardware? Does streaming usage work across all channels? Does the model need its previous reasoning content preserved in assistant messages? Is the coding agent set up correctly for it?
  
  You also need to install many different things in addition to just your coding agent.
  
  All of these things matter. They matter a lot.
  
  The result is that people try a local model and get a result that is neither a fair evaluation of the model nor a polished product experience and this results in both people dismissing local models and energy being distributed across way too many separate efforts instead of getting one effort going great end to end.
  
  This is a terrible way to build confidence.
  
  Too Little Critical Mass
  
  In line with our general "slow the fuck down" mantra, I want to reiterate once more how fast this industry is moving.
  
  Every week there is a new model and a new vibeslopped thing. The attention immediately moves to making the next thing run instead of making one thing run really, really well in one harness. I get the excitement and dopamine hit, but it also means that too little critical mass accumulates behind any one model, hardware, inference engine, harness combo to find out how good it can really become when the entire stack is built around it.
  
  Hosted model providers do not ship a bag of weights and ask you to figure out the rest, and we need to approach that line of thinking for local models too. I want someone to pick one model, pairs it up with one serving path, directly within a coding agent. Initially just for one hardware configuration, then for more. Pick a winner hard. If a tool call breaks, that is a product bug and then it's fixed no matter where in the stack it failed. If the model's reasoning stream is malformed, that is a product bug. If latency is much worse than it should be, that is a product bug. We need to start applying that mentality to local models too.
  
  And not for every model! That is the point. Let's pick one winner and polish the hell out of it. Learn what it takes to make that one configuration good, then take those learnings to the next config.
  
  The DS4 Bet
  
  This is why I am excited about ds4.c. It's Salvatore Sanfilippo's deliberately narrow inference engine for DeepSeek V4 Flash on Macs with 128GB+ of RAM only. It is not a generic GGUF runner and it is not trying to be a framework. It is a model-specific native engine with a Metal path, model-specific loading, prompt rendering, KV handling, server API glue, and tests.
  
  DeepSeek V4 Flash is a good candidate for this kind of experiment because it has a combination of properties that are unusual for local use. It is large enough to feel meaningfully different from many smaller dense models, but sparse enough that the active parameter count makes it plausible to run. It has a very large context window. Since ds4.c targets Macs and Metal only, it can move KV caches into SSDs which greatly helps the kind of workloads we expect from coding agents.
  
  To run ds4.c you don't need MLX, Ollama or anything else. It's the whole package.
  
  Embedding It In Pi
  
  Which made me build pi-ds4 which is a Pi extension to directly embed the whole thing into Pi itself. Taking what ds4 is and dogfooding the hell out of it with a coding agent and zero configuration. To answer the question how good can the local model experience become if Pi treats this as a first-class provider rather than as a pile of manual configuration?
  
  The extension registers ds4/deepseek-v4-flash, compiles and starts ds4-server on demand, downloads and builds the runtime if needed, chooses the quantization based on the machine, keeps a lease while Pi is using it, exposes logs, and shuts the server down again through a watchdog when no clients are left. It doesn't even give you knobs right now, because I want to figure out how to set the knobs automatically.
  
  This is not about hiding the fact that local inference is complicated. It is about putting the complexity in one place where it can be improved, because there is a lot that we need to improve along the stack to make it work better.
  
  I think we can do better with caching and there is probably some performance that can be gained if we all put our heads together.
  
  Focusing and Learning
  
  The experiment I want to run is not "can a local model run?" because we already know that it can. I want to know if, for people with beefed-out Macs for a start, we can get as close as possible to the ergonomics of a hosted provider with decent tool-calling performance: how to get caches to work well, how to improve the way we expose tools in harnesses for these models, and then scale it gradually to more hardware configs and later models.
  
  I also want everybody to have access to this. Engineers need hammers and a hammer that's locked behind a subscription in a data center in another country does not qualify. I know that the price tag on a Mac that can run this is itself astronomical, but I think it's more likely that this will go down. Even worse, Apple right now due to the RAM shortage does not even sell the Mac Studio with that much RAM. So yes, it's a selected group of people where ds4.c will start out.
  
  But despite all of that, what matters is that a critical mass of pepole start to focus their efforts on a thing, tinker with it, improve it, not locked away, out in the open, and most importantly not limited by what the hyperscalers make available.
  
  But if you have the right hardware and you care about local agents, I would love for you to try it within pi:
```
pi install https://github.com/mitsuhiko/pi-ds4
```
  My hope is that this becomes a useful forcing function to really polish one coding agent experience. But really, the focal point should be ds4.c itself.
May 07, 2026
1. 🔗 IDA Plugin Updates IDA Plugin Updates on 2026-05-07 rss
  IDA Plugin Updates on 2026-05-07
  
  Activity:
  - augur
    
    b1402e4f: chore: use workspace lints and add some restriction lints
  - capa
    
    c57422f9: Sync capa rules submodule
  - haruspex
    
    a6242685: fix: typo
    
    449424d9: fix: lints
    
    e19bf4d4: chore: use workspace lints and add some restriction lints
  - idafridascript
    
    ef2ebf74: fix(flutter_ssl_bypass): update comments and delay hook initialization
  - idawilli
    
    7f2ed4f0: idawilli: add idawilli.syntax for syntax highlighting with rich
    
    d6552f8f: migrate to pyproject and lint/format
  - pdb
    
    53b060e8: 改为通过LATEST_IDADIR环境变量来控制输出路径
  - rhabdomancer
    
    9554e1ee: fix: lints
    
    693d0460: chore: use workspace lints and add some restriction lints
2. 🔗 anthropics/claude-code v2.1.133 release
  What's changed
  - Added worktree.baseRef setting (fresh | head) to choose whether --worktree, EnterWorktree, and agent-isolation worktrees branch from origin/<default> or local HEAD. Note: the default fresh changes EnterWorktree's base back to origin/<default> (it has been local HEAD since 2.1.128) — set worktree.baseRef: "head" to keep unpushed commits in new worktrees
  - Added sandbox.bwrapPath and sandbox.socatPath managed settings (Linux/WSL) to specify custom bubblewrap and socat binary locations
  - Added parentSettingsBehavior admin-tier key ('first-wins' | 'merge') to let admins opt SDK managedSettings (parent tier) into the policy merge
  - Hooks now receive the active effort level via the effort.level JSON input field and the $CLAUDE_EFFORT environment variable, and Bash tool commands can read $CLAUDE_EFFORT
  - Improved focus mode behavior
  - Improved memory usage by releasing warm-spare background workers under memory pressure
  - Fixed parallel sessions all dead-ending at 401 after a refresh-token race wiped shared credentials
  - Fixed Edit/Write allow rules scoped to a drive root (C:\) or POSIX / matching incorrectly and always prompting
  - Fixed an unhandled rejection (ECOMPROMISED) when a history or session-log file lock is compromised by clock skew or slow disk
  - Fixed pressing Esc during conversation compaction showing a spurious "Error compacting conversation" notification
  - Fixed HTTP(S)_PROXY / NO_PROXY / mTLS not being respected for the full MCP OAuth flow including discovery, dynamic client registration, token exchange, and token refresh
  - Fixed Read/Write/Edit being denied on mapped network drives passed via --add-dir / SDK additionalDirectories
  - Fixed Remote Control stop/interrupt from claude.ai not fully canceling the CLI session the same way local Esc does, causing queued messages to never advance after interrupting a stuck tool or prompt
  - Fixed /effort in one session unexpectedly changing the effort level of other concurrent sessions, and a related issue where an IDE effort change could be silently dropped
  - Fixed subagents not discovering project, user, or plugin skills via the Skill tool
  - claude --help now lists --remote-control alongside --remote-control-session-name-prefix
  - [VSCode] Fixed claudeCode.claudeProcessWrapper failing with "Unsupported platform" when the extension build doesn't bundle a Claude binary
3. 🔗 r/LocalLLaMA Collected the infinity stones rss
  
  | 2.3 TB of ram in here. 400+ vCores. All thats left is plugging it to the blackwell with the driver to do RDMA, and it’s over. Using Blackwells for prefill, RDMA to the studio mesh for decode. I think this would be the first heterogeneous cluster. I do, however, need help with the Tinygrad Driver to make this work. If anyone with any knowledge on these domains would like to collaborate, let me know via PM. We are very close here. submitted by /u/Street-Buyer-2428
  [link] [comments]
  ---|---
4. 🔗 r/Leeds What should I do about the stressed koi at a restaurant? rss
  
  I'm at a restaurant in Leeds, I'm sure you could figure out which one, which has a koi pond in the middle of the restaurant. It's covered by a large bridge and a thick mesh, and the fish are showing classic signs of stress (not moving, sitting near the bottom, jumping out of the water, and gasping at the surface). Is there a way for me to advocate for better health for them or is it a lost cause as they are the restaurant's property and technically taken care of? Sorry if this is silly it just makes me sad to see them in a bad state.
  
  submitted by /u/moonstone7152
  [link] [comments]
5. 🔗 r/york Goose on Dame Judi Dench Walk rss
  
  | Honk submitted by /u/NervousEnergy
  [link] [comments]
  ---|---
6. 🔗 sacha chua :: living an awesome life Emacs Chat 22: Shae Erisson rss
  [2026-05-08 Fri]: Transcript, yay!
  
  I chatted with Shae Erisson about Emacs, keyboards, Org Mode, and life.
  
  View it via the Internet Archive, watch/comment on YouTube, read the transcript online, download the video / MP3 / transcript, or e-mail me your thoughts!
  - Shae Erisson: Haskell, Python, Swedish, knitting, mountain unicycling, contact juggling
  - Shae Erisson's blog - 1. DO SOMETHING 2. BRAG ABOUT IT
  - Shae Erisson (@shapr@recurse.social) - recurse.social
  - Shae Erisson's blog - Programmers want flow. when programming, light turns RED
  - shapr/markovkeyboard: keyboard layout that changes by markov frequency · GitHub
  Chapters
  
  0:07 Intro
  
  1:01 1999, IRC, community building in Haskell
  
  2:02 Emacs as a light-weight build-your-own-editor toolkit
  
  2:55 LSP, treesitter, Magit, jujutsu, C++, Python, Haskell, rust
  
  3:38 how does a new person experience Emacs? Emacs is always fun.
  
  4:07 Markov keyboard project, moving to Finland, right-handed Dvorak, split keyboard; Jeff Raskin; I am not a koala
  
  6:45 Purpose-specific function keys
  
  7:34 Trackballs, scroll
  
  8:17 1" trackpad rings
  
  8:58 Pair programming: ttyshare, shwim
  
  13:20 Recurse Center, "What is that keyboard? What is that editor?!", Emacs bankruptcy and starter kits
  
  16:09 hippie-expand
  
  17:18 yasnippet
  
  19:01 Function keys
  
  20:05 Org Mode
  
  21:17 Show Org agenda when idle
  
  22:03 Programmers want flow. When programming, light turns red
  
  24:27 ef-themes and modus-themes, season
  
  25:58 htmlize (does this still work on Wayland?)
  
  26:40 lsp-ui-imenu, jumping through rust code
  
  28:30 laptop with 126GB of RAM
  
  29:48 LSP coolness, Haskell, treesitter
  
  32:02 Combobulate
  
  32:52 What else are you using your 126 gigabytes of RAM for?
  
  33:27 TalonVoice
  
  34:46 NixOS, following Steve Purcell about 5 years behind
  
  35:06 envrc
  
  35:54 time-tracking
  
  37:05 taxes with Org Mode, remote lookup
  
  41:02 finding notes with C-s
  
  42:38 Org Mode, managing inbox
  
  46:30 Timestamps
  
  49:14 Org timers
  
  53:56 Org Mode snippets
  
  57:16 Compilation finish function: handle success
  Transcript
  
  Transcript
  
  0:00 Intro
  Sacha: Okay, so I'm going to actually remember to hit go live. I've got a 10 second delay, so if we need to panic, we can panic. Okay, so let's see. I think we are live. Hi, everyone. This is Emacs Chat number 22 after a long hiatus. And today, I'm here with Shae Erisson, who is also like an Emacs friend from a long time back. So this is it. As you were just saying, this is the first time we're actually talking live. And I'm looking forward to hearing about your configuration, how you use Emacs, Shae. But before we dive into that, can you give us a little bit of context? Who you are, what sorts of things you do, and how you use Emacs for that?
  0:57 1999, IRC, community building in Haskell
  Shae: I would say that... I guess I started using Emacs in 1999 when I moved to Finland. And I remember about the same time I was on IRC and I was really frustrated. I remember I got on the Perl IRC channel and I was like, hey, I want an editor that has syntax highlighting. I want to see colors to these words when I'm typing them. And they were like, noob, and they kick-banned me. And I was like, well, maybe I don't want to learn Perl, which I never did. And I guess that was an early introduction into I wanted to be part of communities where people were sharing positive things and building up each other. Actually, I ended up starting the Haskell IRC channel a couple of years later, and that became a very big thing. I would say that I'm mostly known for my work in community building in the Haskell programming language community, because I did that for, I don't know, 15 or 20 years. But I really like Emacs.
  1:58 Emacs as a light-weight build-your-own-editor toolkit
  Shae: So like last week at the same time I had the standing chat with a friend of mine who is also a programmer and he said oh so you're going to do this thing in a week do you want to give me like a preview of the talk and I was like yeah I guess so and some of the things that were really interesting was he was like I've never really tried Emacs I don't know much about it I kind of have this impression that it is a very lightweight build your own editor toolkit and I I was kind of taken aback because, you know, I guess I still have this long ago and far away. I don't know if you remember 8 Megs and Constantly Swapping is what people used to call Emacs and things like that. And I was, it was just kind of, I realized I'm still in my little echo chamber. And this is why I like to talk to other people all the time is because I want to have some exposure to what other people are doing.
  2:51 LSP, treesitter, Magit, jujutsu, C++, Python, Haskell, rust
  Shae: I guess things about Emacs that really changed stuff for me is language server protocol, TreeSitter. Those, I think, are two very powerful tools that are much more generic than, I mean, Magit, of course, is like magic. Although I've mostly switched to jujitsu lately instead for the last year. Let's see, I had, I guess, let's see, I did C++, I did Python, I did a whole lot of Python. And then I had Haskell jobs for five or six years. And then I switched to Rust about a year and a half ago. I now have a Rust job. And one of the things that Prot had asked, I think, or you had asked, and I forget exactly how this went.
  3:35 how does a new person experience Emacs? Emacs is always fun.
  Shae: It was great fun watching your livestream. And it was, how does a new person kind of get comfortable with using Emacs for a particular purpose. And I look for things, in fact, like how do I use Emacs for Rust, Rust development? And I found a couple of good guides on, and I was able to follow most of them, although my Yesnitit stuff is broken and I don't exactly know why tab doesn't work, right? But, you know, like there's always, Emacs is always fun, right? There's so many cool things you could do with it.
  4:03 Markov keyboard project, moving to Finland, right-handed Dvorak, split keyboard; Jeff Raskin; I am not a koala
  Shae: I noticed, I actually hadn't seen your preview page and I noticed that you found my Markov keyboard.
  Sacha: When you say Emacs is fun, I'm reminded of all of your fun, crazy keyboard experiments. It's like, what? I have a feeling you like to tinker with things.
  Shae: Yeah, so I think actually the influences as to how I got to where I am are pretty interesting. So the person that I ended up moving to Finland to for dating her, we started a company, we did projects, and I was the programmer. We had this pretty big project. I guess it was like 350,000 euros. And I mean, that was going to be over four years and we had to kind of complete the whole thing, and I was the programmer and we'd had the lowest bid... I had an IBM model M, you know, the super clicky with like all the... And about three years into it, my arm started really hurting a lot. But I was the only programmer. And nobody else knew all the code. And we had to ship it, because that's how we got paid. And so I ended up pushing through. And at the end of it, my arm just didn't work anymore. So for about a year and three months, what I did was I actually taught myself to type right hand. ...Dvorak, because I was already using two-hand Dvorak, and so I kept programming, but I just... One of the things was... like, I like programming, I like using computers, I don't want to wear out my arms again, I don't want to blow them out, so I ended up switching to split keyboards, and I will show you. This is very much the kind of thing that I like to use, and that is like this.
  Shae: This is an Ergodox Infinity, but there's a lot of other keyboard flavors like this. And one of the things that I particularly like about this... So around the same time I met Jeff Raskin, who wrote the Inhumane Interface. And so for this particular thing, this is like Control and Alt and Hyper and Super and Shift. And this means that under one thumb, I have a lot more modifier keys than you get off of a standard. And it also means... A lot of my problems started with Emacs pinky, the dreaded, the infamous... I think that one of my... I made a keyboard layout called "I am not koala." You may not know this, but koalas have two thumbs. They have one on each side. And that's cool, but I don't have two thumbs, and I realized that when I was trying to grab something, I didn't put my pinky on it. That would be silly, right? I want to put my thumb around it. And so I decided I would move all of my chording keys under my thumbs. And that's kind of how I...
  6:43 Purpose-specific function keys
  Shae: And another thing I did was when I was really only able to use one hand, was I made my function keys mostly purpose-specific. And that was from Jeff Raskin's writings in The Humane Interface. So I guess I'm a programmer who really likes writing code, doesn't want to wear out my arms, and likes to do fun keyboard things, yeah.
  Sacha: Definitely. You're in it for the long term. You don't want to use up all of your arm capacity now and not be able to keep programming in the future. And now there's hardware to make that easier. So I'm glad. Split keyboards with extra thumb keys seem to be very popular in the Emacs community. I'm now tempted to find space in my desk in order to make that happen.
  7:30 Trackballs, scroll
  Shae: Another thing I ended up switching to was I started using trackballs. Oh yeah, yeah. I tend to go completely overboard when trying out new things, so I bought 20 different models of trackballs and ended up settling on this one. The nice thing about this one is that this is how you scroll, and it has four buttons.
  Sacha: That is really cool. I like using ThinkPads, so I've been just living off the tiny little mouse in the middle of the keyboard. But back in the day, I also used a trackball. If I can get to the point where I want to take my hands off the keyboard again in order to do mouse things, that would probably be the direction I would go.
  8:14 1" trackpad rings
  Shae: I had an experiment in that area, which is where I purchased a one-inch touchpad, and I strapped it to my finger. And it was a PS2, and it had a USB converter plugged into it. And the idea was I could keep typing, and then I could move the mouse around without taking my hands off the keyboard. And now they actually have touchpad rings. They came out six months or a year ago. It's relatively recent. But the idea is no change in context.
  Sacha: I've only seen the scroll rings, but now there's a touchpad version. That is interesting.
  Shae: Yeah, I think that's pretty cool stuff. Hardware is actually improving things.
  8:54 Pair programming: ttyshare, shwim
  Shae: Oh, another thing, one of the things you talked about with Prot was how do you learn other people's stuff? And one of the things that I use for pairing, so I have one coworker, and it's a strange, interesting job. I like it a lot. And I met this coworker at a previous job, and one of the things, let's see if I can find it. So we used to, at the previous job, we used this thing called ttyshare. Have you heard of it? ttyshare. It's great. You can run it in a terminal and then you can effectively share your terminal with someone else. And so you have multiplayer terminals and that's neat. It was kind of a pain to set up. You had to make sure that you weren't NATed, you know, like you had to have effectively... someone had to have a public IP. You had to do a couple of other things. And as part of my job, I'm now, I guess, part maintainer for Magic Wormhole, the software.
  Shae: And so one of the things that my coworker wrote was this nifty thing called ShWiM. And it's basically "shell with me." And it's a wrapper around TTY share so that with one single command, you can share a terminal. And the way that we use this is... We both run Emacs as a server, and then we use emacsclient in the terminal to connect.
  Shae: I don't know if you've ever done this, but I can have a terminal right next to this, and if I run emacsclient in a window, then I'm sharing the same thing. This is a graphical chat with Sacha, in the terminal or in the UI, and both of them are updated.
  Sacha: That's fantastic. I remember people were using tmate for something similar before where you could share that. But yeah, it's just making it seamless, making it frictionless. And on the other side, I have also just been using wormhole to send large files back and forth between Karthik and John Wiegley because we have this other Emacs chat thing where we're going to post it eventually, once I finish figuring out how to redact all the personal information and Org files. But yeah, it's great for being able to send things without having to worry about, oh, you know, what's my public IP? Can I tunnel all the different things to get past whatever firewalls there are? So if this also works for terminal things plus Emacs client, that sounds really, really exciting.
  Shae: We've tried some other experiments. One of the things we tried to do was, and the only downside is like, what if my terminal has a different size, then you have to kind of shrink and match. And so we tried to honestly directly bridge to Emacs clients. And because I don't know if you're aware that there's effectively a local socket for the Emacs client that you can have multiple things connect to. But it turns out there's some sort of like system so I couldn't like reach across the network and directly use my co-workers Emacs session and he couldn't use mine. Weird things happened when we tried to do this cross host. As far as I can tell the Emacs client only works in the same host.
  Sacha: That's interesting. Lately, I've also been experimenting with CRDT, which has that Emacs-less plant as well. So that's been nice. But yeah, of course, a lot of people will be kind of stuck with the first challenge of finding someone that they can pair in Emacs with.
  Shae: I understand. And I think I'm honestly very happy that my one single coworker at this job is also a big Emacs user. And so we exchanged cool ideas and worked on stuff. And I'm very happy about that.
  Sacha: Were they already an Emacs person before they joined? Or did you pick the coworker because they were an Emacs person?
  Shae: They picked me. They were pretty much the person who started this thing. And they picked me because they'd worked with me at the previous job. Although I did have an experience like that. I had this massive Emacs config file, like 20,000 lines, and half of it was comments because it had accrued over 20 years.
  13:13 Recurse Center, "What is that keyboard? What is that editor?!", Emacs bankruptcy and starter kits
  Shae: And in 2019, when I first went to the Recurse Center, well, my first batch, I just was extremely extroverted and social. But my second immediate following batch, which is not the common pattern, I was like, okay, my goal is to write a bunch of Haskell, get some Haskell jobs, And so I went to the quiet room on the quiet floor. But then someone else came in, Marianne, my favorite programming friend. And she was like, what is that keyboard you're using? And I was like, ah, this is an Ergodox thing. And then she's like, what is this editor you're using? And I was like, oh, that's Emacs. And I was kind of a grumpy, like, I'm trying to get stuff done. But she was persistent. She was like, show me this thing. And so I was like, I'll show you Emacs. And she was like, this is great. And I was like. This thing? OK, cool. And I was like, I don't think you want my config. You'll probably want a starter kit. And she was like, well, what are starter kits? And I was like, well, I've heard about Spacemacs. I've heard about Doom. And I would try one of those. So she tried Spacemacs. And I guess this next part happened over several months. She tried Spacemacs. And then she was like, I like it, but it's slow. So I'm switching to Doom Emacs. And I would pair with her. And I was like, wow, look at all these cool things that the starter kits can do. I ended up flushing my entire 20-year-old config and kind of starting over and stealing a lot of great ideas from the starter kits. And Marianne is very ambitious, independent, hardworking, very focused. I'm not very focused. But I've learned a lot of things from her and watching her kind of... I haven't done C in Emacs in a long time so it's great fun to watch her learn these new things and then I learned stuff too and yeah it's good to have collaborative people to work with.
  Sacha: So it sounds like if people would like to encourage more people to talk to them about Emacs, feel free to use your strange keyboards out in public.
  Shae: I like that. That's good. That is good. Yeah I think that's reasonable.
  Sacha: Yeah, and I've just recently started digging into the starter kits too, because I realized I don't know much about them. It is really interesting going through them and discovering all these Emacs 31 options that you can enable to simplify your config or improve your workflow and all that stuff. So there's a lot of good stuff in starter kits, even for people who are not newcomers.
  Shae: I agree. And I think there's nothing wrong with just learning a bunch of new things, trying them out, and also throwing them away if you don't like them.
  Sacha: Now that you've declared Emacs bankruptcy and rebuilt your Emacs on top of other people's starter kits, what has made it into your config? What have you kept from those 20 years of tinkering with Emacs that you really wanted to stick around?
  16:06 hippie-expand
  Shae: I think the only thing that has absolutely stuck around is my use of hippie-expand, which is, I believe, a very old... an ancient tool from a different time. Most of the other stuff is kind of gone. Gone to the wayside. But I really like, I honestly really like hippie-expand. And I know that like, I have rarely heard of other people who use hippie-expand. But you use it? I think you just muted yourself.
  Sacha: I also vote for hippie-expand. It's a nice way to try different functions and just say, I just want all these different possible completions to go in there.
  Shae: Yeah. The thing for me that really sold me on hippie-expand is that most of the time when I am... When I'm doing something, I want to say, like, I can already see that word, just pick that one. And so I'll type the first characters and hit, like, meta forward slash, and ta-da, it's usually there. But then sometimes I do really want, like, some Elisp or some other stuff. And so I actually spent a lot of time tuning this the first time.
  17:14 yasnippet
  Shae: I actually only changed it for the first time recently because I was reading a how to write Rust well inside Emacs and they said oh well you want to use yasnippet and so I you know the funny thing is that yasnippet I believe is the thing that got me into Emacs like in 1999 I met this Finnish person Erno Kusala[sp?] in Oulu, Finland and really cool guy I was like, wow, how do you do this? As soon as you open a file, it's got a substructure and a skeleton. And when you type part of a function or something, it just populates it. And he was like, I'm using this snippet command in Emacs. That's why I was like, what's Emacs? It was very exciting. And at the time, I was using Vim. And Vim was not as, I don't want to say, automatable.
  Sacha: Yeah, now with Neovim and Lua, people are writing more extensions for it. But before, you had to know a lot of magic in order to customize Vim.
  Shae: Right, right. I agree. Let's see, what else do I do? I run my own email server, and I, of course, read my email in Emacs. In GNU, no less. Which is, I know, an NNTP reader, but it's still also a great... I used to use twiddle compile and I think that stopped working like six years ago, so I need to get rid of this comment, but there's still a lot of kind of cruft from earlier times.
  18:52 Function keys
  Shae: Remember how I said that I use function keys to have like purpose specific stuff? This was especially true because, I mean, I had my left arm strapped to my chest for like a year and three months before I even started regaining any flexibility, and that meant that... I'm amazed that you could just map them directly to single commands instead of giving in to the temptation to make them prefixes for longer keystrokes. I didn't really have the choice because I had only one arm that worked. It was just a lot harder to do any chording at the time. I still have a lot of these. F3 I use a lot, which is like, oh, what am I working on right now? That is org-clock-goto. A lot of times, I want to have a terminal that's in Emacs, so that's vterm,
  20:02 Org Mode
  Shae: And I actually really do use the calendar all the time. This is like just switch to whatever it is. Of course, my email is here. You know what, let's see... So this... I don't know, have you seen this before? Have you seen this thing called STARTED in an Org mode file?
  Sacha: I use a STARTED state, yes.
  Shae: Well, I got it from you! So if I look at like, my Org Mode configuration, a lot of this STARTED stuff I have from you, I don't know when, but you were the person who introduced me to it.
  Sacha: It's the reminder that I did start working on this. I tend to get distracted by intermediate tasks, so it's nice to be able to say, try to finish these ones first before you move on to the next thing, maybe?
  Shae: I agree. I have the same thing, yeah. And I keep meaning, because this is... I know that you can put Org Mode configuration into the first TODO item. I would really like to move it into the elisp and I just haven't gotten around to it. And it's been 10 years. I mean, maybe I should just do it.
  21:14 Show Org agenda when idle
  Shae: One of the things I did that I found fun... I really have written almost zero Elisp, but I did actually puzzle my way through this a year ago. Since so much of my life is in Org Mode, I learned how to make timers. This is very close to what you get directly out of how to do timers in Emacs. After some amount of time, I want my Org agenda to pop up because I want to say like, oh, what is the stuff I'm supposed to be doing? And what am I forgetting? What has been scheduled? And what is on my to-do list? And I also like to look at what is the stuff I've been working on lately? And I really like that a lot.
  21:58 Programmers want flow. When programming, light turns red
  Shae: Another thing that I realized is that I had a blog post that was wildly popular. Where did I put it? And it was all about Emacs. I don't know if you saw the... Here we go. It was... Ah, here it is. So here it is in... This is very much an Emacs...
  Sacha: Oh, yeah, I remember that one. I put it in Emacs News. I thought it was great.
  Shae: All right, cool.
  Sacha: I would like the kiddo to sometimes be able to acknowledge this, but this is not happening. Still, yes.
  Shae: Right, right. Yeah, and so this was really fun because, like... I had a friend who was in development and there was like millions of dollars spent on how do you detect whether a programmer is in flow and it came down to if they're typing they're probably in flow so and that was it because they tried to look at EGs and doing all kinds of other stuff but it was like if they're typing don't interrupt them. And I don't know, because I do so much in Emacs, I'm not sure how accurate this was. But basically, that's where I learned to do timers the first time. Or maybe... I don't remember which one I did first. And the idea then was as soon as basically my average typing into Emacs has gone up a certain amount, then it will actually switch to busy. And it works just fine. It was a lot of fun to write.
  Sacha: So yeah, interesting use of getting the activity. I've seen other fun implementations of this. I think there's a c-c-c-combo package that makes some fun animation appear if you're typing really quickly.
  Shae: Oh, oh, yeah. I'm guessing because I think Atom, the Atom editor had that for a while. I guess that's where it came from.
  Sacha: So yeah, because you can instrument Emacs and play around with it, you can certainly do all sorts of things based on that information. Okay, so you've got it, you've got it set up so that when you come back to your computer, it'll show you the stuff that you've been working on. And when you're working on the things, you can tell it to tell the rest of the world not to bug you. Gotcha.
  Shae: That's right. [Sacha: What other fun stuff do you have in there?
  24:25 ef-themes and modus-themes, season
  Shae: I discovered that I love the EF themes. I love the Modus themes. They make me very happy. They're just unreasonably pleasant. As someone who has tried every single Emacs theme ever, they're just my favorite themes.
  Shae: And so, at the moment, it's summer... Where did my summer go? How can this be? There we go. How come I'm in spring? Wait, isn't spring over? Hasn't summer just started? You know what I was thinking would be fun would be take the time of day, and you know that the EF themes has spring, summer, autumn, and winter, and I'm not sure if there are dark versions of each of those, but I thought, like I know that Modus themes will do this like check for the local time of when it turns dark, and then it will go from the light theme to the dark theme as soon as the sun hits, and I was like, well, what if I do that for seasons, you know, wouldn't that be cool?
  Sacha: There's this subtle sense of change as you go through the year. But of course you also have this thing there where you just randomize it.
  Shae: Well, I like that. Sometimes it's like I'm just kind of like, ah, I'm bored. I'm just bored of what I'm looking at. And so I will just change my thing. And it's just time for something. I don't know. It seems to work. It's like it gives me a little brain break from what I was staring at. And I did not know I was going to reset the effects scale, but that's fine. Interesting. What else do I have in here?
  25:56 htmlize (does this still work on Wayland?)
  Shae: Oh, Emacs HTMLize. I'm a little sad. I switched to Wayland. And if I remember correctly, HTMLize only works with, or maybe HTMLize still works, and it's the SVG one that doesn't work. Emacs SVG is a thing that if you're running with an X11 backend, you can turn your current screen directly into an SVG, which is really cute. It does not work in Wayland. I think HTMLize does still work. What other things do I have in here? I don't know. I guess a lot of it lately has been trying to make Rust things work smoothly. I've been trying to do some... I wonder does... Oh, cool. That was not what I expected.
  26:37 lsp-ui-imenu, jumping through rust code
  Shae: I just started doing this thing with imenu. imenu integrates nicely with LSP.
  Sacha: That is a very pretty sidebar thing, and I need to learn how to do that.
  Shae: So because I have all these extra modifiers, my s-i is lsp-ui-imenu. And the reason that what I mostly use that for is when I have like a bunch of Rust code and I want to quickly jump through the structure of it. Basically that integrates with LSP, finds all the definitions, and I can quickly jump through it. I used to use lsp-treemacs for that, but lsp-treemacs puts things in its own order, not quite the same order I want, although treemacs is quite nice. I think that the thing to do is that you and I at some time maybe the next time if we do this again we should set up with a Shwim connection and you and I can both share our Emacs and then you can show me cool things that you do and I can show you cool things that I do and then we can start filing over some of the things. How about that?
  Sacha: That sounds fantastic. I know we'd wanted to experiment with pair programming a long time ago so that sounds like a seamless way to do it. And therefore I will go and figure out how to install shim and get it working. I will probably need your help to actually test it. I don't know, I think I can rustle up. Maybe it'll work off my phone. You haven't tried that. But lspui, okay, so I've just been using straight up imenu, like on Neanderthal, but lsp-ui has this fancy grouping of things and colors and stuff, so I definitely want to check that out.
  Shae: I'm a fan, yeah. I don't know. Do I have anything else exciting that goes with this in here?
  28:25 laptop with 126GB of RAM
  Shae: I will say that at the moment, the system I'm working on, I like buying unreasonably powerful laptops. And so, like, this system has 128 gigs of RAM and 24 cores. My previous laptop has 192 gigs of RAM. Long story short, I end up in a lot of cases where I want to use more memory. I've got all these cores. Can you do something with them? Perhaps you've already seen things like LSP doctor, which will say, have you tried this thing? Have you done this other thing? LSP has really changed
  Sacha: I have not. Sorry, would you like to show me this LSP doctor thing? Because I have not ever seen it.
  Shae: Yeah. Do you use language servers much for your development?
  Sacha: I am only just getting used to having a relatively modern 2018 instead of 2010 laptop. And so I have the red squigglies and various things, but I don't know what to do with them yet.
  Shae: Well, I mean, I'm doing a lot of this. So I have...
  29:46 LSP coolness, Haskell, treesitter
  Shae: Originally for me it was like I spent a lot of time with the Haskell language server because I was doing so much Haskell and it was a super powerful thing. In fact, somebody decided to hammer in half of a proof assistant into the Haskell language server and that was magic. You could do incredible stuff with that because you could just grab all of your local variables and transform the whole shape of your function and you could just write little snippets and just have it work. And that was amazing. It wasn't quite... One of the goals that I believe is... For future development of all programming editors, I believe that something like Emacs macros, but instead for abstract syntax trees, I believe this is an essential ingredient that we do not yet have. And I think that TreeSitter is the first step towards there. We now have one of the hats, right? Which is where we can take... TreeSitter is, you know, if you've used it... It is like you write some effectively C code to produce a really fast parser. Or is it like JavaScript that then compiles to C code? I forget exactly how it works. But the nice thing about TreeSitter is, I don't know if you remember, I'm sure you do remember, that if you were writing Python code and you used a triple-quoted string, you had to then add a comment with another quote because regular expressions is how Emacs was doing all the syntax highlighting. And honestly, that was kind of crap. And then there were projects like the Semantic Bovinator that made a full parsing suite in Elisp, which to me is half brilliant and half insane. And then there was TreeSitter, which kind of took over the world because it was... I think that the language server and TreeSitter are the first two of these editor generic pieces, and I suspect there will be more. I think that something where you can modify the abstract syntax tree and then put back to the source is one of those potential paths forward. I hope so.
  Sacha: Yeah, that would be great if you could just do the manipulations and then roundtrip it back into source code. Just regenerate the changed part of your code. That sounds fantastic. So it sounds like you were able to do some kind of manipulation with the Haskell use case that you were describing. Any chance you can show us like the awesomeness?
  Shae: Sadly, that sadly does not work anymore.
  31:58 Combobulate
  Shae: But you know, if you're looking for something in that area, have you heard of a Emacs library called Combobulate?
  Sacha: I have heard of it. I haven't dug into it.
  Shae: So it uses TreeSitter for source code manipulation by, and it's a lot closer to the way that like, you know, in Org Mode, you can like hold meta and arrow to kind of move things around. It uses TreeSitter to let you both move around in the context as well as actually alter the shape. And to me, this is the first step towards this tool that I want, which is where I can write a keyboard macro and have it edit an abstract syntax tree and then spit the results back into the buffer. Yeah.
  Sacha: All right.
  32:46 What else are you using your 126 gigabytes of RAM for?
  Sacha: What else are you using your 126 gigabytes of RAM for?
  Shae: Let's see. Honestly, I'm going to tell you that Rust Analyzer can take a lot of memory. And a Rust compilation can take a lot of cores. And I'm okay with that because I actually, I do like, and I will say that this laptop is actually from this year. So it's a brand new, like, top of the line. But then like, how would I, because I've got like, which I think is a bunch of matrix multiplication hardware. How do I use that from Emacs? I don't know. I'm sure I can find something, you know.
  33:25 TalonVoice
  Sacha: Maybe voice computing?
  Shae: Oh, that's an idea. Yeah, one of my friends, she's using Talon. Have you heard of Talon?
  Sacha: Yeah, I've heard of Talon. There are a couple of videos about people using Talon to code by voice, usually involving memorizing kind of a different alphabet for very quickly accessing different shortcuts. But it sounds really cool, and you sound like you've got the hardware to do something amazing with it.
  Shae: That's true. Well, you know, Talon actually lets you do something very similar to Combobulate, where you can navigate the AST of your source code. You can kind of move around very quickly. I don't know, like, are we like at the end of our? No, no, we're halfway through, right?
  Sacha: We're halfway through. I have about 28 minutes before the kiddo runs out and starts demanding lunch.
  Shae: Okay, well, I feel like I've been driving the structure of our just kind of like dumping random things. Did you have any questions or anything you wanted to cover?
  Sacha: This is all amazing. I come in with no preconceived notions. I'm just like, okay, shapr does cool things with Emacs. Let's hear about it. Let's go, let's go.
  Shae: That works for me. Yeah. I mean, a lot of it's been focused on Rust development lately. Rust and Jujutsu.
  34:45 NixOS, following Steve Purcell about 5 years behind
  Shae: I've been doing a lot of Nix. I'm running NixOS. I don't know if you're familiar, but that's been great fun. It's funny, I feel like I've been following Steve Purcell around from a technical perspective. I'm always about five years behind Steve.
  35:03 envrc
  Shae: I was like, oh, you know, NixOS is kind of a pain with Emacs. And just like this, what was it, NixOS? I forget. Anyway, Steve was like, oh, well, have you tried my library, envrc? And I was like, what's that? And he was like, well, now each buffer can have its own envrc. And I was like, it's perfect. That's exactly what I need. Because previously, every time I switched buffers, it would then go load all of the local everything in Nix. And sometimes that could take a long time, especially if I'm doing Haskell, that could take 10 seconds, and I really don't want that sort of lag. And so Steve Purcell's brilliant library, envrc, says, you know what? Every single buffer can just keep such a thing, and then you can only relit it when you need to. And that's pretty awesome.
  Sacha: That sounds cool, and I should check that out too.
  35:52 time-tracking
  Sacha: @JacksonScholberg has a question. He says, "I was curious about what you were tracking your time working on, how you track it." Is it just Org Clock? So this is how you keep track of the things you're working on and what got interrupted by the new thing that you just added to the stack and so forth?
  Shae: Right. In fact, I have this thing. Honestly, when I sit down on my computer, Just clock in. You'll notice in the bottom right here, we have chat with Sacha, right? And so like, I just kind of clock in stuff. And like, I'm not always, I really kind of need to reorganize my Org mode files because I've been naming them per host because I previously had like a work Org mode and I had a home Org mode. now that my home hardware is also my work hardware I guess and so like I still have my previous laptops things where I'm keeping my events I really need to reorganize things but I mean yeah I schedule things I oh you know I've got a weird thing to show you
  37:01 taxes with Org Mode, remote lookup
  Shae: I decided that it would be great fun to do my taxes.
  Sacha: You are showing me your taxes, do I need to like black out this whole thing?
  Shae: Well, this is actually just an example from the docs. So I could actually share my taxes on it because I mostly don't care. But I think in fact you can figure out exactly how much money I'm making by looking at the open whatever. So the thing about this is that I decided to file all of my tax forms directly into Org Mode spreadsheets and then do remote lookups. So basically each spreadsheet was one particular form. And then once I'd gotten to the bottom, like I need this result, like what's my estimated income? And then I would use the lookup, kind of this cross spreadsheet lookup. And that's how I did my taxes for last year. And then my de facto mother-in-law, she's an accountant, and she didn't exactly do this thing, but it was pretty close. She was like, you've got all your taxes in the spreadsheet. I was like, yeah. And then she looked at it and she was like, what is that? And I was like, anyway. So I got to kind of file everything back out into TurboTax, but that was a fun thing to build.
  Sacha: Yeah, I have something like that too. So for example, whenever I do my tax paperwork, I just have to have like, you know, the step by step checklist. Okay, this is where I need to go to get this number. This is where I can put it in. And then eventually it spits out a table that says, okay, put this in box 11, put this in box 13, so that I don't have to do the steps by hand. Because even before the, you know, for me, I use like simple stacks or whatever, it's web based. But before you get to the point where you can put the numbers in the form, you gotta go to this website, calculate this thing, and Org just makes all of that so much easier.
  Shae: I agree. Yeah.
  Sacha: And this remote lookup thing is something I'm always looking up because Org tables are so powerful, but also I need more examples in my life to remember how to use them.
  Shae: Well, I think it took me four hours the first time to get it all figured out. But I can send you an example without showing it here. I can send you an example because I figured out, I think I've hammered the remote lookup down very thoroughly.
  Sacha: And once you've got it right, you can just keep filling that in or copy and paste it. You have an example of the syntax and that's already all you need.
  Shae: Right. I did run across some limitations of the evaluation method of Org mode spreadsheets. But maybe I've been using them a little too hard, if that makes any sense.
  Sacha: Oh, what kind of limitation?
  Shae: Honestly, I think I finally found a way to say every single... Because it was... So really the way that spreadsheets work is they're much more like Dataflow. And that is just that you end up with, like, either you work from the endpoint, which is like much more Haskell style evaluation, which is where you're like, I need to start here. What depends on this? But in the case where you have a whole bunch of different Org Mode spreadsheets, I think I ended up with this little text style hack where I just ran it a bunch of times. So it's like evaluate, evaluate, evaluate. Because remote lookups I ran, you know, I don't remember. And I think I took notes, but I don't remember. That's one of the great things about Org Mode is that I swear it's my, like, half of my brain is in my Org Mode notes. And whenever I had, I'm like, oh, what was that thing? I'm like, well, fortunately, with my terrible short-term memory, I took copious notes because otherwise I would never be able to get back to it.
  40:55 finding notes with C-s
  Sacha: What is your favorite way of finding those notes?
  Shae: I actually use a lot of C-s just because I kind of have some idea of where they are in my tree structure and I'll also say I use a lot of my Org capture templates and they're not super complicated. I have like a to-do, I have a journal, I have ideas and like random ideas will float into my head like you saw Markov keyboard right it is like the weirdest art piece you've seen all day right and Markup keyboard shows up on the front page of Hacker News once a year or so. And people are like, programmers have gone too far. This cannot possibly be usable by humans or something. And I'm like, well, I don't know. I think it was art. And so a lot of times those things will drop into my head, something like that, where I'm trying to do something else. And so I will quickly write down the idea and then just gotten it out of my head enough that I can continue with what I was doing. And so I have a long list of strange ideas. A recent one was like, you've probably had your teeth worked on once or twice. And you know that the dentist always had to move the light around. And I'm like, but we have really good eye tracking. Wouldn't it make sense to figure out where the dentist or the car mechanic is what they're looking at? And then have the light move around behind them to figure out how to actually light up the place they're looking at, right? We've got vision tracking. Why don't we do this? But I don't really, yeah. I decided maybe I don't want to work on that one right now.
  Sacha: It sounds like an involved project. Yeah. Yeah, yeah, yeah. Okay, so you're capturing, you're stuffing a lot of these ideas into an inbox.
  42:35 Org Mode, managing inbox
  Sacha: A lot of people are probably in the same boat where they've got these inboxes full of ideas. How do you deal?
  Shae: I archive stuff when I'm done with it.
  Sacha: Oh yeah?
  Shae: Yeah, so a lot of times, and I find this very valuable, is like if I look at... Do I have it? Oops, that was not what I meant to do.
  Sacha: Alright, so you basically just do aggressive speed commands, archive, archive, archive, or look at the agenda and just mark a whole bunch of things and say, that's it, that's gone. It was written down and then it can go.
  Shae: Yeah, well, when I'm really done with something, when the thing is finished, then I will just archive it. I mean, do you use Archive much?
  Sacha: I do. I have a function that goes through my inbox file and just archives anything that was marked as done.
  Shae: Oh, nice!
  Sacha: Because that way it clears it up, right? So I'll refile things where I'm like, okay, it's done, but it has important information. I want to put it somewhere else. But if it's just a transitory task that I'm using to remind myself, tomorrow I have to do this, go find the water bottle when it's done, I don't need to know about it in the future. So it's left in my inbox because I checked it off, and then periodically I'll say, clean up inbox. Not only will it remove all of the done things, but if I leave a tag In the title of the task or if the task matches certain regular expressions, it will refile it to the appropriate place in my kind of more permanent thing. So I can say, okay, all of my Emacs related tasks will get automatically refiled to my Emacs category without my having to do that manually.
  Shae: So you're using tagging because I kept trying to do tagging and never quite did it.
  Sacha: I use tagging sometimes when I remember it, but this is also why I use the The regular expression match against the title. I'm using Orgzly on Android to capture the thing on my phone. I might want to say this is a consulting task. File it in the right place so it doesn't get lost in my inbox.
  Shae: Wow. When is your interview so I can learn from your tricks?
  Sacha: This is now. Here we go! You can ask questions. The nice thing about conversations is that we jostle different ideas, and we are like, oh yeah, maybe I should write a blog post about that, because I take it for granted. So now apparently I have to write a blog post about my cleaning up process. My inbox is very long. The other thing, speaking of dealing with really long lists that I picked up from John Wiegley was I also sometimes remember to check this list of random items. So in my agenda, there's also like this, you know, random selection of things that I have not gotten around to thinking about further, but it's there just in case serendipity or boredom make me do something.
  Shae: you know that's... I've thought about having... because you know, I've got the pop-up this little timer that pops up my agenda, but I've thought about maybe adding a section I don't know if I could add a section here but it would be something that says like at the bottom here's two or three random to-do's that have been open for a while just like for garbage collection. Because I know that in Jujutsu, I've got a cool little query that says, if you have any change sets that are more than two weeks old and are not in a permanent branch state, maybe you should do something about them. It's just called to do. It'd be kind of nice to have that for Org Mode as well.
  Sacha: Yeah, it's just, you know, and our brains do these strange things with randomness, right? They're like, oh, I want to see what's new now.
  Shae: Right, right, yeah. Oh, I have a question. You have this thing where you had...
  46:28 Timestamps
  Shae: I saw you taking notes with Prot, and you had this timestamp.
  Sacha: Oh, yeah, yeah, yeah. I'm using it now. Okay, okay. So I have it bound two ways now. I have it as a dabbrev, so dynamic abbreviation, and I also have it as a yasnippet because sometimes I'm using it with either SPC or tab to complete it. And I don't really want to think, I just want to get the timestamp in and then move on. And so abbrevs can run functions to evaluate it. You can insert the timestamp that way. Or yesnippet, of course, can evaluate the thing. And now I have those. It's basically just a wall-clock time so that I can go back and plop in the chapters as time offsets, which are automatically calculated from the YouTube data on when the stream started. So I don't have to manually calculate my chapters. But it's super useful to have these times everywhere. And in this case, during a conversation, I want to be able to say, hey, we talked about something interesting. And then be able to go back to that point in the video later on.
  Shae: So you're matching? Oh, oh, wow.
  Sacha: So my shortcut for yasnippet is "ot" because I never type "ot" elsewhere, and it's close enough. I use Dvorak, so my O is on home row, and T is close by. Also, on the other hand... There you go.
  Shae: Did I already show you that this is actually Dvorak?
  Sacha: Oh, there you go. Now I can see the keycaps. Yeah, earlier it was kind of blurry, but now, yes, yes. So yes, that is my shortcut for inserting the timestamp. I previously added seconds as well, but then I realized that my kind might be false precision. So I just, you know, just use a minute at the moment and then I go back and adjust the timestamps a little bit later. But yeah, you can use abbreviations for all sorts of things, including times and dates and stuff.
  Shae: Have you ever tried Org timestamp?
  Sacha: Yeah, Org timer. So Org timer gives you a relative timestamp, right? You can say Org timer. Oh, okay. So, sorry. Are you talking about the C-u C-c ! or something of that sort? So that's actually what I initially was doing, but then it was too many keystroke word modifiers to remember. And then I had to press RET to select the, you know, thing. So now I just have an abbreviation insert the Org mode formatted timestamp for me. And then I have this code that searches for Org timestamp regular expression and then does the calculation and conversion and stuff.
  49:12 Org timers
  Sacha: So Org timer is a separate thing. It's useful for meetings and things like that. You would say, okay, your Org timer starts at the beginning of the meeting and then you can have a list and it automatically, like if you alt shift enter or something like that in the list, it'll automatically like insert the right timer, relative timer to it. There you go. So there's an org-timer-start. But the reason I didn't go that approach was because then you A. have to remember to actually start the timer and B. then you have to synchronize your time with video time. Which might not have started at the same time. So now I'm just like, okay, wall clock for everything. And then I can do the transformation with whatever I like. And since I'm editing my subtitles in Emacs, I can say, hey, this file started at this time, according to YouTube. And then just, you know, map all of the wall clocks to the appropriate subtitle times.
  Shae: Wow. That's really cool.
  Sacha: Anyway, so timers, relative, absolute, and using abbreviations is great. Which I think actually is a thing that I picked up from Karl. Karl Voit because he also likes to use... He has an abbreviation, not at the Emacs level, but he has an abbreviation on his system level, like with his window manager, so he can use this timestamp trick anywhere, including in Etherpad or wherever else where you want to insert the date and time. That's V-o-i-t, by the way. But yeah, so times are a great way to just leave yourself a pointer to that moment so you can go back to it later.
  Shae: Now I'm curious, how well does that integrate with this sort of thing? Because I really like looking back at my history agenda.
  Sacha: If you have it insert an inactive timestamp, I think it should still show up there. I think it will be a little like those.
  Shae: Yeah, it looks like the... Well, it looks like these two are showing up.
  Sacha: Yeah, yeah, yeah. Yeah, so that's a basic thing that I would have inserted by my either abbrev or... So it's not even dabbrev. It's just regular abbrev in Emacs.
  Shae: What's the difference?
  Sacha: dabbrev is like hippie... Okay, let me just double check here. I feel like dabbrev is sort of hippie expand-ish. It looks in your buffer or possibly other buffers. And I think hippie-expand and dabbrev, they kind of work together. It's an option to have them work together. Okay, so hippie-expand is... Oh, so I see. Hippie-expand is the more advanced version of dabbrev. dabbrev was Dynamic Expand, and Hippie Expand says, yes, that, but try a whole bunch of other things first. But my timestamp thing is actually just done by a regular abbrev, and I will find the thing in my config for "ot". Oh, yeah. I will put it in my chat.
  Shae: My spelling, most people say my emails are spelled really well, but it's only because I have ispell set up.
  Sacha: Yeah, ispell is great. I am learning French and therefore...
  Shae: Oh, c'est très bien. Je parle un peu de français aussi.
  Sacha: Oh, oui. I'm keeping a journal in French on my blog and I have the Tatoeba Project with all the example sentences and I have a consult interface to look up stuff in them so I can just borrow other people's words and try to make it sound more natural. Plus of course the usual searching for words in dictionaries and stuff. Anyway, in the chat, I put in my global abbrev table definition for insert format time string. In case you want to steal that, it's right there.
  Shae: I will definitely save that into my notes here.
  53:53 Org Mode snippets
  Shae: Another thing I use a lot is I use Org Mode snippets. I will tell you that the first time, I guess if I look back at... This is another thing that I have done a lot of in the past, which is where... I love the fact that Org Mode snippets are just executable. I can just run them. I guess two jobs, three jobs ago, there was a case where, because I would keep the results around and look at them, there was a case where, I guess a couple of months before, something got shipped to a customer, and I noticed our database schema had changed and I prevented a tremendous amount of upset and emergency by being like this doesn't look great. I got one from two weeks ago, and it does not match. Something's wrong here. Everybody's like, I don't think so, Shae. And I'm, like, no no no, we do have a problem, we've got to fix this. And they were, like, oh crap! And then I was like, yeah, solved a problem!
  Sacha: Yeah, I basically try to do as much in a snippet instead of in, you know, in a scratch buffer or whatever, just because having that record, the fact that I did it, and also any notes that I had leading up to it and the output of it, it's just so helpful.
  Shae: Oh, I've got a cool thing that I'm doing for work. And that is that our readme file is not only a word file, but we also have the demonstration of our actual thing is done by using like dependent snippets. And so that means that like if you want that, perhaps this is something everyone already knows, I don't know, but we basically are using the results of earlier commands in later places. And the other nice thing about that is that then when we want to check, we have to effectively dock tests, right? When we want to check and see if our software works the way it does in the readme, we evaluate the final Org Mode snippet, which then calls it forward, calls it forward, and then if something goes up or not. Well, I guess I need to fix something. And so it was pretty exciting to put Org Mode niftyness into our, into my Word reading file, you know?
  Sacha: Nice, nice. And you did mention your other coworker is on board with the whole Emacs thing. So that's one of the things that people are often like, I want to use Org Mode and I want to use it for like the documentation or the testing or whatever, but they got to get everyone else on board with the thing. Otherwise it's Jupyter Notebooks or whatever else, right?
  Shae: Right. Okay, so I have a joke for you that I came up with a long time ago, and that is, do you know the only way, there's only one way that Sauron could have organized the invasion of Middle-earth, and do you know what he used?
  Sacha: What?
  Shae: Orc Mode. It's a terrible joke, isn't it?
  Sacha: That's okay. I'm sure someone in the comments will come up with an even worse pun.
  Shae: I'm excited! It's going to be great!
  Sacha: Never underestimate the punniness of the Emacs community.
  Shae: I completely agree. I don't know. Do I have anything else exciting in here?
  57:15 Compilation finish function: handle success
  Shae: I actually really like this one. I used to run all of my tests in compile. F12, I have F12 bound to compile. And one of the things I wanted was, I wanted something where it was, if the compile is successful, don't show me the results, because everything's good. And so since I'm doing stuff in Rust, when I run all the tests, it leaves the buffer up, and I need to get around to actually doing stuff like this for Rustic mode as well, where when the tests pass, just go away, because it's all good. And when the tests don't pass, show me where to... I need to look at the problem. And I got this from Enberg and Emacs, I don't know, 20 years ago. Maybe it was less than 20 years ago, but it probably wasn't. So yeah, there's so much good stuff. Yeah, there's just so much good stuff. And I also like to, oh, look, here we go. You can see that this is long gone, by the way. It's not there anymore.
  Sacha: I have a proper, you know, it's sachachua.com/dotemacs. A lot easier to remember. But yeah, and I think that's, yeah, yeah, I remember that now. defadvice is also obsolete. The new hotness is advice-add or something like that.
  Shae: Oh, really? I'm going to make another TODO item for there.
  Sacha: I was digging through my notes trying to find, do you share your config anywhere?
  Shae: No, but you know, at this point if I share it on YouTube, I might as well just throw it up somewhere. Why not? It's not very exciting. Like if you look at someone like Ross Baker who has magic, like wow, is there some magic coming in from Ross Baker? I'm so excited to see more stuff from him. There's just like, I guess I feel like compared to almost everybody else I know, I feel like a power user. Because I'm like, you know, I wish I could do this thing. A lot of times someone I know is like, well, I did that thing and here's a library. And I'm like, yeah, I'll have to do it. And I just, I guess I feel like I'm a power user. And on the good side, I guess I kind of, I really haven't written that much Elisp ever, like I was saying in the comments during your interview with Prot. And I kind of like to, it's just I guess it's never quite gotten to the top of my stack. And I did decide it was time for me to send money to Parade for at least for themes, if not for like, please teach me some Elisp so I can actually, because you know, it's not that Elisp is hard. It's more like, how do I kind of, what are the things I interact with? What are the words? What's the vocabulary of working with Emacs? I don't actually really know. As a user, sure, I can do cool stuff. I can do Lisp macros. I've done Scheme and Lisp some of the past, but not inside Emacs.
  Sacha: Alright, so let me clarify. After more than 20 years of using Emacs, did you say you feel like a power user or do not feel like a power user?
  Shae: I definitely feel like a power user, but I don't feel like someone who does much of anything with Elisp. I don't really feel like someone who has much of a clue in the internals. And that's not entirely true. I have some of the ideas. But for the most part, I haven't actually needed to know that much about the internals. And sure, I've dug into things like how do you efficiently work with large buffers in your ??, like the ropes data structure and stuff like that. That was more for fun. Although it is something that Emacs does and does extremely well. But I'd kind of like to... There's a lot of things I'd kind of like to change and I don't really have enough of the understanding of the kind of how I would write the Elisp to do it. Here's a good example. When I hit F3, it takes me to the one I'm currently clocked into. Unless I haven't clocked in to something since I started Emacs. And honestly, I would like to use something like org-ql, the Org query language, to go find if I've just started Emacs, and Org does not know about something, you know, I just want you to go search for it. I have so many cores and so much memory, just go find it.
  Sacha: That sounds like an excellent reason to go learn Emacs so that you can have it... If you're not currently clocked in, go find the most recent clocked in task and go there, or maybe present you with a list of things and then go from there. I would love to hear about your Emacs Lisp learning journey because that's one of the big things that moves people from, you know, power users, yes, but users, to using Emacs as a lightweight editor toolkit for something that's custom fit to exactly what their workflow is. And on that note, I'm going to try to wrap up gracefully before the kiddo, you know, just like drags me out here. Thank you so much for doing this. I look forward to more conversations. I'm going to post the transcript and other things like that pretty quickly, I think, because I have this nice workflow now that lets me take screenshots and everything, but there's so much here that I want to unpack. But I hear the kiddo, bye!
  
  #+begin_export 11ty
  
  <a name="end-ec22-transcript"></a></details> #+end_exportbvt
  
  Chat
  
  JacksonScholberg: Emacs is fun
  
  JacksonScholberg: Apple's touchpad is another option
  
  JacksonScholberg: Trackpad
  
  JacksonScholberg: Lol
  
  JacksonScholberg: I was curious about what you are tracking your time working on
  
  JacksonScholberg: How you track it.
  
  JacksonScholberg: You clock in and out to what you are working on. I like that idea.
  
  Bezaar.musicc: That's great!
  
  PuercoPop: the buffer api (properties) is the hardest part for me
  
  charliemcmackin4859: I think you still have a timer going, btw
  
  Find more Emacs Chats or join the fun: https://sachachua.com/emacs-chat
  
  View Org source for this post
  You can e-mail me at sacha@sachachua.com.
7. 🔗 r/Leeds I love this spot. rss
  
  Sidenote : anyone going warehouse this coming Tuesday ?
  
  submitted by /u/Auriv3x
  [link] [comments]
8. 🔗 r/york York City Parade rss
  
  | View from the bus! submitted by /u/York_shireman
  [link] [comments]
  ---|---
9. 🔗 r/reverseengineering The first FREE online WebAssembly Reverse Engineering workbench (and how we built it) rss
  
  submitted by /u/TrustSig
  [link] [comments]
10. 🔗 earendil-works/pi v0.74.0 release
  Changed
  - Updated repository links and package references for the move to earendil-works/pi-mono and @earendil-works/* package scopes.
11. 🔗 The Pragmatic Engineer The Pulse: AI load breaks GitHub – why not other vendors? rss
  Hi, this is Gergely with a bonus, free issue of the Pragmatic Engineer Newsletter. In every issue, I cover Big Tech and startups through the lens of senior engineers and engineering leaders. Today, we cover one out of four topics from last week 's The Pulse issue. Full subscribers received the article below seven days ago. If you 've been forwarded this email, you can subscribe here .
  
  GitHub's reliability has been beyond unacceptable recently: last month, third party measurements pinned it at one nine (right at 90%). This month, reliability has been down to zero nines - 86% - as per a third-party tracker, and last week, things got even worse: a frankly embarrassing data integrity incident, more outages, and a partial explanation from GitHub, eventually.
  
  Data integrity incident
  
  Last Thursday (23 April), this happened: PRs merged via the merge queue using the squash merge method produced incorrect merge commits, when the merge group contained more than one PR. Commits were reverted from subsequent merges: basically, commits were "lost" in the code that was merged!
  
  Thanks to a bug GitHub introduced, the service broke its integrity promise that pull requests would be merged as expected when using squash merge, which is a technique typically used to merge multiple small commits into a single, meaningful commit. This is a big deal: as data integrity promises are some of the most important ones, for services like GitHub.
  
  A total of 2,092 pull requests were impacted, and companies hit by the outage included Modal and Zipline. Effectively, GitHub pushed a bunch of work on affected customers who had to manually untangle and recover lost commits, which GitHub could offer zero assistance with.
  
  Customers had to manually go through their git history and restore missing code. After following manual recovery steps (reverting the squash commit and re-applying commits one by one), all commits should have been recovered.
  
  GitHub later emailed the list of affected commits to customers, but it's odd that GitHub executives seemed to downplay the nature of this outage. After all, an outage that messes with data integrity is a much bigger deal than something like a fall in availability where no data is corrupted.
  
  Can Duruk, software engineer at Modal, was unhappy about GitHub's muted response to the outage:
  
  "The COO going out of their way to find a huge denominator to make the impact appear small feels very dishonest; versus a sincere apology about how this invalidates their entire promise to their customers. We had to dig into their status page about this to even realize they just casually f***ed up our repo."
  
  Outages don't stop
  
  On Monday (27 April), pull requests and issues disappeared from GitHub's web UI:
  
  Pull requests go missing. Source:Mario Zechner Issues also not to be found. Source:David Cramer
  
  This had to do with an Elasticsearch outage on GitHub's backend: the cluster became overloaded and went down. So, while pull requests, issues, and projects didn't vanish altogether, they also didn't show up during the 6-hour-long outage.
  
  There were other outages this week:
  - Some pull requests not showing up (Tuesday, 28 April)
  - Problems with some GitHub Actions (the same day)
  - Incomplete pull requests in repositories (Wednesday, 29 April)
  Also on Tuesday (28 April), security firm Wiz disclosed a critical security issue, where a bad actor could get access to all repositories on GitHub and GitHub Enterprise server by using only a git push command. GitHub fixed the issue on GitHub.com within six hours, but GitHub Enterprise servers that were not updated remain vulnerable.
  
  Famous open source contributor quits GitHub in frustration
  
  On Tuesday, Mitchell Hashimoto, founder of HashiCorp, creator of Ghostty, announced GitHub was unfit for professional work and that he was moving off to Ghostty, the open source terminal that's his main focus. Mitchell's reasoning was dead simple: being on GitHub makes him unproductive (emphasis mine:)
  
  "The past month I've kept a journal where I put an "X" next to every date where a GitHub outage has negatively impacted my ability to work. Almost every day has an X. On the day I am writing this post, I've been unable to do any PR review for ~2 hours because there is a GitHub Actions outage. This is no longer a place for serious work if it just blocks you out for hours per day, every day.
  
  It's not a fun place for me to be anymore. I want to be there, but it doesn't want me to be there. I want to get work done and it doesn't want me to get work done. I want to ship software and it doesn't want me to ship software.
  
  I want it to be better, but I also want to code. And I can't code with GitHub anymore. I'm sorry. After 18 years, I've got to go. I'd love to come back one day, but this will have to be predicated on real results and improvements, not words and promises."
  
  Mitchell's experience suggests that GitHub's official status page is inaccurate from the point of view of a heavy user like himself. The third- party "missing GitHub status page" is likely to be a better estimation: where GitHub's reliability is at zero nines: at 85.51% uptime. That means that a part of GitHub was down for 2-3 hours, per day, on average, for the last 90 days (!!)
  
  Reliability woes: GitHub "not a place for serious work." Source: The Missing GitHub Status Page
  
  Mitchell's complaint sounds straightforward:
  1. As a professional software engineer, it's important to have tools that help you get work done
  2. For months, GitHub has got in the way of his work on open source projects via a flood of outages
  3. It makes no sense to use a product unfit for professional work.
  4. As GitHub shows no signs of improvement, it's worthwhile to move to a different solution which just works
  CTO blames AI agent-fuelled load spike
  
  GitHub CTO, Vlad Fedorov, shared an update on why reliability has been terrible for months at GitHub. He identified the load from agents being much bigger than expected as the culprit. Charts illustrating this were shared by GitHub:
  
  This chart looks eye-catching - but there's just one tiny issue: no Y axis! So, while it tells the story of the load going up slowly and then very fast, we're not told by how much. However, I managed to get data from GitHub, and below is the chart showing the actual load increase over two years:
  
  A load increase of ~3.5x, spread across two years, doesn 't seem so brutal at first glance. It is nothing like a load increase of 10x in a month, and a good chunk of it occurred in recent months. So, why can't GitHub handle it? In a blog post, Fedorov said:
  
  "A pull request can touch Git storage, mergeability checks, branch protection, GitHub Actions, search, notifications, permissions, webhooks, APIs, background jobs, caches, and databases. At large scale, small inefficiencies compound: queues deepen, cache misses become database load, indexes fall behind, retries amplify traffic, and one slow dependency can affect several product experiences."
  
  Here's how the per-second load numbers from January 2023 and today compare:
  
  GitHub took 15 years to achieve the 2023 numbers, and maybe it expected to continue growing in a comparable way in the future. If so, some engineering decisions about long-term infrastructure improvements would have been made obsolete by the arrival of AI agents.
  
  To add to GitHub 's challenges, the company is in the midst of a migration from its own data centers -> Azure. In October last year, GitHub started to move over to Azure - a project expected to take 12 months - because it already had constraints on its own data center capacity.
  
  Such large-scale infrastructure migrations are hard enough when the load on a service is relatively stable; just making sure nothing breaks takes a lot of effort. But moving at a time when load is spiking means that bugs can cause more visible outages. Of course, GitHub can secure a lot more compute capacity on Azure, now they know what to expect.
  
  But other major companies prepared for a 10x increase in infra load, so why not Microsoft / GitHub? A year ago, I did research on how Big Tech was preparing to respond to the impact of AI on their business. Google was improving its internal systems to accommodate for a 10x increase in load. As we covered in The Pragmatic Engineer, in July last year:
  
  "Google is preparing for 10x more code to be shipped. A former Google Site Reliability Engineer (SRE) told me:
  
  "What I'm hearing from SRE friends is that they are preparing for 10x the lines of code making their way into production."
  
  If any company has data on the likely impact of AI tools, it's Google. 10x as much code generated will likely also mean 10x more: code review, deployments, feature flags, source control footprint and, perhaps, even bugs and outages, if not handled with care."
  
  Predicted enormous load increases were not secret knowledge within the industry, yet it seems GitHub was blissfully ignorant of their potential size. According to Vlad, GitHub did eventually plan for a need to increase capacity by 10x, but this was in October 2025, months later. In February 2026, the company is now adjusting that expectation to 30x. He wrote:
  
  "We started executing our plan to increase GitHub's capacity by 10X in October 2025 with a goal of substantially improving reliability and failover. By February 2026, it was clear that we needed to design for a future that requires 30X today's scale."
  
  There's also the question of whether GitHub miscalculated how much time it had to prepare for explosive load growth, and whether it was caught off guard when that growth materialized months sooner than expected at the start of this year.
  
  Given GitHub only started to prepare for a major load increase in October, its current problems are unsurprising. At the scale of GitHub, it's common enough for each team owning a service to plan a year ahead on how much load their service will have, and hardware resources like storage, VMs, and networking are allocated accordingly. Load planning can account for up to half of the preparations, and when reality doesn't conform to plans, some systems can struggle to scale up.
  
  So, on one hand, dealing with a 3.5x increase in load over 2 years should not be such a big deal for most services; especially not ones which can be horizontally scaled (when there's not much state, and scaling is achieved simply by adding new nodes.) But GitHub probably stores a lot more state with pull requests, workflows, projects, etc. This probably makes scaling more tricky when it comes to databases and systems running workflows.
  
  GitHub also has 18 years of tech debt on its hands, and thousands of staff to align as "organizational overhead." As its service load grows faster than before, responding is harder due to all that accumulated "debt":
  - Tech debt: many systems at the company are 10+ years old and are likely patched up, making them more difficult and risky to change
  - Organizational debt: around 4,000 people work at GitHub, of whom 1,000 are engineers. Teams have dependencies with each other, and even seemingly simple work can require dozens of engineers to work together
  - Customer expectations: GitHub cannot break customer workflows, even if doing so would mean changes to systems happen faster
  GitHub finds itself in the 'innovator's dilemma': the company became successful because it built developer workflows that made sense, pre-AI, and it used to be able to accurately forecast service load changes. But now that engineering teams' workflows include AI agents, GitHub's own workflows are not necessarily the best fit, and the company failed to forecast service-level changes.
  
  Other vendors floored by AI load? Not really
  
  One thing that doesn't add up about the situation is that other vendors who are presumably experiencing similar load spikes don't appear to be suffering with reliability issues as much. Vercel, Linear, Resend, Railway, Sentry, and other infra providers see record-level growth thanks to AI, but keep up with the load.
  
  Yes, it's true that AI vendors like Anthropic, OpenAI, and Cursor have some reliability issues, but it's not at the scale of GitHub's. GitHub's direct competitors, GitLab and Bitbucket, presumably see load going up similarly, but they're not going down as much.
  
  An obvious question is how much of GitHub 's pain is self-inflicted? With Microsoft as owner, it has more resources at its disposal than any competitor or startup, and yet failed to predict load increases and is too big to respond with the nimbleness of a startup.
  
  It's undeniable that solving for a major load increase is a hard challenge; it's when the difference between average and standout engineering teams is apparent. GitHub hasn't been responding like a world-class engineering org.
  
  GitHub alternatives?
  
  Every regular user of GitHub feels the pain of ongoing outages. As a dev, you can either hope Microsoft will eventually improve reliability, or seek alternatives. As covered above, Mitchell has chosen to quit and is currently deciding where to take Ghostty.
  
  The obvious alternatives are GitHub's biggest competitors, GitLab, and Bitbucket. Each offers Git hosting, and neither comes with the uptime woes that GitHub is suffering from.
  
  Self-hosted solutions are also an option, like self-hosting your git repo, or going with a self-hosted forge like Forgejo, which is an open source, local-first GitHub alternative.
  
  I also suspect that, soon enough, we'll see startups offering GitHub-like code hosting capabilities, while offering more robust uptime and being architected to handle the 30x-or-more scale which GitHub hopes one day to support.
  
  Read the full issue of last week 's The Pulse , or check out this week 's The Pulse . This week 's issue covers:
  1. Did Anthropic turn hostile on devs because capacity was running low?
  2. Amazon finally allows Claude Code and Codex usage
  3. Meta forcefully assigns engineers to data labelling ahead of job cuts
  4. New trend: small "AI-forward" teams
  5. Industry Pulse: why Meta tracks employees' computer activity, OpenAI starts to move off Datadog, Apple lets slip it uses Claude Code, GitHub -> Xbox transfers at Microsoft, VS Code inserted "coathored by Copilot" even when Copilot did nothing, analysis of the Coinbase layoffs
12. 🔗 r/wiesbaden Freitags essen gehen zu zweit? rss
  
  Moin würde gerne mit einer Freundin an einem Freitag in Wiesbaden essen gehen, es sollte gemütlich sein und nicht so laut. Also eine Atmosphäre haben die es her gibt das man sich gut unterhalten kann. Es sollte vegan/vegetarische Optionen geben. Ich wäre sehr dankbar für eure Tipps da ich mich nicht so gut auskenne.
  
  submitted by /u/JohnTheMonkey2
  [link] [comments]
13. 🔗 r/Leeds why is everyone in fancy dress? rss
  
  I'm in the city centre right now and just wondering why everyone is dressed up? I thought it was the otley run but now I'm unsure because the people in fancy dress are everywhere. This is just me being nosey but I can't find any info about it online so I was wondering if anyone knows.
  
  submitted by /u/MeowTS13
  [link] [comments]
14. 🔗 Simon Willison Notes on the xAI/Anthropic data center deal rss
  
  There weren't a lot of big new announcements from Anthropic at yesterday's Code w/ Claude event, but the biggest by far was the deal they've struck with SpaceX/xAI to use "all of the capacity of their Colossus data center".
  
  As I mentioned in my live blog of the keynote, that's the one with the particularly bad environmental record. The gas turbines installed to power the facility initially ran without Clean Air Act permits or pollution control devices, which they got away with by classifying them as "temporary". Credible reports link it to increases in hospital admissions relating to low air quality.
  
  Andy Masley, one of the most prolific voices pushing back against misleading rhetoric about data centers (see The AI water issue is fake and Data center land issues are fake), had this to say about Colossus:
  
  I would simply not run my computing out of this specific data center
  
  I get that Anthropic are severely compute-constrained, but in a world where the very existence of "AI data centers" is a red-hot political issue (see recent news out of Utah for a fresh example), signing up with this particular data center is a really bad look.
  
  There was a lot of initial chatter about how this meant xAI were clearly giving up on their own Grok models, since all of their capacity would be sold to Anthropic instead. That was a misconception - Anthropic are getting Colossus 1, but xAI are keeping their larger Colossus 2 data center for their own work.
  
  As an interesting side note, the night before the Anthropic announcement, xAI sent out a deprecation notice for Grok 4.1 Fast and several other models providing just two weeks' notice before shutdown, reported here by @xlr8harder from SpeechMap:
  
  This is terrible @xai. I just spent time and money to migrate to grok 4.1 fast, and you're disabling it with less than two weeks notice, after releasing it in November, with no migration path to a fast/cheap alternative.
  
  I will never depend on one of your products again.
  
  Here's SpeechMap's detailed explanation of how they selected Grok 4.1 Fast for their project in March.
  
  Were xAI serving those models out of Colossus 1?
  
  xAI owner Elon Musk (who previously delighted in calling Anthropic "Misanthropic") tweeted the following:
  
  By way of background for those who care, I spent a lot of time last week with senior members of the Anthropic team to understand what they do to ensure Claude is good for humanity and was impressed. [...]
  
  After that, I was ok leasing Colossus 1 to Anthropic, as SpaceXAI had already moved training to Colossus 2.
  
  And then shortly afterwards:
  
  Just as SpaceX launches hundreds of satellites for competitors with fair terms and pricing, we will provide compute to AI companies that are taking the right steps to ensure it is good for humanity.
  
  We reserve the right to reclaim the compute if their AI engages in actions that harm humanity.
  
  Presumably the criteria for "harm humanity" are decided by Elon himself. Sounds like a new form of supply chain risk for Anthropic to me!
  
  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.
15. 🔗 r/wiesbaden Erfahrungen mit Autohaus Can in Wiesbadener Str. ? rss
  
  Wer hat Erfahrung mit dem oben genannten Händler? Seriös oder nicht ?
  
  submitted by /u/HagebuddneLard
  [link] [comments]
16. 🔗 r/LocalLLaMA WARNING: Open-OSS/privacy-filter MALWARE rss
  
  There's this new "model" on Hugging Face titled Open-OSS/privacy-filter which is actually a customized infostealer virus. It's a fake version of the OpenAI privacy filter and it uses a Python-based dropper (loader.py) which downloads a malicious PowerShell command from the internet, which spawns another PowerShell command and downloads a shady EXE file and runs it using Task Scheduler.
  
  Here's a behavior analysis of what the EXE does: https://tria.ge/260507-tnftrsfx5x/behavioral1
  
  I also reported both the dropper and the EXE to Microsoft.
  
  I also reported the repo to HF.
  
  If you use Linux (which is easier to use for AI/ML) you are unaffected as this is a Windows virus.
  
  submitted by /u/charles25565
  [link] [comments]
17. 🔗 earendil-works/pi v0.73.1 release
  New Features
  - Self-update support for the npm scope migration : pi update --self now supports the upcoming package rename from @mariozechner/pi-coding-agent to @earendil-works/pi-coding-agent. After the new package is published, existing global installs can update through the normal self-update flow; pi will uninstall the old global package and install the package name returned by the version check endpoint.
  - Interactive OAuth login selection : OAuth providers can now present multiple login choices in /login, enabling provider-specific interactive authentication flows. See Providers.
  - JSONC-stylemodels.json parsing: models.json now allows comments and trailing commas, making custom provider and model configuration easier to maintain. See Providers and Custom Providers.
  Added
  - Added interactive login selection support so OAuth providers can present multiple login choices (#4190 by @mitsuhiko).
  Changed
  - Changed pi update --self to honor the active package name returned by the Pi version check endpoint, defaulting to the current package when omitted and uninstalling the old global package before installing a renamed package.
  - Changed extension loading to use upstream jiti 2.7 instead of the @mariozechner/jiti fork (#4244 by @pi0).
  - Changed models.json parsing to allow comments and trailing commas (#4162 by @julien-c).
  Fixed
  - Fixed pi -p treating prompts that start with YAML frontmatter as extension flags instead of user messages (#4163).
  - Fixed pending tool results not updating in the live TUI after toggling thinking block visibility while the tool is running (#4167).
  - Fixed /copy reporting success on Linux without writing the clipboard on Wayland-only compositors (Hyprland, Niri, ...) by skipping the X11-only native addon on Linux and routing through wl-copy/xclip/xsel instead (#4177).
  - Fixed HTML session exports to strip skill wrapper XML from rendered user messages (#4234 by @aliou).
  - Fixed OpenAI-compatible chat completion streams that interleave content and tool-call deltas in the same choice.
  - Fixed OpenAI Codex OAuth refresh failures writing directly to stderr while the TUI is active (#4141).
  - Fixed OpenAI Codex Responses requests to send a non-empty system prompt (#4184).
  - Fixed Kimi For Coding model resolution for the Kimi K2 P6 alias (#4218).
  - Fixed Kitty inline image redraws to stay within TUI-owned terminal regions and avoid writing below the active viewport.
  - Fixed Kitty inline image rendering by letting the terminal allocate image ids and bounding parsed image ids to valid values.
  - Fixed inline image capability detection to disable inline images in cmux terminals.
18. 🔗 r/Leeds Leeds cycle lane network is a 'step in the right direction', say campaigners rss
  
  Just wanted to add a bit of positivity around the new cycle lanes in Leeds, as there seems to be a lot of negativity whenever the topic comes up.
  
  Speaking from personal experience, they’ve genuinely changed my life for the better. Up until last year, I hadn’t really ridden a bike since I was a teenager. But after seeing more segregated cycle lanes appear around my area, I realised I could get from my house into the city centre in under 30 minutes almost entirely on protected infrastructure.
  
  I've started cycling regularly, and eventually I sold my car altogether. I now use my bike every other day for commuting, trips into town, canal rides etc etc. I’m healthier, happier, saving loads of money, and honestly enjoy getting around Leeds far more now. It's hilly in parts but stick to a low gear and it's perfectly manageable, ebikes are great alternatives too and can be purchased through the cycle to work schemes (I saved hundreds on my bike).
  
  I also cycle year-round, and I think people massively overestimate how “hardcore” cycling is in the UK. Our weather really isn’t that different from places like the Netherlands. Most of the time you’re completely fine with a decent jacket.
  
  I know the network still has gaps and improvements to make, but for me it’s been a massive step in the right direction and has made cycling feel accessible to normal people again, not just super confident road cyclists.
  
  Just wondering if anyone else has had a similar experience or enjoys using the bike lanes too?
  
  submitted by /u/_testingdude
  [link] [comments]
19. 🔗 jj-vcs/jj v0.41.0 release
  About
  
  jj is a Git-compatible version control system that is both simple and powerful. See
  the installation instructions to get started.
  
  Release highlights
  - jj fix now supports formatting specific line ranges (allowing you to format
    only modified lines); see the configuration manual and notes below for more.
  - The new global flag --no-integrate-operation will let you run a command without
    impacting the repo state or the working copy, which is useful when automated tools
    may create snapshots in the background.
  Breaking changes
  - The --pattern flag for file search now defaults to regex: instead of glob:.
  - jj git push --all/--tracked/-r REVSETS no longer fails when revisions to
    push are private or have conflicts. Bookmarks which aren't eligible to push
    will be skipped.
  - Branch/bookmark patterns passed to jj git clone are now saved to jj's repo
    settings file instead of .git/config. Git fetch refspecs are set to the
    default value.
  Deprecations
  - In the templating language, the Operation type's .tags() function has been
    deprecated in favor of .attributes().
  New features
  - The --pattern flag for file search now accepts various pattern kinds through
    kind:pattern syntax.
  - A new global flag --no-integrate-operation lets you run a command without
    impacting the repo state or the working copy.
  - A new config option diff.git.show-path-prefix can be used to suppress the
    a/ and b/ path prefixes in the diff --git output.
  - jj fix now supports line range-limited formatting via the fix.tools.<name>.line-range-arg
    and run-tool-if-zero-line-ranges configs. This allows running tools only on modified
    lines and fine-grained control over when the tool is run. If you have set the line-range-arg
    config, use --all-lines to match the previous behavior of formatting the entire file.
  - A new replace(pattern, content, replacement) template function is added
    which supports replacement of content in templates, using a lambda to format
    replacement text. It supports all string patterns, including regexes with
    capture groups (e.g. replace(regex:'(\w+) (\w+)', "hello world", |c| c.get(1) ++ " " ++ c.get(2))).
  - New ByteString template type for things like file content.
  - jj gerrit upload now supports the new options --message (-m), --edit
    and --merged. You can now also pass multiple hashtags by repeating the
    --hashtag option.
  - New remotes.<name>.fetch-bookmarks/fetch-tags options to configure
    default fetch targets.
  - JJ_PAGER can now override the ui.pager config, matching JJ_EDITOR for
    callers that need a jj-specific environment override.
  Fixed bugs
  - Improving consistency with git handling of .gitignore, including /
    after entries and \r\r\n for MacOS files.
  - jj status filters untracked paths by fileset
    #9287
  - Improved performance for snapshotting, visibly improving jj status
    speed for large repositories.
  - Pre-existing Git submodule directories are no longer considered conflicts in
    checkouts. #8065.
  - Fixed a panic in jj gerrit upload when run without -r and the
    inferred revision was immutable. #9398
  - jj status respects path filters in working copy summaries.
  - jj git remote rename/remove now updates the trunk() alias.
  - Commands would sometimes incorrectly diagnose a stale working copy and suggest
    running jj op integrate when it would have no effect. This should now be
    much less likely to happen in practice.
    #9314
  Contributors
  
  Thanks to the people who made this release happen!
  - Adrian Freund (@freundTech)
  - ase (@adamse)
  - Austin Seipp (@thoughtpolice)
  - Benjamin Tan (@bnjmnt4n)
  - Björn Kautler (@Vampire)
  - David Higgs (@higgsd)
  - David Rieber (@drieber)
  - dzaima (@dzaima)
  - Federico G. Schwindt (@fgsch)
  - Gaëtan Lehmann (@glehmann)
  - hewigovens (@hewigovens)
  - Ilya Grigoriev (@ilyagr)
  - jonmeow (@jonmeow)
  - Joseph Lou (@josephlou5)
  - Josh McKinney (@joshka)
  - Jun Mukai (@jmuk)
  - Lucas Garron (@lgarron)
  - Martin von Zweigbergk (@martinvonz)
  - Matt Stark (@matts1)
  - Maximilian Gaß (@mxey)
  - OlshaMB (@OlshaMB)
  - Philip Metzger (@PhilipMetzger)
  - rayaq
  - Remo Senekowitsch (@senekor)
  - rishiad (@rishiad)
  - Ryan Patterson (@CGamesPlay)
  - Sebastian Barfurth (@sbarfurth)
  - Thomas Axelsson (@thomasa88)
  - xtqqczze (@xtqqczze)
  - Yuya Nishihara (@yuja)
20. 🔗 r/reverseengineering VLC Media Player MKV Exploit Analysis rss
  
  submitted by /u/eshard-cybersec
  [link] [comments]
21. 🔗 r/york Different angles on one perfect subject 💫 rss
  
  | submitted by /u/Coffee000Oopss
  [link] [comments]
  ---|---
22. 🔗 r/LocalLLaMA Qwen3.6 27B uncensored heretic v2 Native MTP Preserved is Out Now With KLD 0.0021, 6/100 Refusals and the Full 15 MTPs Preserved and Retained, Available in Safetensors, GGUFs and NVFP4s formats. rss
  
  llmfan46/Qwen3.6-27B-uncensored-heretic-v2-Native-MTP-Preserved: https://huggingface.co/llmfan46/Qwen3.6-27B-uncensored-heretic-v2-Native-MTP- Preserved
  
  llmfan46/Qwen3.6-27B-uncensored-heretic-v2-Native-MTP-Preserved-GGUF: https://huggingface.co/llmfan46/Qwen3.6-27B-uncensored-heretic-v2-Native-MTP- Preserved-GGUF
  
  llmfan46/Qwen3.6-27B-uncensored-heretic-v2-Native-MTP-Preserved-NVFP4-GGUF: https://huggingface.co/llmfan46/Qwen3.6-27B-uncensored-heretic-v2-Native-MTP- Preserved-NVFP4-GGUF
  
  llmfan46/Qwen3.6-27B-uncensored-heretic-v2-Native-MTP-Preserved-NVFP4: https://huggingface.co/llmfan46/Qwen3.6-27B-uncensored-heretic-v2-Native-MTP- Preserved-NVFP4
  
  llmfan46/Qwen3.6-27B-uncensored-heretic-v2-Native-MTP-Preserved-NVFP4-MLP- Only: https://huggingface.co/llmfan46/Qwen3.6-27B-uncensored- heretic-v2-Native-MTP-Preserved-NVFP4-MLP-Only
  
  llmfan46/Qwen3.6-27B-uncensored-heretic-v2-Native-MTP-Preserved-GPTQ-Int4: https://huggingface.co/llmfan46/Qwen3.6-27B-uncensored-heretic-v2-Native-MTP- Preserved-GPTQ-Int4
  
  All are confirmed to have their full 15 MTPs retained and preserved.
  
  Comes with benchmark too.
  
  Find all my models here: HuggingFace- LLMFan46
  
  submitted by /u/LLMFan46
  [link] [comments]
23. 🔗 r/Leeds Does anyone else remember when you could buy cats at kirkgate market ? rss
  
  And pirated dad's,before 2010 and other crazy stuff or I'm I confusing it with the wrong place I'm pretty sure we got a cat from there some time in the 2000's but I could be wrong
  
  submitted by /u/TipAdditional4625
  [link] [comments]
24. 🔗 Console.dev newsletter honker rss
  
  Description: Durable queues for SQLite.
  
  What we like: Adds pub/sub, task queue, and event streams to SQLite. No need for client polling or a broker. Shipped as a SQLite extension with bindings for Python, Node, Rust, Go, Ruby, etc. Allows an INSERT and enqueue as part of the same transaction (with rollback). Also supports cron.
  
  What we dislike: Polling is via a SELECT per millisecond per database, which should be lightweight, but is an extra high-frequency query. Still experimental.
25. 🔗 Console.dev newsletter Plow rss
  
  Description: HTTP benchmarking.
  
  What we like: Runs HTTP requests and benchmarks latency and response codes. Configurable concurrency, duration, request count, and ramp up time. Outputs stats to the terminal in real time. Supports JSON output and provides a web UI.
  
  What we dislike: Pretty straightforward HTTP request support, including different methods e.g. POST (with body). For more complex benchmarks, k6 is a good, scriptable alternative.
May 06, 2026
1. 🔗 IDA Plugin Updates IDA Plugin Updates on 2026-05-06 rss
  IDA Plugin Updates on 2026-05-06
  
  Activity:
  - hrtng
    
    f830fda5: "Jump to visited indirect call… (Shift-J)" removed as duplicate, no…
  - idafridascript
    
    222a9114: docs(readme): :memo: update MCP server configuration format in README…
  - sharingan
    
    1feae0e0: organize file & folder
2. 🔗 r/Leeds Anybody in Leeds that can help get hired? rss
  
  I have administrative experience, hospitality, customer service exec experience. Overseas experience with places like hotels and holiday parks.
  
  Im really trying to get anything cash in hand or full time contract literally any job as long as im getting the hours every week and not being blown off.
  
  The jobs could literally be anything I genuinly have no ego when it comes to the title or the work im doing, im almost 20 and im about to be cooked by the system from the outside looking in.
  
  Feels like im running out of time to build something out of myself, and the bills gotta be paid.
  
  submitted by /u/BeingRemarkable2117
  [link] [comments]
3. 🔗 backnotprop/plannotator v0.19.10 release
  Follow @plannotator on X for updates
  
  Missed recent releases? Release | Highlights
  ---|---
  v0.19.9 | OpenCode user-managed workflow, Pi model switch fix, Codex skill install, shimmer removal
  v0.19.8 | 49 themes with syntax highlighting, keyboard shortcut registry, smart code-file path validation, remote URL notifications
  v0.19.7 | Codex Stop-hook plan review, Codex skills, sidebar auto-close, file tree context menu
  v0.19.6 | Non-blocking Pi browser sessions, agent picker dropdown for OpenCode, annotate-last file resolution fix
  v0.19.5 | All-files diff view, clickable code file paths, server-side hide whitespace, non-ASCII path support
  v0.19.4 | All-files diff type, code file viewer, hide whitespace, quick-settings popover
  v0.19.3 | Configurable feedback messages, hide merged PRs in stacked PR selector
  v0.19.2 | Stacked PR review, source line numbers in feedback, diff type dialog re-show, ghost dot removal, docs cleanup
  v0.19.1 | Hook-native annotation, custom base branch, OpenCode workflow modes, quieter plan diffs, anchor navigation
  v0.19.0 | Code Tour agent, GitHub-flavored Markdown, copy table as Markdown/CSV, flexible Pi planning mode, session-log ancestor-PID walk
  v0.18.0 | Annotate focus & wide modes, OpenCode origin detection, word-level inline plan diff, Markdown content negotiation, color swatches
  v0.17.10 | HTML and URL annotation, loopback binding by default, Safari scroll fix, triple-click fix, release pipeline smoke tests
  
  What's New in v0.19.10
  
  v0.19.10 reverts an unreviewed permission mode change that shipped in v0.19.9. The bypass-with-clear-reminder feature (PR #668) relied on Claude Code surfacing systemMessage from hook output, which it does not currently support. That PR has been fully reverted. All other v0.19.9 changes remain intact.
  
  Reverted: Bypass Permissions with /clear Reminder
  
  PR #668 added a synthetic bypassPermissionsClearReminder permission mode that was supposed to emit a system message reminding users to run /clear after plan approval. Testing revealed that Claude Code does not surface systemMessage fields from hook output to the conversation, so the feature had no visible effect. The entire PR has been reverted to avoid shipping dead UI options.
  
  Users on v0.19.9 who selected the "Bypass + /clear Reminder" mode in Settings will fall back to the default permission mode ("Accept Edits") after updating.
  
  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".
  
  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
  - revert: remove bypass clear reminder permission mode (#668) by @backnotprop in 49c55e6
  Full Changelog : v0.19.9...v0.19.10
4. 🔗 backnotprop/plannotator v0.19.9 release
  Follow @plannotator on X for updates
  
  Missed recent releases? Release | Highlights
  ---|---
  v0.19.8 | 49 themes with syntax highlighting, keyboard shortcut registry, smart code-file path validation, remote URL notifications
  v0.19.7 | Codex Stop-hook plan review, Codex skills, sidebar auto-close, file tree context menu
  v0.19.6 | Non-blocking Pi browser sessions, agent picker dropdown for OpenCode, annotate-last file resolution fix
  v0.19.5 | All-files diff view, clickable code file paths, server-side hide whitespace, non-ASCII path support
  v0.19.4 | All-files diff type, code file viewer, hide whitespace, quick-settings popover
  v0.19.3 | Configurable feedback messages, hide merged PRs in stacked PR selector
  v0.19.2 | Stacked PR review, source line numbers in feedback, diff type dialog re-show, ghost dot removal, docs cleanup
  v0.19.1 | Hook-native annotation, custom base branch, OpenCode workflow modes, quieter plan diffs, anchor navigation
  v0.19.0 | Code Tour agent, GitHub-flavored Markdown, copy table as Markdown/CSV, flexible Pi planning mode, session-log ancestor-PID walk
  v0.18.0 | Annotate focus & wide modes, OpenCode origin detection, word-level inline plan diff, Markdown content negotiation, color swatches
  v0.17.10 | HTML and URL annotation, loopback binding by default, Safari scroll fix, triple-click fix, release pipeline smoke tests
  v0.17.9 | Hotfix: pin Bun to 1.3.11 for macOS binary codesign regression
  
  What's New in v0.19.9
  
  v0.19.9 adds a user-managed workflow mode for OpenCode, fixes model switching in Pi's plan approval flow, and introduces a bypass-with-reminder permission mode for Claude Code. Five PRs total, two from first-time contributors.
  
  User-Managed Workflow Mode for OpenCode
  
  OpenCode's plugin previously offered two extremes: manual (slash commands only, no submit_plan tool) and plan-agent/all-agents (full automation with prompt injection and permission overrides). Users who wanted the submit_plan tool without Plannotator modifying their system prompts or agent configuration had no middle ground.
  
  The new user-managed workflow mode fills that gap. It registers the submit_plan tool and all slash commands, but does not inject planning prompts, rewrite tool definitions, or modify OpenCode's agent configuration. Users manage their own prompts and permissions, and Plannotator stays out of the way. To enable it, set workflow: "user-managed" in your opencode.json plugin options.
  
  Existing configurations are unaffected. The default remains plan-agent, and unknown workflow strings continue to fall back to it.
  - #667 by @saksmt, closing #666
  Pi Model Switch on Plan Approval
  
  When Pi users configured separate models for planning and execution (e.g., think with one model, execute with another), approving a plan was supposed to switch to the execution model. It didn't. Pi snapshots its model selection at the start of each agent.prompt() call, so calling pi.setModel() mid-loop had no effect until the next user-initiated turn. The user had to manually prompt the agent after every approval to trigger the switch.
  
  The fix terminates the current agent loop on plan approval by returning terminate: true from the tool response, then uses a deferred sendUserMessage in the agent_end handler to start a fresh turn that picks up the executing model. Execution now continues automatically on the correct model without manual intervention.
  - #677 by @backnotprop, closing #674 (reported by @snowmead)
  Bypass Permissions with /clear Reminder
  
  Claude Code's bypass-permissions mode skips the permission prompt on plan approval, but users often forget to run /clear afterward to reset context. A new "Bypass + /clear Reminder" option in the permission mode dropdown pairs bypass-permissions with a system message nudging the user to clear context after approval.
  
  The mode is available in both the Settings dropdown and the Approve button's extra options. It decomposes to the standard bypassPermissions wire value plus a clearContextNudge flag, so the hook output format is unchanged. Cookie validation was also hardened in this PR: stale or invalid permission mode values now safely fall back to the default instead of flowing through unchecked.
  - #668 by @AgileInnov8tor
  Additional Changes
  - Remove shimmer animation from clickable file paths. The repeating shimmer on .code-file-link elements was distracting while reading plans. File path links now render as normal inline code with cursor and hover cues only. (#676 by @backnotprop, closing #672 reported by @academo)
  - Install Plannotator command skills under Codex home. The installer now places command-overlap skills (plannotator-review, plannotator-annotate, plannotator-last) in ~/.codex/skills/ when Codex is detected, and keeps shared-agent skills in ~/.agents/skills/. Stale cross-scope copies are cleaned up, and a ~/.codex/skills/ directory created by a previous install no longer triggers false Codex detection. (#669 by @backnotprop)
  - Avoid Pi bundled skill conflicts. The installer configures Pi's settings.json to disable bundled Plannotator skills when shared global skills are already installed, eliminating "duplicate skill" warnings. BOM-free UTF-8 writes on Windows prevent encoding issues with Pi's JSON parser.
  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".
  
  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(opencode-plugin): add user-managed workflow mode by @saksmt in #667
  - feat: expose bypass clear reminder permission mode by @AgileInnov8tor in #668
  - fix: install Plannotator command skills under Codex home by @backnotprop in #669
  - fix(ui): remove shimmer animation from clickable file paths by @backnotprop in #676
  - fix(pi): terminate agent loop on plan approval so model switch takes effect by @backnotprop in #677
  New Contributors
  - @saksmt made their first contribution in #667
  - @AgileInnov8tor made their first contribution in #668
  Contributors
  
  @saksmt identified the gap between OpenCode's manual and automated workflow modes and contributed the user-managed option (#667), giving users fine-grained control over prompt injection and tool registration. First contribution to the project.
  
  @AgileInnov8tor built the bypass-with- clear-reminder permission mode (#668), including the synthetic mode decomposition, cookie validation hardening, and the live settings sync fix. First contribution to the project.
  
  Community members whose reports drove fixes in this release:
  - @snowmead: #674 (Pi model switch not taking effect on plan approval)
  - @academo: #672 (shimmer animation distracting on file path links)
  Full Changelog : v0.19.8...v0.19.9
5. 🔗 r/Harrogate Harrogate Traffic Relief rss
  
  The traffic in and around Harrogate is a joke, and has been commented on for as long as I can remember.
  
  but I’m curious, I’ve no idea how to solve it so what are people’s suggestions? It seems to me there’s just no where to speed flow or reroute around bottlenecks.
  
  Better busses? By-passes? How do we fix it?
  
  submitted by /u/CyclePrevious9043
  [link] [comments]
6. 🔗 anthropics/claude-code v2.1.132 release
  What's changed
  - Added CLAUDE_CODE_SESSION_ID environment variable to the Bash tool subprocess environment, matching the session_id passed to hooks
  - Added CLAUDE_CODE_DISABLE_ALTERNATE_SCREEN=1 env var to opt out of the fullscreen alternate-screen renderer and keep the conversation in the terminal's native scrollback
  - Added a "Pasting…" footer hint while a Ctrl+V image paste is being read from the clipboard
  - Fixed external SIGINT (e.g. IDE stop button, kill -INT) not running graceful shutdown — terminal modes are now restored and the --resume hint is printed instead of an abrupt exit
  - Fixed an uncaught exception when the terminal is closed or SSH disconnects mid-session under the native build
  - Fixed --resume failing with no low surrogate in string when a tool error truncation split an emoji; pre-corrupted sessions are sanitized on load
  - Fixed --permission-mode flag being ignored when resuming a plan-mode session with -p --continue/--resume, and plan mode not being re-applied after ExitPlanMode within the same session
  - Fixed fullscreen mode showing a blank screen after laptop sleep/wake or Ctrl+Z/fg until the next keystroke or stream output
  - Fixed cursor landing mid-grapheme on Ctrl+E/A/K/U/arrow keys when an Indic conjunct or ZWJ emoji wraps across lines
  - Fixed vim operators corrupting text containing decomposed (NFD) accented characters
  - Fixed pasting text starting with / silently swallowing the input or triggering an unknown-command reply
  - Fixed pasting dumping stray escape sequences into the prompt when focus events or mouse-tracking reports interleave with the bracketed paste
  - Fixed mouse wheel scrolling being too fast in Cursor and VS Code 1.92–1.104 due to an upstream xterm.js bug
  - Fixed scroll-wheel handling in JetBrains IDE 2025.2 terminals (spurious arrow keys, wrong-direction events, runaway acceleration)
  - Fixed /usage Ctrl+S hanging when copying the stats screenshot to the clipboard on Linux/X11
  - Fixed /terminal-setup showing a contradictory error in Windows Terminal — Shift+Enter is natively supported there
  - Fixed /effort picker not reflecting the CLAUDE_CODE_EFFORT_LEVEL env var override
  - Fixed /status showing the wrong default model for some users
  - Fixed slash command autocomplete popup being capped at ~3–5 visible commands instead of scaling with terminal height
  - Fixed statusline context_window token counts reflecting cumulative session totals instead of current context usage
  - Fixed Alt+T (thinking toggle) not working on macOS terminals without "Option as Meta" enabled (iTerm2, Terminal.app defaults)
  - Fixed dead keyboard input on Windows after re-opening a background session from claude agents
  - Fixed unbounded memory growth (10GB+ RSS) when a stdio MCP server writes non-protocol data to stdout
  - Fixed MCP servers that connect but fail tools/list silently showing 0 tools — they now retry once and show "connected · tools fetch failed" in /mcp
  - Fixed unauthorized claude.ai MCP connectors showing as "failed" instead of "needs auth", and headless -p mode retrying non-transient 4xx connection failures
  - Improved visual consistency in slash command dialogs and /login, /upgrade, /extra-usage dialog spacing
  - Updated the /tui fullscreen startup banner to describe additional renderer benefits (lower memory usage, mouse support, auto-copy on select)
  - Fixed Bedrock and Vertex 400 errors when ENABLE_PROMPT_CACHING_1H is set
7. 🔗 Jeremy Fielding (YouTube) Wall-E Is Getting Complicated. rss
  
  If you want to join my community of makers and Tinkers consider getting a YouTube membership 👉 https://www.youtube.com/@JeremyFieldingSr/join
  
  If you want to chip in a few bucks to support these projects and teaching videos, please visit my Patreon page or Buy Me a Coffee. 👉 https://www.patreon.com/jeremyfieldingsr 👉 https://www.buymeacoffee.com/jeremyfielding
  
  Social media, websites, and other channel
  
  Instagram https://www.instagram.com/jeremy_fielding/?hl=en Twitter 👉https://twitter.com/jeremy_fielding TikTok 👉https://www.tiktok.com/@jeremy_fielding0 LinkedIn 👉https://www.linkedin.com/in/jeremy-fielding-749b55250/ My websites 👉 https://www.jeremyfielding.com 👉https://www.fatherhoodengineered.com My other channel Fatherhood engineered channel 👉 https://www.youtube.com/channel/UC_jX1r7deAcCJ_fTtM9x8ZA
  
  Notes:
  
  Technical corrections
  
  Nothing yet
8. 🔗 @HexRaysSA@infosec.exchange New training updates, plus Spring discounts: mastodon
  
  New training updates, plus Spring discounts:
  • On-demand Starter → 20% off with code STR20
  • AI-powered Intermediate → 40% off (May 12) with code AI-INTER40
  • Malware, Decompiler & Programming → 30% off with code SPRING30
  
  Details + course breakdown: https://hex-rays.com/blog/spring-training- sale-2026
  *Limited time offer, check blog for expiration dates!
9. 🔗 r/LocalLLaMA ZAYA1-8B: Frontier intelligence density, trained on AMD rss
  
  | submitted by /u/carbocation
  [link] [comments]
  ---|---
10. 🔗 r/york Moving back - flat hunting rss
  
  I'm coming home! So excited to be moving back but slightly worried about finding a flat after a few years abroad. I know the drill since the last time I lived there, but wanted to see if anything has changed - do things still move at the speed of light - by the time something hits Rightmove, it's already full of viewings and likely to be gone tomorrow - is that still the case?
  
  I can't remember what month most student lets turn over / when the most availability is...? (I know the new system may impact this)
  
  Should I just book a hotel and wait till I'm in town to sort out viewings? (and trust I'll find somewhere within a week?)
  
  Budget is 1.1-1.5k, would like to be relatively near the uni. I know the dust is still settling from the new Renters' rights and I've read so many posts on here about where to look/ agents to avoid etc, but curious how things feel locally lately.
  
  Last but not least - any anecdotes for getting pets approved since the rule changes? Any differences between getting a cat approved (vs dogs)?
  
  Thanks!
  
  submitted by /u/fruitloopfitness
  [link] [comments]
11. 🔗 r/Leeds Does anyone remember Toyworld Megastore? rss
  
  As a kid I loved this toy shop, it was on the Headrow, attached to the Headrow Shopping Centre (later turned into the core, now demolished) and was to right of the entrance, which the same unit later became GAME. It seems to have had a very short lifespan, opening and closing in the mid 2000s but having another store on the top floor of the Headrow Shopping centre in the 90s.
  
  Some of the only info I can find online, is my own reddit post from 3 years ago, https://www.reddit.com/r/Leeds/comments/z57afp/does_anyone_remember_toyworld_megastore/
  
  I'd love to find a photo of the store, or literally any info/memories - it's basically all gone and I'm so annoyed at myself for not having saved the one photo that existed 3 years ago.
  
  Thank you in advance!
  
  submitted by /u/Same_Ability3423
  [link] [comments]
12. 🔗 r/Yorkshire Silktone Waggonway rss
  
  | I create short history forgotten videos around Yorkshire and specifically Barnsley, here's my latest short Silkstone Waggonway submitted by /u/9arke1
  [link] [comments]
  ---|---
13. 🔗 Hex-Rays Blog New Training Formats, New Workflows, New Skills rss
  
  We’ve made meaningful updates to our training lineup with the introduction of a new on-demand format for beginners, integration of AI into our Intermediate course, and expanded hands-on content across advanced trainings.
14. 🔗 Simon Willison Live blog: Code w/ Claude 2026 rss
  
  I'm at Anthropic's Code w/ Claude event today. Here's my live blog of the morning keynote sessions.
  
  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.
15. 🔗 r/Leeds An afternoon in Leeds. rss
  
  Today I got a lovely change of pace, a hot tap in Leeds just 2 miles from where I live which is great because I've been perpetually up near Consett and Seal Sands sorting out P11's and staying in impersonal hotels and pubs.
  
  So I had a wander into Leeds City Centre on a weekday after sorting out the permits, the change of pace compared to the weekend is huge. Its been years since I've been into Leeds during the week for leisure.
  
  Found it nice to just wander, Im just having a coffee in the indoor market. My wife's coming through after she finishes work and Im treating us to Blue Sakura.
  
  Just some aimless musing. Leeds is a good place and it deserves some aimless musing over a nice coffee.
  
  submitted by /u/EdwardJSuperman
  [link] [comments]
16. 🔗 r/LocalLLaMA None of this will ever get stolen rss
  
  | It's crazy that they're thinking of doing this. There are problems with people stealing catalytic converters off people's cars and now they want to put a rack outside your house!? submitted by /u/martin_xs6
  [link] [comments]
  ---|---
17. 🔗 r/york Lost keys rss
  
  I lost a set of keys with a black carabiner on them, two old style keys and one modern one, within the nunnery lane area.
  
  Any leads?
  I'm really worried😓
  
  submitted by /u/soupygirls
  [link] [comments]
18. 🔗 Simon Willison Vibe coding and agentic engineering are getting closer than I'd like rss
  
  I recently talked with Joseph Ruscio about AI coding tools for Heavybit's High Leverage podcast: Ep. #9, The AI Coding Paradigm Shift with Simon Willison. Here are some of my highlights, including my disturbing realization that vibe coding and agentic engineering have started to converge in my own work.
  
  One thing I really enjoy about podcasts is that they sometimes push me to think out loud in a way that exposes an idea I've not previously been able to put into words.
  
  Vibe coding and agentic engineering are starting to overlap
  
  A few weeks after vibe coding was first coined I published Not all AI-assisted programming is vibe coding (but vibe coding rocks), where I firmly staked out my belief that "vibe coding" is a very different beast from responsible use of AI to write code, which I've since started to call agentic engineering.
  
  When Joseph brought up the distinction between the two I had a sudden realization that they're not nearly as distinct for me as they used to be:
  
  Weirdly though, those things have started to blur for me already, which is quite upsetting.
  
  I thought we had a very clear delineation where vibe coding is the thing where you're not looking at the code at all. You might not even know how to program. You might be a non-programmer who asks for a thing, and gets a thing, and if the thing works, then great! And if it doesn't, you tell it that it doesn't work and cross your fingers.
  
  But at no point are you really caring about the code quality or any of those additional constraints. And my take on vibe coding was that it's fantastic, provided you understand when it can be used and when it can't.
  
  A personal tool for you, where if there's a bug it hurts only you, go ahead!
  
  If you're building software for other people, vibe coding is grossly irresponsible because it's other people's information. Other people get hurt by your stupid bugs. You need to have a higher level than that.
  
  This contrasts with agentic engineering where you are a professional software engineer. You understand security and maintainability and operations and performance and so forth. You're using these tools to the highest of your own ability. I'm finding the scope of challenges I can take on has gone up by a significant amount because I've got the support of these tools.
  
  But I'm still leaning on my 25 years of experience as a software engineer.
  
  The goal is to build high quality production systems: if you're building lower quality stuff faster, I think that's bad. I want to build higher quality stuff faster. I want everything I'm building to be better in every way than it was before.
  
  The problem is that as the coding agents get more reliable, I'm not reviewing every line of code that they write anymore, even for my production level stuff.
  
  I know full well that if you ask Claude Code to build a JSON API endpoint that runs a SQL query and outputs the results as JSON, it's just going to do it right. It's not going to mess that up. You have it add automated tests, you have it add documentation, you know it's going to be good.
  
  But I'm not reviewing that code. And now I've got that feeling of guilt: if I haven't reviewed the code, is it really responsible for me to use this in production?
  
  The thing that really helps me is thinking back to when I've worked at larger organizations where I've been an engineering manager. Other teams are building software that my team depends on.
  
  If another team hands over something and says, "hey, this is the image resize service, here's how to use it to resize your images"... I'm not going to go and read every line of code that they wrote.
  
  I'm going to look at their documentation and I'm going to use it to resize some images. And then I'm going to start shipping my own features. And if I start running into problems where the image resizer thing appears to have bugs or the performance isn't good, that's when I might dig into their Git repositories and see what's going on. But for the most part I treat that as a semi-black box that I don't look at until I need to.
  
  I'm starting to treat the agents in the same way. And it still feels uncomfortable, because human beings are accountable for what they do. A team can build a reputation. I can say "I trust that team over there. They built good software in the past. They're not going to build something rubbish because that affects their professional reputations."
  
  Claude Code does not have a professional reputation! It can't take accountability for what it's done. But it's been proving itself anyway - time and time again it's churning out straightforward things and doing them right in the style that I like.
  
  There's an element of the normalization of deviance here - every time a model turns out to have written the right code without me monitoring it closely there's a risk that I'll trust it at the wrong moment in the future and get burned.
  
  The new challenge of evaluating software
  
  It used to be if you found a GitHub repository with a hundred commits and a good readme and automated tests and stuff, you could be pretty sure that the person writing that had put a lot of care and attention into that project.
  
  And now I can knock out a git repository with a hundred commits and a beautiful readme and comprehensive tests of every line of code in half an hour! It looks identical to those projects that have had a great deal of care and attention. Maybe it is as good as them. I don't know. I can't tell from looking at it. Even for my own projects, I can't tell.
  
  So I realized what I value more than the quality of the tests and documentation is that I want somebody to have used the thing. If you've got a vibe coded thing which you have used every day for the past two weeks, that's much more valuable to me than something that you've just spat out and hardly even exercised.
  
  The bottlenecks have shifted
  
  If you can go from producing 200 lines of code a day to 2,000 lines of code a day, what else breaks? The entire software development lifecycle was, it turns out, designed around the idea that it takes a day to produce a few hundred lines of code. And now it doesn't.
  
  It's not just the downstream stuff, it's the upstream stuff as well. I saw a great talk by Jenny Wen, who's the design leader at Anthropic, where she said we have all of these design processes that are based around the idea that you need to get the design right - because if you hand it off to the engineers and they spend three months building the wrong thing, that's catastrophic.
  
  There's this whole very extensive design process that you put in place because that design results in expensive work. But if it doesn't take three months to build, maybe the design process can be a whole lot riskier because cost, if you get something wrong, has been reduced so much.
  
  Why I'm still not afraid for my career
  
  When I look at my conversations with the agents, it's very clear to me that this is moon language for the vast majority of human beings.
  
  There are a whole bunch of reasons I'm not scared that my career as a software engineer is over now that computers can write their own code, partly because these things are amplifiers of existing experience. If you know what you're doing, you can run so much faster with them. [...]
  
  I'm constantly reminded as I work with these tools how hard the thing that we do is. Producing software is a ferociously difficult thing to do. And you could give me all of the AI tools in the world and what we're trying to achieve here is still really difficult. [...]
  
  Matthew Yglesias, who's a political commentator, yesterday tweeted, "Five months in, I think I've decided that I don't want to vibecode — I want professionally managed software companies to use AI coding assistance to make more/better/cheaper software products that they sell to me for money." And that feels about right to me. I can plumb my house if I watch enough YouTube videos on plumbing. I would rather hire a plumber.
  
  On the threat to SaaS providers of companies rolling their own solutions instead:
  
  I just realized it's the thing I said earlier about how I only want to use your side project if you've used it for a few weeks. The enterprise version of that is I don't want a CRM unless at least two other giant enterprises have successfully used that CRM for six months. [...] You want solutions that are proven to work before you take a risk on them.
  
  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.
19. 🔗 r/reverseengineering pyghidra-mcp Meets Ghidra GUI: Drive Project-Wide RE with Local AI rss
  
  submitted by /u/onlinereadme
  [link] [comments]
20. 🔗 r/york York station gateway what do you think? rss
  
  | submitted by /u/Coffee000Oopss
  [link] [comments]
  ---|---
21. 🔗 r/Leeds I bought a job lot of antique postcards from Leeds off eBay rss
  
  When I saw 50 antique postcards of Leeds on eBay for £20 it was was a no brainer of a buy!
  
  Most date to the first decade of the 20th century and they include lovely, stylised images of streets that look so familiar but also very different. Some also have messages on the back, frankly irrisitable to a nosy person such as myself.
  
  I've posted a gallery of some of the best ones on my Leeds history newsletter, Bury the Leeds, which is free to read and to subscribe to.
  
  https://burytheleeds.substack.com/p/looking-back-at-leeds-through-antique
  
  My favourite is the image of Headingley from 1909 which includes the beast of a stump of the Shire Oak, an ancient tree that was said to have stood on Otley Road for 1,000 years. By the 20th century, only a hulking stump remained before that was destroyed during a storm in 1941. The Original Oak pub is named after it and so is the Skyrack, which is an old timey derivation of 'Shire Oak'.
  
  I also love the one of the fashionable ladies promenading down Woodhouse Moor in 1904 and the very evocative shots of Briggate and Boar Lane, when trams ruled. You can really imagine how these busy streets must have sounded back then.
  
  I'm giving the postcards away with a book I've made featuring some of my most interesting and unusual stories about the city. I know several r/Leeds redditors have ordered copies. I'm celebrating one year of this project now so thanks for the support and to the mods!
  
  submitted by /u/bluetrainlinesss
  [link] [comments]
22. 🔗 r/LocalLLaMA Bad news: Apple drops high-memory Mac Studio configs rss
  
  | Looks like Apple has quietly killed off the higher-memory Mac Studio options. The M3 Ultra Mac Studio is now only available with 96GB RAM. The 512GB option was already removed back in March, and now the 256GB config is gone too. Apple has said both the Mac Studio and Mac mini will stay supply-constrained for the next few months. The Mac mini is also stuck at 48GB RAM max for now. Probably their high-memory chip stock got too expensive to keep producing. This is a real bummer for us! Big unified memory configs were one of the few (relatively) affordable ways to run large models locally. I am glad I own the M3 Utlra 512, will definitely keep this on (my favorite local model is Qwen 397b atm). submitted by /u/jzn21
  [link] [comments]
  ---|---
23. 🔗 r/Yorkshire Please get out there and vote May 7th (tomorrow.) rss
  
  The North is often neglected by the government, so the best chance that YOU have to get the work done in your area is by voting in the local election tomorrow.
  
  If you don’t know who to vote, do your research and see who aligns more with your community. Vote based on who you believe will help your local area the most.
  
  This isn’t a political soapbox post, I won’t tell you who to vote for. Just please, use your voice. There are a lot of cunts who just wanna use your seat and sit on it, and nothing will ever change. This is an important election with a lot of new voices who could genuinely help your local ward. I wish the best for your local area in the next 4 years and that’s why i’m making this post!
  
  We don’t get a lot of chances to enact change, so it’s best to use it when we can.
  
  submitted by /u/coolfunkDJ
  [link] [comments]
24. 🔗 Anton Zhiyanov Solod v0.1: Go ergonomics, practical stdlib, native C interop rss
  Solod (So) is a system-level language with Go syntax and zero runtime. It's designed for two main audiences:
  - Go developers who want low-level control and zero-cost C interop, without having to learn a new language or standard library.
  - C developers who like Go's style.
  The initial version (let's call it v0) was focused on picking a subset of Go and translating it to C. The next logical step was to port Go's standard library and make it easier to interop with C. That's what the v0.1 release I'm presenting today is all about.
  
  Standard library • SQLite bindings • Persistent map • Store and retrieve • Command-line interface • Performance • Wrapping up
  
  Standard library
  
  Solod v0.1 ships with the following stdlib packages ported from Go:
  - io, bufio, and fmt — Abstractions and types for general-purpose I/O.
  - bytes, strings, strconv, and unicode/utf8 — Common byte and text operations.
  - slices and maps — Generic heap-allocated data structures.
  - crypto/rand and math/rand — Generating random data.
  - flag, os, and path — Working with the command line and files.
  - log/slog — Structured logging.
  - time — Measuring and displaying time.
  And a couple of its own packages:
  - mem — Memory allocation with a pluggable allocator interface.
  - c — Low-level C interop helpers.
  Stdlib documentation
  
  In the following sections, I'll demonstrate some of the v0.1 features using a simple example: a persistent key-value store backed by SQLite.
  
  SQLite bindings
  
  Since So doesn't provide database/sql yet, we'll call SQLite directly through its C API. To do this, let's import the necessary headers with the so:include directive and generate extern declarations using the sobind tool:
```
package main

import "solod.dev/so/c"

//so:include <sqlite3.h>

// SQLite constants.
//
//so:extern SQLITE_OK
const sqliteOK = 0
//so:extern SQLITE_ROW
const sqliteRow = 100
//so:extern SQLITE_DONE
const sqliteDone = 101

// SQLite types.
//
//so:extern
type sqlite3 struct{}
//so:extern
type sqlite3_stmt struct{}
//so:extern
type sqlite3_value struct{}
//so:extern
type sqlite3_callback func(any, int32, **c.Char, **c.Char) int32

// SQLite functions.
func sqlite3_open(filename string, ppDb **sqlite3) int32
func sqlite3_prepare_v2(db *sqlite3, zSql string, nByte int32, ppStmt **sqlite3_stmt, pzTail **c.ConstChar) int32
func sqlite3_step(arg0 *sqlite3_stmt) int32
func sqlite3_finalize(pStmt *sqlite3_stmt) int32
func sqlite3_close(arg0 *sqlite3) int32
func sqlite3_exec(arg0 *sqlite3, sql string, callback sqlite3_callback, arg3 any, errmsg **c.Char) int32

// more declarations...
```
  The so:extern directive is required for constants (sqliteOK) and types (sqlite3_stmt). As for functions (sqlite3_prepare_v2), we can just declare them without a body — the transpiler will treat them as extern declarations even without so:extern.
  
  Persistent map
  
  With the SQLite API in place, let's implement a key-value type that wraps the database connection:
```
// SQLMap is a simple key-value store backed by an SQLite database.
type SQLMap struct {
    db *sqlite3
}
```
  Add a constructor that connects to an SQLite database and creates a table to store the items:
```
var ErrCreate = errors.New("sqlmap: create schema failed")
const sqlCreate = "create table if not exists kv (key text primary key, val)"

// NewSQLMap creates a new SQLMap using the provided connection string.
// It opens a connection to the SQLite database and creates the underlying
// key-value table if it does not already exist.
//
// The caller is responsible for calling Close on the returned SQLMap
// when it is no longer needed.
func NewSQLMap(connStr string) (SQLMap, error) {
    var db *sqlite3
    rc := sqlite3_open(connStr, &db)
    if rc != sqliteOK {
        return SQLMap{}, ErrCreate
    }

    rc = sqlite3_exec(db, sqlCreate, nil, nil, nil)
    if rc != sqliteOK {
        sqlite3_close(db)
        return SQLMap{}, ErrCreate
    }
    return SQLMap{db}, nil
}

// Close releases resources associated with the SQLMap.
func (m *SQLMap) Close() {
    sqlite3_close(m.db)
}
```
  As you can see, this So code looks a lot like regular Go code. However, there are some key differences:
  - When compiled, the code is first translated to plain C, then compiled into a native binary using GCC or Clang.
  - Unlike Go, there is no runtime (no automatic heap memory allocation, no garbage collection, no goroutine scheduler).
  - There is no overhead when calling C functions, unlike Go's Cgo.
  - The interop syntax is a bit cleaner. For example, Go's string (sqlCreate in the sqlite3_exec call) automatically decays to C's const char*.
  Store and retrieve
  
  First, let's implement the Set method:
```
var (
    ErrPrepare = errors.New("sqlmap: prepare failed")
    ErrExec    = errors.New("sqlmap: exec failed")
)

const sqlSet = "insert or replace into kv (key, val) values (?, ?)"

// Set stores a string value for the specified key.
func (m *SQLMap) Set(key string, val string) error {
    var stmt *sqlite3_stmt
    rc := sqlite3_prepare_v2(m.db, sqlSet, -1, &stmt, nil)
    if rc != sqliteOK {
        return ErrPrepare
    }
    defer sqlite3_finalize(stmt)

    sqlite3_bind_text(stmt, 1, key, int32(len(key)), nil)
    sqlite3_bind_text(stmt, 2, val, int32(len(val)), nil)

    rc = sqlite3_step(stmt)
    if rc != sqliteDone {
        return ErrExec
    }
    return nil
}
```
  No surprises here, just a bunch of SQLite API calls.
  
  The Get method is more interesting:
```
var ErrNotFound = errors.New("sqlmap: not found")
const sqlGet = "select val from kv where key = ?"

// Get returns the value associated with the specified key.
// The caller owns the returned string and must free it with mem.FreeString.
func (m *SQLMap) Get(a mem.Allocator, key string) (string, error) {
    var stmt *sqlite3_stmt
    rc := sqlite3_prepare_v2(m.db, sqlGet, -1, &stmt, nil)
    if rc != sqliteOK {
        return "", ErrPrepare
    }
    defer sqlite3_finalize(stmt)

    sqlite3_bind_text(stmt, 1, key, int32(len(key)), nil)
    rc = sqlite3_step(stmt)
    if rc == sqliteDone {
        return "", ErrNotFound
    }
    if rc != sqliteRow {
        return "", ErrExec
    }

    text := sqlite3_column_text(stmt, 0)
    tmp := c.String(text)
    result := strings.Clone(a, tmp)
    return result, nil
}
```
  The pointer returned by sqlite3_column_text is managed by SQLite. It becomes invalid after calling sqlite3_finalize (which Get does before returning). Because of this, we need to allocate a copy of the returned value, using strings.Clone in this case.
  
  So's approach to memory allocation is similar to Zig's — all heap allocations must be done explicitly by providing a specific instance of the mem.Allocator interface.
  
  The caller, of course, must free the allocated string:
```
func main() {
    m, err := NewSQLMap(":memory:")
    if err != nil {
        panic(err)
    }
    defer m.Close()

    m.Set("name", "Alice")
    name, err := m.Get(mem.System, "name")
    if err != nil {
        panic(err)
    }
    println("name =", name)
    mem.FreeString(mem.System, name)
}



name = Alice
```
  Here, mem.System is a specific allocator that uses libc's malloc and free. Alternatively, we could use mem.Arena or any other implementation of the mem.Allocator interface:
```
var buf [1024]byte // stack-allocated
arena := mem.NewArena(buf[:])

name, _ := m.Get(&arena, "name")
mem.FreeString(&arena, name) // no-op for arena; can be omitted
```
  Command-line interface
  
  With the SQLMap type in place, let's create a simple CLI using the flag package:
```
var (
    opFlag  string
    keyFlag string
    valFlag string
)

func parseFlags() {
    flag.StringVar(&opFlag, "op", "", "operation: get, set, or del")
    flag.StringVar(&keyFlag, "key", "", "key name")
    flag.StringVar(&valFlag, "val", "", "value (for set operation)")
    flag.Parse()
}

func main() {
    parseFlags()
    // ...
}
```
  Then add command routing:
```
m, err := NewSQLMap("sqlmap.db")
check(err)
defer m.Close()

switch opFlag {
case "set":
    err = m.Set(keyFlag, valFlag)
    check(err)
case "get":
    val, err := m.Get(mem.System, keyFlag)
    check(err)
    println(val)
    mem.FreeString(mem.System, val)
case "del":
    err = m.Delete(keyFlag)
    check(err)
default:
    flag.Usage()
    os.Exit(1)
}



sqlmap -op=set -key=name -val=alice
sqlmap -op=get -key=name
alice
```
  Again, no surprises here — the flag package works just as it does in Go.
  
  Performance
  
  Solod isn't trying to outperform hand-tuned C. Still, performance matters: the code is benchmarked and optimized to run reasonably fast. Since So compiles to plain C and then to native code with full optimizations, the results are sometimes better than Go's.
  
  Here are some highlights from the benchmarks:
  - Buffered I/O is 3x faster than Go.
  - String and byte operations are up to 2.5x faster.
  - Maps are 1.5x faster for modifications.
  - Integer formatting is 2x faster.
  There're no GC pauses and no Cgo bridge cost when calling C libraries. The tradeoff is that you have to handle memory yourself, but as the SQLite example above shows, So's allocator interface makes that pretty manageable.
  
  Solod vs. Go benchmarks
  
  Wrapping up
  
  Solod is still in its early days, but with the v0.1 release, it's ready for hobby projects. The already-ported parts of the Go standard library make it easy to write command-line tools (check out the cat, head, sort, and wc examples). Plus, with native C interop, you can build just about anything else you need.
  
  The next release (v0.2) will likely focus on networking, concurrency, or both — along with more stdlib packages.
  
  If you're interested, take a look at So's readme — it has all the information you need to get started. Or try So online without installing anything.
25. 🔗 r/york York Dungeon investigates 'poltergeist' after tumblers fall from shelves rss
  
  | submitted by /u/Unlikely-Tension-616
  [link] [comments]
  ---|---
26. 🔗 sacha chua :: living an awesome life La semaine du 27 avril au 3 mai rss
  
  lundi 27 avril
  
  J'ai ajouté la capacité de naviguer en temps réel à mon paquet subed.el. C'était déjà très pratique pour ajouter les chapitres à la transcription de ma conversation avec John Wiegley et Karthik Chikmagalur. Elle a besoin d'une petite modification pour convertir les notes que j'avais prises pendant la conversation.
  
  J'ai emmené ma fille à son cours de gymnastique. Il y avait un remplaçant. Je suis ravie de voir que le remplaçant a porté un masque KN-95 sans demander.
  
  Je me suis organisé avec ma mère pour installer l'app BDO Pay sur mon téléphone.
  
  J'ai préparé les éléments pour coudre mon chapeau comme le chapeau que j'avais cousu pour ma fille.
  
  mardi 28
  
  J'ai emmené ma fille à Adventure Alley pour jouer avec ses amies. C'était un peu cher, mais ma fille s'est amusée, donc ce n'est pas un problème si nous allons là-bas de temps en temps.
  
  mercredi 29
  
  L'écran de remplacement est arrivé au magasin Apple, donc je vais aller là-bas demain.
  
  J'ai réécrit une partie de la page EmacsNewbie sur l'EmacsWiki.
  
  Ma fille a cousu mon chapeau.
  
  Sur Stardew Valley, nous avons acheté un cochon et un mouton. Nous avons amélioré le poulailler en un grand poulailler et nous avons ajouté une cuisine à notre maison.
  
  jeudi 30
  
  J'ai été ravie en discutant avec Prot sur l'expérience de l'éditeur Emacs pour les débutants.
  
  Mon mari, ma fille, et moi avons fait du vélo avec son amie et le père de son amie.
  
  Sur Stardew, ma fille a remarqué que j'ai accidentellement acheté une vache que j'appelle Chèvre au lieu de la chèvre que j'ai prévu d'acheter pour le centre communautaire. Oups! Elle s'est très amusée et elle m'a demandé, quand j'achète finalement une chèvre, si je pouvais l'appeler Vache. Les animaux seront très confus, et moi aussi. Je l'ai quand même fait.
  
  vendredi 1er mai
  
  L'école avait un remplaçant et elle n'a pas voulu y assister, donc j'ai prévenu l'école de son absence et nous avons fait un compromis entre ses devoirs et des jeux.
  
  Nous sommes allées au Stockyards pour acheter des tissus pour son maillot de bain. Elle a trouvé les deux couleurs qu'elle voulait, mais il ne restait qu'un yard d'une couleur. Il faudra que nous planifions soigneusement. Nous avons acheté des fils chez Michaels. Elle a aussi acheté une boîte de mochi puffs chez Marry Me Mochi.
  
  Elle a cousu des coutures sur mon chapeau.
  
  samedi 2
  
  Pour le petit-déjeuner, ma fille a préparé une grande omelette en utilisant six œufs. On s'est régalés.
  
  Ma fille était grincheuse parce que j'ai attiré son attention sur son agitation et elle a senti que j'étais sur son dos.
  
  Le magasin Apple n'a pas pu réparer l'écran de ma tablette, donc il l'a remplacé par une nouvelle tablette pour une petite somme. L'Apple Pencil était finalement lié à ma garantie AppleCare+, mais malheureusement, il était en rupture de stock partout en ville, donc il fallait que j'attende pendant environ une semaine.
  
  Une fois rentrée, j'ai trouvé que ma fille s'était calmée. Elle et moi avons joué à Duplo, ce qui est aussi un produit LEGO, mais plus grand que la normale. Je les ai utilisés pour montrer à ma fille des concepts mathématiques comme les permutations et les combinaisons.
  
  dimanche 3
  
  Mon mari et moi avons fait du vélo au centre-ville avec ma fille dans mon vélo cargo. Ma fille et moi avons essayé le mochi chez Kibo (c'était délicieux) avant de continuer chez MEC pour chercher une nouvelle gourde pour remplacer celle que j'ai perdue. Elle n'a rien vu qui lui plaisait. Nous avons aussi acheté un mannequin en bois pour faciliter des prototypes pour coudre et des crayons d'aquarelle pour les explorer.
  
  Une fois rentrés, mon mari a fait cuire un pain de levain qu'il donnera au père de l'amie de notre fille, suite à leur conversation vendredi. Ma fille et moi avons travaillé sur le plan de faire son maillot de bain. Elle a voulu une robe qui a un corsage cache-cœur et une jupe à ourlet tulipe. Pour le dos, elle a voulu des bretelles croisées avec un petit dos goutte.
  
  J'étais fatiguée, donc j'ai fait une sieste. Ma fille est venue me réveiller. J'ai remarqué que mes yeux étaient très secs, donc elle a négocié de m'apporter des gouttes pour les yeux et elle me les a administrées pour 25 cents.
  
  View Org source for this post
  
  You can e-mail me at sacha@sachachua.com.
27. 🔗 tomasz-tomczyk/crit v0.10.5 release
  What's Changed
  
  A maintenance release with broad fixes across the GitHub PR roundtrip, the comment-sync push/pull pipeline, and the local review UI — plus accessibility polish on the sidebar resize handles, a distinct "Approved" state on the review-finish modal.
  
  General
  - feat: distinct "Approved" state for review-finish modal by @tomasz-tomczyk in #427
  - feat: keyboard-accessible sidebar resize handles by @tomasz-tomczyk in #469
  - feat: per-round timeline backend (Stage 1) by @tomasz-tomczyk in #460
  - style: bump comment input font-size to 14px by @tomasz-tomczyk in #441
  - style: align textarea line-height with rendered comment bodies by @tomasz-tomczyk in #444
  Fixes
  - fix: tie agent goroutine to daemon shutdown ctx + add runGit helper by @tomasz-tomczyk in #433
  - fix: small correctness nits (bulk parser err, scheduleWrite doc, dup mkdir) by @tomasz-tomczyk in #432
  - fix: use 127.0.0.1 in internal HTTP clients to match daemon bind by @tomasz-tomczyk in #436 (Thanks @perbu for reporting)
  - fix: clean message when running crit on a repo with no changes by @tomasz-tomczyk in #439 (Thanks @perbu for reporting)
  - fix: hide TOC toggle for single-heading documents by @tomasz-tomczyk in #443
  - fix: propagate local comment deletes to GitHub on push by @tomasz-tomczyk in #461
  - fix: import GitHub thread resolved state on crit pull by @tomasz-tomczyk in #462
  - fix: detect mid-push auth rotation and abort cleanly by @tomasz-tomczyk in #463
  - fix: prefers-reduced-motion spinner gap; rename waitingHasComments; annotate reflow line by @tomasz-tomczyk in #465
  - fix: relax comment drift detection for in-place edits by @tomasz-tomczyk in #466
  - fix: atomically rewrite auth_token + identity on login by @tomasz-tomczyk in #468
  - fix: close finish-review modal on backdrop click by @tomasz-tomczyk in #470
  - fix: allow --range/--pr on clean working tree by @tomasz-tomczyk in #472 (Thanks @ewgdg for reporting!)
  - fix: backward selection across blank-line boundary by @tomasz-tomczyk in #473 (Thanks Matt for reporting!)
  Documentation
  - docs: rewrite AGENTS.md with blocks by @tomasz-tomczyk in #431
  Internal refactors
  - chore: post-v0.10.4 audit cleanup by @tomasz-tomczyk in #426
  - fix: post-v0.10.4 release audit cleanup by @tomasz-tomczyk in #475
  - refactor: bundled cleanup — wrappers, mustGetwd, browser.go, error surfacing by @tomasz-tomczyk in #428
  - refactor: extract review-file CLI logic out of github.go by @tomasz-tomczyk in #429
  - refactor: consolidate atomic-file-write helpers by @tomasz-tomczyk in #430
  - refactor: split main.go and session.go into focused files by @tomasz-tomczyk in #434
  - refactor: release audit cleanup — atomic writes, flag parsing, dead code by @tomasz-tomczyk in #464
  - test: cover gaps in atomic write, auth, watch, sapling, parsers by @tomasz-tomczyk in #440
  - test: GitHub PR roundtrip integration harness by @tomasz-tomczyk in #445
  - test: wait for PR head sha after force-push in roundtrip harness by @tomasz-tomczyk in #457
  - test: integration coverage for resolved_round mapping by @tomasz-tomczyk in #467
  Full Changelog : v0.10.4...v0.10.5
28. 🔗 r/york First-Time DM looking for DnD players in York! rss
  
  Hey everyone! I've been wanting to DM something for a while now and I've been planning a campaign that I'm pretty excited about.
  
  I've got one player on board so far, so I just need three more players to be able to start playing! The two of us are 26/27, so ideally we're looking for people around the same age.
  
  If you're interested, just let me know and I'll DM you with more details 😄
  
  submitted by /u/WeirdoWolfBoy
  [link] [comments]
29. 🔗 r/LocalLLaMA 2.5x faster inference with Qwen 3.6 27B using MTP - Finally a viable option for local agentic coding - 262k context on 48GB - Fixed chat template - Drop-in OpenAI and Anthropic API endpoints rss
  
  2026-05-07 edit: I have updated the hardware based recommendations with more focus on quality. I do not recommend q4_0 KV cache anymore beyond 64k context. After multiple rounds of testing with the different size quants, it appears3 is the optimal number for draft speculative decoding. The fastest and best quality quant is q8_0-mtp. F16, which I have also uploaded is actually better but ultra slow (6x slower than q8_0). Many keep saying 8bit is virtually lossless compared to 16bit, and 6bit almost as good as 8bit, but this is simply not true: time and time again I have noticed huge differences in quality and correctness between 8bit and 16bit versions of various models.
  
  The recent PR to llama.cpp bring MTP support to Qwen 3.6 27B. This uses the built-in tensor layers for speculative decoding. None of the existing GGUF have it, as they need to be converted with this PR.
  
  I have tested it locally on my mac M2 Max 96GB, and the results are amazing: 2.5x speed increase, bringing it to 28 tok/s!
  
  I have converted the most useful quants and uploaded them to HF. Even if you are using apple silicon, you should use those instead of MLX. You can download them here:
  
  https://huggingface.co/froggeric/Qwen3.6-27B-MTP-GGUF
  
  This also includes 7 fixes I made to the original jinja chat template, due to vLLM specificity which broke in other tools:
  
  https://huggingface.co/froggeric/Qwen-Fixed-Chat-Templates
  
  For now, you will need to compile your own version of llama.cpp to use them. It is fairly simple to do:
  
```bash git clone --depth 1 https://github.com/ggml-org/llama.cpp.git cd llama.cpp git fetch origin pull/22673/head:mtp-pr && git checkout mtp-pr

cmake -B build -DGGML_METAL=ON -DCMAKE_BUILD_TYPE=Release cmake --build build --target llama-cli llama-server ```

Then to start serving with the API endpoint, use a command similar to:

bash llama-server -m Qwen3.6-27B-Q5_K_M-mtp.gguf \ --spec-type mtp --spec- draft-n-max 3 \ --cache-type-k q8_0 --cache-type-v q8_0 \ -np 1 -c 262144 --temp 0.7 --top-k 20 -ngl 99 --port 8081

Vision currently crashes llama.cpp when used alongside MTP. Reported 2026-05-06 in the current PR.

That's it. Three optimizations in one command:

Flag | What it does | Impact
---|---|---
--spec-type mtp --spec-draft-n-max 3 | Multi-Token Prediction (built into the model) | 2.5x faster generation
--cache-type-k q8_0 --cache-type-v q8_0 | 8-bit KV cache (instead of 16-bit) | Half the KV memory , negligible quality loss
-c 262144 | 262K context window | Full native context on 48 GB Mac with q8_0 KV

Adjust -m, -c, and --cache-type-k/v for your hardware, according to the tables below.

Here are my recommendations based on your hardware:

Apple Silicon

Qwen3.6-27B is a hybrid model — only 16 of 65 layers use KV cache (verified). The other 48 are linear attention (fixed 898 MiB recurrent state). KV memory is ~4× less than a standard dense model. Runtimes that don't handle this (e.g. vllm) allocate KV for all 65 layers and show much higher memory usage.

Numbers below are total memory used (model + KV cache + 0.9 GB recurrent state). Must leave ≥ 8 GB for macOS (16 GB Macs excepted).

RAM | Quant | KV cache | Max context | Total used | Vision
---|---|---|---|---|---
16 GB | IQ2_M | q8_0 | 42K | 12.0 GB | ✗
24 GB | IQ3_M | | 46K | 16.0 GB | ✗
24 GB | IQ3_M | q8_0 | 91K | 16.0 GB | ✗
32 GB | Q5_K_M | | 74K | 24.0 GB | ✗
32 GB | Q5_K_M | q8_0 | 147K | 24.0 GB | ✗
32 GB | Q4_K_M | | 99K | 24.0 GB | ✓
48 GB | Q6_K | | 262K | 39.7 GB | ✓
48 GB | Q8_0 | | 173K | 40.0 GB | ✓
48 GB | Q8_0 | q8_0 | 262K | 37.3 GB | ✓
64 GB | Q8_0 | | 262K | 45.8 GB | ✓
96 GB | Q8_0 | | 262K | 45.8 GB | ✓

NVIDIA GPU

Same model memory as Apple Silicon, plus ~1 GB CUDA overhead.

VRAM | Quant | KV cache | Max context | Total VRAM used | Vision
---|---|---|---|---|---
12 GB | IQ2_M | q8_0 | 11K | 12.0 GB | ✗
16 GB | IQ3_M | | 30K | 16.0 GB | ✗
16 GB | IQ3_M | q8_0 | 60K | 16.0 GB | ✗
24 GB | Q4_K_M | | 83K | 24.0 GB | ✓
24 GB | Q4_K_M | q8_0 | 167K | 24.0 GB | ✓
24 GB | Q5_K_M | | 58K | 24.0 GB | ✗
48 GB | Q6_K | | 262K | 40.7 GB | ✓
48 GB | Q8_0 | | 262K | 46.8 GB | ✓
80 GB | Q8_0 | | 262K | 46.8 GB | ✓

16 GB Mac: IQ2_M/q8_0 — 42K text-only. No vision.

24 GB Mac: IQ3_M — 46K (f16 KV) or 91K (q8_0). Vision at 32–65K.

32 GB Mac: Q5_K_M — 74K text-only (f16 KV), 147K (q8_0). Q4_K_M for vision at 99K.

48 GB Mac: Q6_K/f16 KV — 262K with vision. Q8_0/q8_0 KV for 262K at higher model quality.

64 GB+ Mac: Q8_0/f16 KV — 262K with vision. Maximum quality at practical speed.

12 GB GPU: IQ2_M/q8_0 — 11K. Very limited, no vision.

16 GB GPU: IQ3_M — 30K (f16 KV) or 60K (q8_0). No vision.

24 GB GPU: Q4_K_M — 83K with vision (f16 KV). Q5_K_M — 58K text-only (f16 KV), 116K (q8_0).

48 GB+ GPU: Q6_K/f16 KV — 262K with vision. Q8_0 for max quality.

Leave KV cache at f16 (blank column) for best quality. Use q8_0 KV only when f16 doesn't give enough context. q4_0 KV should not exceed 64K context.

Vision adds ~0.9 GB for mmproj. macOS needs ≥ 8 GB for itself (16 GB Macs excepted — use ~4 GB). You can increase available memory by raising the wired memory limit, e.g. for a 96 GB Mac: sudo sysctl iogpu.wired_limit_mb=90112 (88 GB). NVIDIA reserves ~1 GB for CUDA.

submitted by /u/ex-arman68
[link] [comments]
30. 🔗 r/wiesbaden Fine Line Tattoo Artist rss
  
  Hey,
  
  Kennst jemand ein gutes Tattoo Studio/ einen guten Tattoo Artist für abstrakte Fine Line Tattoos in Wiesbaden oder Umgebung?Ansonsten auch anderswo:)
  
  submitted by /u/heyheyheyoooooo
  [link] [comments]
31. 🔗 anthropics/claude-code v2.1.131 release
  What's changed
  - Fixed VS Code extension failing to activate on Windows due to a hardcoded build path in the bundled SDK (createRequire polyfill bug)
  - Fixed Mantle endpoint authentication failing with missing x-api-key header
32. 🔗 r/Leeds When is Uniqlo going to open? rss
  
  I was so excited for this opening to be announced last year, at Christmas it said opening soon, then it changed to fall/winter 2026.
  
  It's a long time to fit out a shop.
  
  submitted by /u/used2bfat69
  [link] [comments]
33. 🔗 r/LocalLLaMA Quality comparison between Qwen 3.6 27B quantizations (BF16, Q8_0, Q6_K, Q5_K_XL, Q4_K_XL, IQ4_XS, IQ3_XXS,...) rss
  | The following is a non-comprehensive test I came up with to test the quality difference (a.k.a degradation) between different quantizations of Qwen 3.6 27B. I want to figure out what's the best quant to run on my 16 GB VRAM setup. WHAT WE ARE TESTING First, the prompt:
```
Given this PGN string of a chess game: 1. b3 e5 2. Nf3 h5 3. d4 exd4 4. Nxd4 Nf6 5. f4 Ke7 6. Qd3 d5 7. h4 * Figure out the current state of the chessboard, create an image in SVG code, also highlight the last move.
```
  I want to see if the models can:
  - Able to track the state of the board after each move, to reach the final state (first half of move 7)
  - Generate the right SVG image of the board, correctly place the pieces, highlight the last move
  And yes, if you are questioning. It could be possible that the model was trained to do the same thing on existing chess games, so I came up with some random moves, the kind of moves that no players above 300 elo would ever have played. For those who are not chess players, this is how the board supposed to look like after move 7. h4. Btw, you supposed to look at the pieces positions and the board orientation, not image quality because this is just a screenshot from Lichess. https://preview.redd.it/6lsfvzy8wfzg1.png?width=1586&format=png&auto=webp&s=94634b461528a6ecc6728eefd23072ab28c3769d CAN OTHER MODELS SOLVE IT? Before we go to the main part, let me show the result from some other models. I find it interesting that not many models were able to figure out the board state, let alone rendering it correctly. Qwen 3.5 27B It was mostly figured out the final position of the pieces, but still render the original board state on top. Highlighted the wrong squares, and the board orientation is wrong. https://preview.redd.it/oanbebp9xfzg1.png?width=1078&format=png&auto=webp&s=b72af75a10f4a9f4d897699b404580370bd29d9e Gemma 4 31B Nice chess dot com flagship board style, i would say it can figure out the board state, but failed to render it correctly. The square pattern also messed up. https://preview.redd.it/w5jwi05nxfzg1.png?width=1640&format=png&auto=webp&s=33e6f21f56c4e98df92c828103ac10714e578973 Qwen3 Coder Next I don't know what to say, quite disappointed. https://preview.redd.it/knltp8h1yfzg1.png?width=1348&format=png&auto=webp&s=1e9207cd1dfd08b049eaa13727703be732d2cb96 Qwen3.6 35B A3B As expected, 35B always be the fastest Qwen model, but at the same time, managed to fail the task successfully in many different ways. This is why I decided to find a way to squeeze 27B into my 16 GB card. The speed alone just not worth it. https://preview.redd.it/orti5kdhyfzg1.png?width=3360&format=png&auto=webp&s=c29a3aae9683e5ceaa15c59ae32adecabdd1b6b6 HOW QWEN3.6 27B SOLVE IT? All the models here are tested with the same set of llama.cpp parameters:
  - temp 0.6
  - top-p 0.95
  - top-k 20
  - min-p 0.0
  - presence_penalty 1.0
  - context window 65536
  BF16 version was from OpenRouter, Q8 to Q4_K_XL versions was on a L40S server, the rest are on my RTX 5060 Ti. The SVG code generated directly on Llama.cpp Web UI without any tools or MCP enabled (I originally ran this test in Pi agent, only to found out that the model tried to peek into the parent folders and found the existing SVG diagrams by higher quants, copied most of it). BF16 - Full precision This is the baseline of this test. It has everything I needed: right position, right board orientation, right piece colors, right highlight. The dotted blue line was unexpected, but it also interesting, because later on you will see, not many of the high quants generate this. https://preview.redd.it/lgizkjklzfzg1.png?width=1424&format=png&auto=webp&s=d7867b55735d3d875e0e36aecbaf3c3f0d1dbd58 Q8_0 As expected Q8 retains pretty much everything from the full precision except the line. https://preview.redd.it/6wjnq6ff0gzg1.png?width=1610&format=png&auto=webp&s=f0d20ff4717b972efffced49ac8d43075fa97eb5 Q6_K We start to see some quality loss here. I mean the placement of the rank 5 pawns. The look of the pieces are mostly because Q6 decided to use a different font. None of the models here trying to draw its own pieces in this test. https://preview.redd.it/kcqj81vl0gzg1.png?width=1608&format=png&auto=webp&s=66c7a219e79a8f6ecf44e27489f337b4016185b5 Q5_K_XL Looks very similar with Q8, but it is worth noticing that the SVG code of Q5 version is 7.1 KB, while Q8 is 4.7 KB. https://preview.redd.it/6wshu7g01gzg1.png?width=1506&format=png&auto=webp&s=289db354fea59c456d8bd2dc7abdbcc1e4282ffd Q4_K_XL and IQ4_XS If you ignore the font choice, you will see Q4_K_XL is a more complete solution, because it has the board coordinates. https://preview.redd.it/pzdghdtm1gzg1.png?width=3326&format=png&auto=webp&s=10c3d7758459f223d195107353f1ec76565cd31d Q3_K_XL and Q3_K_M https://preview.redd.it/56gttur62gzg1.png?width=3330&format=png&auto=webp&s=4af27d8a652e2deef6c14485d0fff4bd3651097f IQ3_XXS Now here's the interesting part, everything was mostly correct, the piece placements and the highlight, and there's the line on the last move! But IQ3_XXS get the board orientation wrong, see the light square on the bottom left? https://preview.redd.it/7jnzxy324gzg1.png?width=1608&format=png&auto=webp&s=178f72f51e65866497f16e861b04c0c448fce774 Q2_K_XL This is just a waste of time. But hey, it got all the pieces positions right. The board is just not aligned at all. https://preview.redd.it/3z63d7bv4gzg1.png?width=1604&format=png&auto=webp&s=f6723b28248327c55bede4e42a4a0cfbe962fb74 SO, WHAT DO I USE? I know a single test is not enough to draw any conclusion here. But personally, I will never go for anything below IQ4_XS after this test (I had bad experience with Q3_K_XL and below in other tries). On my RTX 5060 Ti, I got like pp 100 tps and tg 8 tps for IQ4_XS with vanilla llama.cpp (q8 for both ctk and ctv, fit on). But with TheTom's TurboQuant fork, I managed to get up to pp 760 tps and tg 22 tps , by forcing GPU offload for all layers (-ngl 99), quite usable.
```
llama-cpp-turboquant/build/bin/llama-server -fa 1 -c 75000 -np 1 --no-mmap --temp 0.6 --top-p 0.95 --top-k 20 --min-p 0.0 --presence_penalty 1.0 -ctk turbo4 -ctv turbo2 -ub 128 -b 256 -m Qwen3.6-27B-IQ4_XS.gguf -ngl 99
```
  The only down side is I have to keep the context window below 75k, and use turbo4/turbo2 for KV cache quant. Below are some example of different KV cache quants. https://preview.redd.it/y0y7o6h09gzg1.png?width=3320&format=png&auto=webp&s=bd7c855100ff63c9bb666a4f4a61b966ad6eebca https://preview.redd.it/dyrru7z19gzg1.png?width=3314&format=png&auto=webp&s=d54238d7a31c6cd8858f84df67ff588dc22d726b You can see all the result directly here https://qwen3-6-27b-benchmark.vercel.app/ submitted by /u/bobaburger
  [link] [comments]
  ---|---
34. 🔗 r/reverseengineering ant4g0nist/pyre: Ghidra decompiler in your browser rss
  
  submitted by /u/Nightlark192
  [link] [comments]
35. 🔗 anthropics/claude-code v2.1.129 release
  What's changed
  - Added --plugin-url <url> flag to fetch a plugin .zip archive from a URL for the current session
  - Added CLAUDE_CODE_FORCE_SYNC_OUTPUT=1 env var to force-enable synchronized output on terminals that auto-detection misses (e.g. Emacs eat)
  - Added CLAUDE_CODE_PACKAGE_MANAGER_AUTO_UPDATE: when set on Homebrew or WinGet installations, Claude Code runs the upgrade command in the background and prompts to restart
  - Plugin manifests: themes and monitors should now be declared under "experimental": { ... }. Top-level declarations still work but claude plugin validate will warn
  - Gateway /v1/models discovery for the /model picker is now opt-in via CLAUDE_CODE_ENABLE_GATEWAY_MODEL_DISCOVERY=1 (was automatic in 2.1.126–2.1.128)
  - Ctrl+R history picker now defaults to searching all prompts across all projects, matching pre-2.1.124 behavior. Press Ctrl+S to narrow to the current project or session
  - Third-party deployments (Bedrock, Vertex, Foundry, or ANTHROPIC_BASE_URL gateway) no longer see spinner tips pointing at first-party Anthropic surfaces
  - skillOverrides setting now works: off hides from model and /, user-invocable-only hides from model only, name-only collapses description
  - The claude_code.pull_request.count OTel metric now counts PRs/MRs created via MCP tools, not just shell commands
  - Policy refusal error messages now include the API Request ID for easier support debugging
  - Fixed API errors with unrecognized 400 status codes showing raw JSON instead of the underlying error message
  - Fixed /clear not resetting the terminal tab title after a conversation
  - Fixed session title chip from /rename disappearing while a permission or other dialog is active
  - Fixed agent panel below the prompt being hidden when subagents are running (regression in 2.1.122)
  - Fixed external-editor handoff (Ctrl+G) blanking the conversation history above the prompt
  - Fixed /context dumping its rendered ASCII visualization grid into the conversation, wasting ~1.6k tokens per call
  - Fixed /agents Library list arrow-key navigation: the highlighted agent now stays visible when the list exceeds the viewport
  - Fixed /branch success message not including the new branch's session id for /resume
  - Fixed bold headers with keycap/ZWJ/skin-tone emoji losing trailing characters in fullscreen mode
  - Fixed server-managed settings policy not applying for enterprise/team users whose stored OAuth credentials lacked the user:inference scope
  - Fixed OAuth refresh race after wake-from-sleep that could log out all running sessions
  - Fixed 1-hour prompt cache TTL being silently downgraded to 5 minutes
  - Fixed cache-miss warning appearing spuriously after /clear or compaction when changing /effort or /model
  - Fixed Bash(mkdir *), Bash(touch *) and similar allow rules not being honored for in-project paths
  - Fixed deniedMcpServers patterns with a *:// scheme wildcard not matching mixed-case hostnames
  - Fixed harmless WebSocket warning being logged as an error in --debug during voice mode
  - [VSCode] Fixed /clear not clearing the conversation context and displayed transcript
36. 🔗 HexRaysSA/plugin-repository commits sync repo: ~1 changed rss
```
sync repo: ~1 changed

## Changes
- [HashDB](https://github.com/oalabs/hashdb-ida):
  - 1.10.0: archive contents changed, download URL changed
```
37. 🔗 Ampcode News Amp, Rebuilt rss
  Today we're starting to roll out the new Amp.
  
  Not all of it, not yet. But the first piece: a rebuilt Amp CLI. Codename: Neo.
  
  In The Coding Agent is Dead we wrote about where this is going: agents with longer leashes, less handholding, and many more places to run. Not just one agent in one terminal. Agents prompted from anywhere, running everywhere.
  
  That's the new Amp we're building.
  
  But the terminal still matters and will matter. There will be moments where you want the agent right next to you.
  
  So we rebuilt the CLI first. It is still Amp in your terminal. But it's running on a completely new architecture: remote-controllable, compaction-first, plugin-powered, and much faster. Built for what's coming.
  
  Let's walk through it.
  
  Remote Control
  
  When you start a thread in the new Amp CLI, you can now remote control it from ampcode.com.
  
  You'll not only get live updates but you can also send messages, queue and dequeue them, or cancel what the agent is currently doing:
  
  The architecture that enables this is the reason we rewrote Amp. And remote control is just the start.
  
  No More Manual Context Management
  
  A core principle behind the rebuild: build for what the frontier models can do now, in 2026, and what they will be able to do in the future. Do not build for what once was.
  
  Today's leading frontier models are great at handling compaction.
  
  So Amp now manages context for you.
  
  You don't have to watch context percentages anymore, or decide when to handoff, or extract information from a thread in a panic.
  
  When the context window fills up, Amp now compacts the thread: it summarizes the current context, starts a fresh window with that summary, and keeps going.
  
  Compaction now runs automatically when the context window is 90% full.
  
  It was also the first thing we added to the new architecture. During one migration, we had to shut it off for a day and everyone complained. One beta-user reported: "I love having auto-compaction. NOT missing handoff..."
  
  So handoff is out. Compaction is in.
  
  Plugins
  
  With this release we're officially releasing the Amp Plugin API.
  
  Amp plugins can:
  - Handle events — amp.on(...) for tool calls, tool results, and agent lifecycle events
  - Add tools — amp.registerTool(...) for custom tools the agent can call
  - Add commands — amp.registerCommand(...) for command palette actions
  - Show UI elements — ctx.ui.notify(...), ctx.ui.confirm(...), ctx.ui.input(...), and ctx.ui.select(...)
  - Ask AI questions — amp.ai.ask(...) for yes/no classification with confidence and reasoning
  Here, for example, is a plugin that registers a tool called ask_user_choice. The agent can use it to present the user with options:
```
// .amp/plugins/ask-user-choice.ts

import type { PluginAPI } from '@ampcode/plugin'

export default function (amp: PluginAPI) {
    amp.registerTool({
        name: 'ask_user_choice',
        description:
            'Present the user with a multiple choice question when there are several possible approaches and you need them to pick one. Use when you have 2-5 concrete options to choose from.',
        inputSchema: {
            type: 'object',
            properties: {
                question: { type: 'string', description: 'The question to ask the user' },
                options: {
                    type: 'array',
                    items: { type: 'string' },
                    description: 'The options to choose from (2-5 items)',
                },
            },
            required: ['question', 'options'],
        },
        async execute(input, ctx) {
            const question = input.question as string
            const options = input.options as string[]
            const optionsList = options.map((opt, i) => `${i + 1}. ${opt}`).join('\n')

            const answer = await ctx.ui.input({
                title: question,
                helpText: `${optionsList}\n\nType the number of your choice`,
                submitButtonText: 'Select',
            })

            if (!answer) return 'User dismissed the question without choosing.'

            const index = parseInt(answer.trim(), 10) - 1
            if (index >= 0 && index < options.length) {
                return `User selected option ${index + 1}: ${options[index]}`
            }
            return `User responded with: ${answer}`
        },
    })
}
```
  That's it: a single file in .amp/plugins and Amp gets a new tool. It looks like this:
  
  The Amp Plugin API documentation has more examples, including a full permissions plugin.
  
  Queuing & Steering
  
  Queuing messages is now the default. When you send a message while the agent is busy, it'll get added to the queue instead of stopping and interrupting the agent.
  
  This, too, we think fits the models of today and tomorrow better. They work for longer and need fewer mid-flight yanks.
  
  If you want to fast-track a queued message, you can steer.
  
  Steering lets you send a queued message as soon as possible, not just when the agent becomes idle. The next time a tool result is sent up to the agent, for example.
  
  Use ↑ to select a queued message, then steer it with ⏎:
  
  You can also hit Esc Esc to interrupt the agent and send immediately.
  
  Permissions
  
  Amp will no longer ask for permission before running tools.
  
  What was once the --dangerously-allow-all flag is now the default behavior for users who have not configured permissions.
  
  The old permissions system still exists. It's now a built-in plugin. If your existing Amp settings already opt into permissions — through amp.permissions, amp.dangerouslyAllowAll: false, or amp.guardedFiles.allowlist — Amp loads that plugin and works as before. (When the plugin is active, it applies in both amp and amp --execute.)
  
  Why change the default?
  
  A year ago tool calls were simpler to check: inspect the name, inspect the arguments, do string-based matching, allow or deny. Now, frontier models write throwaway scripts to get stuff done. They chain shell commands.
  
  It's near-impossible to determine statically whether a tool invocation will be destructive or not.
  
  When a model writes five 20-line Python scripts in parallel to do something, checking whether a tool call contains rm -rf gives you a false sense of security.
  
  On top of that, there are now custom skills and scripts, specifically built for agents. And different organizations have different policies around which model is allowed to call which tool.
  
  So permissions now live in the Plugin API.
  
  If you need a policy, build the one that matches your setup. Point Amp at the Amp Plugin API and ask it to help you.
  
  Performance & Efficiency
  
  The old Amp CLI got slow with huge threads. Neo doesn't. Here's a comparison, using a thread with around 5000 messages:
  
  Metric Old New Improvement
  
  CPU% (mean ± sd) 84.1% ± 1.6% 17.4% ± 8.8% 79% less CPU
  
  CPU% (peak) 86.3% 25.8% —
  
  Memory (idle) 1814 MB 540 MB 70% less memory
  
  Rendering performance has improved, too.
  
  Before:
  
  After:
  
  What's Gone
  
  We also removed features. Of course we did, otherwise it wouldn't be an Amp release, would it?
  
  Our goal is to keep you on the frontier. Amp should not make you work like it's still 2025.
  
  Some features made sense when models needed more babysitting, more manual context management, more careful steering. They don't anymore. When a feature starts tying you to the old way to use agents, it goes.
  
  Handoff is gone. As described above, compaction made it obsolete. There are some valid use cases for Handoff even when there's enough space left in the context, but we don't think it warrants the complexity introduced by many small, connected threads.
  
  You can also still reference other threads and Amp will read them and extract the relevant information.
  
  For example, you can use Ctrl+O and thread: new to create a new thread, then hit Enter to quickly insert a reference to the previous thread. Amp will use that reference along with the rest of your prompt to read the previous thread.
  
  Amp no longer rolls back file changes when you edit or restore a message. We've found ourselves using this less and less as models advanced. The models are now good enough to undo changes for you, with more finesse than a rollback. And, the truth is, the rollback feature was always best-effort: if the agent wrote and ran code that generated files, we didn't keep track of that without elaborate snapshotting.
  
  Skill management: Amp still supports Agent Skills but we no longer offer commands or subcommands to add, remove, or update skills. That's better done by separate tools, such as skills.
  
  User-invokable skills: We also removed support for user-invokable skills. The latest generation of models now invokes skills reliably.
  
  Themes: Custom themes made it harder to keep the CLI legible, polished, and recognizably Amp. We’d rather ship one good interface than support many broken-looking ones.
  
  Manual bash invocation: in the old Amp CLI you could invoke bash commands by using $ and $$ in the prompt editor. An interesting idea a year ago, but now with models being ever more capable at running commands on their own and without blowing up their context window (and that context window being unlimited, practically) it's no longer useful.
  
  Rollout
  
  We’re rolling Neo out over the next few days. If you want to skip the line, send us an email. We'll flip the switch for you.
  
  This is the first piece of the new Amp.
  
  More soon.