🏡
  • ↔
  • →

to read (pdf)

  1. DomainTools Investigations | DPRK Malware Modularity: Diversity and Functional Specialization
  2. EXHIB: A Benchmark for Realistic and Diverse Evaluation of Function Similarity in the Wild
  3. Neobrutalism components - Start making neobrutalism layouts today
  4. Debunking zswap and zram myths
  5. Building a Pipeline for Agentic Malware Analysis | Tim Blazytko

generated: April 11, 2026 at 00:09:52

  1. April 10, 2026
    1. 🔗 r/wiesbaden Suche Karten für Museum x Schlachthof am 25.04. rss

      Titel..

      Grüße

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

    2. 🔗 r/Harrogate Food recommendations rss

      Recommendations for nice food in Harrogate (casual dress)?? I am visiting this weekend, and would love some recommendations for dinner, breakfast or any nice character pubs.

      I have looked at the orchid which looks amazing but will be in casual clothes after mooching all day!

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

    3. 🔗 r/york York Wargaming Discord etc. rss

      Hi all,

      Does one exist? As me and my friends are getting older and busier it’s sometimes tough to link up. I was hoping to find a means to get some games when I have chance.

      Various systems, but perhaps less popular ones.

      I know TM has a group chat but I don’t have facebook.

      Appreciate the help.

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

    4. 🔗 r/york Visited this week, one of my favourite cities. rss

      Visited this week, one of my favourite cities. | 6 hour drive away, stayed in the area for a few days. Took my kid for the first time, absolutely loved the Railway Museum submitted by /u/Dizzy_Key_7400
      [link] [comments]
      ---|---

    5. 🔗 r/york Station short stay car park open or closed? rss

      Hello,

      I've heard mixed feedback about the short stay car park - is it open/available via the portico on weekends? Also does it still have the 20-minute grace period or have they changed that?

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

    6. 🔗 r/Yorkshire Leeds Trinity University students ordered to pay back maintenance loans given in error rss

      Leeds Trinity University students ordered to pay back maintenance loans given in error | submitted by /u/Legitimate-Break-143
      [link] [comments]
      ---|---

    7. 🔗 r/reverseengineering Nuitka to python. Nuitka is not really cython code due to dependencies I recommend to create new python compiler for protect your source not by weak compiler like Nuitka also you need decrypt xored nuitka blob in 4.0 (very easy task) rss

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

    8. 🔗 r/york Ken Cooke rss

      Ken Cooke | This guy is a true Yorkie. 101 years old and a Normandy Veteran. This morning he has been at the Cocoa Works on Haxby Rd sharing his stories of what it used to be like during his 49 years working for Rowntrees. He stood talking for 20 minutes or so with a captivated audience. From the old family-like workplace culture to his time away during WW2 and then back doing different roles until he retired in 1989. Incredible. submitted by /u/York_shireman
      [link] [comments]
      ---|---

    9. 🔗 r/Leeds Missing headphones found rss

      I've found a pair of headphones at the bottom of Greek Street All Bar One so if you're missing any I've dropped them off into the bar, you'll just need to provide a description of them to staff to collect them

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

    10. 🔗 r/LocalLLaMA Final voting results for Qwen 3.6 rss

      Final voting results for Qwen 3.6 | 7 days have passed. Hopefully, the release will start soon https://x.com/ChujieZheng/status/2039909917323383036 submitted by /u/jacek2023
      [link] [comments]
      ---|---

    11. 🔗 r/Leeds Waterlane Boathouse Illustration rss

      One of the few places in Leeds I hadn't drawn yet, finally got round to drawing Waterlane Boathouse at night with the swans. Hope you enjoy this :)

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

    12. 🔗 r/Harrogate Furniture poverty on the rise, Harrogate charity says rss

      Furniture poverty on the rise, Harrogate charity says | submitted by /u/Kagedeah
      [link] [comments]
      ---|---

    13. 🔗 r/reverseengineering I'm doing a free monthly live series where I reverse-engineer iOS apps from the App Store and show what's exposed in the binary. First session soon. rss

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

    14. 🔗 r/Yorkshire The path rss

      The path | North Yorkshire submitted by /u/Damo_f_
      [link] [comments]
      ---|---

    15. 🔗 r/wiesbaden Internet (DSL) in Wiesbaden – Erfahrungen mit Anbietern? rss

      Hi zusammen,

      ich suche aktuell einen Internet (DSL) Anschluss in Wiesbaden und überlege zwischen Telekom, Vodafone, O2 und 1&1. Mir ist vor allem wichtig, dass die Verbindung stabil ist und der Preis passt.

      Wie sind eure Erfahrungen mit den Anbietern hier vor Ort? Gibt es Unterschiede oder ist es am Ende ähnlich? Und kennt jemand vielleicht auch gute lokale Anbieter?

      Danke euch!

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

    16. 🔗 r/york House share questions rss

      Hello! I've recently bought my first home and have a spare room going unused at the moment, I've been considering opening it up to be rented to make a little extra money but don't really know. So I thought I'd ask here! If anyone knows what amount of rent would be reasonable or has advice, or is just interested in getting a place i'd love to hear from folks, thanks!

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

    17. 🔗 r/LocalLLaMA the state of LocalLLama rss

      the state of LocalLLama | submitted by /u/Beginning-Window-115
      [link] [comments]
      ---|---

    18. 🔗 HexRaysSA/plugin-repository commits sync repo: +2 releases rss 
      sync repo: +2 releases

## New releases
- [BinSync](https://github.com/binsync/binsync): 5.14.0
- [IDAssist](https://github.com/symgraph/IDAssist): 1.7.0
  2. April 09, 2026
    1. 🔗 IDA Plugin Updates IDA Plugin Updates on 2026-04-09 rss

      IDA Plugin Updates on 2026-04-09

      New Releases:

      Activity:

    2. 🔗 r/Yorkshire Over Spurn Point at Sunset rss

      Over Spurn Point at Sunset | submitted by /u/UntidyLives
      [link] [comments]
      ---|---

    3. 🔗 r/Yorkshire Man, 60, and woman, 38, arrested in Barnsley, South Yorkshire on suspicion of murder after pedestrian, 45, dies in collision. rss

      submitted by /u/108CA
      [link] [comments]

    4. 🔗 Kagi release notes April 9th, 2026 - Tuning the Orchestra rss

      Improvements and bug fixes

      Kagi Search

      Kagi Assistant

      • Mobile app: Assistant has gray empty bar at top of screen #9570 @RMLight
      • Page context in assistant searches are limited #10167 @jonathan-s
      • Assistant thread history dates do not update dynamically when an old chat is continued #10278 @xx
      • Research Assistant searches fail on certain queries #10110 @doggofan
      • Kagi Assistant turns ssh commands into <mailto:user@domain> links even once corrected #8521 @xMotus
      • Editing a prompt with a file, removes it? #5653 @Thibaultmol

      Kagi Small Web

      • iOS Small Web Dark Mode App Icon #10136 @Cal4T5
      • Add a tap-based way to switch posts
      • Fixed incorrect text formatting for bookmark titles

      Kagi Translate

      • Warning badge when translating to/from language using custom instructions
      • Wordplay and puns lost in translation are now detected and surfaced to the user if word insights are enabled @zark
      • Fixed Spanish text sometimes appearing in French translations on Standard mode @UAguy
      • Fixed Japanese/Chinese/Korean IME first character being lost in empty editor @jisaker
      • Proofreading a Word Document #8810 @jmvleal
      • Translate UI does not respect settings #9944 @mmartinortiz
      • Fix: clear button not working on mobile due to composing state #unknown @unknown
      • Same Language bug #10134 @KikoAnimations
      • Fixed website translation stacking duplicate header bars when switching languages, and Google redirect URLs not being unwrapped
      • Fixed clear button not working on mobile after pasting, restoring history, or during keyboard composition
      • Fixed error when pasting rich text from webpages
      • Fixed translation between same-language variants (e.g. pt-BR to pt-PT) echoing input instead of translating
      • Fixed intermittent text-to-speech 503 errors
      • Renamed "Azeri" to "Azerbaijani" to match ISO 639 standard
      • Korean formality settings now apply to ko-KR locale @Hanbyeol
      • Decreased AI refusals when translating text and images
      • Pin "Detect Language" at the top of the source language selector for quick access @pineafan
      • Add Montenegrin as an option in Translate @mb
      • Improved keyboard shortcuts @mb

      Blast from the past

      Kagi's April Fools' homepage redesigned as a 1990s web portal, with a bright orange/yellow color scheme, starry border, retro logo, a "Fetch!" search button, nostalgic suggested searches like "Dial-up or ISDN?", sections for blog posts, app downloads, and community links, sidebar ads for Orion Browser and Kagi merch, and a deliberately broken PHP visitor counter in the footer.

      The retro homepage we implemented for April Fools may be gone, but many of you are not ready to let go of the nostalgia just yet.

      Here's a dedicated URL to bring it back whenever you want: https://kagi.com/?year=1996

      This sets a cookie so your device remembers. To undo it, click Back to the Future at the bottom of the page or visit https://kagi.com/?year=present_day

      Post of the week

      Here is this week's featured social media mention:

      Social media post from dietrich at burrito.space reading: "normalize paying for critical social infrastructure (or running it) works for search: i am a happy paying customer of kagi.com, a search engine that finally shows me results relevant to what i search for"

      Follow us and tag us in your comments, we love hearing from you!

      Kagi tip of the week 💡

      Did you know you can set up URL redirects to reroute search results to the sites or frontends you prefer? Here's how, with examples from the community.

      Kagi art

      AI and ads are a toxic combo. Across the Kagi ecosystem, there are no ads, and we're actively working to keep slop out of your search results. Read more about Kagi's SlopStop initiative here.

      Comic showing an "AI Slop Machine" fed by boxes labeled "ADS" via conveyor belt, spewing out piles of slop, while stick figures watch in disgust saying "So THAT'S what it's made from?!"

    5. 🔗 r/LocalLLaMA Opus = 0.5T × 10 = ~5T parameters ? rss

      Opus = 0.5T × 10 = ~5T parameters ? | submitted by /u/Wonderful-Ad-5952
      [link] [comments]
      ---|---

    6. 🔗 r/reverseengineering FLARE Learning Material rss

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

    7. 🔗 r/Leeds PSA If you want to quit smoking/vaping: Free Stop Smoking Service in Leeds rss

      Hi! I’m not associated with them or anything, just a long-time smoker trying to kick this nasty habit and thought I’d share for anyone else in the same boat.

      The Leeds Stop Smoking Service is completely free & accessible for all.

      Even if you’re only thinking about quitting or if you merely want to cut

      down on smoking it’s worth looking at their website.

      - You don’t need a GP referral to sign up, simply fill up their online form. It took me 10 minutes to answer all the questions and I was able to get an appointment within a week.

      - They offer both remote (via telephone) and face-to-face appointments with a counsellor OR free resources and support if you want to stop smoking by yourself.

      - It’s a 4-6 week long programme with check-in calls from your designated counsellor. Peer support groups are also available.

      - You can choose between free e-cigarettes (via their Swap to Stop initiative) or choose from a variety of Nicotine Replacement therapy supplies (gums, patches, and inhalators etc), and you can get your supplies mailed directly to you.

      They’ll tailor their recommendations to fit whatever position you’re in. Whether you’re just trying to reduce smoking or quit completely, or if you’re also managing a chronic illness or mental health condition while quitting, they’re there to help.

      Sign up here:

      1. General Stop Smoking Service

      2. Health Conditions Stop Smoking Service (specialised support if you have a diagnosed common mental illness or long-term physical health conditions)

      3. To refer someone else

      or call them at: 0800 169 4219

      Additional resources:

      - The NHS Stop Smoking app

      - National Smokefree helpline: 0300 123 1044

      (9am to 8pm Monday to Friday, and 11am to 4pm Saturday and Sunday)

      - Recommended reading & clinically approved:

      The Allen Carr’s Easy Way to Stop Smoking

      ••••

      My personal experience if you’re interested:

      I opted for a remote appointment and the counsellor I was assigned was incredibly empathetic and non-judgmental; she really listened and asked all the right questions such as why I want to quit and so on, and we came up with a combination of NRT supplies that would best fit my needs over the phone. For me, e-cigarettes weren’t an option because of my poor impulse control (thanks, ADHD!) and I ended up vaping more during past quitting attempts. And the hardest part of the habit for me to crack is the oral fixation and the smoking “ritual” so we opted for the inhalator (instead of patches) and gum for when my cravings are too intense. I also got a bunch of free resources and additional info in a follow-up email.

      I’m only a week in, but I’m doing much better with the additional support compared to all my previous quitting attempts. I couldn’t wait to share as I think it’s a wonderful resource that not many know of.

      Thanks for reading :)

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

    8. 🔗 r/Yorkshire Ingleborough viewed from Whernside earlier this week rss

      Ingleborough viewed from Whernside earlier this week | submitted by /u/SonicShadow
      [link] [comments]
      ---|---

    9. 🔗 backnotprop/plannotator v0.17.7 release

      Follow @plannotator on X for updates

      Missed recent releases? Release | Highlights
      ---|---
      v0.17.6 | Bun.serve error handlers for diagnostic 500 responses, install.cmd cache fix
      v0.17.5 | Fix VCS detection crash when p4 not installed, install script cache path fix
      v0.17.4 | Vault browser merged into Files tab, Kanagawa themes, Pi idle session tool fix
      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

      What's New in v0.17.7

      v0.17.7 fixes the "fetch(req) did not return a Response object" error that affected OpenCode users running opencode web, opencode serve, or any mode that starts the HTTP server (including --port or --hostname flags).

      Fix: OpenCode Web/Serve Mode Compatibility

      OpenCode recently added Node.js support alongside Bun. To bridge its Hono app to Node's HTTP server, OpenCode uses @hono/node-server, which includes a createAdaptorServer function. That function unconditionally patches global.Response with a polyfill class — a necessary step for Node.js, which lacks native web API globals.

      The problem: in opencode web and opencode serve modes, this patch runs before plugins load. When the plannotator plugin calls Bun.serve() and the fetch handler returns new Response(...), it's constructing the hono polyfill, not Bun's native Response. Bun validates return types using internal type tags, not instanceof, so it rejects the polyfill and shows its default error page. The error() handler added in v0.17.6 also uses new Response(...), which is why it didn't fire either — the error handler's own response was also a polyfill.

      Plain opencode TUI without --port or server config was never affected. In that mode, OpenCode routes requests through an internal RPC bridge instead of starting an HTTP server, so createAdaptorServer never runs and global.Response stays native.

      The fix detects the polyfill by walking the prototype chain. Hono sets up Object.setPrototypeOf(Response2.prototype, GlobalResponse.prototype), so the parent prototype's constructor is the original native Response. The plugin recovers it and restores globalThis.Response before any server code runs. When Response hasn't been patched, the detection check fails safely and the fix is a no-op.

      Install / Update

      macOS / Linux:

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

      Windows PowerShell:

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

      Pin a specific version:

      curl -fsSL https://plannotator.ai/install.sh | bash -s -- --version v0.17.7

      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.

      OpenCode: Clear cache and restart:

      rm -rf ~/.cache/opencode/packages/@plannotator ~/.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.

      What's Changed

      • fix: recover native Response when patched by hono node-server adapter by @backnotprop

      Community

      @Zengwenj reported the original issue in #528. @xxJava provided the p4 stack trace and confirmed cross-platform reproduction. @boris-gorbylev and @chocochu confirmed on macOS. @jehu-rodriguez confirmed 0.17.6's error handler didn't fire, which was the key clue that the issue was a non-Response return rather than an exception. The latest reporter confirmed opencode web as the specific trigger, which led directly to identifying the hono adapter's global.Response patch as the root cause.

      Full Changelog : v0.17.6...v0.17.7

    10. 🔗 r/york Can anyone who has recently had work done on their car please let me know what the hourly rate was? I’ve just had work done on mine and I’m not sure if I’ve been ripped off or not. Thank you rss

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

    11. 🔗 r/reverseengineering Analyzing a Denuvo bypass approach based on virtualization. rss

      submitted by /u/Medium-Piano-4488
      [link] [comments]

    12. 🔗 backnotprop/plannotator v0.17.6 release

      Follow @plannotator on X for updates

      Missed recent releases? Release | Highlights
      ---|---
      v0.17.5 | Fix VCS detection crash when p4 not installed, install script cache path fix
      v0.17.4 | Vault browser merged into Files tab, Kanagawa themes, Pi idle session tool fix
      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

      What's New in v0.17.6

      v0.17.6 adds error handlers to all three Bun servers (plan, review, annotate) so that unhandled exceptions produce a diagnostic 500 response instead of Bun's opaque default error page. This release also adds OpenCode cache clearing to the Windows CMD install script, which was missing entirely.

      Server Error Handlers

      Several OpenCode users reported seeing Bun's default error page ("You're seeing this because fetch(req) did not return a Response object") when using submit_plan. The root cause remains under investigation, but the default Bun error page provides zero diagnostic information, making it impossible to identify the actual exception from user reports alone.

      All three servers (plan review, code review, annotate) now register an error handler with Bun.serve(). When the fetch handler throws for any reason, the error handler catches it, logs the full exception to stderr, and returns a 500 response with the error message. Normal requests are unaffected. The only change in behavior is on error paths that were previously showing the opaque Bun page.

      This gives us the diagnostic information we need. The next user who hits this issue will see the actual error message instead of the generic Bun page, and can include it in their report.

      Windows CMD Install Script Cache Fix

      The install.cmd script had no OpenCode cache clearing at all. Users who installed or updated via CMD on Windows kept running stale cached plugin versions indefinitely. The script now clears %USERPROFILE%\.cache\opencode\packages\@plannotator alongside the existing bun cache paths, matching the behavior already present in install.sh and install.ps1 since v0.17.5.

      Install / Update

      macOS / Linux:

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

      Windows PowerShell:

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

      Pin a specific version:

      curl -fsSL https://plannotator.ai/install.sh | bash -s -- --version v0.17.6

      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 ~/.cache/opencode/packages/@plannotator ~/.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: add Bun.serve error handlers for diagnostic 500 responses by @backnotprop
      • fix: add OpenCode cache clearing to install.cmd by @backnotprop

      Community

      @Zengwenj, @xxJava, @boris- gorbylev, and @chocochu reported and confirmed #528. The error handler addition is a direct response to the difficulty of diagnosing the reported Bun error page without exception details.

      Full Changelog : v0.17.5...v0.17.6

    13. 🔗 r/Leeds Leeds vs Manchester uni rss

      So I have a conditional offer from both Manchester and Leeds. I’ve visited both, and I really like both! I am in for biological sciences at Manchester and biochemistry at Leeds.

      I was wondering if any of you guys currently go there or went there, what was your experience like? Did you regret your choice? I’m looking to come back to America after my studies here, so if any of yiu guys did that let me know!!

      Socially, how was it? I’m into running and biking so I would love to join a triathlete club here or whatever. Is there good routes around? (I know they are both in the city, but maybe some trails accessible by train?)

      Which city is your favorite? Which is more student friendly, safety and expenseses wise? Let me know!!

      From a worried high school senior

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

    14. 🔗 r/LocalLLaMA Local (small) LLMs found the same vulnerabilities as Mythos rss

      Local (small) LLMs found the same vulnerabilities as Mythos | submitted by /u/CyberAttacked
      [link] [comments]
      ---|---

    15. 🔗 backnotprop/plannotator v0.17.5 release

      Follow @plannotator on X for updates

      Missed recent releases? Release | Highlights
      ---|---
      v0.17.4 | Vault browser merged into Files tab, Kanagawa themes, Pi idle session tool fix
      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

      What's New in v0.17.5

      v0.17.5 is a hotfix for a server crash affecting plannotator review on systems without Perforce installed, plus a fix for stale OpenCode plugin caches that the install script failed to clear.

      VCS Detection Crash When Perforce Is Not Installed

      When running plannotator review, the server detects which version control system manages the current directory. The detection loop tries each provider in order: git first, then Perforce (p4). The Perforce provider calls Bun.spawn(["p4", "info"]) to check for a workspace. On systems where the p4 binary isn't installed, Bun.spawn throws an ENOENT error that was not caught. The unhandled exception crashed the Bun server process.

      This affected every user who doesn't have Perforce installed and ran plannotator review. The git provider's detection had the same vulnerability — if git wasn't in $PATH (possible on some Windows configurations), the spawn would throw before Perforce detection even ran.

      Both providers now catch spawn failures and return false, allowing the detection loop to continue to the next provider or fall back to git as the default. Perforce support continues to work for users who have it installed.

      Install Script Cache Path Fix

      The install script clears cached OpenCode plugin packages to force a fresh download on the next run. The cache-busting targeted ~/.cache/opencode/node_modules/@plannotator, but OpenCode actually stores plugin packages at ~/.cache/opencode/packages/@plannotator. Users who ran the install script to update were still running the old cached plugin version in OpenCode until the cache expired or was manually cleared.

      Both install.sh and install.ps1 now clear the correct path.

      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.5

      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 ~/.cache/opencode/packages/@plannotator ~/.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: catch VCS detection spawn failures when p4/git not in PATH by @backnotprop in #527
      • fix: correct OpenCode cache path in install scripts by @backnotprop in #527

      Community

      @Zengwenj reported the crash in #528 with a clear reproduction path and suspected cause. @xxJava confirmed the issue on both Windows and macOS and provided the full stack trace that pinpointed the exact line in p4.ts. @boris- gorbylev and @chocochu confirmed the issue on macOS with OpenCode.

      Full Changelog : v0.17.4...v0.17.5

    16. 🔗 r/york help me raise money for homeless people in york! rss

      help me raise money for homeless people in york! | apologies to the mods if this counts as self-promotion, but I'm hoping charity events might be an exception? on april 30 i will be sleeping outdoors at york community stadium to raise money for Hoping Kitchen and KEYS who both support homeless and vulnerable people in York (with other people as part of an event, i'm not just going to scale the walls and break in) i volunteer a few times a week with Carecent and Hoping Kitchen and i think everyone we help is so wonderful and deserves as much support as possible, which is why i'm really hoping i might be able to help raise some money for them this year. it obviously does not compare to actually sleeping rough in any way, and at worst I will be uncomfortable and probably not sleep at all, but my pets will miss me lots and be very sad. i am trying to raise at least £250 and currently have £0 of donations and i’m worried everyone will think i have no friends if no one sponsors me soon :( donate here or feel free to ask any questions! submitted by /u/kittywenham
      [link] [comments]
      ---|---

    17. 🔗 r/Harrogate Mens Casual Football rss

      My husband used to be an OK footballer - played into being a young adult in local leagues. He'd like to get back into playing in a team but isn't sure where to start. He doesn't have reddit so has asked me to post this for him.

      He's 45 and looking to play once or twice a week just casually for fitness and fun. Advice welcome.

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

    18. 🔗 Locklin on science Beyond Quantum with Khrennikov rss

      I’ve gone through Khrennikov’s “Beyond Quantum” book and write some notes for the crowd. I’ve also had a look at his book “Contextual Approach to Quantum Formalism,” and at least glanced at his more fruity books. Mostly this is a review of Beyond Quantum, which is a presentation of a group of “sub quantum” ideas. […]

    19. 🔗 r/Leeds Slimy facial recognition van set up on New York Street rss

      Disgusting to see, when did such surveillance tools and technology become so normalised?

      Not gonna claim this area doesn't have it's issues, it sure does. But lazily plopping a facial recognition van is absolutely not the way to deal with this. It's the same characters round here committing most of the crimes, all it takes is a bit of actual policing. Not this gross overreach

      A little afraid I'm gonna find out in the comments that most people are fine to see this

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

    20. 🔗 r/reverseengineering Porting Mac OS X to the Nintendo Wii rss

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

    21. 🔗 r/york The York food waste "saints" who feed city's children rss

      The York food waste "saints" who feed city's children | submitted by /u/Kagedeah
      [link] [comments]
      ---|---

    22. 🔗 r/Yorkshire 19 new family hubs open in Yorkshire and the Humber to support parents rss

      19 new family hubs open in Yorkshire and the Humber to support parents | More families are set to benefit from extra support on their doorstep. Nineteen new Best Start Family Hubs have opened across Yorkshire and the Humber, forming part of a new national network to support parents and children from pregnancy through to school age. The hubs offer free stay and play sessions, infant feeding advice, parenting support, and early help for children with special educational needs and disabilities (SEND), aiming to provide easier access to vital services under one roof. Hubs are designed to help families save up to £200 per year by reducing the need for private classes and offering free services such as stay and play. Additional support on debt and welfare is also available. Each hub includes outreach workers and practitioners to help identify and address additional needs early, ensuring families are not bounced between different services. Healthy Babies support will be integrated into the hubs, including midwifery, health visiting, infant feeding, and perinatal mental health support. The government plans to deliver up to 2,000 satellite locations by the end of 2028, offering family services from health centres, libraries, leisure centres, and churches to improve access. Across Yorkshire and the Humber, newly opened hubs include New Bewerley Children's Centre Family Services in Leeds, sites across Kirklees, 12 locations in East Riding of Yorkshire, and Scarborough Library. More than 200 hubs are now open nationally, with the government pledging to have 1,000 in operation by the end of 2028. submitted by /u/coffeewalnut08
      [link] [comments]
      ---|---

    23. 🔗 r/wiesbaden Jetzt auch in Wiesi rss

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

    24. 🔗 r/Leeds Skaters over 30 rss

      I've recently gotten back into skateboarding at age 34 and I was wondering if there are any skater groups in Leeds for people over 30, or a little older than kids at least.

      If not, would anybody here be willing to start one up?

      Thanks!

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

    25. 🔗 r/LocalLLaMA Gemma 4 on Llama.cpp should be stable now rss

      With the merging of https://github.com/ggml-org/llama.cpp/pull/21534, all of the fixes to known Gemma 4 issues in Llama.cpp have been resolved. I've been running Gemma 4 31B on Q5 quants for some time now with no issues.

      Runtime hints:

      • remember to run with --chat-template-file with the interleaved template Aldehir has prepared (it's in the llama.cpp code under models/templates)
      • I strongly encourage running with --cache-ram 2048 -ctxcp 2 to avoid system RAM problems
      • running KV cache with Q5 K and Q4 V has shown no large performance degradation, of course YMMV

      Have fun :)

      (oh yeah, important remark - when I talk about llama.cpp here, I mean the source code, not the releases which lag behind - this refers to the code built from current master)

      Important note about building: DO NOT currently use CUDA 13.2 as it is CONFIRMED BROKEN (the NVidia people are on the case already) and will generate builds that will not work correctly.

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

    26. 🔗 r/Yorkshire Gannet launching gracefully from a rock at RSPB Bempton Cliffs rss

      Gannet launching gracefully from a rock at RSPB Bempton Cliffs | submitted by /u/aspiranthighlander
      [link] [comments]
      ---|---

    27. 🔗 r/Leeds Recruitment agencies that aggressively help you find a role? rss

      I haven’t found my niche yet and looking to try new things, so temporarily contract work would be good for me atm. I have some qualifications and experience in a professional setting but im awful at interviews and not getting enough to improve that. I am currently feeling the pressure to find something quickly and was hoping someone could help with the names of some recruitment firms that secure interviews on your behalf… Cheers.

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

    28. 🔗 r/LocalLLaMA It's insane how lobotomized Opus 4.6 is right now. Even Gemma 4 31B UD IQ3 XXS beat it on the carwash test on my 5070 TI. rss

      It's insane how lobotomized Opus 4.6 is right now. Even Gemma 4 31B UD IQ3 XXS beat it on the carwash test on my 5070 TI. | submitted by /u/FrozenFishEnjoyer
      [link] [comments]
      ---|---

    29. 🔗 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.

    30. 🔗 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.

  3. April 08, 2026
    1. 🔗 IDA Plugin Updates IDA Plugin Updates on 2026-04-08 rss

      IDA Plugin Updates on 2026-04-08

      Activity:

      • python-elpida_core.py
        • 8dc18b89: feat: remove code_edit exclusion from Stage 2 — the system speaks its…
        • a9aec531: fix: desperation guard — cycle 52 heartbeat is run-complete, not crisis
        • b8154d26: feat: Parliament rebalancing — evidence-based provider reassignment
    2. 🔗 r/Yorkshire Can’t have anything these days rss

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

    3. 🔗 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

    4. 🔗 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":

      This is a pretty basic pelican. The bicycle is mangled, the pelican itself has a rectangular beak albeit with a hint of pouch curve below it. Not a very good one.

      And this one for "Thinking":

      Much better. Clearly a pelican. Bicycle is the correct shape. Pelican is wearing a blue cycling helmet (albeit badly rendered). Not a bad job at all.

      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.

      This sounded to me like Meta's Segment Anything, (I later heard that it's not, this is a native feature of the model itself via a tool call with a custom system prompt). 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:

      It's a photo of a raccoon wearing a disposable coffee cup and some newspaper and banana peel as a hat. It's pretty good

      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 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:

      OpenCV image analysis dashboard titled "OpenCV Analysis: Raccoon Trash Hat" with four panels: top-left shows the original 1280x1280 photo of a raccoon wearing a trash-lid hat with a coffee cup and newspaper on top in an alley; top-right shows a Canny edge detection version with white edges on black background labeled "Canny Edges - 4.6% density"; bottom-left shows "Top 5 Dominant Colors" as swatches with values RGB(20, 19, 24): 35.3%, RGB(43, 43, 47): 34.2%, RGB(84, 80, 79): 18.3%, RGB(139, 135, 131): 6.3%, RGB(210, 213, 208): 5.8%; bottom-right shows "Color Histograms" line chart with Red, Green, and Blue channels plotted from 0-250 on x-axis and 0-35000 on y-axis, peaking around value 25-50.

      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:

      Visual grounding analysis of a raccoon photo titled "Visual Grounding: Found 8 objects" with colored dot annotations on the image marking each detected object: coffee cup (515,205) in yellow, banana peel (569,261) in light yellow, newspaper (399,279) in blue, right eye (461,396) in magenta, left eye (582,397) in pink, nose (514,472) in cyan, raccoon (553,548) in green, and trash can lid (550,892) in red. A legend at the bottom lists all objects with their normalized 0-1000 coordinates. Footer text reads "Coordinates are 0-1000 normalized. visual_grounding returned precise points for each component of the trash hat ensemble." Watermark reads "Meta AI".

      [...]

      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:

      Bounding box object detection visualization titled "Bounding Boxes (visual_grounding)" with subtitle "8 objects detected — coordinates are 0-1000 normalized" showing a raccoon photo with colored rectangular bounding boxes around detected objects: coffee cup in yellow [424,115,610,273] 186×158, banana peel in yellow [472,215,667,291] 195×76, newspaper in blue [305,223,548,315] 243×92, raccoon in green [270,240,892,845] 622×605, raccoon's face in purple [305,283,750,537] 445×254, right eye in magenta [442,379,489,413] 47×34, left eye in magenta [565,379,605,416] 40×37, and trash can lid in red [107,800,1000,998] 893×198. A legend at the bottom shows each object's name, coordinates, and pixel dimensions in colored cards. Watermark reads "Meta AI".

      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:

      1. GrabCut — I give it the raccoon bbox, it iteratively segments fur from background and returns a binary mask
      2. 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!

      Screenshot of a Meta AI conversation where the user uploaded a photo of pelicans on rocks and asked "Count the pelicans". response reads: "That rocky haul-out is packed — I count 25 brown pelicans in your photo. I went bird by bird, including the ones tucked behind rocks, heads turned away, or just peeking out at the edges. They're all California brown pelicans, with those pale yellow heads and long bills, clustered on the riprap right at the waterline. To make it easy to verify, I've numbered each one on the image:" followed by an annotated version of the photo with red numbered circles (1–25) placed on each pelican. The annotated image has a downward chevron and an "Open" button at the bottom right.

      Here's that overlay exported as HTML.

      Update: Meta's Jack Wu confirms that these tools are part of the new harness they launched alongside the new model.

      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.

    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. 🔗 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]

    8. 🔗 r/LocalLLaMA It finally happened, I actually had a use case for a local LLM and it was brilliant rss

      It finally happened, I actually had a use case for a local LLM and it was brilliant | https://preview.redd.it/6v2q5726j0ug1.png?width=2950&format=png&auto=webp&s=142b34c6829d80d7ff807a3a589441463d0babf9 I've had aerosinusitis a few times before in my life and it was fairly painful, but not something that happens often. Today on a flight I had an overwhelming bout of it, the pressure was genuinely unbearable, and I had no painkillers with me. I was on a cheap flight, in the cheap seats so no Wifi. I've been playing around with local LLMs on my laptop for a year or so, but it's always been pure novelty. It suddenly dawned on me that I could use Gemma 4 mid-air, and so I pulled out my laptop and asked for any way I could possibly reduce the pain. The Toynbee Maneuver, which I had never in my life heard of, slowly but surely relieved the pressure. Within 10 mins I felt completely fine. It may sound trivial, but without local AI I would have been in blinding pain for probably 90 mins – so it was a rare moment when new technology actually makes a palpable difference to your life. Sharing this here because my wife didn't care and I felt if anyone would appreciate this small win it would be this community. submitted by /u/EntertainerFew2832
      [link] [comments]
      ---|---

    9. 🔗 r/wiesbaden The vendor at the newspaper stand just kind of accepted it rss

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

    10. 🔗 r/Leeds Leeds nail tech recommendations rss

      I've never gotten my nails done before but I wanna try out smth like this as a treat! Any recommendations for a Leeds based nail artist who could do this?

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

    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:

      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:

      Full Changelog : v0.17.1...v0.17.2

    14. 🔗 r/LocalLLaMA kepler-452b. GGUF when? rss

      kepler-452b. GGUF when? | 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/LocalLLaMA It looks like we’ll need to download the new Gemma 4 GGUFs rss

      https://huggingface.co/unsloth/gemma-4-E2B-it-GGUF

      https://huggingface.co/unsloth/gemma-4-26B-A4B-it-GGUF

      by u/danielhanchen:

      We just updated them again in response to:

      1. kv-cache : support attention rotation for heterogeneous iSWA https://github.com/ggml-org/llama.cpp/pull/21513
      2. CUDA: check for buffer overlap before fusing - CRITICAL fixes <unused24> tokens https://github.com/ggml-org/llama.cpp/pull/21566
      3. vocab : add byte token handling to BPE detokenizer for Gemma4 https://github.com/ggml-org/llama.cpp/pull/21488
      4. convert : set "add bos" == True for Gemma 4 https://github.com/ggml-org/llama.cpp/pull/21500
      5. common : add gemma 4 specialized parser https://github.com/ggml-org/llama.cpp/pull/21418
      6. llama-model: read final_logit_softcapping for Gemma 4 https://github.com/ggml-org/llama.cpp/pull/21390
      7. llama: add custom newline split for Gemma 4 https://github.com/ggml-org/llama.cpp/pull/21406

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

    17. 🔗 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]

    18. 🔗 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]

    19. 🔗 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]

    20. 🔗 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]

    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.

generated: April 11, 2026 at 00:12:10