🏡

to read (pdf)

generated: April 09, 2026 at 00:09:13

April 09, 2026
1. 🔗 Console.dev newsletter Skir rss
  
  Description: Declarative language for types & APIs.
  
  What we like: Define the schema then generate idiomatic, type-safe code (Python, Go, Java, Rust, TS, etc). Dynamic serialization options e.g. binary or JSON. VS Code extension & LSP tooling. Supports backwards compatibility when changing schemas.
  
  What we dislike: Compile-time errors if you add a field, but don’t regenerate the code - this is the opposite to protobuf which handles it by defaulting values. This may be better, depending on your philosophy.
2. 🔗 Console.dev newsletter Atomic rss
  
  Description: Knowledge graph.
  
  What we like: Local, open source, markdown-based knowledge base. Auto-generates wiki articles from tags. Built-in semantic search with vector embeddings. Supports different types e.g. markdown notes, web clips, articles. Supports MCP. Can be an HTTP server without a desktop UI.
  
  What we dislike: Everything is self hosted so you need to do some setup work. This is also a benefit.
April 08, 2026
1. 🔗 backnotprop/plannotator v0.17.4 release
  Follow @plannotator on X for updates
  
  Missed recent releases? Release | Highlights
  ---|---
  v0.17.3 | Sticky lane repo/branch badge overflow fix
  v0.17.2 | Supply-chain hardening, sticky toolstrip and badges, overlay scrollbars, external annotation highlighting, Conventional Comments
  v0.17.1 | Pi PR review parity, parseRemoteUrl rewrite, cross-repo clone fixes, diff viewer flash fix
  v0.17.0 | AI code review agents, token-level annotation, merge-base diffs
  v0.16.7 | Gemini CLI plan review, install script skills directory fix
  v0.16.6 | Perforce support, Pi shared event API, suggested code prefill, file tree expand fix
  v0.16.5 | Resize handle scrollbar fix, VS Code Marketplace publish
  v0.16.4 | Compound planning improvement hook, GitHub Enterprise + self-hosted GitLab, dockview workspace, new themes
  v0.16.3 | Pi phase configuration, CLI help, untracked file discovery fix, review scroll reset
  v0.16.2 | Draggable comment popovers, cross-file annotation visibility, custom diff fonts, OpenCode verbose log fix
  v0.16.1 | SSE stream idle timeout fix for external annotations API
  v0.16.0 | GitHub Copilot CLI, external annotations API, bot callback URLs, interactive checkboxes, print support, diff display options
  
  What's New in v0.17.4
  
  v0.17.4 ships three PRs: a sidebar consolidation that folds the Obsidian vault browser into the Files tab, three new Kanagawa themes, and a Pi regression fix from @dmmulroy.
  
  Vault Browser Merged into Files Tab
  
  The sidebar previously had separate "Files" and "Vault" tabs when an Obsidian vault was configured. The two tabs had identical tree UI but parallel state, and switching between them broke the mental model of "files are files."
  
  The Vault tab is gone. Vault directories now appear as collapsible sections inside the Files tab, beneath project directories, marked with an Obsidian icon in the section header. Annotation count badges still appear per- directory. Disabling the vault in Settings removes the section without affecting project file browsing.
  
  Two server-side gaps accompany this change. The annotate server (both Bun and Pi) was missing the /api/obsidian/vaults, /api/reference/obsidian/files, and /api/reference/obsidian/doc endpoints — vault files were unreachable when opening linked docs via plannotator annotate ./. Those endpoints are now present on all three servers (plan, review, annotate).
  
  The sticky header lane was also incorrectly suppressed whenever a linked doc was active. That gate has been removed. The sticky bar now follows scroll behavior consistently regardless of mode.
  
  Net change is -334 lines: one Files tab handles all directory types uniformly.
  
  #526
  
  Kanagawa Themes
  
  Three Kanagawa variants join the theme picker as dark-only themes, placed alphabetically after Gruvbox:
  - Kanagawa Dragon — warmest variant, ash-black base (#181616) with muted teal accent
  - Kanagawa Wave — the classic Kanagawa, cool blue-purple base (#1f1f28) with purple accent
  - Kanagawa Bones — same base as Wave, earthier character, cyan-blue primary with brighter purple accent
  Colors are mapped directly from the official Ghostty Kanagawa palette.
  
  #524
  
  Additional Changes
  - Pi: planning tool stripped on fresh sessions. PR #446 refactored the Pi session_start handler to use applyPhaseConfig() but left the idle branch calling only restoreSavedState(), which no-ops when there's no saved state. On fresh sessions that had never entered planning mode, plannotator_submit_plan remained in the active tool set — a regression from #387. The idle branch now explicitly strips planning-only tools when there is no saved state to restore. (#525 by @dmmulroy)
  Install / Update
  
  macOS / Linux:
```
curl -fsSL https://plannotator.ai/install.sh | bash
```
  Windows:
```
irm https://plannotator.ai/install.ps1 | iex
```
  Pin a specific version:
```
curl -fsSL https://plannotator.ai/install.sh | bash -s -- --version v0.17.4
```
  Claude Code Plugin: Run /plugin in Claude Code, find plannotator , and click "Update now".
  
  Copilot CLI:
```
/plugin marketplace add backnotprop/plannotator
/plugin install plannotator-copilot@plannotator
```
  Gemini CLI: The install script auto-detects ~/.gemini and configures hooks, policy, and slash commands. See apps/gemini/README.md for manual setup.
  
  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
```
  VS Code Extension: Install from the VS Code Marketplace. Tested with Claude Code running in VS Code's integrated terminal. Not currently compatible with Anthropic's official VS Code extension due to upstream hook bugs.
  
  What's Changed
  - feat(sidebar): merge vault browser into files tab + UX polish by @backnotprop in #526
  - fix(pi): strip planning-only tools on fresh idle sessions by @dmmulroy in #525
  - feat(themes): add Kanagawa Dragon, Wave, and Bones themes by @backnotprop in #524
  Contributors
  
  @dmmulroy tracked down and fixed a regression in the Pi tool-scoping logic he originally authored in #387 (#525). This is his fourth contribution to the project.
  
  Full Changelog : v0.17.3...v0.17.4
2. 🔗 Simon Willison Meta's new model is Muse Spark, and meta.ai chat has some interesting tools rss
  Meta announced Muse Spark today, their first model release since Llama 4 almost exactly a year ago. It's hosted, not open weights, and the API is currently "a private API preview to select users", but you can try it out today on meta.ai (Facebook or Instagram login required).
  
  Meta's self-reported benchmarks show it competitive with Opus 4.6, Gemini 3.1 Pro, and GPT 5.4 on selected benchmarks, though notably behind on Terminal-Bench 2.0. Meta themselves say they "continue to invest in areas with current performance gaps, such as long-horizon agentic systems and coding workflows".
  
  The model is exposed as two different modes on meta.ai - "Instant" and "Thinking". Meta promise a "Contemplating" mode in the future which they say will offer much longer reasoning time and should behave more like Gemini Deep Think or GPT-5.4 Pro.
  
  A couple of pelicans
  
  I prefer to run my pelican test via API to avoid being influenced by any invisible system prompts, but since that's not an option I ran it against the chat UI directly.
  
  Here's the pelican I got for "Instant":
  
  And this one for "Thinking":
  
  Both SVGs were rendered inline by the Meta AI interface. Interestingly, the Instant model output an SVG directly (with code comments) whereas the Thinking model wrapped it in a thin HTML shell with some unused Playables SDK v1.0.0 JavaScript libraries.
  
  Which got me curious...
  
  Poking around with tools
  
  Clearly Meta's chat harness has some tools wired up to it - at the very least it can render SVG and HTML as embedded frames, Claude Artifacts style.
  
  But what else can it do?
  
  I asked it:
  
  what tools do you have access to?
  
  And then:
  
  I want the exact tool names, parameter names and tool descriptions, in the original format
  
  It spat out detailed descriptions of 16 different tools. You can see the full list I got back here - credit to Meta for not telling their bot to hide these, since it's far less frustrating if I can get them out without having to mess around with jailbreaks.
  
  Here are highlights derived from that response:
  - Browse and search. browser.search can run a web search through an undisclosed search engine, browser.open can load the full page from one of those search results and browser.find can run pattern matches against the returned page content.
  - Meta content search. meta_1p.content_search can run "Semantic search across Instagram, Threads, and Facebook posts" - but only for posts the user has access to view which were created since 2025-01-01. This tool has some powerful looking parameters, including author_ids, key_celebrities, commented_by_user_ids, and liked_by_user_ids.
  - "Catalog search" - meta_1p.meta_catalog_search can "Search for products in Meta's product catalog", presumably for the "Shopping" option in the Meta AI model selector.
  - Image generation. media.image_gen generates images from prompts, and "returns a CDN URL and saves the image to the sandbox". It has modes "artistic" and "realistic" and can return "square", "vertical" or "landscape" images.
  - container.python_execution - yes! It's Code Interpreter, my favourite feature of both ChatGPT and Claude.
    
    Execute Python code in a remote sandbox environment. Python 3.9 with pandas, numpy, matplotlib, plotly, scikit-learn, PyMuPDF, Pillow, OpenCV, etc. Files persist at /mnt/data/.
    
    Python 3.9 is EOL these days but the library collection looks useful.
    
    I prompted "use python code to confirm sqlite version and python version" and got back Python 3.9.25 and SQLite 3.34.1 (from January 2021).
  - container.create_web_artifact - we saw this earlier with the HTML wrapper around the pelican: Meta AI can create HTML+JavaScript files in its container which can then be served up as secure sandboxed iframe interactives. "Set kind to html for websites/apps or svg for vector graphics."
  - container.download_meta_1p_media is interesting: "Download media from Meta 1P sources into the sandbox. Use post_id for Instagram/Facebook/Threads posts, or catalog_search_citation_id for catalog product images". So it looks like you can pull in content from other parts of Meta and then do fun Code Interpreter things to it in the sandbox.
  - container.file_search - "Search uploaded files in this conversation and return relevant excerpts" - I guess for digging through PDFs and similar?
  - Tools for editing files in the container - container.view, container.insert (with new_str and insert_line), container.str_replace. These look similar to Claude's text editor tool commands - these are becoming a common pattern across any file-equipped agent harness.
  - container.visual_grounding - see below, this one is fun.
  - subagents.spawn_agent - the sub-agent as a tool pattern. "Spawn an independent sub-agent for research, analysis, or delegation. It returns its final text response."
  - third_party.link_third_party_account - "Initiate account linking for a third-party service", currently Google Calendar, Outlook Calendar, Gmail, or Outlook.
  Image analysis in the container
  
  Let's talk about that container.visual_grounding one. Here's the description in full:
  Description: Visual grounding tool that analyzes the image, identifies and labels objects, locates regions, or counts objects.
  
  Parameters:
  
  object_names (array, required)
  
  image_path (string, default "")
  
  format_type ("bbox"|"point"|"count"|null, default "bbox")
  
  title (string|null)[string]
  So it can take an image path, optional object names and return things in format bbox, point or count.
  
  Sounds to me like Meta's Segment Anything. I decided to take it for a spin.
  
  Prompt:
  
  generate a photo of a raccoon sitting on a trash can wearing trash as a hat
  
  Response:
  
  Here you go — king of the alley, in full regalia:
  
  Coffee cup crown, banana peel brim, newspaper feather. Peak raccoon fashion. Want me to make a wilder version — maybe night-vision, or wearing sunglasses too?
  
  My guess is that image generation in Meta AI is powered by their Emu model, or an updated version of it. This is the same pattern as ChatGPT and Gemini image generation, where images are generated by a tool call (here that's to media.image_gen).
  
  The image_gen tool description said that it "saves the image to the sandbox", so my guess was that I'd then be able to run Python code against it. I tried:
  
  use python OpenCV to analyze that image and find out neat things about it
  
  Annoyingly it did not show me the code it ran, but it did create this image:
  
  Pretty neat! We can both generate images and then use them with Python tools.
  
  Next, the visual_grounding tool. Knowing the names of the tools makes it easy to refer to them in prompts:
  
  Now try the container.visual_grounding tool
  
  The response (full response here):
  
  Done — visual_grounding pinpointed every piece of the outfit with pixel-level precision:
  
  [...]
  
  Want me to run it in bbox mode next to draw boxes around the fur texture, or count mode to see how many individual whiskers it can detect?
  
  Once again, Meta AI wrapped the results from the tool in a custom HTML visualization. That's clearly point mode, but how about the others?
  
  I prompted:
  
  yes draw bounding boxes, can it do masks too?
  
  Response:
  Yes — bounding boxes work great. Masks? Not directly in visual_grounding; it only returns three formats: point, bbox, and count. No pixel-level segmentation masks.
  
  Here's the bbox output:
  
  What you’re seeing:
  
  raccoon: big box from (270,240) to (892,845) — covers 62% of the width, basically the whole animal
  
  coffee cup: (424,115)-(610,273) — sits highest, 158px tall in the 0-1000 space
  
  banana peel: (472,215)-(667,291) — overlaps the cup's base, confirming it's draped over the side
  
  newspaper: (305,223)-(548,315) — left ear coverage
  
  trash can lid: (107,800)-(1000,998) — spans almost the full image width at the bottom
  
  face: (305,283)-(750,537) — tight crop around the mask
  
  eyes: both ~40×37 pixel boxes, perfectly level at y=379
  
  Notice how the boxes nest: face is inside raccoon, eyes inside face, hat pieces overlap each other but stay above the face box. The tool is doing real object localization, not just guessing centers.
  
  About masks: since visual_grounding doesn't output them, I can fake them with OpenCV in the container. Two quick options:
  
  GrabCut — I give it the raccoon bbox, it iteratively segments fur from background and returns a binary mask
  
  SAM-style color threshold — use the bbox plus k-means to isolate the coffee cup or banana peel
  
  Want me to generate an actual alpha mask for the raccoon (cut it out from the alley), or for the trash hat pieces separately? Takes about 10 seconds and I can give you a transparent PNG.
  Here's the HTML for that bbox visualization.
  
  Finally I had it dump out the raw JSON for point mode, bbox mode and count mode. You can see that all here. The count mode is particularly interesting - here's that in full:
  [ { "object_name": "raccoon whisker", "points": [ {"x": 403, "y": 445}, {"x": 397, "y": 458}, {"x": 392, "y": 472}, {"x": 391, "y": 485}, {"x": 398, "y": 497}, {"x": 415, "y": 512}, {"x": 618, "y": 446}, {"x": 622, "y": 461}, {"x": 625, "y": 475}, {"x": 628, "y": 488}, {"x": 635, "y": 501}, {"x": 651, "y": 518} ], "count": 12 }, { "object_name": "raccoon paw claw", "points": [ {"x": 406, "y": 845}, {"x": 424, "y": 847}, {"x": 441, "y": 842}, {"x": 473, "y": 833}, {"x": 596, "y": 830}, {"x": 635, "y": 844}, {"x": 660, "y": 843}, {"x": 679, "y": 838} ], "count": 8 }, { "object_name": "trash item on head", "points": [ {"x": 514, "y": 191}, {"x": 568, "y": 263}, {"x": 392, "y": 274} ], "count": 3 }, { "object_name": "eye", "points": [ {"x": 462, "y": 395}, {"x": 582, "y": 398} ], "count": 2 }, { "object_name": "ear", "points": [ {"x": 359, "y": 313}, {"x": 680, "y": 294} ], "count": 2 } ]
  So Meta AI has the ability to count a raccoon's whiskers baked into the default set of tools.
  
  Which means... it can count pelicans too!
  
  Here's that overlay exported as HTML.
  
  Maybe open weights in the future?
  
  On Twitter Alexandr Wang said:
  
  this is step one. bigger models are already in development with infrastructure scaling to match. private api preview open to select partners today, with plans to open-source future versions.
  
  I really hope they do go back to open-sourcing their models. Llama 3.1/3.2/3.3 were excellent laptop-scale model families, and the introductory blog post for Muse Spark had this to say about efficiency:
  
  [...] we can reach the same capabilities with over an order of magnitude less compute than our previous model, Llama 4 Maverick. This improvement also makes Muse Spark significantly more efficient than the leading base models available for comparison.
  
  So are Meta back in the frontier model game? Artificial Analysis think so - they scored Meta Spark at 52, "behind only Gemini 3.1 Pro, GPT-5.4, and Claude Opus 4.6". Last year's Llama 4 Maverick and Scout scored 18 and 13 respectively.
  
  I'm waiting for API access - while the tool collection on meta.ai is quite strong the real test of a model like this is still what we can build on top of it.
  
  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.
3. 🔗 badlogic/pi-mono v0.66.1 release
  Changed
  - Changed the Earendil announcement from an automatic startup notice to the hidden /dementedelves slash command.
4. 🔗 anthropics/claude-code v2.1.97 release
  What's changed
  - Added focus view toggle (Ctrl+O) in NO_FLICKER mode showing prompt, one-line tool summary with edit diffstats, and final response
  - Added refreshInterval status line setting to re-run the status line command every N seconds
  - Added workspace.git_worktree to the status line JSON input, set when the current directory is inside a linked git worktree
  - Added ● N running indicator in /agents next to agent types with live subagent instances
  - Added syntax highlighting for Cedar policy files (.cedar, .cedarpolicy)
  - Fixed --dangerously-skip-permissions being silently downgraded to accept-edits mode after approving a write to a protected path
  - Fixed and hardened Bash tool permissions, tightening checks around env-var prefixes and network redirects, and reducing false prompts on common commands
  - Fixed permission rules with names matching JavaScript prototype properties (e.g. toString) causing settings.json to be silently ignored
  - Fixed managed-settings allow rules remaining active after an admin removed them until process restart
  - Fixed permissions.additionalDirectories changes in settings not applying mid-session
  - Fixed removing a directory from settings.permissions.additionalDirectories revoking access to the same directory passed via --add-dir
  - Fixed MCP HTTP/SSE connections accumulating ~50 MB/hr of unreleased buffers when servers reconnect
  - Fixed MCP OAuth oauth.authServerMetadataUrl not being honored on token refresh after restart, fixing ADFS and similar IdPs
  - Fixed 429 retries burning all attempts in ~13 seconds when the server returns a small Retry-After — exponential backoff now applies as a minimum
  - Fixed rate-limit upgrade options disappearing after context compaction
  - Fixed several /resume picker issues: --resume <name> opening uneditable, Ctrl+A reload wiping search, empty list swallowing navigation, task-status text replacing conversation summary, and cross-project staleness
  - Fixed file-edit diffs disappearing on --resume when the edited file was larger than 10KB
  - Fixed --resume cache misses and lost mid-turn input from attachment messages not being saved to the transcript
  - Fixed messages typed while Claude is working not being persisted to the transcript
  - Fixed prompt-type Stop/SubagentStop hooks failing on long sessions, and hook evaluator API errors displaying "JSON validation failed" instead of the actual message
  - Fixed subagents with worktree isolation or cwd: override leaking their working directory back to the parent session's Bash tool
  - Fixed compaction writing duplicate multi-MB subagent transcript files on prompt-too-long retries
  - Fixed claude plugin update reporting "already at the latest version" for git-based marketplace plugins when the remote had newer commits
  - Fixed slash command picker breaking when a plugin's frontmatter name is a YAML boolean keyword
  - Fixed copying wrapped URLs in NO_FLICKER mode inserting spaces at line breaks
  - Fixed scroll rendering artifacts in NO_FLICKER mode when running inside zellij
  - Fixed a crash in NO_FLICKER mode when hovering over MCP tool results
  - Fixed a NO_FLICKER mode memory leak where API retries left stale streaming state
  - Fixed slow mouse-wheel scrolling in NO_FLICKER mode on Windows Terminal
  - Fixed custom status line not displaying in NO_FLICKER mode on terminals shorter than 24 rows
  - Fixed Shift+Enter and Alt/Cmd+arrow shortcuts not working in Warp with NO_FLICKER mode
  - Fixed Korean/Japanese/Unicode text becoming garbled when copied in no-flicker mode on Windows
  - Fixed Bedrock SigV4 authentication failing when AWS_BEARER_TOKEN_BEDROCK or ANTHROPIC_BEDROCK_BASE_URL are set to empty strings (as GitHub Actions does for unset inputs)
  - Improved Accept Edits mode to auto-approve filesystem commands prefixed with safe env vars or process wrappers (e.g. LANG=C rm foo, timeout 5 mkdir out)
  - Improved auto mode and bypass-permissions mode to auto-approve sandbox network access prompts
  - Improved sandbox: sandbox.network.allowMachLookup now takes effect on macOS
  - Improved image handling: pasted and attached images are now compressed to the same token budget as images read via the Read tool
  - Improved slash command and @-mention completion to trigger after CJK sentence punctuation, so Japanese/Chinese input no longer requires a space before / or @
  - Improved Bridge sessions to show the local git repo, branch, and working directory on the claude.ai session card
  - Improved footer layout: indicators (Focus, notifications) now stay on the mode-indicator row instead of wrapping below
  - Improved context-low warning to show as a transient footer notification instead of a persistent row
  - Improved markdown blockquotes to show a continuous left bar across wrapped lines
  - Improved session transcript size by skipping empty hook entries and capping stored pre-edit file copies
  - Improved transcript accuracy: per-block entries now carry the final token usage instead of the streaming placeholder
  - Improved Bash tool OTEL tracing: subprocesses now inherit a W3C TRACEPARENT env var when tracing is enabled
  - Updated /claude-api skill to cover Managed Agents alongside the Claude API
5. 🔗 r/wiesbaden Dein erster Pulli: Strickworkshop in Wiesbaden Westend rss
  
  Hey zusammen 🤍
  
  bei unseren KNIT&MEET Events kam öfter die Frage auf, wie man eigentlich den ersten Pulli strickt. Deshalb haben wir für Samstag in Wiesbaden einen kleinen Workshop dazu organisiert.
  
  In der ersten Hälfte geht’s um die Basics: wie Pullis aufgebaut sind, wie man Patterns liest und worauf man am Anfang achten sollte. In der zweiten Hälfte schauen wir uns auch mitgebrachte Patterns an, beantworten Fragen und helfen beim Start.
  
  Falls das hier für jemanden interessant ist, schicke ich die Infos gern per DM oder poste den Link in die Kommentare :)
  
  submitted by /u/authentic_n_creative
  [link] [comments]
6. 🔗 r/wiesbaden Yoga in Kastel rss
  
  Hat jemand Lust auf Outdoor Yoga in Mainz-Kastel am Rhein? Jeder ist Willkommen. Ich bin Yoga Lehrerin und würde gerne eine Community hier aufbauen ✨
  
  submitted by /u/flowyogamarie
  [link] [comments]
7. 🔗 jcrist/msgspec Version 0.21.0 release
  - Fix a segfault on Python 3.13+ that could occur when creating structs that contained a __dict__, instead of only using __slots__ (#960).
  - Improve type annotations for msgspec.UNSET (#975).
  - Fix hashing of decoded tuples on Python 3.14 (#980).
  - Add ref_template arg to msgspec.json.schema (#983).
  - Add missing libm linkage to some architectures (#993).
  - Fix memory leak when decoding sets (#991).
  - Add uniqueItems annotation to set/frozenset JSON schemas (#984).
  - BREAKING : Call __post_init__ from msgspec.structs.replace/copy.replace (#1000).
8. 🔗 r/york York therapists rss
  
  I'm looking for recommendations for therapists in the York area who specialise in adults dealing with the effects of being abused as a child/teen by a parent, and ideally has experience with Autistic people. Who have you really clicked with? I'm particularly interested in people who are clear and concise, and who don't talk in circles or metaphors.
  
  Ideally based in the city center, or Acomb.
  
  Thank you!
  
  submitted by /u/I-am-a-commotion
  [link] [comments]
9. 🔗 r/wiesbaden The vendor at the newspaper stand just kind of accepted it rss
  
  submitted by /u/elena4047
  [link] [comments]
10. 🔗 badlogic/pi-mono v0.66.0 release
  New Features
  - Earendil startup announcement with bundled inline image rendering and a linked blog post for April 8 and 9, 2026.
  - Interactive Anthropic subscription auth warning when Anthropic subscription auth is active, clarifying that Anthropic third-party usage draws from extra usage and is billed per token.
  Fixed
  - Fixed bare readline import to use node:readline prefix for Deno compatibility (#2885 by @milosv-vtool)
  - Fixed auto-retry to treat stream failures like request ended without sending any chunks as transient errors (#2892)
  - Fixed interactive startup notices to render after the initial resource listing, and added a bundled Earendil startup announcement with inline image rendering for April 8 and 9, 2026. Moved the blog link above the image to avoid overlap with terminal image rendering.
  - Fixed interactive mode to warn when Anthropic subscription auth is active, so users know Anthropic third-party usage draws from extra usage and is billed per token.
11. 🔗 r/Leeds Rhinos fan to take on 108-mile ultra-marathon for MNDA rss
  
  submitted by /u/TexturePackReview
  [link] [comments]
12. 🔗 backnotprop/plannotator v0.17.3 release
  Follow @plannotator on X for updates
  
  Missed recent releases? Release | Highlights
  ---|---
  v0.17.1 | Pi PR review parity, parseRemoteUrl rewrite, cross-repo clone fixes, diff viewer flash fix
  v0.17.0 | AI code review agents, token-level annotation, merge-base diffs
  v0.16.7 | Gemini CLI plan review, install script skills directory fix
  v0.16.6 | Perforce support, Pi shared event API, suggested code prefill, file tree expand fix
  v0.16.5 | Resize handle scrollbar fix, VS Code Marketplace publish
  v0.16.4 | Compound planning improvement hook, GitHub Enterprise + self-hosted GitLab, dockview workspace, new themes
  v0.16.3 | Pi phase configuration, CLI help, untracked file discovery fix, review scroll reset
  v0.16.2 | Draggable comment popovers, cross-file annotation visibility, custom diff fonts, OpenCode verbose log fix
  v0.16.1 | SSE stream idle timeout fix for external annotations API
  v0.16.0 | GitHub Copilot CLI, external annotations API, bot callback URLs, interactive checkboxes, print support, diff display options
  v0.15.5 | Custom display names, GitHub viewed file sync, expand/collapse all in file tree, search performance, WSL fix
  v0.15.2 | Compound Planning skill, folder annotation, /plannotator-archive slash command, skill installation via platform installers
  
  What's New in v0.17.3
  
  v0.17.3 is a substantial release covering ten PRs — supply-chain hardening with SLSA build attestations, a major plan header overhaul with sticky toolstrip and badges, overlay scrollbars across the entire app, inline highlighting for external annotations, Conventional Comments in code review, and several smaller fixes from the community. Two contributors from outside the core team shipped changes this cycle.
  
  Sticky Toolstrip and Badges
  
  The stickyActionsEnabled setting previously only pinned the right-side action buttons. The annotation toolstrip (selection mode + editor mode toggles) and the left-side badges (repo, branch, plan diff) scrolled away with the document, forcing you back to the top to switch modes or jump into a diff.
  
  A new ghost sticky lane fades in once you scroll past the original toolstrip, pinning the toolstrip and badges on the same horizontal plane as the action buttons. The compact bar uses a row layout for badges and hides label text on inactive toolstrip modes to leave room. Top-of-document rendering is unchanged. The lane stays hidden in plan-diff mode, archive mode, linked-doc mode, and when sticky actions is off. Honors prefers-reduced-motion.
  
  #510
  
  Conventional Comments in Code Review
  
  The code review annotation toolbar now has an optional Conventional Comments label picker — suggestion, issue, nitpick, question, and others, with an inline blocking/non- blocking toggle per label. Annotations export in conventional format (**label** (decoration): text) as plain markdown, compatible with GitHub PRs and any text-based review system.
  
  A dedicated Comments settings tab houses the master toggle (off by default), a label editor for adding/editing/deleting/reordering custom labels, per-label blocking decorator toggle, an educational "how it works" section linking to the spec, and live example output. Drafts persist label and decoration state across file switches.
  
  #501
  
  Unified Plan Header Dropdown and Agent Instructions
  
  Plan mode's header has been consolidated. The sprawled desktop toolbar (mode toggle, standalone Settings button, custom export sub-dropdown) and the separate mobile menu are now a single PlanHeaderMenu rendered at all breakpoints, modeled on the existing review header menu. The version number and release notes link moved into the dropdown footer.
  
  A new "Agent Instructions" item copies a clipboard payload teaching external agents (Claude Code, Codex, custom scripts) how to POST annotations into the live session via /api/external-annotations. The instruction body lives in packages/ui/utils/planAgentInstructions.ts so it can be edited independently of UI code.
  
  The PR also fixes a long-standing bug where the Send Annotations / Approve cluster was hidden whenever a linked doc was active, blocking submission for users running plannotator annotate ./ once they opened a file.
  
  #515
  
  Header Polish: Coordinated Shrinking, Share/Copy Cleanup
  
  Sticky header label shrinking is now driven by measured geometry instead of fixed pixel reserves. A ResizeObserver on the wrapper plus another on the action button cluster computes exactly how much room is available; both sides of the header shrink in lockstep so they stay horizontally aligned as long as possible. Below ~340px of plan area the ghost bar stacks below the action buttons.
  
  "Quick Share" and "Quick Copy" are now plain "Share" and "Copy". Share opens the existing export modal so it benefits from the short-link path for large payloads instead of dumping a 50KB hash URL straight to the clipboard.
  
  The sidebar rail no longer pushes the background grid pattern 30px to the right — it floats over the document area, and the grid paints edge-to-edge under the sidebar flags.
  
  #519
  
  Overlay Scrollbars
  
  Wide, translucent, full-length overlay scrollbars across plan mode and code review, replacing the 6px WebKit rail that was hard to grab. Click the track to page-animate toward the click; drag the thumb smoothly; no layout shift; Firefox parity; respects prefers-reduced-motion; disappears in print.
  
  Backed by overlayscrollbars-react wrapped in a new OverlayScrollArea component. Native scroll semantics stay on the viewport element so existing scrollIntoView and scrollTo calls still work. Wrapped containers include the main plan viewer, annotation panel, sidebar tabs, settings and export modals, file tree, review sidebar, AI chat tab, PR comments timeline, and PR summary/checks dock panels.
  
  #509, closing #354
  
  Inline Highlighting for External Annotations
  
  External annotations posted via POST /api/external-annotations can now optionally highlight the matching originalText span inline in the rendered plan — COMMENT renders yellow, DELETION renders strikethrough. Annotations without originalText or of type GLOBAL_COMMENT continue to render sidebar- only.
  
  No protocol or schema change. Tools choose inline vs global purely by what they supply. If originalText doesn't match anywhere in the rendered DOM, the annotation degrades gracefully to sidebar-only with a console warning. PATCH and DELETE through the API correctly remove and reapply highlights as state changes.
  
  #511
  
  Supply-Chain Hardening
  
  The release pipeline now generates SLSA build provenance attestations for every released binary. Each of the twelve cross-compiled binaries (six Plannotator targets, six paste-service targets) is signed via Sigstore and recorded in Rekor through actions/attest-build-provenance. Top-level workflow permissions have been tightened to contents: read with per-job overrides.
  
  Installers now accept a --version v0.X.Y flag (and positional form), so you can pin to a specific version instead of always pulling latest. The default behavior is unchanged.
  
  Attestation verification is opt-in via three mechanisms with documented precedence: a --verify-attestation CLI flag, a PLANNOTATOR_VERIFY_ATTESTATION=1 environment variable, or { "verifyAttestation": true } in ~/.plannotator/config.json. Off by default to match how rustup, brew, bun, deno, and helm handle attestation — turning it on hard-fails the install if gh isn't available, so opt-in is never silently skipped. Anyone can still verify any release manually with gh attestation verify.
  
  The same PR fixes a Windows installer crash where cmd.exe's enabledelayedexpansion was eating the ! characters in an embedded node -e script during Gemini settings merge.
  
  #512, closing #506 and parts of #507
  
  Additional Changes
  - Numbered list rendering. Ordered lists like 1., 2., 10. were rendered as bullet points because the parser collapsed all list types into a single block kind. The parser now captures the numeric marker and tags the block as ordered; a new computeListIndices helper assigns CommonMark-correct display numbers including streak break/restart on mixed siblings and independent numbering for nested ordered sublists. The renderer uses tabular-nums so 9 to 10 doesn't jitter (#520)
  - Underscore italics. The custom markdown renderer supported *italic* but not _italic_. Now both work, while intraword underscores like snake_case continue to render as plain text (#504 by @foxytanuki, closing #502)
  - Perforce added files on Windows. P4-added files were missing from the review UI on Windows because p4 where stdout uses \r\n line endings; splitting on \n left a stray \r in every file path except the last, causing Bun.file() to silently fail. The fix normalizes line endings on all P4 command output and replaces fragile index-based parsing with p4 -ztag where field-based parsing, which is also more robust for stream depots and overlay mappings (#494 by @l10veu602)
  Install / Update
  
  macOS / Linux:
```
curl -fsSL https://plannotator.ai/install.sh | bash
```
  Windows:
```
irm https://plannotator.ai/install.ps1 | iex
```
  Pin a specific version:
```
curl -fsSL https://plannotator.ai/install.sh | bash -s -- --version v0.17.3
```
  Claude Code Plugin: Run /plugin in Claude Code, find plannotator , and click "Update now".
  
  Copilot CLI:
```
/plugin marketplace add backnotprop/plannotator
/plugin install plannotator-copilot@plannotator
```
  Gemini CLI: The install script auto-detects ~/.gemini and configures hooks, policy, and slash commands. See apps/gemini/README.md for manual setup.
  
  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
```
  VS Code Extension: Install from the VS Code Marketplace. Tested with Claude Code running in VS Code's integrated terminal. Not currently compatible with Anthropic's official VS Code extension due to upstream hook bugs.
  
  What's Changed
  - fix(ui): render numerals for ordered list items by @backnotprop in #520
  - feat(plan): simplify share/copy + sticky header polish by @backnotprop in #519
  - chore: supply-chain hardening — version pinning, SLSA attestations, install fix by @backnotprop in #512
  - feat(plan): unified header dropdown + Agent Instructions by @backnotprop in #515
  - feat: Zed-style overlay scrollbars by @backnotprop in #509
  - feat(plan): complete sticky actions — pin toolstrip + badges on scroll by @backnotprop in #510
  - feat(ui): highlight external SSE annotations inline on plan text by @backnotprop in #511
  - fix: support underscore italics in markdown renderer by @foxytanuki in #504
  - feat: add Conventional Comments support to code review by @backnotprop in #501
  - fix(review): show P4 added files in code review by @l10veu602 in #494
  Contributors
  
  @foxytanuki returned with the underscore italics fix (#504, closing #502). The custom markdown renderer now treats _italic_ and *italic* as equivalent emphasis while leaving snake_case alone. Their fourth contribution to the project.
  
  @l10veu602 fixed the Perforce added-files regression on Windows (#494). The bug was a classic \r\n line-ending issue in p4 where stdout that left stray carriage returns in file paths, causing Bun.file() to silently miss them. The fix also swaps fragile index-based parsing for p4 -ztag structured output, which holds up better on stream depots and overlay mappings. Verified on a real P4 workspace going from 13 files visible to all 17.
  
  Community members who reported issues addressed in this release:
  - @djamatgit: #506 (install.cmd Gemini settings merge crash on Windows)
  - @rooterkyberian: #507 (supply-chain hardening — items 1 & 2)
  - @Thraka: #502 (underscore italics not rendering)
  - @dillonoconnor: #354 (couldn't grab the scrollbar)
  Full Changelog : v0.17.1...v0.17.3
13. 🔗 backnotprop/plannotator v0.17.2 release
  Follow @plannotator on X for updates
  
  Missed recent releases? Release | Highlights
  ---|---
  v0.17.1 | Pi PR review parity, parseRemoteUrl rewrite, cross-repo clone fixes, diff viewer flash fix
  v0.17.0 | AI code review agents, token-level annotation, merge-base diffs
  v0.16.7 | Gemini CLI plan review, install script skills directory fix
  v0.16.6 | Perforce support, Pi shared event API, suggested code prefill, file tree expand fix
  v0.16.5 | Resize handle scrollbar fix, VS Code Marketplace publish
  v0.16.4 | Compound planning improvement hook, GitHub Enterprise + self-hosted GitLab, dockview workspace, new themes
  v0.16.3 | Pi phase configuration, CLI help, untracked file discovery fix, review scroll reset
  v0.16.2 | Draggable comment popovers, cross-file annotation visibility, custom diff fonts, OpenCode verbose log fix
  v0.16.1 | SSE stream idle timeout fix for external annotations API
  v0.16.0 | GitHub Copilot CLI, external annotations API, bot callback URLs, interactive checkboxes, print support, diff display options
  v0.15.5 | Custom display names, GitHub viewed file sync, expand/collapse all in file tree, search performance, WSL fix
  v0.15.2 | Compound Planning skill, folder annotation, /plannotator-archive slash command, skill installation via platform installers
  
  What's New in v0.17.2
  
  v0.17.2 is a substantial release covering ten PRs — supply-chain hardening with SLSA build attestations, a major plan header overhaul with sticky toolstrip and badges, overlay scrollbars across the entire app, inline highlighting for external annotations, Conventional Comments in code review, and several smaller fixes from the community. Two contributors from outside the core team shipped changes this cycle.
  
  Sticky Toolstrip and Badges
  
  The stickyActionsEnabled setting previously only pinned the right-side action buttons. The annotation toolstrip (selection mode + editor mode toggles) and the left-side badges (repo, branch, plan diff) scrolled away with the document, forcing you back to the top to switch modes or jump into a diff.
  
  A new ghost sticky lane fades in once you scroll past the original toolstrip, pinning the toolstrip and badges on the same horizontal plane as the action buttons. The compact bar uses a row layout for badges and hides label text on inactive toolstrip modes to leave room. Top-of-document rendering is unchanged. The lane stays hidden in plan-diff mode, archive mode, linked-doc mode, and when sticky actions is off. Honors prefers-reduced-motion.
  
  #510
  
  Conventional Comments in Code Review
  
  The code review annotation toolbar now has an optional Conventional Comments label picker — suggestion, issue, nitpick, question, and others, with an inline blocking/non- blocking toggle per label. Annotations export in conventional format (**label** (decoration): text) as plain markdown, compatible with GitHub PRs and any text-based review system.
  
  A dedicated Comments settings tab houses the master toggle (off by default), a label editor for adding/editing/deleting/reordering custom labels, per-label blocking decorator toggle, an educational "how it works" section linking to the spec, and live example output. Drafts persist label and decoration state across file switches.
  
  #501
  
  Unified Plan Header Dropdown and Agent Instructions
  
  Plan mode's header has been consolidated. The sprawled desktop toolbar (mode toggle, standalone Settings button, custom export sub-dropdown) and the separate mobile menu are now a single PlanHeaderMenu rendered at all breakpoints, modeled on the existing review header menu. The version number and release notes link moved into the dropdown footer.
  
  A new "Agent Instructions" item copies a clipboard payload teaching external agents (Claude Code, Codex, custom scripts) how to POST annotations into the live session via /api/external-annotations. The instruction body lives in packages/ui/utils/planAgentInstructions.ts so it can be edited independently of UI code.
  
  The PR also fixes a long-standing bug where the Send Annotations / Approve cluster was hidden whenever a linked doc was active, blocking submission for users running plannotator annotate ./ once they opened a file.
  
  #515
  
  Header Polish: Coordinated Shrinking, Share/Copy Cleanup
  
  Sticky header label shrinking is now driven by measured geometry instead of fixed pixel reserves. A ResizeObserver on the wrapper plus another on the action button cluster computes exactly how much room is available; both sides of the header shrink in lockstep so they stay horizontally aligned as long as possible. Below ~340px of plan area the ghost bar stacks below the action buttons.
  
  "Quick Share" and "Quick Copy" are now plain "Share" and "Copy". Share opens the existing export modal so it benefits from the short-link path for large payloads instead of dumping a 50KB hash URL straight to the clipboard.
  
  The sidebar rail no longer pushes the background grid pattern 30px to the right — it floats over the document area, and the grid paints edge-to-edge under the sidebar flags.
  
  #519
  
  Overlay Scrollbars
  
  Wide, translucent, full-length overlay scrollbars across plan mode and code review, replacing the 6px WebKit rail that was hard to grab. Click the track to page-animate toward the click; drag the thumb smoothly; no layout shift; Firefox parity; respects prefers-reduced-motion; disappears in print.
  
  Backed by overlayscrollbars-react wrapped in a new OverlayScrollArea component. Native scroll semantics stay on the viewport element so existing scrollIntoView and scrollTo calls still work. Wrapped containers include the main plan viewer, annotation panel, sidebar tabs, settings and export modals, file tree, review sidebar, AI chat tab, PR comments timeline, and PR summary/checks dock panels.
  
  #509, closing #354
  
  Inline Highlighting for External Annotations
  
  External annotations posted via POST /api/external-annotations can now optionally highlight the matching originalText span inline in the rendered plan — COMMENT renders yellow, DELETION renders strikethrough. Annotations without originalText or of type GLOBAL_COMMENT continue to render sidebar- only.
  
  No protocol or schema change. Tools choose inline vs global purely by what they supply. If originalText doesn't match anywhere in the rendered DOM, the annotation degrades gracefully to sidebar-only with a console warning. PATCH and DELETE through the API correctly remove and reapply highlights as state changes.
  
  #511
  
  Supply-Chain Hardening
  
  The release pipeline now generates SLSA build provenance attestations for every released binary. Each of the twelve cross-compiled binaries (six Plannotator targets, six paste-service targets) is signed via Sigstore and recorded in Rekor through actions/attest-build-provenance. Top-level workflow permissions have been tightened to contents: read with per-job overrides.
  
  Installers now accept a --version v0.X.Y flag (and positional form), so you can pin to a specific version instead of always pulling latest. The default behavior is unchanged.
  
  Attestation verification is opt-in via three mechanisms with documented precedence: a --verify-attestation CLI flag, a PLANNOTATOR_VERIFY_ATTESTATION=1 environment variable, or { "verifyAttestation": true } in ~/.plannotator/config.json. Off by default to match how rustup, brew, bun, deno, and helm handle attestation — turning it on hard-fails the install if gh isn't available, so opt-in is never silently skipped. Anyone can still verify any release manually with gh attestation verify.
  
  The same PR fixes a Windows installer crash where cmd.exe's enabledelayedexpansion was eating the ! characters in an embedded node -e script during Gemini settings merge.
  
  #512, closing #506 and parts of #507
  
  Additional Changes
  - Numbered list rendering. Ordered lists like 1., 2., 10. were rendered as bullet points because the parser collapsed all list types into a single block kind. The parser now captures the numeric marker and tags the block as ordered; a new computeListIndices helper assigns CommonMark-correct display numbers including streak break/restart on mixed siblings and independent numbering for nested ordered sublists. The renderer uses tabular-nums so 9 to 10 doesn't jitter (#520)
  - Underscore italics. The custom markdown renderer supported *italic* but not _italic_. Now both work, while intraword underscores like snake_case continue to render as plain text (#504 by @foxytanuki, closing #502)
  - Perforce added files on Windows. P4-added files were missing from the review UI on Windows because p4 where stdout uses \r\n line endings; splitting on \n left a stray \r in every file path except the last, causing Bun.file() to silently fail. The fix normalizes line endings on all P4 command output and replaces fragile index-based parsing with p4 -ztag where field-based parsing, which is also more robust for stream depots and overlay mappings (#494 by @l10veu602)
  Install / Update
  
  macOS / Linux:
```
curl -fsSL https://plannotator.ai/install.sh | bash
```
  Windows:
```
irm https://plannotator.ai/install.ps1 | iex
```
  Pin a specific version:
```
curl -fsSL https://plannotator.ai/install.sh | bash -s -- --version v0.17.2
```
  Claude Code Plugin: Run /plugin in Claude Code, find plannotator , and click "Update now".
  
  Copilot CLI:
```
/plugin marketplace add backnotprop/plannotator
/plugin install plannotator-copilot@plannotator
```
  Gemini CLI: The install script auto-detects ~/.gemini and configures hooks, policy, and slash commands. See apps/gemini/README.md for manual setup.
  
  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
```
  VS Code Extension: Install from the VS Code Marketplace. Tested with Claude Code running in VS Code's integrated terminal. Not currently compatible with Anthropic's official VS Code extension due to upstream hook bugs.
  
  What's Changed
  - fix(ui): render numerals for ordered list items by @backnotprop in #520
  - feat(plan): simplify share/copy + sticky header polish by @backnotprop in #519
  - chore: supply-chain hardening — version pinning, SLSA attestations, install fix by @backnotprop in #512
  - feat(plan): unified header dropdown + Agent Instructions by @backnotprop in #515
  - feat: Zed-style overlay scrollbars by @backnotprop in #509
  - feat(plan): complete sticky actions — pin toolstrip + badges on scroll by @backnotprop in #510
  - feat(ui): highlight external SSE annotations inline on plan text by @backnotprop in #511
  - fix: support underscore italics in markdown renderer by @foxytanuki in #504
  - feat: add Conventional Comments support to code review by @backnotprop in #501
  - fix(review): show P4 added files in code review by @l10veu602 in #494
  Contributors
  
  @foxytanuki returned with the underscore italics fix (#504, closing #502). The custom markdown renderer now treats _italic_ and *italic* as equivalent emphasis while leaving snake_case alone. Their fourth contribution to the project.
  
  @l10veu602 fixed the Perforce added-files regression on Windows (#494). The bug was a classic \r\n line-ending issue in p4 where stdout that left stray carriage returns in file paths, causing Bun.file() to silently miss them. The fix also swaps fragile index-based parsing for p4 -ztag structured output, which holds up better on stream depots and overlay mappings. Verified on a real P4 workspace going from 13 files visible to all 17.
  
  Community members who reported issues addressed in this release:
  - @djamatgit: #506 (install.cmd Gemini settings merge crash on Windows)
  - @rooterkyberian: #507 (supply-chain hardening — items 1 & 2)
  - @Thraka: #502 (underscore italics not rendering)
  - @dillonoconnor: #354 (couldn't grab the scrollbar)
  Full Changelog : v0.17.1...v0.17.2
14. 🔗 r/LocalLLaMA kepler-452b. GGUF when? rss
  
  | submitted by /u/the-grand-finale
  [link] [comments]
  ---|---
15. 🔗 r/reverseengineering Runtime JavaScript instrumentation via CDP (no monkeypatching, works inside closures) rss
  
  submitted by /u/filippo_cavallarin
  [link] [comments]
16. 🔗 r/Harrogate Window cleaners rss
  
  Best window cleaners in Harrogate? Preferably via ladder rather than telescopic pole. Thanks.
  
  submitted by /u/Outrageous-Square-21
  [link] [comments]
17. 🔗 r/reverseengineering [Tool] Rikune: A reverse-engineering MCP server that turns PE triage, Ghidra analysis, runtime evidence, and source-like reconstruction into reusable tools for any LLM rss
  
  submitted by /u/MomOxIao_FoReVEr
  [link] [comments]
18. 🔗 r/wiesbaden Gravity Trail rss
  
  Ich habe soviele Mythen und Märchen gehört, was ist denn nun wirklich passiert?
  
  submitted by /u/pathetichypocrit
  [link] [comments]
19. 🔗 r/reverseengineering Reverse-engineered the Whoop 4.0 BLE protocol — CRC-32 with non-standard polynomial, 96-byte real-time data packets rss
  
  submitted by /u/batoba
  [link] [comments]
20. 🔗 anthropics/claude-code v2.1.96 release
  What's changed
  - Fixed Bedrock requests failing with 403 "Authorization header is missing" when using AWS_BEARER_TOKEN_BEDROCK or CLAUDE_CODE_SKIP_BEDROCK_AUTH (regression in 2.1.94)
21. 🔗 Pagefind/pagefind v1.5.1 release
  
  v1.5.1
22. 🔗 r/reverseengineering From UART to Root: Vendor Shell Escape on a Uniview IP Camera rss
  
  submitted by /u/Vymmy
  [link] [comments]
23. 🔗 r/Leeds "What's on?" Wednesday - April 08, 2026 rss
  "What's on?" Wednesday
  
  Our weekly post where people can highlight local events or interesting things that are coming up in the next week. It doesn't have to be your event, but this is a place where reasonable exceptions to our self-promotion rules are allowed. Please check whether the event you're posting about is already mentioned. If you're adding your own event, please try to answer any questions people may have in the comments.
  
  You can also ask questions if you're looking for something to do, e.g. "Does anyone know of a good pub quiz in the centre on Thursday?"
  
  " What's on?" rules:
  1. Leeds based events only
  2. Must be taking place in the next 7 days (next Wednesday included)
  3. Posts highlighting an event should include:
    
    Event name
    
    Date and time
    
    Location
    
    Price(s) (if applicable)
  4. A description of the event and a relevant link is recommended but not required
  The rules may evolve over time as we find out how things work. Please send any feedback to the mod team.
  
  submitted by /u/AutoModerator
  [link] [comments]
24. 🔗 Mario Zechner I've sold out rss
  
  I've sold out
25. 🔗 Armin Ronacher Mario and Earendil rss
  
  Today I'm very happy to share that Mario Zechner is joining Earendil.
  
  First things first: I think you should read Mario's post. This is his news more than it is ours, and he tells his side of it better than I could. What I want to do here is add a more personal note about why this matters so much to me, how the last months led us here, and why I am so excited to have him on board.
  
  Last year changed the way many of us thought about software. It certainly changed the way I did. I spent much of 2025 building, probing, and questioning how to build software, and in many more ways what I want to do. If you are a regular reader of this blog you were along for the ride. I wrote a lot, experimented a lot, and tried to get a better sense for what these systems can actually do and what kinds of companies make sense to build around them. There was, and continues to be, a lot of excitement in the air, but also a lot of noise. It has become clear to me that it's not a question of whether AI systems can be useful but what kind of software and human-machine interactions we want to bring into the world with them.
  
  That is one of the reasons I have been so drawn to Mario's work and approaches.
  
  Pi is, in my opinion, one of the most thoughtful coding agents and agent infrastructure libraries in this space. Not because it is trying to be the loudest or the fastest, but because it is clearly built by someone who cares deeply about software quality, taste, extensibility, and design. In a moment where much of the industry is racing to ship ever more quickly, often at the cost of coherence and craft, Mario kept insisting on making something solid. That matters to me a great deal.
  
  I have known Mario for a long time, and one of the things I admire most about him is that he does not confuse velocity with progress. He has a strong sense for what good tools should feel like. He cares about details. He cares about whether something is well made. And he cares about building in a way that can last. Mario has been running Pi in a rather unusual way. He exerts back- pressure on the issue tracker and the pull requests through OSS vacations and other means.
  
  The last year has also made something else clearer to me: these systems are not only exciting, they are also capable of producing a great deal of damage. Sometimes that damage is obvious; sometimes it looks like low-grade degradation everywhere at once. More slop, more noise, more disingenuous emails in my inbox. There is a version of this future that makes people more distracted, more alienated, and less careful with one another.
  
  That is not a future I want to help build.
  
  At Earendil, Colin and I have been trying to think very carefully about what a different path might look like. That is a big part of what led us to Lefos.
  
  Lefos is our attempt to build a machine entity that is more thoughtful and more deliberate by design. Not an agent whose main purpose is to make everything a little more efficient so that we can produce even more forgettable output, but one that can help people communicate with more care, more clarity, and joy.
  
  Good software should not aim to optimize every minute of your life, but should create room for better and more joyful experiences, better relationships, and better ways of relating to one another. Especially in communication and software engineering, I think we should be aiming for more thought rather than more throughput. We should want tools that help people be more considerate, more present, and more human. If all we do is use these systems to accelerate the production of slop, we will have missed the opportunity entirely.
  
  This is also why Mario joining Earendil feels so meaningful to me. Pi and Lefos come from different starting points. There was a year of distance collaboration, but they are animated by a similar instinct: that quality matters, that design matters, and that trust is earned through care rather than captured through hype.
  
  I am very happy that Pi is coming along for the ride. Me and Colin care a lot about it, and we want to be good stewards of it. It has already played an important role in our own work over the last months, and I continue to believe it is one of the best foundations for building capable agents. We will have more to say soon about how we think about Pi's future and its relationship to Lefos, but the short version is simple: we want Pi to continue to exist as a high-quality, open, extensible piece of software, and we want to invest in making that future real. As for our thoughts of Pi's license, read more here and our company post here.
April 07, 2026
1. 🔗 IDA Plugin Updates IDA Plugin Updates on 2026-04-07 rss
  IDA Plugin Updates on 2026-04-07
  
  Activity:
  - augur
    
    bc92ca7b: chore: update dependencies
  - capa
    
    0798528b: ci: use explicit and per job permissions (#3002)
    
    c55b0686: ci: fix web rules failure (#3003)
    
    ed7e0cd7: lint: replace black/isort/flake8 with ruff (#2992)
    
    ac1cba74: feat: update vivisect to 1.3.2 (#3001)
    
    ed6b40e9: Merge pull request #3000 from mandiant/dependabot/npm_and_yarn/web/ex…
  - DriverBuddy-7.4-plus
    
    f87787e9: Sync security-review.yml from .github repo
    
    583074d2: Sync auto-copilot-code-cleanliness-review.yml from .github repo
    
    f99d929e: Sync auto-llm-issue-review.yml from .github repo
    
    1e2b0ece: Sync trigger-all-repos.yml from .github repo
    
    29d1ff04: Sync auto-llm-pr-review.yml from .github repo
    
    4cc9e38a: Sync auto-label-comment-prs.yml from .github repo
    
    a3cd8c0b: Sync auto-label.yml from .github repo
    
    74620e5b: Sync auto-sec-scan.yml from .github repo
    
    eb8c7fcd: Sync auto-gpt5-implementation.yml from .github repo
    
    34c2593c: Sync swarm-mode.yml from .github repo
    
    dbf9f7a4: Sync auto-assign-copilot.yml from .github repo
    
    bc0b1b03: Sync auto-assign-pr.yml from .github repo
    
    f72ce60b: Sync workflows-sync-template-backup.yml from .github repo
    
    ff1522b2: Sync auto-tag-based-review.yml from .github repo
    
    036f8459: Sync runner-smoke-test.yml from .github repo
    
    1620d21f: Sync daily-continuous-progress.yml from .github repo
    
    dcb59862: Sync auto-close-issues.yml from .github repo
    
    948f1658: Sync auto-copilot-functionality-docs-review.yml from .github repo
    
    ce3c09ec: Sync oz-pr-review.yml from .github repo
  - ghidra
    
    505a59ff: Merge remote-tracking branch 'origin/GP-0-dragonmacher-test-fixes-4-7…
    
    44bd56bb: Test fixes
  - haruspex
    
    f89231e6: chore: update dependencies
  - ida-structor
    
    1afadd01: feat: Materialize deferred symbolic accesses when index bounds are found
    
    de5cbc3e: feat: Improve subobject detection using pointer flow edges
    
    b4e63d35: feat: Track symbolic array accesses and support named variable synthesis
    
    5afb49b1: feat: Expand bounded array accesses and improve alias offset tracking
    
    1acb065e: chore: Add debug logging for constant tracking in access collector
  - idamcp
    
    75af175f: fix port assignment
  - IDAPluginList
    
    3b6b426c: chore: Auto update IDA plugins (Updated: 19, Cloned: 0, Failed: 0)
  - IDEA
    
    4c7e96ac: Refine typed refresh and add type workflow regression coverage
    
    6c35fdbc: Downgrade struct field access classification to hints
    
    d9d945c1: Add struct workflow helpers and typed export tools
    
    f92a527e: Slim search output and implement local/stack rename
    
    7978d76c: Normalize export paths and persist staged IDBs
  - pharos
    
    217bf2a0: Merge pull request #303 from sei-eschwartz/fix-cycle
    
    4fd85d2f: Refactor reasonClassAtOffset_int to avoid cycles
  - python-elpida_core.py
    
    67b98628: fix: desperation guard reads stale MIND heartbeat as live crisis
  - rhabdomancer
    
    efa2142c: chore: update dependencies
  - Rikugan
    
    84f00d2d: Merge pull request #35 from buzzer-re/dev
    
    90146269: perf(ui): reduce restore, markdown, and bulk renamer overhead
    
    767fd59b: fix(ui): align Qt test stubs and qt_compat typing with runtime usage
    
    d5d3d078: fix(tests): isolate stubbed modules to prevent CI order-dependent fai…
  - sighthouse
    
    1f98a8ca: Fix missing dependency inside sighthouse-client
    
    a24a2dd7: CI github fixed order for documentation after pypi push
    
    a2bfe738: Simply/fix the ghidra installation and improve [+] Bump package versi…
    
    3103903a: Simply/fix the ghidra installation and improve [+] Bump package versi…
2. 🔗 r/Leeds Guitar Pedal shops in Leeds? rss
  
  Hi, I'm looking to shop around for some guitar pedals (like phasers etc) and I'd love to demo some. I'm aware PMT has now unfortunately closed, and I do miss the days of Big Deal and Dawsons. I love Hobgoblin and still frequent the store there, and wondering where else in Leeds I can go to browse?
  
  York has some great shops to visit too but I'd like to look more locally.
  
  Thank you!
  
  submitted by /u/blissedandgone
  [link] [comments]
3. 🔗 r/wiesbaden Mountainbike/Downhill Trails rss
  
  Wo gibt es in Wiesbaden und Umgebung gute Trails zum Mountainbiken und/oder Downhill fahren?
  
  Gibt es eventuell sogar eine eigene Community?
  
  Bin recht neu bei dem Thema und für alle Vorschläge dankbar :-)
  
  submitted by /u/Excellent_Scheme_247
  [link] [comments]
4. 🔗 anthropics/claude-code v2.1.94 release
  What's changed
  - Added support for Amazon Bedrock powered by Mantle, set CLAUDE_CODE_USE_MANTLE=1
  - Changed default effort level from medium to high for API-key, Bedrock/Vertex/Foundry, Team, and Enterprise users (control this with /effort)
  - Added compact Slacked #channel header with a clickable channel link for Slack MCP send-message tool calls
  - Added keep-coding-instructions frontmatter field support for plugin output styles
  - Added hookSpecificOutput.sessionTitle to UserPromptSubmit hooks for setting the session title
  - Plugin skills declared via "skills": ["./"] now use the skill's frontmatter name for the invocation name instead of the directory basename, giving a stable name across install methods
  - Fixed agents appearing stuck after a 429 rate-limit response with a long Retry-After header — the error now surfaces immediately instead of silently waiting
  - Fixed Console login on macOS silently failing with "Not logged in" when the login keychain is locked or its password is out of sync — the error is now surfaced and claude doctor diagnoses the fix
  - Fixed plugin skill hooks defined in YAML frontmatter being silently ignored
  - Fixed plugin hooks failing with "No such file or directory" when CLAUDE_PLUGIN_ROOT was not set
  - Fixed ${CLAUDE_PLUGIN_ROOT} resolving to the marketplace source directory instead of the installed cache for local-marketplace plugins on startup
  - Fixed scrollback showing the same diff repeated and blank pages in long-running sessions
  - Fixed multiline user prompts in the transcript indenting wrapped lines under the ❯ caret instead of under the text
  - Fixed Shift+Space inserting the literal word "space" instead of a space character in search inputs
  - Fixed hyperlinks opening two browser tabs when clicked inside tmux running in an xterm.js-based terminal (VS Code, Hyper, Tabby)
  - Fixed an alt-screen rendering bug where content height changes mid-scroll could leave compounding ghost lines
  - Fixed FORCE_HYPERLINK environment variable being ignored when set via settings.json env
  - Fixed native terminal cursor not tracking the selected tab in dialogs, so screen readers and magnifiers can follow tab navigation
  - Fixed Bedrock invocation of Sonnet 3.5 v2 by using the us. inference profile ID
  - Fixed SDK/print mode not preserving the partial assistant response in conversation history when interrupted mid-stream
  - Improved --resume to resume sessions from other worktrees of the same repo directly instead of printing a cd command
  - Fixed CJK and other multibyte text being corrupted with U+FFFD in stream-json input/output when chunk boundaries split a UTF-8 sequence
  - [VSCode] Reduced cold-open subprocess work on starting a session
  - [VSCode] Fixed dropdown menus selecting the wrong item when the mouse was over the list while typing or using arrow keys
  - [VSCode] Added a warning banner when settings.json files fail to parse, so users know their permission rules are not being applied
5. 🔗 Simon Willison Anthropic's Project Glasswing - restricting Claude Mythos to security researchers - sounds necessary to me rss
  
  Anthropic didn't release their latest model, Claude Mythos (system card PDF), today. They have instead made it available to a very restricted set of preview partners under their newly announced Project Glasswing.
  
  The model is a general purpose model, similar to Claude Opus 4.6, but Anthropic claim that its cyber-security research abilities are strong enough that they need to give the software industry as a whole time to prepare.
  
  Mythos Preview has already found thousands of high-severity vulnerabilities, including some in every major operating system and web browser. Given the rate of AI progress, it will not be long before such capabilities proliferate, potentially beyond actors who are committed to deploying them safely.
  
  [...]
  
  Project Glasswing partners will receive access to Claude Mythos Preview to find and fix vulnerabilities or weaknesses in their foundational systems—systems that represent a very large portion of the world’s shared cyberattack surface. We anticipate this work will focus on tasks like local vulnerability detection, black box testing of binaries, securing endpoints, and penetration testing of systems.
  
  There's a great deal more technical detail in Assessing Claude Mythos Preview’s cybersecurity capabilities on the Anthropic Red Team blog:
  
  In one case, Mythos Preview wrote a web browser exploit that chained together four vulnerabilities, writing a complex JIT heap spray that escaped both renderer and OS sandboxes. It autonomously obtained local privilege escalation exploits on Linux and other operating systems by exploiting subtle race conditions and KASLR-bypasses. And it autonomously wrote a remote code execution exploit on FreeBSD's NFS server that granted full root access to unauthenticated users by splitting a 20-gadget ROP chain over multiple packets.
  
  Plus this comparison with Claude 4.6 Opus:
  
  Our internal evaluations showed that Opus 4.6 generally had a near-0% success rate at autonomous exploit development. But Mythos Preview is in a different league. For example, Opus 4.6 turned the vulnerabilities it had found in Mozilla’s Firefox 147 JavaScript engine—all patched in Firefox 148—into JavaScript shell exploits only two times out of several hundred attempts. We re-ran this experiment as a benchmark for Mythos Preview, which developed working exploits 181 times, and achieved register control on 29 more.
  
  Saying "our model is too dangerous to release" is a great way to build buzz around a new model, but in this case I expect their caution is warranted.
  
  Just a few days (last Friday) ago I started a new ai-security-research tag on this blog to acknowledge an uptick in credible security professionals pulling the alarm on how good modern LLMs have got at vulnerability research.
  
  Greg Kroah-Hartman of the Linux kernel:
  
  Months ago, we were getting what we called 'AI slop,' AI-generated security reports that were obviously wrong or low quality. It was kind of funny. It didn't really worry us.
  
  Something happened a month ago, and the world switched. Now we have real reports. All open source projects have real reports that are made with AI, but they're good, and they're real.
  
  Daniel Stenberg of curl:
  
  The challenge with AI in open source security has transitioned from an AI slop tsunami into more of a ... plain security report tsunami. Less slop but lots of reports. Many of them really good.
  
  I'm spending hours per day on this now. It's intense.
  
  And Thomas Ptacek published Vulnerability Research Is Cooked, a post inspired by his podcast conversation with Anthropic's Nicholas Carlini.
  
  Anthropic have a 5 minute talking heads video describing the Glasswing project. Nicholas Carlini appears as one of those talking heads, where he said (highlights mine):
  
  It has the ability to chain together vulnerabilities. So what this means is you find two vulnerabilities, either of which doesn't really get you very much independently. But this model is able to create exploits out of three, four, or sometimes five vulnerabilities that in sequence give you some kind of very sophisticated end outcome. [...]
  
  I've found more bugs in the last couple of weeks than I found in the rest of my life combined. We've used the model to scan a bunch of open source code, and the thing that we went for first was operating systems, because this is the code that underlies the entire internet infrastructure. For OpenBSD, we found a bug that's been present for 27 years, where I can send a couple of pieces of data to any OpenBSD server and crash it. On Linux, we found a number of vulnerabilities where as a user with no permissions, I can elevate myself to the administrator by just running some binary on my machine. For each of these bugs, we told the maintainers who actually run the software about them, and they went and fixed them and have deployed the patches patches so that anyone who runs the software is no longer vulnerable to these attacks.
  
  I found this on the OpenBSD 7.8 errata page:
  
  025: RELIABILITY FIX: March 25, 2026 All architectures
  
  TCP packets with invalid SACK options could crash the kernel.
  
  A source code patch exists which remedies this problem.
  
  I tracked that change down in the GitHub mirror of the OpenBSD CVS repo (apparently they still use CVS!) and found it using git blame:
  
  Sure enough, the surrounding code is from 27 years ago.
  
  I'm not sure which Linux vulnerability Nicholas was describing, but it may have been this NFS one recently covered by Michael Lynch .
  
  There's enough smoke here that I believe there's a fire. It's not surprising to find vulnerabilities in decades-old software, especially given that they're mostly written in C, but what's new is that coding agents run by the latest frontier LLMs are proving tirelessly capable at digging up these issues.
  
  I actually thought to myself on Friday that this sounded like an industry-wide reckoning in the making, and that it might warrant a huge investment of time and money to get ahead of the inevitable barrage of vulnerabilities. Project Glasswing incorporates "$100M in usage credits ... as well as $4M in direct donations to open-source security organizations". Partners include AWS, Apple, Microsoft, Google, and the Linux Foundation. It would be great to see OpenAI involved as well - GPT-5.4 already has a strong reputation for finding security vulnerabilities and they have stronger models on the near horizon.
  
  The bad news for those of us who are not trusted partners is this:
  
  We do not plan to make Claude Mythos Preview generally available, but our eventual goal is to enable our users to safely deploy Mythos-class models at scale—for cybersecurity purposes, but also for the myriad other benefits that such highly capable models will bring. To do so, we need to make progress in developing cybersecurity (and other) safeguards that detect and block the model’s most dangerous outputs. We plan to launch new safeguards with an upcoming Claude Opus model, allowing us to improve and refine them with a model that does not pose the same level of risk as Mythos Preview.
  
  I can live with that. I think the security risks really are credible here, and having extra time for trusted teams to get ahead of them is a reasonable trade-off.
  
  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.
6. 🔗 r/york First trip to your wonderful city rss
  
  | A few of my favourite shots. Not so much time for pictures with the children in tow these days but still managed a couple keepers. submitted by /u/MicroWave
  [link] [comments]
  ---|---
7. 🔗 r/reverseengineering ida-mcp 2.1: Progressive Tool Discovery, Background Analysis, and Batch Operations rss
  
  submitted by /u/jtsylve
  [link] [comments]
8. 🔗 r/Leeds Cherry blossoms in Leeds 🌸 rss
  
  Finally have a day off after 11 days working straight so I’m planning to go touch some grass tomorrow (yay!).
  
  Any suggestions on places with beautiful cherry blossoms in bloom in a spot that I can also do a little picnic, and not too far away from city centre?
  
  Heard someone said Temple Newsam or Roundhay park, but I’m not sure if there’s any blossoms blooming there now yet.
  
  Any suggestions would be greatly appreciated. Thank you x
  
  submitted by /u/AnOtterInAMug
  [link] [comments]
9. 🔗 r/Yorkshire Rivers of Yorkshire Rhyme rss
  
  My grandma used to recite a poem or nursery rhyme about the rivers of Yorkshire. 45 years later I can't remember it! Does anyone know what this rhyme could be?
  
  submitted by /u/Lumpy_Geologist7644
  [link] [comments]
10. 🔗 r/Leeds North Street LS2 rss
  
  Headed up to North Street today. Loads going on, seems like a nice part of town. I always avoided that area as you head up to Little London but almost feels nicer and safer now than other areas of town (city centre). Is this a recent boom or have I just had my blinkers on? Anyone know the plans on what they are doing around that area?
  
  submitted by /u/Olivrrpb
  [link] [comments]
11. 🔗 r/Yorkshire Yorkshire Devolution rss
  
  Something a little different for the community here. What's your thought on Yorkshire devolution to the historic county?
  
  I've heard that there was recently a One Yorkshire deal that the Tories rejected and that the Yorkshire mayors work pretty closely with each other now. I also know we have a really strong identity, proud folk and unique customs and dialect that make us an ideal group for one devolution. But I just wanted to know what people think? Do you want a Yorkshire Parliament like Wales's has? Or are you not that fussed? Lerrus av a kall abaht it!
  
  P.s. I've always thought us Northerners squabble too much anyway and that's why Westminster always gets its way!
  
  submitted by /u/masa8910
  [link] [comments]
12. 🔗 @binaryninja@infosec.exchange Join us tomorrow, Wednesday April 8th @ 3pm ET, for a sneak peak at Binary mastodon
  
  Join us tomorrow, Wednesday April 8th @ 3pm ET, for a sneak peak at Binary Ninja 5.3!
  
  We'll take a look at all the new major features coming to 5.3, from expanded architecture and platform support, core analysis features, new debugger features, brand new UIs, and so much more. Follow along with latest dev, or join us tomorrow to see what's worth all the hype: https://youtube.com/live/iD8UidhFbhg
13. 🔗 r/LocalLLaMA Every day I wake up and thank God for having me be born 23 minutes away from a MicroCenter rss
  
  | submitted by /u/gigaflops_
  [link] [comments]
  ---|---
14. 🔗 r/Leeds Good Boy (the Stephen Graham film, not the dog one) currently in cinema was filmed in Leeds during freshers after a Leeds game at 10pm. It's pretty hectic and shows off some bits of Leeds including lower Briggate. rss
  
  87% on Rotten Tomatoes and very good. A bit of a strange one kinda like a Yorgos Lanthimos film.
  
  If anyone has watched and can identify all the Leeds/Yorkshire locations I'd be interested.
  
  submitted by /u/montfree
  [link] [comments]
15. 🔗 r/Harrogate Best bars for a date night rss
  
  hi all,
  
  i am taking my girlfriend out to Harrogate tmrw for her birthday! I have booked La Feria as our dinner in the evening but wondered what were the best bars are to go to before and after are meal.
  
  just to note we are dressing up nicely - she’ll be in a dress and I’ll be in a shirt. just wondered if that fits the vibe of La Feria and if you know any nice bars that suits that is nice for the evening!!
  
  submitted by /u/GarlicCharacter3247
  [link] [comments]
16. 🔗 r/york Scenic Drives (ideally circular) - Leaving York rss
  
  Hi
  
  Can anyone recommend any drives that you can easily do within an hour or so (total drive time) with the following ideal criteria:
  
  - A scenic and reasonably quiet route
  
  - Ideally circular (leave York - head out and back to York eventually)
  
  - Something that's not necessarily well known
  
  - A nice village pub to call in at along the way
  
  - That's all!
  
  All recommendations welcome, thank you.
  
  submitted by /u/HeroRon
  [link] [comments]
17. 🔗 r/LocalLLaMA GLM-5.1 rss
  
  | submitted by /u/danielhanchen
  [link] [comments]
  ---|---
18. 🔗 r/Leeds Trying to get to Leeds station in the morning from Bramley with all the road works rss
  
  There is a lot of road works in Kirkstall and people were delayed. My flight is 12pmin the afternoon and I have to get all the way to Manchester..
  
  Thnking of setting off between 6:00 and 7:00 a.m.
  
  would you recommend an Uber? I think the buses might be out of whack that morning with all the road works. I did speak to the person on the road works and they said that all the road work starts around 9:00 which means there's no room for error in me getting up early.
  
  submitted by /u/Crazy_Screen_5043
  [link] [comments]
19. 🔗 r/Leeds Anyone near Headingley able to offer an emergency puppy cuddle for a very overdue pregnant woman? rss
  
  Bit of an unusual one, but my sister-in-law is very overdue with her first baby, desperate to avoid induction, and absolutely mad about dogs, while sadly unable to own one.
  
  I wondered whether anyone near Headingley has a friendly puppy and might be willing to let her have a short, supervised interaction, just some gentle fuss, cuddles, and a bit of puppy time. The hope, honestly, is to get a bit of oxytocin flowing and lift her spirits, as she completely melts around dogs.
  
  We are not looking to borrow a dog or put anyone out, just a brief visit with the owner present, ideally somewhere convenient and public if that suits you better.
  
  Bit of a long shot, but hey ho.
  
  Thank you!
  
  submitted by /u/Desecron
  [link] [comments]
20. 🔗 r/LocalLLaMA Auto-creation of agent SKILLs from observing your screen via Gemma 4 for any agent to execute and self-improve rss
  
  | AgentHandover is an open-source Mac menu bar app that watches your screen through Gemma 4 (running locally via Ollama) and turns your repeated workflows into structured Skill files that any agent can follow. I built it because every time I wanted an agent to handle something for me I had to explain the whole process from scratch, even for stuff I do daily. So AgentHandover just watches instead. You can either hit record for a specific task (Focus Record) or let it run in the background where it starts picking up patterns after seeing you repeat something a few times (Passive Discovery).
  Skills get sharper with every observation, updating steps, guardrails, and confidence scores as it learns more. The whole thing is an 11-stage pipeline running fully on-device, nothing leaves your machine, encrypted at rest. One- click agent integration through MCP so Claude Code, Cursor, OpenClaw or anything that speaks MCP can just pick up your Skills. Also has a CLI if you prefer terminal. SImple illustrative demo in the video, Apache 2.0, repo: https://github.com/sandroandric/AgentHandover Would love feedback on the approach and curious if anyone has tried other local vision or OS models for screen understanding...thxxx submitted by /u/Objective_River_5218
  [link] [comments]
  ---|---
21. 🔗 r/LocalLLaMA You can now fine-tune Gemma 4 locally 8GB VRAM + Bug Fixes rss
  | Hey guys, you can now fine-tune Gemma 4 E2B and E4B in our free Unsloth notebooks! You need 8GB VRAM to train Gemma-4-E2B locally. Unsloth trains Gemma 4 ~1.5x faster with ~60% less VRAM than FA2 setups: https://github.com/unslothai/unsloth We also found and did bug fixes for Gemma 4 training:
  1. Grad accumulation no longer causes losses to explode - before you might see losses of 300 to 400 - it should be 10 to 15 - Unsloth has this fixed.
  2. Index Error for 26B and 31B for inference - this will fail inference for 26B and 31B when using transformers - we fixed it.
  3. use_cache=False had gibberish for E2B, E4B - see https://github.com/huggingface/transformers/issues/45242
  4. float16 audio -1e9 overflows on float16
  You can also train 26B-A4B and 31B or train via a UI with Unsloth Studio. Studio and the notebooks work for Vision, Text, Audio and inference. For Bug Fix details and tips and tricks, read our blog/guide: https://unsloth.ai/docs/models/gemma-4/train Free Colab Notebooks: | E4B + E2B (Studio web UI) | E4B (Vision + Text)-Vision.ipynb) | E4B (Audio)-Audio.ipynb) | E2B (Run + Text)-Text.ipynb)
  ---|---|---|---
  
  Thanks guys!
  
  submitted by /u/danielhanchen
  [link] [comments]
22. 🔗 r/york casualties of the storm :( rss
  
  | on the riverbank near cinder lane and in homestead park submitted by /u/whtmynm
  [link] [comments]
  ---|---
23. 🔗 r/wiesbaden FDP und Pro Auto bekommen Schnappatmung rss
  
  submitted by /u/Happycosinus
  [link] [comments]
24. 🔗 r/reverseengineering AI just hacked one of the world's most secure operating systems in four hours. rss
  
  submitted by /u/EchoOfOppenheimer
  [link] [comments]
25. 🔗 r/Yorkshire World Coal Carrying Championship 2026! rss
  
  | A beloved tradition in the village of Gawthorpe. The competition takes place annually with men, women and children taking part (the kids don't carry coal!) This year we had good weather and a turnout of many hundreds of spectators to cheer along the runners. Congratulations to all those taking part, where even completing the race is a feat in itself. submitted by /u/Paradoxbox00
  [link] [comments]
  ---|---
26. 🔗 r/york Jorvik Tickets for Today or early tomorrow? rss
  
  We’re visiting York- arrived yesterday and leave midday tomorrow. I’m an idiot and didn’t prebook tickets to the Jorvik museum and they’re sold out. By any small chance is there anyone who has tickets they can’t use that we could buy for today or early tomorrow?
  
  submitted by /u/SnooCats1465
  [link] [comments]
27. 🔗 r/LocalLLaMA Turns out Gemma 4 had MTP (multi token prediction) all along rss
  
  | Hey Everyone, While I was trying to utilize Gemma 4 through the LiteRT api in my android app, I noticed that Gemma 4 was throwing errors when loading it on my Google Pixel 9 test device of the "mtp weights being an incompatible tensor shape". I did some digging and found out there's additional MTP prediction heads within the LiteRT files for speculative decoding and much faster outputs. Well turns out I got confirmation today from a Google employee that Gemma 4 DOES INDEED have MTP but it was "removed on purpose" for "ensuring compatibility and broad usability". Well would've been great to be honest if they released the full model instead, considering we already didn't get the Gemma 124B model leaked in Jeff Dean's tweet by accident. Would've been great to have much faster Gemma 4 generation outputs, ideally on the already fast MoE. Maybe someone can reverse engineer and extract the tensors and the math based on the compute graph in LiteRT? Here's a link to the conversation: https://huggingface.co/google/gemma-4-E4B-it/discussions/5 submitted by /u/Electrical-Monitor27
  [link] [comments]
  ---|---
28. 🔗 r/Yorkshire Yorkshire, UK 🇬🇧 rss
  
  submitted by /u/DraftNotSent
  [link] [comments]
29. 🔗 r/reverseengineering DeepZero: An automated, agentic vulnerability research pipeline for finding kernel zero-days rss
  
  submitted by /u/watchdogsrox
  [link] [comments]
30. 🔗 backnotprop/plannotator v0.17.1 release
  Follow @plannotator on X for updates
  
  Missed recent releases? Release | Highlights
  ---|---
  v0.17.0 | AI code review agents, token-level annotation, merge-base diffs
  v0.16.7 | Gemini CLI plan review, install script skills directory fix
  v0.16.6 | Perforce support, Pi shared event API, suggested code prefill, file tree expand fix
  v0.16.5 | Resize handle scrollbar fix, VS Code Marketplace publish
  v0.16.4 | Compound planning improvement hook, GitHub Enterprise + self-hosted GitLab, dockview workspace, new themes
  v0.16.3 | Pi phase configuration, CLI help, untracked file discovery fix, review scroll reset
  v0.16.2 | Draggable comment popovers, cross-file annotation visibility, custom diff fonts, OpenCode verbose log fix
  v0.16.1 | SSE stream idle timeout fix for external annotations API
  v0.16.0 | GitHub Copilot CLI, external annotations API, bot callback URLs, interactive checkboxes, print support, diff display options
  v0.15.5 | Custom display names, GitHub viewed file sync, expand/collapse all in file tree, search performance, WSL fix
  v0.15.2 | Compound Planning skill, folder annotation, /plannotator-archive slash command, skill installation via platform installers
  v0.15.0 | Live AI chat in code review, plan archive browser, folder file viewer, resizable split pane, Pi full feature parity
  
  What's New in v0.17.1
  
  v0.17.1 is a patch release that fixes PR review in the Pi extension and addresses several cross-platform bugs found during an exhaustive parity audit of every server endpoint between Bun and Pi runtimes.
  
  Pi PR Review
  
  The Pi extension's plannotator-review command was completely ignoring PR URL arguments and always falling back to local git diffs. v0.17.1 implements the full PR review flow: URL parsing, authentication checks, PR metadata fetch, and local worktree creation for both same-repo and cross-repo PRs. Same-repo PRs use git worktree add --detach with the PR's head ref; cross-repo forks use a shallow clone with tracking refs for both branches.
  
  Beyond the missing PR flow, an audit of all 27 review server feature areas uncovered 12 parity gaps in the Pi server. These ranged from missing diagnostic logging on PR actions to incorrect access guards that would have allowed diff switching in PR mode. All have been fixed.
  - #503
  Remote URL Parsing
  
  parseRemoteUrl has been rewritten to handle the full range of git remote formats. The previous regex incorrectly matched HTTPS URLs with non-standard ports (e.g., https://gitlab.example.com:8443/group/project.git) as SSH, and failed on multi-segment GitLab paths like group/subgroup/project. The new implementation handles SSH, SSH with port (ssh://git@host:22/path), standard HTTPS, and HTTPS with custom ports as separate cases. This fix applies to both Bun and Pi runtimes.
  - #503
  Cross-Repo Clone Fixes
  
  Cross-repo PR clones (forks from different organizations) had two issues. The gh repo clone and glab repo clone commands don't accept a --hostname flag, so self-hosted GitHub Enterprise and GitLab instances would fail. The fix uses GH_HOST and GITLAB_HOST environment variables instead, which both CLIs respect. The shallow fetch depth has also been increased from 50 to 200 commits to handle PRs with longer histories.
  - #503
  Additional Changes
  - Git Add button hidden in PR mode. The staging button was incorrectly visible during PR reviews because the server returned diffType: undefined and the client defaulted to "uncommitted". The client now disables staging when PR metadata is present
  - Diff viewer theme flash fix. Switching files in the diff viewer caused a brief flash of the wrong theme. The Pierre diff library's theme was being computed asynchronously via requestAnimationFrame; the initial state now reads CSS custom properties synchronously so the correct background appears on the first frame
  - Resolved/Outdated filters in PR comments. The PR comments tab now has toggle buttons to hide resolved or outdated review threads. Filters use the same green and amber color tokens as the existing status badges and integrate with the existing Clear Filters control
  Install / Update
  
  macOS / Linux:
```
curl -fsSL https://plannotator.ai/install.sh | bash
```
  Windows:
```
irm https://plannotator.ai/install.ps1 | iex
```
  Claude Code Plugin: Run /plugin in Claude Code, find plannotator , and click "Update now".
  
  Copilot CLI:
```
/plugin marketplace add backnotprop/plannotator
/plugin install plannotator-copilot@plannotator
```
  Gemini CLI: The install script auto-detects ~/.gemini and configures hooks, policy, and slash commands. See apps/gemini/README.md for manual setup.
  
  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
```
  VS Code Extension: Install from the VS Code Marketplace. Tested with Claude Code running in VS Code's integrated terminal. Not currently compatible with Anthropic's official VS Code extension due to upstream hook bugs.
  
  What's Changed
  - fix(pi): full PR review parity with Bun server by @backnotprop in #503
  Full Changelog : v0.17.0...v0.17.1
31. 🔗 r/LocalLLaMA Gemma 4 26b A3B is mindblowingly good , if configured right rss
  
  Last few days ive been trying different models and quants on my rtx 3090 LM studio , but every single one always glitches the tool calling , infinite loop that doesnt stop. But i really liked the model because it is rly fast , like 80-110 tokens a second , even on high contex it still maintains very high speeds.
  
  I had great success with tool calling in qwen3.5 moe model , but the issue i had with qwen models is that there is some kind of bug in win11 and LM studio that makes the prompt caching not work so when the convo hits 30-40k contex , it is so slow at processing prompts it just kills my will to work with it.
  
  Gemma 4 is different , it is much better supported on the ollama cpp and the caching works flawlesly , im using flash attention + q4 quants , with this i can push it to literally maximum 260k contex on rtx 3090 ! , and the models performs just aswell.
  
  I finally found the one that works for me , its the unsloth q3k_m quant , temperature 1 and top k sampling 40. i have a custom system prompt that im using which also might be helping.
  
  I've been testing it with opencode for the last 6 hours and i just cant stop , it cannot fail , it exiplained me the whole structure of the Open Code itself , and it is a huge , like the whole repo is 2.7GB so many lines of code and it has no issues traversing around and reading everything , explaining how certain things work , i think im gonna create my own version of open code in the end.
  
  It honestly feels like claude sonnet level of quality , never fails to do function calling , i think this might be the best model for agentic coding / tool calling / open claw or search engine.
  I prefer it over perplexity , in LM studio connected to search engine via a plugin delivers much better results than perplexity or google.
  
  As for vram consumption it is heavy , it can probably work on 16gb it not for tool calling or agents , u need 10-15k contex just to start it. My gpu has 24gb ram so it can run it at full contex no issues on Q4_0 KV
  
  submitted by /u/cviperr33
  [link] [comments]
32. 🔗 Jessitron Adding Correctness Conditions to Code Changes rss
  
  Today I looked at the first PR on our new project repo. It added a new run script, but the README didn’t mention it. The proposed change was incomplete, because the documentation was out of sync.
  
  Did I comment on the PR? heck no. I want to fix this problem for all PRs, not just this one. We can automate this stuff now.
  
  Correctness condition: All PRs include updates to all relevant documentation files.
  
  How can we make this true?
  
  Instructions - We can change AGENTS.md to instruct our coding agent to look for documentation files and update them.
  Verification - We can add a reviewer agent to check each PR for missed documentation updates.
  
  This is two changes, so I can break this work into two parts. Which of these should we do first?
  
  Changing the instructions is easy.
  
  If we do instructions first, it’s easy. It will work most of the time. When I try it on this little PR, it will certainly work, and then I can claim victory and move on to the next feature.
  
  Then later, on some future PR, the agent will miss updating some documentation. Will I notice? No. In fact: I hope not. If I’m looking through PRs to a level of detail that includes all documents in the PR and also documentation files not in the PR, then we have failed to automate enough of this project. (This project does not deserve that level of scrutiny.)
  
  Changing instructions without verification gives me no guarantee of my correctness condition.
  
  Adding validation is sufficient.
  
  If we do validation first, then every PR will be checked for missed documentation updates. Incorrect PRs will be rejected, so the coding agent will have to update the documentation.
  
  My correctness condition will be guaranteed. Well, as guaranteed as I can get it with this nondeterministic automation. The reviewing agent will have only one task, so it won’t forget to check for needed documentation updates. If we ever catch it being wrong, then we must update its instructions.
  
  If we never implement the instructions change, then PRs will take longer, because some agent has to respond to the PR comments, and then the feedback loop runs again.
  
  With verification in place, the instructions change is an optimization!
  
  Validation before implementation.
  
  It’s a little like test-first development, but at a higher level. We’re adding a check to every feature implementation, not just one.
  
  It’s more like property testing than unit testing. We aren’t hard-coding “every feature should update the README.” We’re stating a property: the documentation should be up-to-date after every feature change.
  
  Now my PR reviews are also system reviews: what about this PR should have been different? How can we change the agent’s context and feedback to make that different? Now test that system change on this PR before we fix it.
  
  This is the new Boy Scout Rule. It went from “leave the codebase cleaner than I found it” to “make the whole develoment system stronger than it was.”
  
  It’s all part of programming the agents to program our software.
33. 🔗 Jamie Brandon 0058: borrow-checking surprises, books, links rss
  
  (empty)
34. 🔗 Jamie Brandon Borrow-checking surprises rss
  
  (empty)
35. 🔗 Mitchell Hashimoto The Building Block Economy rss
  
  (empty)
April 06, 2026
1. 🔗 IDA Plugin Updates IDA Plugin Updates on 2026-04-06 rss
  IDA Plugin Updates on 2026-04-06
  
  Activity:
  - augur
    
    aa5847a0: feat: update ida plugin stub and metadata
    
    9ff757e1: doc: improve compatibility info
  - capa
    
    70f275ac: build(deps-dev): bump types-protobuf (#2994)
    
    63aa5729: build(deps-dev): bump mypy from 1.19.1 to 1.20.0 (#2993)
    
    63edbedb: build(deps-dev): bump lodash from 4.17.23 to 4.18.1 in /web/explorer …
  - efiXplorer
    
    29960936: update guids submodule (#139)
  - Greffe
    
    19e36ac1: Merge pull request #72 from Lixhr/70-core-avoid-overwriting-instrumen…
    
    9458749b: add branch overlap detection on close targets
    
    17aa102d: Merge pull request #71 from Lixhr/69-test-instrument-every-instructions
    
    497cca77: Add batch adds
    
    90f54e65: Merge pull request #68 from Lixhr/65-core-set-and-call-handler
    
    638e8906: fix wrong register saving order
    
    11d9a781: fix segfault on targets added from config file
    
    d6882068: Fix non-thumb branch / wrong ret sp offset
  - haruspex
    
    dcf1bcba: feat: improve ida plugin stub and metadata
    
    9d2107db: doc: improve compatibility info
    
    2fa79f55: doc: improve compatibility info
  - ida-pro-mcp
    
    9f489ca3: Merge pull request #345 from JohnsterID/test/pr335-unsafe-gating-cove…
    
    66af3ff6: Merge pull request #337 from JohnsterID/fix/ida-rpc-query-params
    
    cb6e84cd: Restrict GHA to this repo
    
    29f6ae93: Merge pull request #346 from hzqst/main
    
    30774f3a: Merge pull request #341 from ZehMatt/token-optimizations
    
    bbca7351: Fix [MCP] « notifications/initialized (0.0ms) ERROR: Method 'notific…
    
    256cc92e: Merge pull request #343 from hzqst/main
    
    b8be0301: Use better approach to detect idalib headless mode: ida_kernwin.is_id…
    
    779d707d: Fix https://github.com/mrexodia/ida-pro-mcp/issues/342
    
    a0bd04db: test: add coverage for @unsafe/@ext decorator sets and extension gating
    
    c5360f62: fix: preserve ?ext= query params from -ida-rpc URL
  - python-elpida_core.py
    
    fe666cbd: fix: add CONVERGENCE to Rhythm enum — ECS crash on cycle 1
    
    7350af96: feat: D16 Stage 2 — Witnessed Agency + Stage 1 gap closure
  - rhabdomancer
    
    c06d888a: doc: update changelog
    
    c97e8a1e: doc: improve compatibility info
  - UltraKernelDumper
    
    ea1cae2c: Add full project source excluding large target folder and build artif…
2. 🔗 backnotprop/plannotator v0.17.0 release
  Follow @plannotator on X for updates
  
  Missed recent releases? Release | Highlights
  ---|---
  v0.16.7 | Gemini CLI plan review, install script skills directory fix
  v0.16.6 | Perforce support, Pi shared event API, suggested code prefill, file tree expand fix
  v0.16.5 | Resize handle scrollbar fix, VS Code Marketplace publish
  v0.16.4 | Compound planning improvement hook, GitHub Enterprise + self-hosted GitLab, dockview workspace, new themes
  v0.16.3 | Pi phase configuration, CLI help, untracked file discovery fix, review scroll reset
  v0.16.2 | Draggable comment popovers, cross-file annotation visibility, custom diff fonts, OpenCode verbose log fix
  v0.16.1 | SSE stream idle timeout fix for external annotations API
  v0.16.0 | GitHub Copilot CLI, external annotations API, bot callback URLs, interactive checkboxes, print support, diff display options
  v0.15.5 | Custom display names, GitHub viewed file sync, expand/collapse all in file tree, search performance, WSL fix
  v0.15.2 | Compound Planning skill, folder annotation, /plannotator-archive slash command, skill installation via platform installers
  v0.15.0 | Live AI chat in code review, plan archive browser, folder file viewer, resizable split pane, Pi full feature parity
  v0.14.5 | GitLab merge request review, login page image fix, Windows install path fix
  
  What's New in v0.17.0
  
  v0.17.0 introduces AI-powered code review agents, token-level annotation in diffs, and merge-base diffs for PR-accurate comparisons. Three of the six PRs in this release came from external contributors, one of them a first-timer.
  
  AI Code Review Agents
  
  Codex and Claude Code can now run as background review agents directly from the Plannotator code review UI. Select an agent, launch it, and watch live log output stream into a detail panel while the agent works. When it finishes, its findings appear as external annotations in the diff viewer, tagged by severity.
  
  Codex agents use their built-in codex-review command and produce priority- level findings (P0 through P3). Claude agents use a custom multi-agent prompt covering bug detection, security, code quality, and guideline compliance, with each finding classified as important, nit, or pre-existing. Both agents' findings include reasoning traces that explain the logic behind each annotation.
  
  For PR reviews, the server automatically creates a local worktree so agents have full file access without affecting your working directory. Same-repo PRs use git worktree; cross-repo forks use a shallow clone with tracking refs for both branches. Pass --no-local to skip the worktree if you don't need file access.
  
  The Pi extension has full agent review parity: stdin/stdout/stderr handling, live log streaming, result ingestion, and vendored review modules with import rewriting.
  - #491
  Token-Level Code Selection
  
  The diff viewer now supports clicking individual syntax tokens to annotate them. Hover a token to see it underlined; click to open the annotation toolbar with the token's text and position as context (e.g., "Line 47: processOrder"). Token metadata is stored on the annotation and surfaced in sidebar badges and exported feedback.
  
  Gutter-based line selection continues to work independently. The two selection modes don't interfere with each other.
  - #500
  Merge-Base Diffs
  
  A new "Current PR Diff" option in the diff type selector uses git merge-base to find the common ancestor between your branch and the default branch, then diffs from that point. This produces the same diff you'd see on a GitHub pull request page. The existing "vs main" option (git diff main..HEAD) is still available but includes upstream changes that arrived after you branched, which can be noisy.
  - #485 by @yonihorn
  Additional Changes
  - @ file reference support in annotate. OpenCode-style @file.md references now resolve correctly in /plannotator-annotate. The resolver strips the leading @ as a fallback when the literal filename doesn't exist, while still preferring real files named @something.md if present (#488 by @Exloz)
  - Markdown hard line breaks and list continuations. Two-trailing-space and backslash hard breaks now render as <br> elements. Indented continuation lines after list items merge into the preceding bullet instead of becoming orphan paragraphs (#483, closing #482)
  - Explicit local mode override. Setting PLANNOTATOR_REMOTE=0 or false now forces local mode, bypassing SSH auto-detection. Previously only 1/true had explicit meaning (#481 by @foxytanuki, closing #480)
  - PR file content merge-base fix. File contents for expandable diff context are now fetched at the merge-base commit instead of the base branch tip. When the base branch has moved since the PR was created, the old file contents didn't match the diff hunks, causing crashes in the diff renderer. The fix fetches the merge-base SHA via GitHub's compare API and falls back gracefully if unavailable
  Install / Update
  
  macOS / Linux:
```
curl -fsSL https://plannotator.ai/install.sh | bash
```
  Windows:
```
irm https://plannotator.ai/install.ps1 | iex
```
  Claude Code Plugin: Run /plugin in Claude Code, find plannotator , and click "Update now".
  
  Copilot CLI:
```
/plugin marketplace add backnotprop/plannotator
/plugin install plannotator-copilot@plannotator
```
  Gemini CLI: The install script auto-detects ~/.gemini and configures hooks, policy, and slash commands. See apps/gemini/README.md for manual setup.
  
  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
```
  VS Code Extension: Install from the VS Code Marketplace. Tested with Claude Code running in VS Code's integrated terminal. Not currently compatible with Anthropic's official VS Code extension due to upstream hook bugs.
  
  What's Changed
  - feat(review): token-level code selection for annotations by @backnotprop in #500
  - feat(review): AI review agents, local worktree, and UI polish by @backnotprop in #491
  - fix(annotate): support @ markdown file references by @Exloz in #488
  - feat(review): add merge-base diff option for PR-style diffs by @yonihorn in #485
  - fix: handle markdown hard line breaks and list continuations by @backnotprop in #483
  - fix(remote): support explicit local override by @foxytanuki in #481
  - fix(review): use merge-base SHA for PR file contents by @backnotprop
  New Contributors
  - @Exloz made their first contribution in #488
  Contributors
  
  @Exloz contributed the @ file reference fix for OpenCode's annotate mode (#488), including comprehensive test coverage for edge cases like real @-prefixed filenames and quoted input. First contribution.
  
  @yonihorn returned with the merge-base diff option (#485), giving PR reviews the same diff semantics GitHub uses.
  
  @foxytanuki continued contributing with the explicit local mode override (#481), their third PR after the CLI help message and SSE timeout fix.
  
  Community members who reported issues addressed in this release:
  - @rcdailey: #482 (markdown hard line breaks not rendering)
  - @foxytanuki: #480 (PLANNOTATOR_REMOTE=false semantics)
  Full Changelog : v0.16.7...v0.17.0
3. 🔗 r/Yorkshire Richmond gleaming in the spring sunshine today. rss
  
  submitted by /u/Still_Function_5428
  [link] [comments]
4. 🔗 r/Yorkshire No better place.. rss
  
  | Average photo. submitted by /u/Melodic_Position_590
  [link] [comments]
  ---|---
5. 🔗 r/LocalLLaMA What it took to launch Google DeepMind's Gemma 4 rss
  
  | 💎💎💎💎 submitted by /u/jacek2023
  [link] [comments]
  ---|---
6. 🔗 r/york What’s the name of the trio who play in York? rss
  
  They are a three piece, violin, guitair and double bass and they play covers in York. They’re bloody fantastic but cannot remember their name
  
  submitted by /u/rjle_x
  [link] [comments]
7. 🔗 jesseduffield/lazygit v0.61.0 release
  The big one in this release is support for GitHub pull requests. They are shown as little GitHub icons next to each branch that has one, and you can open a PR in the browser by pressing shift-G. To enable this, all you need to do is install the gh tool if you haven't already, and log in using gh auth login.
  
  What's Changed
  
  Features ✨
  - Show pull requests against branches by @jesseduffield in #2781
  Enhancements 🔥
  - Add support for clicking on arrows in the file list to expand/collapse directories by @blakemckeany in #5365
  - Remove empty directories after discarding untracked files by @stefanhaller in #5408
  - Make file sort order and case sensitivity configurable, and default to mix files and folders by @stefanhaller in #5427
  - Allow customizing the window width/height thresholds for when to use portrait mode by @stefanhaller in #5452
  - Log hashes of local branches when deleting them by @stefanhaller in #5441
  - Add condition field to custom command prompts by @mrt181 in #5364
  Fixes 🔧
  - Fix staging only some lines of a block of consecutive changes by @stefanhaller in #5396
  - Fix the expanded layout of the branches panel (half and full screen modes) by @stefanhaller in #5413
  - Fix searching commits or main view after switching repos by @stefanhaller in #5424
  - Scroll to top when showing subcommits by @stefanhaller in #5425
  - Fix patch commands when git config has color=always by @matthijskooijman in #5405
  - Don't stage out-of-date submodules when asking user to auto-stage after resolving conflicts by @stefanhaller in #5440
  Maintenance ⚙️
  - Remove go-git dependency by @stefanhaller in #5420
  - Make Debian/Ubuntu install command architecture-independent by @discapes in #5386
  - Bump github.com/buger/jsonparser from 1.1.1 to 1.1.2 by @dependabot[bot] in #5423
  - fix: pin 7 unpinned action(s), extract 1 inline secret to env var by @dagecko in #5439
  - Fix dependabot config file by @stefanhaller in #5443
  - Bump actions/cache from 4 to 5 by @dependabot[bot] in #5444
  - Bump actions/download-artifact from 7 to 8 by @dependabot[bot] in #5445
  - Bump actions/upload-artifact from 6 to 7 by @dependabot[bot] in #5446
  - Bump github.com/lucasb-eyer/go-colorful from 1.3.0 to 1.4.0 by @dependabot[bot] in #5447
  - Bump github.com/spf13/afero from 1.9.5 to 1.15.0 by @dependabot[bot] in #5448
  - Bump github.com/creack/pty from 1.1.11 to 1.1.24 by @dependabot[bot] in #5449
  - Bump github.com/stretchr/testify from 1.10.0 to 1.11.1 by @dependabot[bot] in #5450
  - Bump github.com/sanity-io/litter from 1.5.2 to 1.5.8 by @dependabot[bot] in #5451
  - Bump github.com/adrg/xdg from 0.4.0 to 0.5.3 by @dependabot[bot] in #5456
  - Bump github.com/spkg/bom from 0.0.0-20160624110644-59b7046e48ad to 1.0.1 by @dependabot[bot] in #5457
  - Bump github.com/integrii/flaggy from 1.4.0 to 1.8.0 by @dependabot[bot] in #5458
  - Bump github.com/sahilm/fuzzy from 0.1.0 to 0.1.1 by @dependabot[bot] in #5459
  - Bump github.com/sasha-s/go-deadlock from 0.3.6 to 0.3.9 by @dependabot[bot] in #5460
  Docs 📖
  - Add a note about AI to CONTRIBUTING.md by @stefanhaller in #5404
  - Update redo keybinding in README.md by @unikitty37 in #5387
  - Fix grammar in the contributor guide by @Rohan5commit in #5392
  I18n 🌎
  - Update translations from Crowdin by @stefanhaller in #5476
  Performance Improvements 📊
  - Improve performance of discarding many files by @stefanhaller in #5407
  New Contributors
  - @blakemckeany made their first contribution in #5365
  - @discapes made their first contribution in #5386
  - @unikitty37 made their first contribution in #5387
  - @Rohan5commit made their first contribution in #5392
  - @matthijskooijman made their first contribution in #5405
  - @dagecko made their first contribution in #5439
  - @mrt181 made their first contribution in #5364
  Full Changelog : v0.60.0...v0.61.0
8. 🔗 @binaryninja@infosec.exchange Tired of unzipping your password-protected malware samples just to analyze mastodon
  
  Tired of unzipping your password-protected malware samples just to analyze them? We've got you covered.
  
  Our latest blog post covers Container Transforms and how Binja now handles nested binary formats with structure and provenance intact.
  
  Read it here: https://binary.ninja/2026/03/31/container- transforms.html
9. 🔗 r/york Wedding Venues in and around York rss
  
  Hi all. My fiancé and I are looking for twilight wedding packages (late afternoon to evening) in and around York for maybe a year from now. We are looking for a low to medium price point and we'd love to hear what venues are a good place to get married at.
  
  submitted by /u/HarryBuckley49
  [link] [comments]
10. 🔗 r/wiesbaden Sprach Schule in Frankfurt/Wiesbaden rss
  
  submitted by /u/Alert-Count8542
  [link] [comments]
11. 🔗 r/Yorkshire Hand painted Yorkshire artworks by Paul Halmshaw. rss
  
  | submitted by /u/Far-Elephant-2612
  [link] [comments]
  ---|---
12. 🔗 r/york Catering Rec's rss
  
  Hi, looking for recommendations for a caterer/someone to do food for my son's Christening. I quite like the idea of a graze table style spread, but not set on this.
  
  Thanks!
  
  submitted by /u/aprodog
  [link] [comments]
13. 🔗 r/york My Visit To The City Today - lots of photos. rss
  
  | submitted by /u/danum1962
  [link] [comments]
  ---|---
14. 🔗 r/york Original Ghost Walk (1973) vs. Mad Alice, which one should I book ? rss
  
  Hi All, I'll be visiting York soon and I badly want to do a ghost tour. Ive been looking for choices and Im torn between 2.
  
  I really love the fact that the Original Ghost Walk is the oldest in the world, that authenticity is pulling me.
  
  But I see everyone raving about Mad Alice (The Bloody Tour) for the performance. For those who have done both, which one feels more like a genuine dive into York's history ? (or) should I even care about history and just look to have fun ?
  
  I’m staying overnight specifically to do one of these, so I want to make sure I pick the one that actually feels worth after dark.
  
  submitted by /u/Lanky_Cartoonist_743
  [link] [comments]
15. 🔗 r/Leeds 18f in leeds wanting a creative circle rss
  
  Hi, I’m 18 and based in Leeds. I’m really into the idea of filmmaking and creative stuff in general (making videos, trying out ideas, etc.), and I’d love to meet people around my age who are into the same kind of thing.
  
  I’m still pretty new to it and trying to build a creative circle, so I’m supperr desperate for people who want to make things together, collaborate, or just chat about creative ideas.
  
  If anyone knows of any places, groups, or communities in Leeds where people like this hang out, I’d really appreciate any suggestions too.
  
  Feel free to message me if you’re interested 😭🙏🏾
  
  submitted by /u/Sufficient_Leg_5141
  [link] [comments]
16. 🔗 sacha chua :: living an awesome life YE12: Categorizing Emacs News, epwgraph, languages rss
  View in the Internet Archive, watch or comment on YouTube, or email me.
  
  Chapters:
  - 00:41:21 epwgraph
  - 00:54:56 learning languages
  Thanks for your patience with the audio issues! At some point, I need to work out the contention between all the different processes that I want to be listening to the audio from my mic. =)
  
  In this livestream, I categorize Emacs News for 2026-04-06, show epwgraph for managing Pipewire connections from Emacs, and share some of my language learning workflows.
  
  View Org source for this post
  
  You can e-mail me at sacha@sachachua.com.
17. 🔗 r/Leeds Sharps bin disposal in Leeds? rss
  
  Hi there,
  
  Does anyone know where I can dispose of a sharps bin in Leeds?
  
  It’s for syringes and needles for a medication I am prescribed by an online company.
  
  Thanks in advance!
  
  submitted by /u/No-Stick9557
  [link] [comments]
18. 🔗 r/york Jumble sale! rss
  
  🛍️ Jumble Sale – Saturday 11th April! 🛍️
  
  A fantastic jumble sale will be taking place on Saturday 11th April, 2pm – 4pm at the Sheriff Hutton Village Hall, in support of Shopmobility York.
  
  The wonderful Sheriff Hutton Jumblies will be running the sale on our behalf – and if you’ve been before, you’ll know it’s always a brilliant event with plenty of bargains to be found!
  
  ✨ Details:
  
  • ⏰ Time: 2pm – 4pm
  
  • 📍 Location: Village Hall, Sheriff Hutton Road, York YO60 6RA
  
  • 💷 Entry: Just 50p
  
  • 🚶 It’s always popular – arriving early to join the queue is highly recommended!
  
  🎟️ Don’t miss the tombola, and be sure to visit the cake stall for some delicious homemade treats!
  
  🙏 Donations still welcome! If anyone is still wanting to donate items, please contact to arrange collection or drop off.
  
  Come along, grab a bargain, and support a great cause – we’d love to see you there!
  
  JumbleSale #ShopmobilityYork #CommunityEvent
  
  submitted by /u/Single-Ad-5317
  [link] [comments]
19. 🔗 r/reverseengineering Cracking a Malvertising DGA From the Device Side rss
  
  submitted by /u/AdTemporary2475
  [link] [comments]
20. 🔗 r/york Walking into York by the Ouse rss
  
  | submitted by /u/York_shireman
  [link] [comments]
  ---|---
21. 🔗 sacha chua :: living an awesome life 2026-04-06 Emacs news rss
  There's a lot of buzz around the remote code execution thing that involves Git, but it seems to be more of a Git issue than an Emacs one. This might be a workaround if you want, and in the meantime, don't check out git repositories you don't trust. There's no page for the Emacs Carnival for April yet, but you can start thinking about the theme of "newbies/starter kits" already, and I'm sure Cena or someone will round things up afterwards. Enjoy!
  - Workaround for the Git-related security issue that lots of people are talking about (@stackeffect@social.tchncs.de)
  - Upcoming events (iCal file, Org):
    
    Emacs.si (in person): Emacs.si meetup #4 2026 (v #živo) https://dogodki.kompot.si/events/c4ee8c26-c668-491e-91b3-b466578b83e2 Mon Apr 6 1900 CET
    
    Emacs Paris: S: Emacs workshop in Paris (online) https://emacs-doctor.com/ Tue Apr 7 0830 America/Vancouver - 1030 America/Chicago - 1130 America/Toronto - 1530 Etc/GMT - 1730 Europe/Berlin - 2100 Asia/Kolkata - 2330 Asia/Singapore
    
    OrgMeetup (virtual) https://orgmode.org/worg/orgmeetup.html Wed Apr 8 0900 America/Vancouver - 1100 America/Chicago - 1200 America/Toronto - 1600 Etc/GMT - 1800 Europe/Berlin - 2130 Asia/Kolkata – Thu Apr 9 0000 Asia/Singapore
    
    Atelier Emacs Montpellier (in person) https://lebib.org/date/atelier-emacs Fri Apr 10 1800 Europe/Paris
    
    London Emacs (in person): Emacs London meetup https://www.meetup.com/london-emacs-hacking/events/313909207/ Tue Apr 14 1800 Europe/London
    
    Emacs Berlin: In-Person-Only Emacs-Berlin Stammtisch https://emacs-berlin.org/ Tue Apr 14 1900 Europe/Berlin
    
    M-x Research: TBA https://m-x-research.github.io/ Wed Apr 15 0800 America/Vancouver - 1000 America/Chicago - 1100 America/Toronto - 1500 Etc/GMT - 1700 Europe/Berlin - 2030 Asia/Kolkata - 2300 Asia/Singapore
    
    Protesilaos Stavrou: Emacs live stream with Sacha Chua on 2026-04-16 17:30 Europe/Athens
  - Emacs configuration:
    
    Announcing Anju (Reddit) - mouse interactions for modeline, context menu, and main menu
    
    Emacs Redux: Repeat Mode: Stop Repeating Yourself (Irreal)
    
    backpack 0.4.0 - adds self-documenting inventory browser (Reddit)
  - Emacs Lisp:
    
    Almighty Lisp: Lisp & Emacs Essentials - almightylisp.com (HN)
    
    Dave Pearson: nukneval.el v1.3 unload and re-evaluate
    
    Creating an Emacs Package from Concept to MELPA (Part 7) (57:13)
    
    How to run a function when my buffer selection changes? - updated with window-state-change-hook
    
    Yay Emacs live: Reorganizing my Emacs configuration so that my defuns are tangled to separate files (01:48:56)
    
    Sacha Chua: YE11: Fix find-function for Emacs Lisp from org-babel or scratch (YouTube, 08:19)
  - Appearance:
    
    New package: outline-stars.el (Reddit)
    
    occult.el - collapse buffer regions into single-line summaries (Reddit)
    
    Make the left margin shine!
    
    Senka07/yotsuba-emacs-theme · GitHub (Reddit)
  - Navigation:
    
    Tip about using other-window-prefix C-x 4 4
    
    Tip about using windmove
  - Writing:
    
    Curtis McHale: Check Spelling in Emacs (YouTube 06:38)
    
    Dave Pearson: blogmore.el v3.1
  - Denote:
    
    Protesilaos Stavrou: Emacs: new sequence scheme for the ‘denote-sequence’ package
  - Org Mode:
    
    [EMACS LAB] #3: Introduction to Org Mode (01:57:55)
    
    aravindps/org-gtd: Things 3 style GTD for Emacs — org-mode agenda views, ⌘ keybindings, context tags. Works with Doom and vanilla Emacs. · GitHub (r/emacs, r/orgmode)
    
    [BLOG] #27 bbb:OrgMeetup on Wed, February 11, 19:00 UTC+3 - Ihor Radchenko (@yantar92@fosstodon.org) notes
    
    Import, export, and integration:
    
    lopeztel/ox-dnd-html: Emacs export org files to D&D themed html · GitHub (Reddit)
    
    Adding org-protocol support (Reddit)
    
    Sacha Chua: Extract PDF highlights into an Org file with Python (YouTube 04:27)
    
    James Endres Howell: My first advice! (in Emacs Lisp) - specifying HTML boilerplace for org-static-blog
    
    RSS feeds for your org-mode website (@bgtdsword@toot.io)
    
    Org-mode - Various font sizes LaTeX (04:14)
    
    Org development:
    
    ol: Allow targets as search option in id: links
    
    org-babel: Fix and extend `org-babel-update-intermediate' variable
    
    Query before attempting to overwrite existing attachment/DnD/yank file
    
    Merge branch 'bugfix'
    
    etc/ORG-NEWS: Remove announcement about bugfix
  - Completion:
    
    Emacs Redux: Declutter M-x with read-extended-command-predicate
    
    [RELEASE] let-completion v0.2.0: full overhaul of Elisp completion - 46 binding forms, function argument candidates, expandable registry, fully customizable two-column annotations (Reddit)
    
    rougier/nano-vertico: Emacs / nano + vertico · GitHub (Reddit)
  - Coding:
    
    Mike Olson - eglot-python-preset and eglot-typescript-preset: Now on MELPA (Reddit)
    
    Function to make eglot add IWYU headers without doing an autocomplete in the buffer
    
    Dave Pearson: make-phony.el v1.3 for Makefiles
    
    Daskeladden/shipit: Code review in Emacs · GitHub (Reddit)
  - Shells:
    
    Ghostel - terminal emulator powered by libghostty (Reddit)
  - Mail, news, and chat:
    
    Thanos Apollo: Bringing jabber.el Back From the Dead (@debacle@framapiaf.org)
    
    mastodon.el 2.0.14 - jump to quoting toot, bugfixes, annotations (@mousebot@todon.nl)
  - Multimedia:
    
    Using Android TTS in Emacs
  - Fun:
    
    Anybody interested in writing SDL games in Emacs Lisp?
    
    Emacs + SDL: unblocking the unblockable (emacs-devel)
    
    Dave Pearson: eg.el v1.2 Norton Guide?, thinks.el v1.13 thought bubbles, binclock.el v1.12 binary clock, obfusurl.el v2.2 obfuscating URLs
  - AI:
    
    I run my company from Emacs (HN)
    
    Crafting an AI-Driven Workflow System - System Crafters Live! (01:52:03)
    
    Will using Emacs give you an edge in the AI-era? (45:08, Reddit, Reddit)
    
    The Agent-Native Editor Was Invented in 1976
  - Community:
    
    Emacs ATX Meetup. April 2026. - YouTube (2:04:58)
    
    Sacha Chua: #YayEmacs 10: Emacs coaching with Prot: Emacs workflows and streaming (YouTube 01:06:30)
    
    Sacha Chua: Thinking about Emacs coaching goals with Prot
    
    Protesilaos Stavrou: Emacs coaching with Sacha Chua
    
    Emacs Carnival March 2026: Mistakes and Misconceptions
    
    The Comfort Trap (@len@toot.si)
    
    Christian Tietze: Emacs Mistakes and Misconceptions That Held Me Back in 2019
    
    Einar Mostad: Emacs mistakes and misconceptions
    
    Prot Asks: Hjalmar about Emacs for music, the joy of art, and Internet sociability (02:04:24)
    
    Alvaro Ramirez: …and then there were three (expect delays) (Irreal)
    
    A Cult AI Computer’s Boom and Bust - YouTube (Irreal)
  - Other:
    
    Emacs Docs (Reddit, @maxxcan@mastodon.social)
    
    Thanos Apollo: Gnosis 0.10: Import Anki, Merge Everything Into One
    
    doom emacs install on manjaro linux walkthrough on hyper-v vm (17:29)
  - Emacs development:
    
    On keybindings and the slow erosion of help's utility - long discussion
    
    New option vc-dir-auto-hide-up-to-date
    
    * lisp/vc/diff-mode.el (diff-mode-read-only-map): Bind 'v'.
    
    * etc/NEWS: Announce Org update.
    
    ; Fix documentation of last change
    
    Recursively check dependencies for package compatibility
    
    Inform macOS Accessibility Zoom of cursor position (bug#80624)
    
    New macro setopt-local and function set-local (bug#80709)
    
    Add xref-edit-mode (bug#80616)
  - New packages:
    
    compilation-history: Track compilation history in SQLite (MELPA)
    
    corg: Header completion for org-mode (MELPA)
    
    evim: Evil Visual Multi - Multiple cursors for evil-mode (MELPA)
    
    ghostel: Terminal emulator powered by libghostty (MELPA)
    
    meshmonitor-chat: Chat client for MeshMonitor (Meshtastic) (MELPA)
    
    occult: Collapse and reveal buffer regions (MELPA)
    
    org-dt: Dynamic templating loader (MELPA)
    
    org-grimoire: Emacs-native static site generator (MELPA)
    
    org-invox: Invoice management for contractors using Org mode (MELPA)
  Links from reddit.com/r/emacs, r/orgmode, r/spacemacs, Mastodon #emacs, Bluesky #emacs, Hacker News, lobste.rs, programming.dev, lemmy.world, lemmy.ml, planet.emacslife.com, YouTube, the Emacs NEWS file, Emacs Calendar, and emacs-devel. Thanks to Andrés Ramírez for emacs-devel links. Do you have an Emacs-related link or announcement? Please e-mail me at sacha@sachachua.com. Thank you!
  
  View Org source for this post
  
  You can e-mail me at sacha@sachachua.com.
22. 🔗 r/Yorkshire I don’t think any place can match this vibe that Yorkshire has✨ rss
  
  | @ travelandchill1 submitted by /u/ScrollAndThink
  [link] [comments]
  ---|---
23. 🔗 r/Leeds Few more photos rss
  
  Couple more photos this morning, although I got told off. Apparently Wellington Place don't permit commercial photography without prior agreement.
  
  I'm in my work clothes with a Red S9 posting pics on Reddit lol.
  
  submitted by /u/Phil-pot
  [link] [comments]
24. 🔗 Pagefind/pagefind v1.5.0 release
  Hey! This is a big one. Pagefind 1.5.0 has been fermenting for a while, and addresses a lot of long-standing issues and feature requests. This release brings an entirely new search UI built on web components, major improvements to search relevance and ranking, diacritics support, automatic CJK segmentation, Web Worker search, notably smaller indexes, and a much faster indexing binary. Enormous thanks to everyone who contributed features and fixes, as well as to everyone who tested the beta releases and provided feedback ❤️ - @bglw
  
  If you only read this far, I should mention up front: The existing Default UI and Modular UI remain available and supported for now, so you can upgrade your sites to Pagefind v1.5.0 without migrating to the Component UI.
  
  Pagefind Component UI
  
  Pagefind ships a brand new UI system built entirely on web components. The Component UI gives you searchboxes, modals, result lists, and filter controls as composable <pagefind-*> elements that you can mix, match, and style with CSS variables.
  
  The Component UI is available as vendored files in your /pagefind/ output directory, or as an npm package to install and import.
  
  The best way to get a feel for the new components is on the 📘 Pagefind Component UI page of the docs, where interactive examples of various components are shown.
  
  Extra goodies with the Component UI:
  - Greatly improved accessibility over the Default UI
  - Keyboard navigation through search results
  - Configurable keyboard shortcuts (thanks @miketheman !)
  - Full custom templates for rendering results and placeholders
  - Exported types for Component UI npm consumers (thanks @vanruesc !)
  - Support for multiple scoped Pagefind instances on one page
  - A range of CSS variables available for light-touch customization (thanks @miketheman for some of these!)
  - Improved RTL and locale-specific rendering
  Search Relevance, and Searching Metadata
  
  Pagefind now searches metadata by default! Importantly, this means it now searches the title metadata. Matches in titles are now taken into account, and search results are very hard to shake from prime positions if all (or much) of the title matches the search query.
  
  You can configure the weight of any metadata field. See 📘 Configuring Metadata Weights to change the title boost or apply custom weights to your own metadata fields.
  
  Beyond metadata searching, a bunch of weird and wonderful ranking bugs were resolved:
  - Metadata-only matches now return results. Previously, if a page matched the search query only in its metadata (e.g. the title) but not in the body content, it would be missed. These pages now correctly appear in results.
  - Word splitting and indexing was revisited to properly handle diacritics, stemming, and compound words together. This fixes a broad set of edge cases where compound word parts weren't indexed correctly.
  - Loading index chunks now correctly uses stemmed terms. This was a discrepancy in how chunks were identified, and could cause some hard to pin down issues where the wrong chunk would be loaded for a search term, leaving you with no (or fewer) results.
  - A couple of pathways left you with only the first matching chunk loaded, which would also give you fewer results. Words that straddle multiple chunks now behave better.
  - Fancy-pants unicode characters in words could really mess up the chunk loading, which has been fixed.
  Diacritics Support
  
  We finally properly support matching across diacritics. You can now find your cafés without remembering how to type é.
  
  By default, exact diacritic matches are preferred. So if you're searching "cafe", pages with "cafe" will rank higher than pages with "café". Getting this relevance right by default was the final piece of the puzzle for shipping this, which is why it took a while to land. See 📘 Configuring Diacritic Similarity to adjust how this plays out on your site.
  
  If you need strict matching, set exactDiacritics: true to disable normalization entirely — "cafe" will only match "cafe", and "café" will only match "café". 📘 Exact Diacritics
  
  Multilingual Improvements
  
  Thanks browsers! Pagefind now taps into Intl.Segmenter to chop search queries in CJK (Chinese, Japanese, Korean) non-whitespace-delimited languages. This was already done during indexing by Pagefind, but users searching still had to delimit their queries. Now searching "这是一段简单的测试文本" searches for the words "这", "是", "一段", "简单", "的", "测试", and "文本", which is also how that sentence was indexed.
  
  We also updated the underlying stemming library (thanks @uded !) which brings stemming support for Polish and Estonian (and Esperanto, if anyone is out there indexing some lang="eo" pages). The Snowball upgrade also improves stemming quality across many already-supported languages.
  
  Indexing Performance
  
  The indexing binary (the one you install through npx or your wrapper of choice) is now both smaller (so, faster to download) and faster to run, by quite a lot on both fronts. On some sites, indexing is more than twice as fast. Thanks to @zmre for much of this!
  
  Search Performance
  
  Pagefind's search now runs in a Web Worker automatically. This doesn't make the search faster, per se, but it dramatically improves perceived performance on large websites by keeping the main thread responsive. If Web Workers are unavailable, it falls back to the main thread automatically.
  
  Plus: Some low-hanging fruit was picked off, and Pagefind's index chunks are now ~45% smaller thanks to delta-encoding page numbers and word locations.
  
  New Search Options
  - metaCacheTag — Allows you to configure the cache-busting tag on the metadata file (which is fetched fresh on every page load). For offline/PWA scenarios where assets need to be served with service workers, this can now be overridden.
  - plain_excerpt — Search results and sub-results now include a plain_excerpt field containing the excerpt text without highlight mark tags, for those who want to handle highlighting themselves (or don't want it at all).
  - matchedMetaFields — Search results now include a matchedMetaFields field listing which metadata fields matched the search query.
  - includeCharacters is now available in the Node and Python wrapper APIs.
  UI Translations
  - Added Greek (el) translations. (PR #1019 — thanks @Yoda-Soda !)
  - Improved Chinese Traditional (zh-TW) translations. (PR #990 —thanks @510208 !)
  - Improved German (de) translations. (PR #953 —thanks @randomguy-2650 !)
  - Added translations for new Component UI strings across all existing languages.
  Other bits and bobs
  - Fixed relative image URLs (e.g. ./image.png) breaking when displayed in search results. (PR #1087)
  - Fixed Python x86_64 macOS wheel being incorrectly tagged as arm64. (PR #950 — thanks @lioman !)
  - Fixed Python wheel tags being written in compressed form. (PR #989 — thanks @ichard26 !)
  - Excluded the vendor directory from the main pagefind PyPI package. (PR #991)
  - Migrated Python wrapper build tooling from Poetry to uv. (PR #934 — thanks @SKalt !)
  - Fixed subresult URLs ignoring page meta URL overrides. (PR #1076)
  - Fixed subresult highlight mark color. (PR #1024)
  - Index chunk fetches are now throttled to avoid overwhelming the network on large sites. (PR #1071)
  - Added Windows ARM64 (aarch64-pc-windows-msvc) as a supported platform. (PR #1079)
  - For crate consumers: Moved actix-web and related serving dependencies behind a serve feature flag (PR #1023)
  Looking Forward
  
  The Component UI is the new recommended way to add search to your site, and future UI work will focus there. The Default UI and Modular UI are sticking around for now, but the Component UI is where new features will land first.
  
  Thanks again to everyone who contributed to this release!
25. 🔗 r/reverseengineering /r/ReverseEngineering's Weekly Questions Thread rss
  
  To reduce the amount of noise from questions, we have disabled self-posts in favor of a unified questions thread every week. Feel free to ask any question about reverse engineering here. If your question is about how to use a specific tool, or is specific to some particular target, you will have better luck on the Reverse Engineering StackExchange. See also /r/AskReverseEngineering.
  
  submitted by /u/AutoModerator
  [link] [comments]
26. 🔗 r/wiesbaden Karosseriebauer / Lackierer rss
  
  Moin,
  
  mir ist jemand gegen das geparkte Auto gedonnert.
  
  Verkleidung der Frontstoßstange und Kotflügel müssen gemacht werden.
  
  Der Unfallverursacher ist bekannt und seine Versicherung zahlt.
  
  Habt ihr Tipps für einen wirklich guten Karosseriebauer / Lackierer?
  
  Und eventuell auch einen gescheiten Anwalt für Verkehrsrecht?
  
  submitted by /u/BabaJoe
  [link] [comments]
27. 🔗 r/LocalLLaMA I technically got an LLM running locally on a 1998 iMac G3 with 32 MB of RAM rss
  
  | Hardware: • Stock iMac G3 Rev B (October 1998). 233 MHz PowerPC 750, 32 MB RAM, Mac OS 8.5. No upgrades. • Model: Andrej Karpathy’s 260K TinyStories (Llama 2 architecture). ~1 MB checkpoint. Toolchain: • Cross-compiled from a Mac mini using Retro68 (GCC for classic Mac OS → PEF binaries) • Endian-swapped model + tokenizer from little-endian to big-endian for PowerPC • Files transferred via FTP to the iMac over Ethernet Challenges: • Mac OS 8.5 gives apps a tiny memory partition by default. Had to use MaxApplZone() + NewPtr() from the Mac Memory Manager to get enough heap • RetroConsole crashes on this hardware, so all output writes to a text file you open in SimpleText • The original llama2.c weight layout assumes n_kv_heads == n_heads. The 260K model uses grouped-query attention (kv_heads=4, heads=8), which shifted every pointer after wk and produced NaN. Fixed by using n_kv_heads * head_size for wk/wv sizing • Static buffers for the KV cache and run state to avoid malloc failures on 32 MB It reads a prompt from prompt.txt, tokenizes with BPE, runs inference, and writes the continuation to output.txt. Obviously the output is very short, but this is definitely meant to just be a fun experiment/demo! Here’s the repo link: https://github.com/maddiedreese/imac-llm submitted by /u/maddiedreese
  [link] [comments]
  ---|---
28. 🔗 r/Yorkshire Anybody here ever been to Market Weighton? Easily one of the nicest small towns in East Yorkshire in my opinion. rss
  
  I haven't been to Market Weighton since around 2012 but plan on visiting again when I'm next in Hull again, always loved visiting Market Weighton when I lived in East Yorkshire.
  
  submitted by /u/AcadiaNo1039
  [link] [comments]
29. 🔗 badlogic/pi-mono v0.65.2 release
  
  No content.