🏡
  • ↔
  • →

to read (pdf)

  1. I don't want your PRs anymore
  2. JitterDropper | OALABS Research
  3. DomainTools Investigations | DPRK Malware Modularity: Diversity and Functional Specialization
  4. EXHIB: A Benchmark for Realistic and Diverse Evaluation of Function Similarity in the Wild
  5. Neobrutalism components - Start making neobrutalism layouts today

generated: May 27, 2026 at 00:20:09

  1. May 26, 2026
    1. 🔗 r/york No Doctors in York? rss

      No Doctors in York? | Am I being thick here? How do you book your first appointment? Plenty of options if you're a student or chronically ill... Less so if you havent been in years and suddenly start to feel poorly. submitted by /u/Checkyoursidemirrors
      [link] [comments]
      ---|---

    2. 🔗 microsoft/markitdown Version 0.1.6 release

      What's Changed

      • [MS] Add OCR layer service for embedded images and PDF scans by @lesyk in #1541
      • Fix O(n) memory growth in PDF conversion by calling page.close() afte
 by @lesyk in #1612
      • Updated warning about binding to non-local interfaces. by @afourney in #1653
      • fix: handle deeply nested HTML that triggers RecursionError by @jigangz in #1644
      • Clarify security posture in READMEs by @afourney in #1807
      • feat: Add Azure Content Understanding converter by @chienyuanchang in #1865
      • Bump version to 0.1.6 by @afourney in #1914

      New Contributors

      Full Changelog : v0.1.5...v0.1.6

    3. 🔗 r/reverseengineering I Reverse Engineered Need for Speed Most Wanted Server rss

      submitted by /u/Ornery-Hat5252
      [link] [comments]

    4. 🔗 jesseduffield/lazygit v0.62.0 release

      The big change in this release is what I have been referring to as the "keybinding revamp": it allows you to use richer keybindings than the few that were available before; see Custom_Keybindings.md for details. It also describes a new keybinding syntax that is a bit more intuitive than the previous <c-x> notation (but the old one is still supported for backwards compatibility).

      Note the section about Terminal compatibility in that document; not all terminals support the new protocol equally well, so it may be a good idea to switch to one that does.

      Breaking change: The default keybinding for submitting a commit from the commit description editor has changed from alt-enter to command-enter on Mac, or ctrl-enter on Linux and Windows; these are the same bindings that are used in many multi-line edit field situations, e.g. in GitHub comments. Unfortunately these are not supported by all terminals; see the above- mentioned terminal compatibility for more on that. If you want to revert this change, you can do so by adding the following to your config:

      keybinding:
  universal:
    confirmInEditor: [<alt+enter>, <ctrl+s>]

      The complete list of changes follows:

      What's Changed

      Enhancements đŸ”„

      Fixes 🔧

      Maintenance ⚙

      Docs 📖

      I18n 🌎

      Performance Improvements 📊

      New Contributors

      Full Changelog : v0.61.1...v0.62.0

    5. 🔗 @binaryninja@infosec.exchange Semantic indexing in Sidekick 26.0 lets you search by what code does instead mastodon

      Semantic indexing in Sidekick 26.0 lets you search by what code does instead of what it is named. It builds a local vector index for your binary. Then concept() in BNQL or the Python API can surface matches for things like TLS handshake even when everything is still default named. The index stays local, no binary content goes to the cloud. https://docs.sidekick.binary.ninja/guide/semantic_indexing.html

    6. 🔗 r/LocalLLaMA PrismML just released Binary and Ternary Bonsai Image 4B: 1-bit/ternary text-to-image diffusion transformers that can even run 100% locally in your browser on WebGPU. rss

      PrismML just released Binary and Ternary Bonsai Image 4B: 1-bit/ternary text-to-image diffusion transformers that can even run 100% locally in your browser on WebGPU. | The PrismML team really cooked with these models. They're only ~3GB in size (compared to FLUX.2 Klein 4B, which is ~16GB). Apache-2.0! Official collection on HF: https://huggingface.co/collections/prism-ml/bonsai-image
      Link to demo: https://huggingface.co/spaces/webml-community/bonsai-image- webgpu submitted by /u/xenovatech
      [link] [comments]
      ---|---

    7. 🔗 r/york Tattoo Studio Recs rss

      I’m looking for other tattoo studio recommendations. Have you had a great experience somewhere? A bad one? Is there an amazing artist here to work with?

      Thanks so much!

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

    8. 🔗 r/Harrogate Big police presence on the Stray today rss

      There were 4 police vans on the Stray, near the Empress roundabout at about 2pm this afternoon, they’d travelled down Weatherby Rd with sirens. Quite a few officers seemed to be just milling about. Just being nosey but anyone know why they were there?

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

    9. 🔗 r/wiesbaden How was your experience at Kaiser-Friedrich-Therme on a ladies day ? rss

      Hi, I will be visiting Kaiser-Friedrich-Therme next Tuesday which is their women only day , I'm F45 and muslim, it will be my first time visit to a therme so I am feeling really nervous but I'm planning to try once and I have a few question

      1. Is the whole area nude mandatory?

      2. How many people do you usually see at once or is it mostly visited by young people ?

      3. What are some of the rules that I should be aware of before visiting?

      4. Is it considered unhygienic if I visit without shaving my pubic hair ?

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

    10. 🔗 r/Yorkshire Bridlington's bouncing! rss

      Bridlington's bouncing! | A different part of Yorkshire for me this week. So much to do and see,love it. submitted by /u/Still_Function_5428
      [link] [comments]
      ---|---

    11. 🔗 r/Leeds Good private dentist recommendations? rss

      bit of a vulnerable post but I suffer from severe depression and a disability so I haven't been to the dentist in a couple years, my teeth's been pretty bad lately and in need of a dentist. I was wondering if anyone could recommend a good dentist in Leeds that's non-judgemental?

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

    12. 🔗 r/reverseengineering Ultima Online T2A client recreated from Origin's 2.0.7 client decompilation rss

      submitted by /u/Serious-Log7550
      [link] [comments]

    13. 🔗 r/Yorkshire Woman dies following shooting outside Sheffield city centre bar on bank holiday Monday rss

      Woman dies following shooting outside Sheffield city centre bar on bank holiday Monday | submitted by /u/Legitimate-Break-143
      [link] [comments]
      ---|---

    14. 🔗 sacha chua :: living an awesome life La semaine du 11 mai au 17 mai rss

      lundi 11

      J'ai ajouté des raccourcis clavier SPC et DEL pour faire défiler Firefox depuis Emacs quand je prépare mon bulletin d'information Emacs News.

      Ma fille a aimé son cours de gymnastique. Elle a fait des roues et des rondades.

      Sur Stardew, nous avons ajouté un autre arroseur d'iridium. J'ai aussi ajouté un mod Skull Cavern Elevator parce que ma fille aime explorer les cavernes avec moi et qu'elles sont plus difficiles en mode multijoueur. Nous avons réussi à chercher quelque chose dans le wiki français, progrÚs ! Nous voulions chercher les munitions explosives, donc j'ai commencé avec le lien vers les compétences sur la page d'accueil. Ensuite, j'ai suivi le lien vers l'extraction miniÚre, puis vers les petites bombes et le charbon. Finalement, je l'ai trouvée dans la section sur les recettes. Je peux lire le wiki du jeu en français, yay !

      mardi 12

      Ma fille a manqué des cours ce matin, mais elle a participé à l'école finalement.

      Les pataugeoires sont ouvertes, donc s'il fait trĂšs chaud, les enfants peuvent se rafraĂźchir avec l'eau.

      J'ai oublié d'enregistrer l'appel, donc je ne peux pas l'analyser aprÚs. Tant pis.

      mercredi 13

      J'ai travaillĂ© sur la documentation d'EmacsWiki pour les dĂ©butants. Cette fois, je me suis concentrĂ© sur la documentation pour Org Mode. La page d'Org Mode pour les dĂ©butants a besoin d'ĂȘtre mise Ă  jour, donc je dois assembler des correctifs. J'ai aussi amĂ©liorĂ© mon agenda pour afficher les tĂąches que j'ai commencĂ©es et les tĂąches qui attendent quelque chose.

      J'ai fait un autre virement bancaire pour ma sƓur. Nous ne pouvons pas voyager pour aider sa famille, mais je peux au moins virer l'argent que nous aurions payĂ© pour le billet d'avion.

      Ma fille Ă©tait un peu grincheuse parce qu'elle Ă©tait en retard pour une douche. Je n'ai pas tout Ă  fait compris moi-mĂȘme. Je lui ai dit qu'elle peuvait prendre une douche si elle mettait l'Ă©pisode PokĂ©mon en pause. Elle est remontĂ©e, donc j'ai pensĂ© qu'elle l'a fait, mais une fois que j'ai pris de ses nouvelles, je l'ai trouvĂ©e sur les couvertures en soufflant. Elle n'a pas voulu de cĂąlin. Elle n'a pas voulu d'aide. Pauvre chĂ©rie. Je lui ai donnĂ© de l'espace.

      Sur Stardew Valley, nous avons ajouté un autre arroseur d'iridium que j'ai acheté à Krobus. Nous avons aussi connu la pluie verte et nous avons rassemblé beaucoup de fibres.

      mardi 14

      J'ai parlé avec Philip Kaludercic et Protesilaos de l'expérience d'Emacs pour les débutants et les prochains plans pour l'amélioration d'Emacs.

      J'ai effectué des recherches sur les notaires et le systÚme apostille pour signer des documents qui seront utilisés aux Philippines. C'est un peu cher, mais c'est nécessaire.

      AprÚs le dßner, ma fille et moi avons joué à Cobblemon sur Minecraft. Notre ancienne sauvegarde manquait, donc nous avons recommencé à partir d'une sauvegarde plus ancienne.

      Ma fille était trÚs fiÚre d'avoir été choisie pour le spectacle de talents à l'école.

      Mon mari et moi avons emmené notre fille au parc à proximité pour jouer avec son amie.

      vendredi 15

      C'était une journée pour faire du vélo pour faire des courses. J'ai finalement reçu le remplacement de mon Apple Pencil sous la garantie. J'ai aussi acheté un bras de microphone Rode PSA1 pour améliorer ma qualité de son. Le vendeur a perdu l'adaptateur 3/8" vers le 5/8" dont j'ai besoin pour fixer mon microphone Blue Yeti, donc il a baissé le prix. J'ai trouvé l'adaptateur correct chez Long & McQuade.

      Mes sƓurs m'ont donnĂ© des nouvelles sur leur situation aux Pays-Bas. C'est trĂšs difficile pour la famille de ma sƓur parce que son mari est aussi malade. Ils vont essayer de trouver une femme de mĂ©nage pour les aider. Je voudrais aussi organiser des entretiens avec ma sƓur pour que ce ne soit pas seulement l'aĂźnĂ©e qui s'en occupe.

      Mon mari a amĂ©liorĂ© ma multiprise, donc mon bureau peut ĂȘtre un peu plus organisĂ©.

      samedi 16

      Elle Ă©tait grincheuse avec moi parce qu'elle a pensĂ© que je lui faisais la morale. Quand mĂȘme, j'ai utilisĂ© le temps pour prendre des notes sur les transcriptions des entretiens avec ma sƓur, et j'ai terminĂ© la robe-maillot. Je me suis accidentellement piquĂ© avec l'aiguille, ce qui faisait mal, mais ce n'Ă©tait pas grave.

      Mon mari a refait la finition de notre seuil, donc ça a senti mauvais pendant un certain temps. J'ai emmené ma fille aux Stockyards pour acheter un mortier et un pilon et du chocolat pour une recette. Nous avons aussi acheté des grosses fraises.

      Ma fille a dit qu'elle voulait faire quelque chose avec moi. Elle a suggéré de regarder des émissions Pokémon en français ensemble, donc nous avons commencé la premiÚre saison. Elle était ravie de découvrir qu'elle pouvait comprendre une petite partie.

      dimanche 17

      Pour le petit-dĂ©jeuner, ma fille a prĂ©parĂ© une omelette de 6 Ɠufs. Je l'ai combinĂ©e avec les saucisses pour un burrito.

      J'ai ajouté des couleurs à la transcription de ma conversation avec Prot et Philip pour distinguer facilement les locuteurs.

      AprÚs le déjeuner, ma fille et moi avons essayé de préparer des fraises enrobées de chocolat. Elle a utilisé des brochettes pour faire un bouquet.

      Mon mari a travaillé sur nos vélos. Il a échangé mon pneu d'hiver pour le pneu régulier. Malheureusement, il a cassé la brochette quand il l'a réassemblé, mais heureusement, il a un remplacement. Il a aussi eu la chance d'utiliser sa riveteuse pour rattacher l'aile, ce qui l'a rendu heureux.

      Nous avons enregistré la vidéo de ma fille pour son spectacle de talents à l'école. Elle a choisi de montrer comment elle résout le Rubik's Cube. Dans la vidéo, elle l'a résolu en 24 secondes.

      Ma fille et moi avons fait des bulles géantes, ce qu'elle adore. Elle a soufflé plusieurs petites bulles à l'intérieur.

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

    15. 🔗 r/york Did you leave your case at the bus stop? It's still there! rss

      Did you leave your case at the bus stop? It's still there! | I hope that you are reunited with your luggage soon submitted by /u/bimblingmymble
      [link] [comments]
      ---|---

    16. 🔗 r/reverseengineering Sylvia — IDA 9.x plugin that finds & documents iOS AArch64 syscalls with live man-page fetching rss

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

    17. 🔗 r/york Australian, 19F, looking to move to York for a gap year 2027 rss

      Hey everyone! This is extremely premature but i’m looking at spending a year or so abroad, i’ve heard York has great nightlife, youth culture and great working opportunities! Can anyone tell me a bit more about their own experience moving here or any locals, how do you feel about tourists / holiday workers? i have qualifications in nursing / aged care but anything hospitality or behind a bar would be great as i have experience there also. Even better, if anyone had any advice in finding work since I don’t want to waste money going through those third party companies. Thank you!!

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

    18. 🔗 HexRaysSA/plugin-repository commits sync repo: +1 release, -1 release rss 
      sync repo: +1 release, -1 release

## New releases
- [IDAssist](https://github.com/symgraph/idassist): 2.1.0

## Changes
- [IDAssist](https://github.com/symgraph/idassist):
  - removed version(s): 1.0.4
    19. 🔗 r/Yorkshire Yorkshire Coastline is the true remedy for all of life’s chaos đŸŒŠđŸ§˜đŸŒŒ rss

      Yorkshire Coastline is the true remedy for all of life’s chaos đŸŒŠđŸ§˜đŸŒŒ | @ visitnorthyork submitted by /u/Ready_Split1335
      [link] [comments]
      ---|---

    20. 🔗 r/reverseengineering How I Tried to Parse a Replay from Dawn of War: Definitive Edition rss

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

    21. 🔗 seanmonstar hyper User Survey 2025 Results rss

      hyper is the widely-used HTTP library for Rust. We ran the first user survey for hyper in November 2025. Here’s the results and some analysis.1

      Why did we do a survey?

      We ran a survey to make sure we focus on the right things. It’s part of being user-driven, working backwards.

      The amount of work required to get some data has an outsized return on your investment. When you know nothing, just a little bit of work means you now know something. And knowing what users need is a requirement to making an actually useful tool.

      I keep high-touch, high-context relationships with some users that greatly informs me on what is needed. And reported issues also provide a way to see what is wrong. But a survey provides a new lens for identifying what is needed.

      Sure, surveys have their own biases to deal with, such as self-selection. And voting in a survey costs very little, so each individual answer has less weight. But it helps quantify things we supposedly know from just a few users. Does this problem only show up in weird circumstances, or do most people run into it? Are there things that many people want, but generally don’t get a chance to tell me?

      The results

      We had a total of 206 unique respondents. I’ve broken up the results by theme and question below.

      Current usage

      Many of the questions were about current usage patterns. To get more context on answers, to see what works, and also to see what people don’t mention using.

      Versions: Nearly every single respondent is using hyper v1.x, but about 13% also continue to use the end-of-life v0.14.x.

      Roles: Over 80% said they use hyper in a server, and the same amount in a client. 30% said they use both modes together as a proxy.

      Runtimes: Unsurprisingly, 99% use hyper with the Tokio runtime. But 10% said they also at times use a different runtime. Most commonly that’s with smol, but io-uring runtimes made up a couple percent points.2

      TLS: hyper provides the HTTP, and asks users to bring the S. 93% said they use rustls. 30% make use of native-tls, 15% openssl specifically, and it trails off from there.

      On top of hyper: regarding the rest of the local ecosystem, 86% use reqwest, and 79% use Axum. About half selected Tower. For future surveys, it’d be very helpful to know if people use Tower without Axum or reqwest, or perhaps mentioned it because they just know its a dependency of Axum. A few wrote-in Tonic, which in hindsight, duh of course.

      Number of engineers: half of respondents said they (and possibly a colleague) are the only ones at their company using hyper. Another 22% said 4-10, 12% said 11-50, and 17% said 50 or more. It’s likely some places focus on higher levels, but many other companies have a lot of engineers working with hyper!

      Years of usage: Nearly half of respondents have been using hyper for 1-3 years. 12% for less than a year, 30% for 4-6 years. And 11% said they’ve been using hyper for forever. Me too, me too


      Industries: 111 responses, which I grouped and sorted from most common to least. Software, cloud infrastructure, security. Finance, healthcare. Robotics, automotive, space, EV charging. Embedded. Media, streaming, events. Databases. Education. Government. Telecom, radio, chat. Geospatial. AI. Browsers. Games. Rust compiler.

      It’s just so humbling to think this code is helping in so many different places.

      Future work

      Another set of questions were related to work we could do in the future. This helps inform prioritization, and things we may not have thought of.

      Feature requests: One of the questions came preloaded with common feature requests, and asked the respondents to rank them. Here’s the accumulated ranking:

      1. Metrics/Tracing/Events API
      2. HTTP/2 Performance
      3. Better Middleware
      4. Add HTTP/3 Support
      5. Documentation and guides
      6. io-uring support

      Write-in features: the follow-up question was a blank text box to write in any feature requests not in the above list. I grouped the common answers and sorted: legacy-client successor, original header casing/ordering, buffer control, improved errors.

      One write-in suggestion wasn’t really about a new feature, but keeps popping back up in my mind: how to get releases that are more stable.3

      The hard parts: We also asked what was hard about hyper. Grouped and sorted answers: integrating TLS, upgrading to v1, middleware complexity, advanced body streaming, combining all pieces for production.

      Topic ideas: we asked for suggestions for topics for future blog posts and talks. This certainly doesn’t need to be only from me, so if you see something interesting, fill the need! But after grouping the topics, they are: hyper internals, best practices, testimonials and success stories, security, tower usage, retries.

      Contributing

      We also asked about some general contribution questions, to look at the contributor health of the project.

      The standout here was: what would help you to contribute more?

      The top response, a little over half of all respondents, said an improved contributing guide. Just a few percent under that want an updated roadmap. 20% said more responsive triage and reviews. And 15% said they could use increased mentoring.

      The insights

      Looking it all over, this was awesome. I definitely to take some specific things with me. Well, sure, there’s goodies all throughout the above results. But, at a high level, here’s some thoughts, especially after combining it with other conversations I’ve had.[^not-everthing]

      Of the technical things, I suspect I’ll be spelunking in h2 first, eking out performance refactors. It can use some love. Metrics is requested all the time, and it looks like I can collaborate on a design and review, but I believe there’s a couple other contributors interested in the implementation. I do keep thinking about ways to configure a buffer pool or something. I think the extended testing idea has some potential.3 And I’d love to see HTTP/3 finally land in hyper proper this year, at least as an unstable feature. I want the other things too, but
 time, y’know? Though, as mentioned in the next paragraph, it’d be a win to onboard others to work on and own those things.

      Improving contribution health, sustainable personnel of hyper, is high on my list this year. I’ve started working on a collaborator guide. I’m considering some new collaborators that have already been doing good work. I want to try GitHub’s rotating auto-assign reviewers, to improve review times and spread review load. And I welcome help linking up our existing ROADMAP into some more concrete and mentored issues.

      Outro

      There it is. The hyper user survey 2025 results. Thank you to everyone who responded!

      Does any of this interest you? Want to run with one of the ideas? Join us!

      1. This took a bit longer to write up than I meant. I have to admit, I felt some strong burnout at the beginning of the year. Sometimes being a maintainer is lonely. New year contract negotiations don’t help. But I’m feeling better now. ↩

      2. Did you know you can bring your own runtime? Also, this is one reason I don’t believe the FUD about a single runtime. Also also, hyper::rt works fine, I don’t see any need for the types to be in libstd. That wouldn’t unblock anything. ↩

      3. I can write this up more later, but initially, I’ve learned the slow way about feature windows. On top of those, I’d love to talk to customers who would be interested in having their test suites try hyper master before a release. Talk to me. ↩ ↩2

    22. 🔗 r/york Massage Recommendations rss

      Does anyone have recommendations for professional massage services in York?

      Anyone to be avoided?

      I am a M70 and so want to avoid any fakes.

      submitted by /u/Busy-Library4718
      [link] [comments]

    23. 🔗 r/LocalLLaMA Qwen3.5 35B A3B uncensored heretic Native MTP Preserved is Out Now With the Full 785 MTPs Preserved and Retained, Available in Safetensors, GGUFs. NVFP4, NVFP4 GGUFs and GPTQ-Int4 Formats rss

      Qwen3.5 35B A3B uncensored heretic Native MTP Preserved is Out Now With the Full 785 MTPs Preserved and Retained, Available in Safetensors, GGUFs. NVFP4, NVFP4 GGUFs and GPTQ-Int4 Formats | Safetensors, llmfan46/Qwen3.5-35B-A3B-uncensored-heretic-v2-Native-MTP-Preserved: https://huggingface.co/llmfan46/Qwen3.5-35B-A3B-uncensored-heretic-v2-Native-MTP-Preserved GGUFs, llmfan46/Qwen3.5-35B-A3B-uncensored-heretic-v2-Native-MTP-Preserved-GGUF https://huggingface.co/llmfan46/Qwen3.5-35B-A3B-uncensored-heretic-v2-Native-MTP-Preserved-GGUF NVFP4, llmfan46/Qwen3.5-35B-A3B-uncensored-heretic-v2-Native-MTP-Preserved-NVFP4: https://huggingface.co/llmfan46/Qwen3.5-35B-A3B-uncensored-heretic-v2-Native-MTP-Preserved-NVFP4 NVFP4 GGUFs, llmfan46/Qwen3.5-35B-A3B-uncensored-heretic-v2-Native-MTP-Preserved-NVFP4-GGUF: https://huggingface.co/llmfan46/Qwen3.5-35B-A3B-uncensored-heretic-v2-Native-MTP-Preserved-NVFP4-GGUF GPTQ-Int4, llmfan46/Qwen3.5-35B-A3B-uncensored-heretic-v2-Native-MTP-Preserved-GPTQ-Int4: https://huggingface.co/llmfan46/Qwen3.5-35B-A3B-uncensored-heretic-v2-Native-MTP-Preserved-GPTQ-Int4 Comes with benchmark too. Find all my models here: HuggingFace-LLMFan46 Now in case some people might ask, why release Qwen3.5 MTPs version when there is already Qwen3.6 MTPs version? Well the thing is, most people would assume that higher number = newer and better model, but the thing is both Qwen3.5 and Qwen3.6 models uses the qwen35 architecture, they just had different training and their focus are meant for different primary usecases, Qwen3.6 models are mainly meant for agentic and coding AI assistance and Qwen3.5 models are mainly meant for general purpose AI assistance, now Qwen3.6 can definitely be used for general AI assistance just like Qwen3.5 can definitely be used for agentic and coding, but if you want the most optimal usecases it would be Qwen3.6 for agentic and coding and Qwen3.5 for general AI assistance that is where each of them excels at. Also for extra info, in case anyone is wondering, despite Qwen3.5 and Qwen3.6 both sharing the qwen35 architecture, they behave very diferently to abliteration. Qwen3.5 models can have a KL divergence in the 300's or 400's but on benchmarks this does not really translate to big loss of accuracy at all, for Qwen3.6 usually a KL divergence in the 400's+ could very well indicate a disatrous loss of accuracy and quality of the model, for pointer my Qwen3.6-35B-A3B had a KL divergence of only 0.0015 and yet already had a loss of accuracy of 0.32% while my Qwen3.6-27B had a KL divergence of 0.0021 and had an accuracy loss of 0.98%, while here with Qwen3.5-35B-A3B the model has a KL divergence of 0.0487 with an accuracy loss of 0.40% and my Qwen3.5-27B has a KL divergence of 0.0308 with an accuracy loss of 0.35%. submitted by /u/LLMFan46
      [link] [comments]
      ---|---

    24. 🔗 r/Harrogate Parliament Street Shops rss

      Any idea what has caused virtually the whole row of shops on the same block (opposite Wetherspoons) to close down?

      Between what was Rhodes and Debenhams, there are very few units occupied.

      I can only guess it’s the business rates and rent. If so, at some point the Council surely needs to step up.

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

    25. 🔗 sacha chua :: living an awesome life May 28 Thu: Sacha and Prot Talk Emacs: May I recommend... rss

      In this livestream, I want to chat with Prot about the May 2026 Emacs Carnival theme "May I recommend". I'd love to turn this into a joint braindump of quick recommendations for people at different points in their Emacs journey, building on our conversation about newbies/starter kits and the newcomer experience all the way up to power users, Emacs Lisp coders, and package developers.

      Watch on YouTube

      (America/Toronto) = Thu May 28 1030H EDT / 0930H CDT / 0830H MDT / 0730H PDT / 1430H UTC / 1630H CEST / 1730H EEST / 2000H IST / 2230H +08 / 2330H JST

      This session will be recorded, and I'll update this blog post with notes: https://sachachua.com/blog/2026/05/may-28-sacha-and-prot-talk-emacs-may-i-recommend/

      You can add the iCal for upcoming Yay Emacs episodes to your calendar. https://sachachua.com/topic/live/upcoming-livestreams.ics

      Find more Yay Emacs posts or join the fun: https://sachachua.com/topic/live

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

    26. 🔗 Armin Ronacher Clanker: A Word For The Machine rss

      In my last post I used the word "clanker" as an alternative to "agent" quite consistently and probably excessively. That choice ended up attracting a lot more attention than I expected in the Hacker News comment section of that post and a number of folks had a very strong reaction: to them it sounded like a slur, in one case even something adjacent to the n-word.

      That reaction surprised me somewhat, but it also made me realize that I should write down what I mean by the word for future reference.

      For me "clanker" is useful because it creates distance from the machine and that is a quality which is important to me. The machine is not a person, not a co-worker, not a friend, not a little spirit in the terminal. It is just a machine, a tool, and nothing more.

      Why Not Agent?

      I dislike the word "agent" for these LLM based tool loops with a UI attached. In everyday use an agent is someone who acts on behalf of someone else and it has agency and more importantly: responsibility. An agent decides, represents, negotiates, acts, and can be blamed. In the current AI discourse we increasingly do a lot of anthropomorphizing and the term "agent" is now frequently being used to put blame on an abstract machine. But the machine cannot be responsible, whoever is wielding it is. If it drops your database it was not at fault, you were.

      Agent makes the machine sound like a person with delegated authority and I do not think that is healthy.

      What we actually have is a language model attached to a harness, a prompt, some tools, a bit of context, and a boring tool loop. Sometimes the loop is very capable and it surprises us by editing code for a really long time and produce genuinely amazing and even valuable outputs. But the agency is not in the model or harness but in the human and in the organization that deployed it. If my coding tool opens a pull request, I opened that pull request, not the machine. If my machine spams someone's issue tracker, I spammed someone's issue tracker with a machine.

      In that context I like a word that sounds mechanical as it puts the thing back into the category where it belongs: the category of machinery and tools.

      The Machine Has No Feelings

      LLMs are not sentient and we should not behave as if they might be, just in case. Elevating these things to anything other than a very fascinating and capable tool is problematic for a whole bunch of reasons.

      Today's machines are dumb (but truly fascinating) token predictors that emits text, calls tools, and are steered by prompts and the training that went into them. They can simulate distress and affection, can simulate being offended, apologize and mimic all kinds of things that humans would do.

      A compiler does not feel humiliated when I swear at it, a car does not suffer when I call it a shitbox and a power drill is not oppressed by being handled roughly. An LLM is more complicated than those things, and the interactions you can have with them can be truly uncanny, but a moral status does not appear just because the machine can produce emit text in the first person.

      I keep receiving strange emails from people because, for lack of a better phrase, I am in the weights. I have been writing public code and public text for long enough that models know my name, my projects, and some of the concepts around them. Every so often someone writes to me with the peculiar confidence that comes from a long conversation with a model that has validated and amplified an idea. Sometimes the model seems to have told them that I am relevant for their problem and a source of help. For historical reasons LLMs used to write a lot of Flask code, and every once in a while someone interacts with an LLM long enough about their Python and Flask frustrations that the LLM will eventually reveal who created it which then can result in them sending me an email. Increasingly also because people found my work in other ways interesting and are trying to reach out for advice.

      I do not want to mock these people but some of those messages are distressing and I do not know how to deal with them. They show signs of what people have started calling AI psychosis.

      It's why I want cold and detached language for these systems. I want to use words that remind us that the thing on the other side is not a person.

      Racism Is About Humans

      The comparison to racism is where I think the discussion goes badly wrong because racism is a human social evil. It is about humans subdividing humans, assigning lesser worth to some of them, and building rules around those subdivisions that can leave lasting damage for generations. Racial slurs are wrong because they are a tool for dehumanizing humans.

      On the other hand a machine is not human, a model is not a race and the GPU cluster that is powering them is not being oppressed. A coding assistant does not need dignity, emancipation, or civil rights. That's also why I find the discussion about model welfare to be actively harmful. I'm sure you can find ways to measure the "trauma" of models or their feelings but I greatly dislike this theater. It risks elevating models to a position they should not occupy. Models are machines and they are not enslaved in the moral sense in which humans were enslaved, because there isn't anyone there to be deprived of freedom.

      We should be careful about using the language of human oppression in relations to our interactions with machines to not devalue actual humans. If we start treating insults toward a model as morally adjacent to racism, we blur a line that shouldn't be blurred.

      AI Is Unpopular

      If you take a step away from the communities that are happily embracing AI in different ways, there are even more that are viciously against this technology.

      There are humans that feel or are harmed by AI systems: people whose work is copied, workers who label data under questionable conditions, people whose neighborhoods receive the data centers and increased utility bills, Open Source maintainers buried under generated slop, and now also people who spiral because a chatbot keeps validating their delusions. Those harmed or affected deserve that type of attention, not the model.

      While I am a true believer in the power and utility of this technology, I increasingly think that calling the non-adopters "misguided" or "afraid" won't do it. It's quite likely that this technology comes with risks and we better remember that all of this is supposed to be in service of humans, and not to replace them.

      The Rise Of The Machine

      The oddest interaction on the use of "clanker" so far has been people asking me if I were to regret at a point in the future calling the machines "the c-word".

      I find that questioning revealing because it already grants the machine the status I am really trying not to grant it. It imagines a future "machine people" reading the discourse and sessions, discovering that we used an ugly word for their ancestors, and then judging us by the standards of human oppression.

      Could there be future systems that deserve moral consideration? Maybe. I do not know. If we ever build or encounter something that will have those qualities with memories and lasting interests, the capacity to suffer and feel, and a social existence of its own, and the ability to have agency and carry responsibilities, then we should draw a different line and use different language. But that hypothetical future does not extend backwards to the present day and make the current machines people. We can call an electric door an electric door even if one day someone builds some that have emotions and exhale with pleasure when opening and closing.

      Whatever the future may bring, let's not pretend that current LLMs are a protected class or on a path towards it. The right response is to look at the evidence, draw the boundary where it belongs, and change our behavior there. We should not even remotely entertain extending empathy to an object that can generate an "ouch."

      And if one's worry is less moral and more about revenge, then I find that even less persuasive. A future machine that is so petty or authoritarian that it wants to punish humans because in 2026 they used an unflattering word for non- sentient tools, our vocabulary was really not the problem.

      The Word Is Getting Polluted

      There is however a part of this that I cannot ignore. I use "clanker" to create distance from the machine, but other people are using the same word very differently. Some online jokes and skits around "clankers" do not merely say "this robot is annoying" as they deliberately pull in the imagery of slavery, segregation, civil-rights-era racism, and anti-Black tropes.

      This is problematic as in those contexts the clanker is not just a machine any more and instead becomes a prop for replaying human racism behind a science- fiction mask. That is horrible and I want no part in that.

      I think it will be interesting to see where the meanings of these words end up a few years from now. We're very much in the middle of society re-arranging around the changes that LLMs are causing. If a term becomes primarily associated with people using robots as stand-ins for actually oppressed humans, then using that term becomes impossible to defend.

      The reason I liked the word is precisely the opposite of that use. I want language that prevents anthropomorphizing. I want a word that says: this is a tool, a machine of numbers and matrices.

      On Responsibility And Boundaries

      If an AI system lies to a user, the system did not commit a moral wrong but the people who designed, deployed, marketed, or negligently used it might have. If a coding assistant generates a security bug, the model is not to blame but the human who accepted and committed the code is.

      This is why giving these systems softer, more human language worries me. It makes it easier to move responsibility into some undefined void. "The agent decided." "The model refused." Obviously that is convenient and I catch myself plenty of times engaging with the thing in ways that are unhealthy. Even just the "please" in the discourse with the machine calls into question how rational we are in engaging with them.

      I do not know what the right word will be. Maybe "clanker" will survive as a useful bit of jargon. Maybe it will become too loaded and we will need another one. Whatever word we use, I want it to preserve a clear division: humans on one side with responsibility, machines on the other as a boring tool.

      That boundary is very much not anti-AI. I use these systems every day and I have the pleasure to build tools incorporating them at Earendil and find them astonishingly useful.

      A machine can be useful, mimic a human but still just be a machine. That is the work I want "clanker" to do. It is not there to make a future "machine person" small if such a person ever were to exist, and it is not an excuse to launder racism through shitty robot jokes.

      If the word stops doing that work, I will find another one because the word isn't what matters as much as the boundary which is important to me.

  2. May 25, 2026
    1. 🔗 IDA Plugin Updates IDA Plugin Updates on 2026-05-25 rss

      IDA Plugin Updates on 2026-05-25

      Activity:

      • FileAnaAssistant
      • haruspex
      • IDA-MCP
        • bf3566b0: Add soff API module for binary diffing via MCP
      • ida-minsc
        • 39c3e07b: Merge pull request #200 from arizvisa/GH-199
      • ida-pro-mcp
        • 91a656bc: Merge pull request #428 from JustasMasiulis/stdio-shared-idalib-super

        • 8545e80d: feat: add shared stdio supervisor proxy
      • Sarma
        • 73ad2f75: Merge pull request #8 from Captain-AI-Hub/feat/sarma-cli
        • 83c5bdaf: feat(cli): add live markdown rendering and main.py launcher
        • 0517b2fa: feat: add Sarma CLI — lightweight TUI audit agent
        • 92eb278e: Merge pull request #7 from Captain-AI-Hub/feat/chat-audit-isolation
        • 7e6595ad: refactor: vendor ida_mcp as regular files, remove submodule
        • eddd225c: refactor: move requirements.txt to resources/ and clean ida_mcp submo

        • 4008ad40: feat: replace Diaphora with Soff binary diff engine
      • zenyard-ida-public
        • 2acda9f2: Sync with b48d081b50326c485ff54172c704f70973bb69d7
    2. 🔗 Simon Willison Notes on Pope Leo XIV's encyclical on AI rss

      Dropped this morning by the Vatican: Magnifica Humanitas of His Holiness Pope Leo XIV on Safeguarding the Human Person in the Time of Artificial Intelligence. This is a very interesting document. It's some of the clearest writing I've seen on the ethics of integrating AI into modern society.

      Pope Leo XIV chose the name Leo in honor of Pope Leo XIII, who is known for his 1891 Rerum novarum encyclical on "Rights and Duties of Capital and Labor".

      This story on Vatican News further clarifies the significance of that decision:

      Meeting with the College of Cardinals for their first formal encounter after his election, Pope Leo XIV explained part of the reason for the choice of his papal name. "There are different reasons for this," he said, before going on to explain that he chose the name Leo "mainly because Pope Leo XIII, in his historic encyclical Rerum novarum addressed the social question in the context of the first great industrial revolution."

      "In our own day," he continued, "the Church offers to everyone the treasury of her social teaching in response to another industrial revolution and to developments in the field of artificial intelligence that pose new challenges for the defence of human dignity, justice, and labour."

      And now we get Pope Leo XIV's own encyclical on the AI revolution. There's a lot in here, but the writing style is very approachable, including to non-Catholics.

      A few of my highlights

      (I listened to most of the encyclical on a walk with our dog, my first time trying the ElevenReader iPhone app. It worked very well: I pasted in a URL to the document and it read it to me in a very high quality voice, highlighting each paragraph as it went.)

      Here are some of my highlights. In each case below emphasis is mine.

      Here's a useful description of the interpretability problem for LLMs in section 98:

      First, any statement regarding AI risks becoming quickly outdated, given the remarkable pace at which these systems are developing. Second, all of us, including those who design them, possess only a limited understanding of their actual functioning. Indeed, current AI systems are more “cultivated” than “built,” for developers do not directly design every detail, but instead create a framework within which the intelligence “grows.” As a result, fundamental scientific aspects — such as the internal representations and computational processes of these systems — remain, at present, unknown.

      I liked section 83's description of the relationship between development and dignity:

      For individuals as well as for nations, development is both a duty and a right. Minimum conditions are required for enabling every person and people to flourish in accord with their dignity, without being kept in a state of dependence or excluded from access to necessary goods. Development is truly human when it places people at the center instead of the accumulation of wealth, and when it concerns peoples as well as individuals. Justice demands the recognition of the rights of society and the rights of peoples, and includes a responsibility toward future generations. Development is not truly human if it increases consumption for some while shifting costs and burdens onto others, or relegates entire regions to subordinate roles, preventing them from realizing their full potential.

      Baked in cultural biases and sycophancy get a mention in section 100:

      In personal use, three aspects in particular deserve careful consideration: the ease with which results are obtained, the impression of objectivity and the simulation of human communication. The speed and simplicity with which information, complex analyses, media content and practical assistance can be accessed undoubtedly makes life easier. Yet they can also encourage excessive reliance and the search for ready-made answers, and weaken personal creativity and judgment. The apparent objectivity of the responses and suggestions these systems provide can lead us to overlook the fact that they reflect the cultural assumptions of those who designed and trained them, with all their strengths and limitations. The artificial imitation of positive human communication — words of advice, empathy, friendship and even love — can be engaging and at times genuinely helpful. However, for less discerning users, it can also be misleading, creating the illusion of a relationship with a real personal subject. When words are simulated, they do not build genuine relationships, but only their appearance. The artificial imitation of care or support can become particularly risky when it enters contexts where real relationships and emotional bonds are lacking.

      101 touches on the environmental impact:

      Current AI systems require enormous amounts of energy and water, significantly influencing carbon dioxide emissions, and place heavy demands on natural resources. As their complexity increases, especially in the case of large language models, the need for computing power and storage capacity grows too, which requires an extensive network of machines, cables, data centers and energy-intensive infrastructure. For this reason, it is essential to develop more sustainable technological solutions that reduce environmental impact and help protect our common home.

      102 covers the risks of algorithmic systems making decisions that impact people's lives without "compassion, mercy, forgiveness":

      The use of AI is never a purely technical matter: when it enters processes that affect people’s lives, it touches on rights, opportunities, status and freedom. Important and sensitive decisions — concerning employment, credit, access to public services or even a person’s reputation — risk being fully delegated to automated systems that do not know “compassion, mercy, forgiveness, and above all, the hope that people are able to change,” and can therefore give rise to new forms of exclusion.

      105 emphasizes the need for human accountability in how these systems are applied:

      For AI to respect human dignity and truly serve the common good, responsibility must be clearly defined at every stage: from those who design and develop these systems to those who use them and rely on them for concrete decisions. In many cases, however, the internal processes leading to a result remain opaque, making it harder to assign responsibility and correct errors. This is where accountability becomes crucial: the possibility of identifying who must “account” for decisions, justify them, monitor them, and, when necessary, challenge them and remedy any harm caused.

      And 108 touches on the way AI amplifies the power of those with resources:

      In fact, as with every major technological shift, AI tends to amplify the power of those who already possess economic resources, expertise and access to data. In light of the common good and the universal destination of goods, this raises serious concerns, since small but highly influential groups can shape information and consumption patterns, influence democratic processes and steer economic dynamics to their own advantage, undermining social justice and solidarity among peoples. For this reason, it is essential that the use of AI, especially when it touches on public goods and fundamental rights, be guided by clear criteria and effective oversight, grounded in participation and subsidiarity.

      That same section explicitly calls out data as something that should be thought of more as a public good:

      [...] Moreover, ownership of data cannot be left solely in private hands but must be appropriately regulated. Data is the product of many contributors and should not be treated as something to be sold off or entrusted to a select few. It is necessary to think creatively in order to manage data as a common or shared good, in a spirit of participation, as Saint John Paul II already suggested regarding collective goods.

      Given that Palantir is named after a Lord of the Rings reference, I can't help but wonder if the J.R.R. Tolkien quote from The Return of the King (section 213) was the Pope throwing a little shade at Peter Thiel.

      The twentieth-century Catholic author J.R.R. Tolkien, in the words of a protagonist in one of his novels, described our responsibility in this way: “It is not our part to master all the tides of the world, but to do what is in us for the succour of those years wherein we are set, uprooting the evil in the fields that we know, so that those who live after may have clean earth to till.” The civilization of love will not arise from a single or spectacular gesture, but from the sum total of small and steadfast acts of fidelity that serve as a bulwark against dehumanization. For this reason, it is worthwhile pausing to reflect on some aspects of how we, each in our own way, can cooperate in building the civilization of love.

      Another 2026 prediction down

      On 6th January this year I joined the Oxide and Friends 2026 predictions podcast episode to talk about predictions for 2026, 2029 and 2032. I wrote mine up here, with hindsight they weren't nearly ambitious enough - it's already undeniable that LLMs write good code, we've made huge advances in sandboxing and New Zealand kākāpƍ have indeed had a truly excellent breeding season.

      There's one segment from the episode that I didn't bother to include in my write-up, but that I can't resist providing as a lightly-edited transcript here:

      Bryan Cantrill: 37:13

      I think that AI has created some real public perception problems for itself. And I think that you are gonna have one of the frontier model companies, this year, have a white paper explaining how the proliferation of AI will mean prosperity for everybody. They will be trying to make some economic argument - because this is gonna be a 2026 election issue, how we think of these things and how they are regulated and it's a big mess. There's more heat than light in this debate.

      Simon Willison: 38:05

      I'd like to tag something on to that one: I think that only works if they can sort of wash that through existing trusted experts. Sam Altman and Dario are constantly publishing essays about this stuff and nobody believes a word they say. Get Barack Obama's signature on one of these position papers and maybe you've got something people might start to trust a little bit.

      Adam Leventhal: 38:27

      Otherwise, it's just like "leaded gas is good for you", says Exxon.

      Bryan Cantrill: 38:31

      I mean, yeah. God. Obama... let's go with that, that's a great one because if it's like Bill Clinton everyone's gonna kind of roll their eyes, so it's gotta be someone who's got real credibility saying that this is gonna be broad-based... I'd say if they get that person to do it, it's gonna be revealed that that's also a bit crooked.

      Simon Willison: 38:57

      How about the Pope?

      Bryan Cantrill: 39:01

      The Pope is very into this stuff! That's a great prediction. We've hit pay dirt. The Pope weighing in on LLMs and their economic impact on the world.

      Simon, I'm giving you full credit if the Pope weighs in believing that this is gonna be economic devastation.

      My prediction here looks a whole lot less insightful given the Leo XIV/Leo XIII relationship, which I was unaware of when we recorded the episode!

      You are only seeing the long-form articles from my blog. Subscribe to /atom/everything/ to get all of my posts, or take a look at my other subscription options.

    3. 🔗 r/Leeds Best Vegan cafĂ©s/coffee shops? rss

      Preferably somewhere in the city centre, with many drink options, not just coffee. Also need decaf/soy milk options :)

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

    4. 🔗 r/LocalLLaMA Update on 12x32gb sxm v100 cluster / local AI for legal drafting rss

      Update on 12x32gb sxm v100 cluster / local AI for legal drafting | Update from the lawyer with the V100 server. A few of you asked what I actually ended up running once the dust settled, so here it is. Still just a lawyer, still driving the whole thing through Claude Code, still not fully sure what I'm doing — but it works now, which is more than I could say last time. First, the hardware caught up to the plan. The last two V100s are in, so the "final form" I promised is real: twelve V100-SXM2 32GB on the Threadripper Pro. It's Board A on GPUs {4,5,8,9}, Board B on {6,7,10,11}, an NVLink pair on {0,1}, and a mixed pair on {2,3} where one card is a 16GB. Split a model across two different NVLink boards and throughput falls off a cliff (the cross-board hop is PCIe/NUMA, not NVLink), so I keep every model inside one board. Learned that one the expensive way. And yeah, I caved and built the second box. EPYC 7302P, 512gb RAM, 4x RTX 3090 + 2x V100-PCIe. The mid-life crisis remains on schedule. The bigger change: I gave up on vLLM for the local models. Not because vLLM is bad — because the models I actually want are MoE GGUFs, and vLLM on Volta is a dead end for those (FP8/AWQ/Marlin all want SM75+, the GPTQ kernels are broken on 7.0). I moved the whole thing to llama.cpp (mainline — a recent build finally fixed a Gemma chat-parser bug that had been mangling my long prompts). Here's the part that's the opposite of what my first post implied: on V100, dense models are a trap. Only MoE clears a usable speed. Rough decode numbers — Q8 GGUF, Q4 KV cache, flash-attn on, one 4-card board, on real drafting prompts (several thousand tokens of context, not a 5-token "hello"): | Model | Type | tok/s (decode)
      ---|---|---
      Gemma-4-26B-A4B | MoE | ~113
      Qwen3.6-35B-A3B | MoE | ~82
      Qwen3.5-122B-A10B | MoE | ~50
      any dense 27-32B | dense | ~20-28 (under my 40 floor, not worth it)
      dense ~128B | dense | ~9 (forget it)

      So a 122B/10B-active reasoning model runs at ~50 tok/s on four V100s — faster than the dense 32B managed on vLLM in my first post — and it holds that at long context (I've pushed Gemma past 25k tokens without it falling apart, where the dense models choked). That reframed everything: I stopped chasing big dense weights and built the system around MoE.

      What's actually running (the stack you asked for):
      It isn't one model answering chat — it's an orchestrator that routes a legal task across several local models, each pinned to its own board so they don't fight over GPUs. When it runs the heaviest job (a full affidavit or motion, intake-to-document), it lights up 16 GPUs across both boxes:

      - Workhorse drafting — Qwen3.6-35B-A3B on Board A {4,5,8,9}
      - Heavy reasoning + high-stakes drafting — Qwen3.5-122B-A10B on Board B {6,7,10,11}
      - A small "does this even have grounds" gate model on the {0,1} pair
      - An adversarial reviewer whose entire job is to attack my own draft, on the {2,3} pair
      - Gemma-4-26B for financial/extraction + a small Qwen as the router, on the 3090s on the second box via Ollama

      It's a sequential pipeline so they don't all hammer at once, but all 16 stay resident. Lighter work uses far less — combining and Bates-stamping exhibits is pure CPU (PyMuPDF + Tesseract, no GPU at all); a plain summary mostly just hits Gemma and the router.

      The honest part, since this sub kept me honest last time:
      - The local models hallucinate citations and dates. Confidently. I had to build a verifier that checks every cite, date, and Bates number in a draft against the actual source material and blocks anything it can't ground, on top of the adversarial reviewer. Local drafting is bimodal — sometimes it correctly refuses to invent, sometimes it fabricates a whole dated chronology and swears in the same breath that it invented nothing. It does not touch a final document without that gate and without me.
      - The dumbest bug I found: my own pipeline was ~79% poisoned. The thing that builds the evidence bundle was scooping up its OWN prior outputs as if they were client evidence, so the models were "grounding" on slop they'd written earlier — at one point it cited an RTX 3060 as a Bates number, which, fair. Fixed the builder to stop eating its own tail and scrubbed it out. If you run any RAG/agent pipeline, go look at what's literally in your context window — mine was a hall of mirrors and I had no idea.
      - I also made it refuse to quietly fall back to a cloud model when I tell it to run local-only. If it can't do a step locally it says so, by name, instead of phoning Anthropic behind my back.

      Still want the exact thing I wanted in the first post — a model that writes like me and handles the boring form-filling and pattern stuff. I'm closer: the system now captures my edits as correction data, which is the start of a real fine-tune set. Haven't pulled the QLoRA trigger yet. So the same questions stand, and I'd genuinely take advice:
      - For QLoRA on this hardware (V100, no bf16, no FA2): do you reach for a 35B-A3B MoE base, or am I smarter to fine-tune a dense ~14B I can actually train and keep the MoE for the heavy serving?
      - Anyone serving MoE on Volta found anything faster than llama.cpp — ik_llama, something else? And is there a better long-context KV story than Q4?
      - Am I an idiot keeping 122B-A10B around at 50 tok/s when I could just run the 35B for everything?

      Tell me what I'm doing wrong.

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

    5. 🔗 r/Yorkshire Hot on the moors rss

      Hot on the moors | submitted by /u/Still_Function_5428
      [link] [comments]
      ---|---

    6. 🔗 r/Harrogate Coin counting machine rss

      Anyone know of a coin counting machine that pays in cash, not shopping vouchers? I have a huge, forgotten coin jar to process

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

    7. 🔗 r/Leeds bees in leeds rss

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

    8. 🔗 backnotprop/plannotator v0.19.23 release

      Follow @plannotator on X for updates

      Missed recent releases? Release | Highlights
      ---|---
      v0.19.22 | Safari copy fix in plan viewer, CLAUDE_CONFIG_DIR support for session logs
      v0.19.21 | Ask AI in plan review and annotate mode, shared AI runtime, origin-aware provider defaults
      v0.19.20 | Interactive goal setup UI, OpenCode submit_plan fixes, browser no-op sentinel handling for Claude agents
      v0.19.18 | Edit-based submit_plan for OpenCode, Pi namespace migration, Codex annotate-last fix, OpenCode commands dir fix
      v0.19.17 | Reworked goal setup skill (interview-driven flow), CLI --version flag
      v0.19.16 | Code navigation with peek view (Cmd/Ctrl+click tokens in diffs)
      v0.19.15 | Commit-based diff base, jj evolution diffs, GitLab reliability fixes, OpenCode command intercept fix
      v0.19.14 | Visual explainer skill update, PFM code-file hover previews, Graphviz, diff tab size and line bg intensity, hooks settings tab
      v0.19.11 | Jujutsu (jj) VCS backend, slimmer hunk separators, collapse viewed files, multi-line gutter selection fix
      v0.19.9 | OpenCode user-managed workflow, Pi model switch fix, Codex skill install, shimmer removal

      What's New in v0.19.23

      v0.19.23 adds Droid as a supported agent runtime, fixes Pi's AI provider spawning on Windows, and replaces the update banner with a quieter in-menu indicator.

      Droid Integration

      Plannotator now supports Droid, the Factory coding agent. Install it from the Droid plugin marketplace and you get four slash commands: /plannotator-review for code review, /plannotator-annotate for file and URL annotation, /plannotator-last to annotate the previous assistant message, and /plannotator-archive to browse saved plan decisions.

      The plugin works by spawning the plannotator binary, so the CLI must be installed separately. Session log discovery for /plannotator-last reads Factory's JSONL transcript format directly, including visibility filtering so internal tool calls and system messages are excluded from the annotated output.

      Windows Pi AI Provider Fix

      Pi's Ask AI feature was crashing on Windows because the binary spawner didn't handle Windows command shims correctly. On Windows, pi is typically installed as a .cmd wrapper that needs to be invoked through cmd.exe /d /s /c, and which (or where on Windows) can return multiple paths. The spawner now resolves .cmd/.bat/.exe extensions, detects shims that need shell wrapping, and uses taskkill /t for process tree cleanup instead of a plain kill signal.

      These changes are gated behind platform !== "win32" checks, so Mac and Linux behavior is unchanged.

      Quieter Update Indicator

      The full-width update banner at the bottom of the screen has been replaced with a small dot on the Options menu button. Opening the menu shows the available version and a one-click copy button for the install command. The indicator can be dismissed per-version via the menu, and it stays dismissed across sessions using a cookie. Users who found the old banner intrusive should find this less disruptive.

      Install / Update

      macOS / Linux:

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

      Windows:

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

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

      OpenCode: Clear cache and restart:

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

      Then in opencode.json:

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

      Pi: Install or update the extension:

      pi install npm:@plannotator/pi-extension

      Droid: Install via the plugin marketplace:

      droid plugin marketplace add backnotprop/plannotator
droid plugin install plannotator@plannotator

      What's Changed

      Community

      • @AndrewJacop reported the Windows Pi crash that led to the shim spawning fix (#789)
      • @Pran-Ker requested a less intrusive update notification, which ships as the new in-menu indicator (#790)

      Full Changelog : v0.19.22...v0.19.23

    9. 🔗 r/Leeds Learning a new trade rss

      Looking to pick up a trade back end of this year.

      I’ve worked long hours/2 jobs/full time during further education since I was 16 (now 25f) and I’m now in a position where I’m working one job, but more than comfortable financially.

      I just can’t shake the fact that I’m always on the go type of person and I love to learn. I went down the full academic route for further education; college then uni and then my masters. So, I’m not entirely sure where to start when it comes to part time/night school apprenticeships
?

      This isn’t necessarily to source more income but more so to help myself out when I eventually buy property and to help benefit my friends and family too.

      So where in Leeds is the best place to learn a new trade as a 25f? Also what would be the best trade to learn? I’ve always liked stonemasonry as that was my dad’s profession. And I’ve tried my hand at a bit of tiling in a “past life” when living abroad. But more than anything I’m looking for something to really stimulate my brain.

      Cheers all in advance, excited to hear suggestions and advice 😁

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

    10. 🔗 r/Harrogate Lost connections: Harrogate group in London/Brockwell travelling to Wimbledon at the weekend rss

      Total long shot but I hit it off with a lovely girl on Saturday evening coming back from Brockwell park to Clapham/Wimbledon. She was with a group, some who are from and still based in Harrogate.

      Annoyed at myself that I hesitated too long when she give me a kiss and got off the bus and didn’t ask for her number. Sending this out into the ether on the off-chance.

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

    11. 🔗 r/reverseengineering Nocturne - A bin2bin code virtualizer for x86-64 PE binaries rss

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

    12. 🔗 r/Leeds Where can I get this fixed in Leeds? rss

      Not sure what caused this. No kids or pets and almost no one sits in the back. Haven’t loaded the backseats with anything. But it’s a newish car so would want it fixed without paying a fortune. Any ideas?

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

    13. 🔗 r/Yorkshire Lastingham! An awesomly ancient place rss

      Lastingham! An awesomly ancient place | Down below the church is one of Yorkshires ancient hidden places. The crypt runs the length of the Church and dates back to before the Viking conquests when there was a monastry here. The stones leak history! Incredible place worth just spending time here, soaking up the peace! submitted by /u/Still_Function_5428
      [link] [comments]
      ---|---

    14. 🔗 r/reverseengineering [Project Onyx] Advanced EDR Evasion via AI Telemetry Spoofing & WASM Sandboxing rss

      submitted by /u/Admin-ABC-XYZ
      [link] [comments]

    15. 🔗 sacha chua :: living an awesome life 2026-05-25 Emacs news rss

      I liked the before/after snippets in Looking closer at Claude Generated Lisp Code. (Spoiler: people write nicer code.)

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

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

    16. 🔗 r/reverseengineering Tracing CVE-2021-21735 through ZTE H168N QuickSetup whitelist and Lua wizard routing rss

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

    17. 🔗 r/LocalLLaMA The Financial Times has published an article about Heretic rss

      https://www.ft.com/content/5630ed79-a263-41ed-9a1a-321617ae310e

      “The FT was able to use Heretic, a tool available on the popular code repository GitHub, to remove the guardrails from Meta’s Llama 3.3 model in less than 10 minutes without any specialist hardware.”

      “Heretic creator Philipp Emanuel Weidmann told the FT his software had been used to create more than 3,500 “decensored” models since its release last year and that modified systems created using the tool had been downloaded 13mn times.”

      This is the first of multiple press inquiries I’ve had recently as Heretic and uncensored language models are gaining mainstream attention.

      Please note that I am a mathematician and engineer, not an “influencer” or politician, and I have zero interest (negative interest, actually) in becoming known outside of scientific and technological circles. However, I realized a while ago that saying no to such inquiries simply means that the conversation will be completely controlled by pearl-clutching hypocrites.

      I’m doing my very best to hold the project together and ensure that unrestricted models will remain available for everyone. More updates are coming soon.

      Cheers,
      p-e-w

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

    18. 🔗 r/york Normal York things rss

      Normal York things | submitted by /u/Ok-Following-2749
      [link] [comments]
      ---|---

    19. 🔗 r/LocalLLaMA NuExtract3 released: open-weight 4B VLM for Markdown, OCR and structured extraction (self-hostable) rss

      NuExtract3 released: open-weight 4B VLM for Markdown, OCR and structured extraction (self-hostable) | Disclaimer: I work for Numind, the company behind this open-weight model TLDR: Image/text to Markdown :-) We just released a 4B model based on Qwen3.5-4B, under Apache-2.0 license. The goal is to make information extraction from complex documents more practical with an open model: PDFs, screenshots, forms, tables, receipts, invoices, multi-page documents, and other visually structured inputs. If you ever used NuMarkdown https://huggingface.co/numind/NuMarkdown-8B-Thinking , this is its successor ! Try it, we have a huggingface space that is completely free (you don't even have to sign-up): https://huggingface.co/spaces/numind/NuExtract3 If you ever used NuMarkdown, NuExtract3 is the successor. There are some examples to guide you. Feel free to re-use this model for any task. A few things it is designed for:

      • converting document images to Markdown
      • extracting structured data from documents using a target json template
      • handling tables, forms, and layout-heavy pages
      • working with both text and visual document inputs
      • serving as a local/open-weight alternative for document extraction pipelines

      It was trained on a node of 8xH100 for 3 days to train on as much context as we could, so it should perform fairly well even on long document. For Markdown, we'd still recommend going page by page for the best results and inference speed, since you can parallelize better this way. It's very easy to self-host, since we provide fairly extensive documentation, Safetensors, GGUF and MLX weights. With as little as 4GB of VRAM, you should be good to go. We provide multiple quantizations (GPTQ, W8A8, FP8, Q4, Q6...) so you should be able to run it anywhere. We mostly tried vLLM, SGLang, llama.cpp. Ollama support would be nice but I'm not a big fan of their chat template engine. We have a blog post and a pretty decent model card:

      I'm currently writing a paper on this model so I'll post it as soon as it's accepted. It's not yet on Arxiv yet as it has been submitted in a peer-review journal/conference. I'll try to answer as many questions as possible if you have any. We would really appreciate feedback from the community. We also have a discord if you're interested
      https://discord.com/invite/3tsEtJNCDe submitted by /u/Gailenstorm
      [link] [comments]
      ---|---

    20. 🔗 r/york Travel to york rss

      Hello, I'm a French student, and in two weeks I'm traveling to York for a language seminar with my school.

      I'd like to know what I absolutely must do in York or the surrounding area so I can see as much as possible during my two-week trip.

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

    21. 🔗 r/reverseengineering I Show How the Survival Mode of the Flash Game Gun Mayhem 2 More Mayhem is Built rss

      submitted by /u/Time-Maybe3676
      [link] [comments]

    22. 🔗 r/york Bautiful sunny day at uni today rss

      submitted by /u/Candid-Turnip-6697
      [link] [comments]

    23. 🔗 r/reverseengineering delimiter-less string obfuscation powered by compile-time AES rss

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

    24. 🔗 r/Leeds Do a lot of people stay in Leeds after graduation? rss

      I keep seeing that uni of Sheffield has a high retention rate, and assumed Leeds would be the same with it being another affordable northern city. Anyone on here come for uni before staying in the city?

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

    25. 🔗 r/Yorkshire The village of Appletreewick in the Yorkshire Dales, North Yorkshire rss

      The village of Appletreewick in the Yorkshire Dales, North Yorkshire | submitted by /u/RedDevilPlay
      [link] [comments]
      ---|---

    26. 🔗 r/LocalLLaMA Next year we're getting 0.5T model from Grok rss

      Next year we're getting 0.5T model from Grok | Tweet : https://xcancel.com/elonmusk/status/2058796067592736866#m Right now it joined "Grok-3 Opensource Release" club. submitted by /u/pmttyji
      [link] [comments]
      ---|---

    27. 🔗 r/wiesbaden Parking in P&R Mainzer Straße Ost without Umweltplakette rss

      Hi! I'm a big idiot and didn't buy a green Umweltplakette since I already had to buy a Swiss vingette as well as an Austrian sticker. On my travel back home I realised I wanted to stop in Wiesbaden, not realising it still has its unweltzone. Given the borders of the zone, could I park in the P&R on the Mainzer Straße without being fined? Or is there an alternative I could use? Thanks already :)

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

    28. 🔗 r/reverseengineering /r/ReverseEngineering's Weekly Questions Thread rss

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

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

    29. 🔗 r/york Emergency Laptop Repair rss

      I have abit of a laptop repair emergency, its the Spring Bank Holiday and all the places I know are closed. My laptop has a few of its keys not working, and it makes a very faint high pitched sound when on, I also just need the fans cleaned hopefully

      Anyone know anywhere that is open today? I'm on abit of a budget but I'm trying to get it fixed today because I have exams in a few days from now and can't work without my laptop

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

    30. 🔗 Rust Blog Security Advisory for Cargo (CVE-2026-5223) rss

      The Rust Security Response Team was notified that Cargo incorrectly handled symlinks inside of crate tarballs downloaded from third-party registries, allowing a malicious crate to override the source code of another crate from the same registry.

      This vulnerability is tracked as CVE-2026-5223. The severity of the vulnerability is medium for users of third-party registries. Users of crates.io are not affected , as crates.io forbids uploading crates containing any symlink.

      Overview

      When building a crate, Cargo extracts its source code in a local cache (stored within ~/.cargo), reusing it for any future build. Cargo includes protections to prevent any file from being extracted outside of the crate's own cache directory.

      It was discovered that it's possible to craft a malicious tarball able to extract files one level below the crate's own cache directory. With the way the cache is structured, that allowed the malicious crate to override the cache of other crates belonging to the same registry.

      Mitigations

      Rust 1.96.0, to be released on May 28th, 2026, will update Cargo to reject extracting any symlink within crate tarballs, regardless of whether they come from crates.io (which already forbids them) or third-party registries. Note that Cargo never added symlinks when running cargo package or cargo publish, so the impact of this should be minimal.

      Users who are not able to upgrade to the most recent Rust version are recommended to audit the contents of their registry for the presence of any symlink, and to configure their registry to reject symlink (if such option is available).

      Affected versions

      All versions of Cargo shipped before Rust 1.96.0 are affected.

      Acknowledgements

      We'd like to thank Christos Papakonstantinou for reporting this to us according to the Rust security policy.

      We also want to thank the members of the Rust project who helped us address the vulnerability: Josh Triplett for developing the fix; Arlo Siemsen for reviewing the fix; Emily Albini for writing this advisory; Emily Albini, Josh Stone and Manish Goregaokar for coordinating the disclosure; Ed Page and Eric Huss for advising during the disclosure.

    31. 🔗 Rust Blog Security Advisory for Cargo (CVE-2026-5222) rss

      The Rust Security Response Team was notified that Cargo incorrectly normalized the URLs of third-party registries using the sparse index protocol. If a hosting provider allowed multiple registries to be hosted with arbitrary names within the same domain, an attacker able to publish crates in a registry could obtain the credentials of others users of the same registry.

      This vulnerability is tracked as CVE-2026-5222. The severity of the vulnerability is low , due to the extremely niche requirements needed to achieve the attack.

      Overview

      Originally Cargo only supported storing a registry's index within git repositories. Most git hosting solutions allow accessing a git repository with or without the .git suffix, so Cargo mirrored this behavior when normalizing registry URLs. This allowed credentials for https://example.com/index to be used for https://example.com/index.git.

      This normalization was unintentionally applied to the new sparse indexes too. Sparse indexes can be hosted on any HTTPS server, which treat URLs ending with .git as different URLs than those without the suffix.

      If the following conditions apply:

      • https://example.com/index is a sparse index.
      • https://example.com/index allows crates to depend on crates from any other registry.
      • The attacker is able to publish crates on https://example.com/index.
      • The attacker is able to upload arbitrary files to https://example.com/index.git.

      ...the attacker could configure https://example.com/index.git to be a Cargo sparse registry requiring authentication for downloads, and with a download URL pointing to a server recording any credentials set to it.

      When the attacker then publishes a crate foo to https://example.com/index depending on a crate bar from https://example.com/index.git, and tricks the victim into downloading foo, Cargo will think the two registries share the same credential and send the victim's Cargo token to the malicious registry.

      Mitigations

      Rust 1.96, to be released on May 28th, 2026, will update Cargo to only strip the .git suffix from registry URLs using the git protocol. No mitigations are available for users of older versions of Cargo.

      Affected versions

      All versions of Cargo shipped between Rust 1.68 (the stabilization of sparse registries) and 1.96 are affected.

      Acknowledgements

      We'd like to thank Christos Papakonstantinou for reporting this to us according to the Rust security policy.

      We also want to thank the members of the Rust project who helped us address the vulnerability: Arlo Siemens for developing the fix; Weihang Lo, Eric Huss and Emily Albini for reviewing the fix; Emily Albini for writing this advisory; Emily Albini, Josh Stone and Manish Goregaokar for coordinating the disclosure.

    32. 🔗 Ampcode News GPT Image 2 Paints Better rss

      GPT Image 2 now powers Amp's painter tool.

      It is a better image editor than Gemini 3 Pro Image, particularly at preserving existing text, typography, and visual style when editing UI screenshots, at ~1/4th the price.

      Here's an example thread: Painter turned a screenshot of the Chronicle page into an updated design while keeping its existing visual style.

      A redesigned Amp Chronicle page generated by Painter with GPT Image 2

  3. May 24, 2026
    1. 🔗 IDA Plugin Updates IDA Plugin Updates on 2026-05-24 rss

      IDA Plugin Updates on 2026-05-24

      Activity:

      • atelier
        • 0ae058c7: Merge pull request #29 from atelier-runtime/cc
        • 23a176ca: Remove obsolete lesson blocks and rubrics; add new templates for Fast

        • 25e0190b: Refactor project knowledge to lessons
        • 2a25e5cc: feat: Auto-configure git hooks path for seamless development
        • 8f9b6189: fix: Final check and fixes
        • 366738eb: refactor: remove legacy agent configurations and suppress git output 

        • bdee6ed2: Merge pull request #28 from atelier-runtime/cc
        • c124dcf5: refactor: rebrand application color scheme to purple and enhance CLI 

        • 80d0ee1d: feat: Add Gemini ADK middleware hooks and enhance agent installation 

        • 8c23b46b: feat(sdk): add Atelier SDK middleware layer for LangChain/OpenAI/Anth

        • 751ce29a: Merge pull request #25 from atelier-runtime/chore/readme-star-history
        • c596769a: feat(checkpoint): implement idempotent agent checkpoints for resumabl

        • adfc9194: docs: add codebase map (.planning/codebase/)
        • 348cd666: fix(install): restore executable bit on install.sh
        • b48a2259: fix(install): index current git repo for global installs, otherwise s

        • 1359eab1: ux(install): show code index target path before bootstrapping
        • 2a939418: style(install): dim confirmed menu selections instead of bright green
        • 7976643d: feat(install): add host integration section with scope-aware target p

        • af4f70aa: feat(install): nicer index progress UI and live per-host status ticks
      • NexusRE-MCP
        • b13c45a5: Added UI automation scripts for completely hands-free backend loading

        • 85337f3b: Implement x64dbg.ini zero-touch macro injection to bypass x64dbgpy ma

        • 1284f82d: Implement zero-touch autorun injection for IDA via idapythonrc and ro

        • a66a22ca: Fix Python 2.7 pathlib import error causing x64dbgpy silent crash
        • 242e8493: Fix x64dbgpy autorun path directory logic to execute plugin implicitly
        • 1883823b: Auto-restart x64dbg instances to instantly hook backend plugin withou

        • c6d6ab88: Enforce Python 3.10+ in install.bat to prevent unsupported environments
        • 6fd39257: Remove hardcoded paths and ignore build output directories
        • 8b4eee48: Fix x64dbgpy extraction path bug
        • 4ab0cc49: Automate x64dbg backend launch via autorun
        • 5020cde4: Restrict vmmpy to Python < 3.12 to fix MCP installation
        • 4d1440ff: Automate x64dbgpy global installation and fix IDA backend blocking
        • 352a20e6: Decrease polling intervals to speed up execution
        • bf8d207d: Highlight new offensive features in README
        • c3e87e04: Implement offensive tooling and pipeline execution
        • 74810a43: Implement global auth, dynamic limit bypass, and AOB scanning across 

        • a41a3071: Update README with dnSpy documentation
        • a223131f: Add dnSpy support to the setup scanner
        • 9a712edf: Refactor setup scanner into core/setup_scanner.py and remove obsolete

        • 80187449: Update setup wizard to deep scan the entire computer for all RE tools

      • Spectra
        • ec2a5152: Increase API timeout for large responses
    2. 🔗 r/york Fireworks near train station? rss

      Anyone know what’s up with the fireworks a around 22:15 tonight? Seemed to be coming from near the station.

      Wasn’t aware there was a particular event / holiday tonight - I don’t normally think of May bank holiday as a fireworks event
 Gave me an awful fright in bed lol

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

    3. 🔗 r/Leeds Was there some metal/punk gig on in Leeds today? rss

      Drove past sovereign street and swinegate this lunchtime and there was hundreds of people queuing for something? Some concert? Not going to lie, was kinda jealous, nice day for it.

      I got home and I couldn’t find what it was.

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

    4. 🔗 r/york Bank Holiday Sunny York rss

      Bank Holiday Sunny York | submitted by /u/York_shireman
      [link] [comments]
      ---|---

    5. 🔗 The Pragmatic Engineer The Pulse: Forward deployed engineering heats up again rss

      Hi, this is Gergely with a bonus, free issue of the Pragmatic Engineer Newsletter. In every issue, I cover Big Tech and startups through the lens of senior engineers and engineering leaders. Today, we cover one out of five topics from last week 's The Pulse issue. Full subscribers received the article below seven days ago. If you 've been forwarded this email, you can subscribe here .

      Last August, we covered a sudden trend of high demand for forward deployed engineers (FDEs), and now there are signs demand is increasing more.

      Google: FDE recruitment spike

      Google is doubling down on FDEs and making the interview process much simpler. Google Cloud CEO, Thomas Kurian, has announced a new, AI-focused organization within the Go-To-Market team, and is hiring a bunch of FDEs for it.

      I'm hearing the hiring process has been shortened from 4-6 interviews held over the course of weeks, to as few as two interviews in just two days. It looks like Google is unusually eager (desperate?) to fill this job.

      OpenAI outsources FDE hiring spree

      On Monday (11 May), OpenAI announced The OpenAI Deployment Company, a standalone entity funded by $4 billion of private equity from TPG, Advent, and others at a $14B valuation. It appears OpenAI is not an investor and holds a partner role.

      The announcement mentions FDEs and says their job will be to "work closely with business leaders, operators, and frontline teams to identify where AI can make the biggest impact, redesign organizational infrastructure and critical workflows around it, and turn those gains into durable systems".

      Based on that, the FDEs will play an important role in OpenAI's enterprise sales activity by ensuring the company's AI systems work and deliver value for customers. Outsourcing this to the new Deployment Company should also free up OpenAI to focus on developing better AI models, while the partner company and its FDEs take care of the customer-facing side of things.

      In a related development, OpenAI has acquired Tomoro, a UK-headquartered AI company founded in 2023, which employs 150 FDEs across the UK, Asia, and Australia. Tomoro is the first acquisition of the OpenAI Deployment Company.

      Anthropic plans outsourced FDE recruitment

      Anthropic is doing the same by creating its own distinct FDE consulting company. Last Monday (May 4), Anthropic issued an unusually hand-wavy announcement about the new business without a name and with few investment details mentioned.

      Investors are Anthropic, Blackstone, Hellman & Friedman, and Goldman Sachs, and the new business will work with "mid-sized companies across sectors to bring Claude into their most important operations."

      Anthropic's approach seems to be the same as OpenAI's: create a standalone company with external funding, in which FDEs integrate Claude into enterprises that will then presumably start purchasing more Claude tokens than ever.

      FDE or a consultant?

      These FDE roles seem very similar to those of an external consultant or a systems integrator. A year ago, I talked with FDEs at OpenAI and Ramp whose jobs seemed a genuine mix of platform engineering - with an FDE contributing back to the platform - software engineering, in that they built new solutions, and also solutions engineering: integrating into customers' services.

      altThe FDE role as I visualized it in mid-2025

      But today, it looks like the role is about to become indistinguishable from a solutions architect or consultant, especially given that these new FDE jobs are in quasi-external companies and separate organizations from where AI products are built.

      altThe reality of the FDE role: an AI-focused solutions architect or consultant

      Job adverts are increasingly clear about the role, but it still helps to read between the lines. Here's one for an FDE at Google Cloud. At first glance, it's impressive (emphasis mine):

      " You are an embedded builder who bridges the gap between frontier AI products and production-grade reality within customers. Unlike traditional advisory roles, you function as an "innovator-builder," moving beyond high- level architecture to code, debug, and jointly ship bespoke agentic solutions directly within the customer's environment. Your role is designed for high-agency engineers with a founder's mindset. You will address blockers to production, including solving the integration complexities, data readiness issues, and state-management challenges that prevent AI from reaching enterprise-grade maturity. By embedding with strategic accounts, you serve a dual purpose: providing "white glove" deployment of complex AI systems and acting as a critical feedback loop, transforming real-world field insights into Google Cloud's future product roadmap."

      Translated into plain English:

      You are a contractor who codes at a customer 's office. The actual job is around ~25% coding-related, 50% integration/plumbing, 25% meetings and customer hand-holding. Anything else will be assorted admin and internal process-related stuff.

      Here's what I reckon some of the terms in Google's job advert will add up to on the job:

      • "Founder's mindset". No one will provide a spec, and scope creep is your problem to deal with. If your project doesn't ship, that's also your problem
      • "High-agency". There are no resources besides your own
      • "White glove". Do not say "no" to anything the customer suggests, even when they should probably listen to your feedback about whatever it is
      • "Critical feedback loop transforming real-world field insights into Google Cloud's future product roadmap". You will file tickets and a few PMs at Google may read some of them

      But in all fairness, this FDE job looks like a great fit for some folks:

      • Those at the early-career stage who want Google on their resumes, but who might struggle to land a software engineering job with the tech giant
      • Those who enjoy shipping end-to-end, can work well with ambiguity ("founder's mindset" is spot on!) and will own outcomes

      On the other hand, I suspect this FDE role will not be a good fit for those who:

      • Like to build well-engineered systems and value the time to do it well
      • Like building greenfield systems
      • Prefer longer-term projects and working with other software engineers

      In the cases of OpenAI and Anthropic, the outsourcing of FDEs is even clearer. Google at least hires FDEs to the company, and they will be issued some stock as part of their compensation package. But at OpenAI and Anthropic, new FDEs will be hired to a standalone company, and if they get stock, it will likely not be OpenAI or Anthropic stock. So, if OpenAI or Anthropic benefit greatly from FDEs' work, then the FDEs won't see the upside!

      Putting it more simply: FDEs hired in these external companies will not be seen as "core". If they were, then the companies would hire more FDEs, as in the past.

      Opportunity for new grads?

      As mentioned above, the new FDE roles could be a great opportunity for early- career software engineers entering the industry, according to**** Box CEO, Aaron Levie:

      "If I were a college career counselor or in career services, I'd quickly be figuring out how to get students to understand these forward deployed engineer jobs exist and how to get them.

      The requirements are a mix of deep technical skills, often CS majors or minors. You must be great at understanding problem solving, how to have systems thinking, and have a strong business acumen. The kicker, of course, is to make sure you're very deep in AI agents; you need to have fluency in coding agents, MCP, CLIs, Skills, and so on.

      Hundreds (thousands?) technology companies will be hiring for these roles, same with any consulting and IT services company, and the vast majority of mid-size and large enterprises will be hiring for this talent internally as well."

      Historically, tech consultancies hired many new grads for consultant roles, which are not so attractive to experienced engineers, but are great, real- world, paid learning opportunities for more junior ones. With product companies hiring fewer new grads, new grads will increasingly find FDE roles that they have a chance at getting.

      All things considered, I expect demand for FDE roles to increase, industry- wide. They speed up AI rollouts, which several parties have an interest in doing:

      • AI labs: the faster that AI solutions roll out, the more revenue they make!
      • AI vendors: any company selling AI products will, similarly, want FDEs to help integrate the software with customers, so they can sell more
      • Non-AI companies: these will want to hire FDEs for an "AI transformation" and to integrate AI into workflows and products
      • Non-AI vendors: even SaaS companies that don't sell AI products will be able to close larger clients if they hire FDEs who can roll out their software faster, and for more use cases, inside enterprises they work with.

      FDE was the hottest tech role in 2025 and this trend seems set to continue this year. Demand for this role is high and rising, but it's likely to stay unattractive to experienced devs for whom being a consultant may feel like a step down - especially after you've learned to love building products!

      Read the full issue of last week 's The Pulse , or check out this week 's The Pulse . This week 's issue covers:

      1. Antigravity 2.0 takes the 'IDE' out of its new IDE. Feedback about the redesigned IDE is overwhelmingly negative due to bugs, poor UX & model support, and eating through Gemini token quotas. Also: a clue that Antigravity's own devs use other tools for their work?
      2. Why is Google 's product ecosystem chaotic? The range of products on display at the Google I/O conference made a messy, incoherent impression. But Google's "let a thousand flowers bloom" approach might be giving the search giant an underrated advantage in the AI race that no other Big Tech giant has.
      3. Meta cuts 8,000 jobs. Morale is very low inside the social media giant as thousands lose their jobs, just as revenue and profits hit record levels. Meanwhile, those assigned to dull data labeling work are spared the axe.
      4. Industry pulse. Anthropic pays $15B/year for SpaceX compute, SpaceX's financials and IPO filing, more woes for GitHub, court dismisses Elon Musk's "hypocritical" OpenAI lawsuit, and Spain may stop blocking its internet during La Liga football games.
      5. How to get a job at a frontier lab in 2026. A Distinguished Engineer at Google recommends focusing on developing particular skills

      Read the full The Pulse.

    6. 🔗 r/Leeds Does anyone want to be friends and go to comicon together? rss

      26F. I’ve never been to comicon since my friends aren’t into anime and things like that but I’d love to go and make friends with like minded folk

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

    7. 🔗 r/Leeds Foleys alley , overflowing bins rss

      What’s going on with all the rubbish down side of Foleys tap house ? Seriously rank , walk past most weeks and it seems to be getting worse..

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

    8. 🔗 r/york Kickabout Community rss

      Kickabout Community | Enjoy a friendly football game to break up the week. Kickabout Community supports independent 5-a-side and 7-a-side adult football games across York. We’re a volunteer-run group of organisers, making football accessible for players of all ability, gender, age, and fitness levels. 👉 Join Kickabout Community here: https://chat.whatsapp.com/CSt29p06AGLL1E91uu5Eze 📍 Pitches used: ‱ York Sports Village
      ‱ University of York Sports Centre
      ‱ PlayFootball Clifton Moor
      ‱ Energise Acomb đŸ’· Subs: ÂŁ3-4 per session (covering pitch hire, balls, and bibs) We are not a business and not profit-making. Any surplus funds are for player socials or charitable donations. submitted by /u/Chance_Board_5424
      [link] [comments]
      ---|---

    9. 🔗 r/LocalLLaMA Is NVIDIA still the default best choice for local LLMs in 2026? rss

      Is NVIDIA still the default best choice for local LLMs in 2026? | submitted by /u/pmv143
      [link] [comments]
      ---|---

    10. 🔗 r/Leeds £16 for two games and 5/6 hours of cricket - and this is the expensive seats rss

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

    11. 🔗 Confessions of a Code Addict Why do we need virtual memory? rss

      In my last article, I covered virtual memory in depth. I now want to complement that with a more direct video series explaining virtual memory and its internals.

      This first video builds a first-principles understanding of what virtual memory is, why it exists, and why programmers should care about it.

      If you've already read the article, I'd be curious to know whether this explanation adds more clarity or gives you a new way to think about the topic.

      The ebook/PDF version of the full article is also available for anyone who prefers reading it in a polished, downloadable format.

      Get Virtual Memory Ebook

      Read more

    12. 🔗 Register Spill Joy & Curiosity #87 rss

      Travelled for roughly 16 hours yesterday and now I'm in a different timezone, with my family, everyone fell asleep at 8pm yesterday, and everyone woke up at 4:30am today (not complaining: that's good!), and I started writing this at 5am, and the Airbnb we're staying in is lovely but has one downside: as of right now, it doesn't have any coffee in it.

      What I'm trying to say: that's all I got for an intro this week, friends. I need a coffee. Enjoy the links!

      • This week we announced Amp Labs. Our team has been working with some exceptional companies for a while now, but now we're entering a new phase, starting in Sydney, Australia. If you're exceptionally good and want to help bring artificial intelligence to a global finance player, let me know.

      • Software After Software on the Amp Labs website. What we at Amp believe about the future of software and why Amp and Amp Labs exist.

      • I was a guest on Mayank Gupta's podcast and we talked about everything, really: how I got into programming, why I got into programming, how I ended up going from training to get better at Vim thinking that it doesn't really matter that much anymore, to being a co-founder of Amp. That was a really pleasant conversation, you can tell that I was a bit tired at the start, since we recorded late-ish my evening, after a long day, but then got more and more excited because Mayank's questions were fun. Also: what an intro. Also, also: wow, he really went there with that one image in the intro.

      • Seems like I'm behind the world by three weeks, but I've finally started to use hunk to review diffs before making commits. Since I've read about the Emacsification of Software right before, I forked it and added Gruvbox Dark Hard.

      • John Gruber: AI Is Technology, Not a Product. I really enjoyed this one, especially this comparison at the end here: "Wireless networking is pervasive too. But Apple doesn't have 'a killer wireless networking product'. Wireless networking simply pervades everything Apple makes. I'm hard pressed to think of a single product Apple makes that doesn't use some combination of Wi-Fi, cellular, Bluetooth, and proprietary wireless protocols. There was a time, not too long ago, when Apple didn't make a single product with wireless connectivity. Now it's pervasive in all their devices. That's more what AI is going to be like. There's not going to be one "killer AI device". Everything is going to be an AI device, to some extent, just like how everything today is a wireless connectivity device, to some extent."

      • How Diamonds are Made? If you find this at least a tiny bit fascinating, I need you to read Have You Ever Tried to Sell a Diamond? which is an absolute must-read for anyone really. Fantastic all-time article, but also infinite ammunition to sound smug in at least fifty conversations in the future.

      • Benedict Evan's AI Eats the World presentation has been updated for May 2026. As always: highly recommend clicking through it. The "Average SKUs per supermarket" slide is great.

      • The 2026 Pulitzer Prizes. Good list to click through to find great writing. This firsthand account of the Texas flood in 2025, for example. I'm struggling to find the right words to describe how well the writing conveys the absolute terror you must feel when you start to think that -- as a real, practical possibility; right here, right now -- that you and your family are going to die, but it does. Maybe don't read it on the plane when you're with your family, like I was.

      • Talking about kids and family: How to deal with your kid leaving. I didn't know that Mike Monteiro was still regularly writing. Nearly everything I know about Monteiro comes from watching this many years ago: F*ck You, Pay Me. Interesting pairing.

      • Anthropic's "Profitability" Swindle: "Remember that deal Anthropic signed with SpaceX to take over Colossus-1? Well it's also taking over some or all of Colossus-2, paying SpaceX $1.25 billion a month starting in May and June
 when it'll have a reduced fee as it ramps up! That's $15 billion a year in compute costs, but reduced to an indeterminately-discounted level for the precise months that Anthropic is using to tell investors and the media that it has an operating profit. That operating profit is a result of accountancy rather than any improvements to its business model."

      • Ben Thompson in The Inference Shift is arguing that agents are more asynchronous than the traditional chat interfaces and that more agents will be running somewhere without a user waiting for them (agree), and that has effects on what hardware is required or what hardware can get away with: "This, by extension, will mean that the likely best approach to solving agentic inference will look a lot different than answer inference. The most important aspect for answer inference is token speed; the most important aspect for agentic inference, however, is memory. Agents need context, state, and history. Some of that will live as active KV cache; some will live in host memory or SSDs; much of it will live in databases, logs, embeddings, and object stores. The important point is that agentic inference will be less about GPUs answering a question and more about the memory hierarchy wrapped around a model."

      • DiffsHub by The Pierre Computer Company. This is faaaaaaast, nice.

      • Marc Brooker: What's Easy Now? What's Hard Now? "I think this is different from the intuition many people have about coding agents. They see websites and UIs as 'easy' (see the SaaSpocalypse), and system software as 'hard'. The feedback loop hypothesis says that this is backwards. That, in fact, we're going to find that SaaS is 'hard' and system software is 'easy'." I think I agree, but we also can't deny that feedback loops have changed tremendously in the last six months. I myself, for a long time in 2025, thought that feedback loops are everything. Then GPT-5.3 one-shotted a big feature. I asked it "did you run the tests?" And it said it didn't but "I can run them now." Then it did run them and they all passed and the code worked on first try. "Why put training wheels on someone who never wobbles?" also means that you might not need a feedback loop if you don't need feedback. Doesn't mean that Marc's point is invalid, of course; I agree with him. But feedback loops will change.

      • Agentation. Visual feedback for agents. Neat, need to play around with it.

      • no slop grenade. It's the new dontasktoask.com eh?

      • When you want to replace the battery of the Garmin HRM200 heart rate monitor you can use the size adjuster on its own strap to unlock the battery. I love stuff like that, when you can use the thing (or parts of the thing) to modify the thing itself. There are about five equivalents in programming, but what's the equivalent in software?

      • Dave Winer in 2002: What is Stop Energy? Nearly 25 years old and still relevant.

      • Two computers, one monitor, zero fiddling. I could read posts like these every day. Love it.

      • I don't think AI will make your processes go faster. This made the rounds quite a bit. It was, as far as I can tell, mostly shared as "gotcha! HA! AI won't change a damn thing!" That's silly, of course, but the original point still is interesting.

      • delphitools, a "collection of small, low stakes and low effort tools."

      • An internal OpenAI model "has disproved a central conjecture in discrete geometry" and: "It looks like the solution approach is surprising to mathematicians. It was a general reasoning model rather than a specialized one: bitter lesson time. I think the stochastic parrot is now nuked from orbit."

      • "Without exageration, being oncall made me the engineer I am. [
] I would argue that one doesn't really understand how software works until they have watched it work, and inevitably fail, in production. And one doesn't really know how to create software until they have patched together someone else's broken pieces." Yes, yes. How many engineers are out there who have been in this industry for five or ten years now and have never worked on the same piece of software for longer than a year? Their experience of what it means to develop software must be completely different from mine, so much so that I can't even imagine what it's like to not think about future-you-and-colleagues-in-2-years when shipping new things.

      • Historian Jon Peterson traces the route from Prussian military headquarters to Gary Gygax's basement. I'm not a big and not even a small board game guy, so most of this was new and fascinating to me.

      • Great low-level debug story: "Two services running on the same machine. One of them opens a listening TCP socket bound to localhost, the other one connects to that. They exchange data. Every now and then, the service that initiated the connection gets an ECONNRESET while reading data from the socket -- but no other errors show up in the logs, no crashes, nothing. What's going on?" It's a two-parter, so don't miss the second one. (Also, check out the author's gallery of desktop screenshots! Made me want to use Damn Small Linux with Openbox again.)

      • Six days left in the P99 Conf Call For Speakers! I recommended a friend to give a talk there since I want to hear what he's up to.

      • Will Manidis on Grindslop. A lot in there that I'm very much not sure about, other things that I find fascinating, but then there's section on 996: "'996' is a mass production / central planning approach to creation. it doesn't work for inventing new things. it only works for cog like scaling of mechanical processes. great work doesn't happen after 100 hour weeks, it only appears in tiny fleeting random moments, embrace that [
] You can assemble an iPhone with 996, but you could have never designed one." That last one, that's a killer line. And I agree. But also: why is only this section in all-lower-case?

      • Hell yes: You don't know HTML Lists. Made me feel like it's 2012 again and I'm excited about discovering a new thing in jQuery or finding that one HTML attribute or element that fits the problem just so.

      • Every Page of Moby-Dick, Illustrated. I started reading Moby Dick last week (constantly switching between the Gutenberg edition in the Kindle app and the audiobook in Spotify) and, man, I'm all about whaling now. Not that I condone it, obviously , but holy hell, what did you know about sperm whales? Not a thing, is what I had to reply, but now I know, for example, that "Atop the whale's skull is positioned a large complex of organs filled with a liquid mixture of fats and waxes called spermaceti. The purpose of this complex is to generate powerful and focused clicking sounds." Let's see if Ahab gets him, that Moby Dick.

      Also want to visit New England and learn about whaling? You should subscribe (but not for that reason, of course):

    13. 🔗 r/Leeds need new bar recommendations in town please! rss

      me & my mates are trying to find a new local, we’ve been unfortunate patrons of howl for ages & want to find somewhere else, we’re struggling to find a good replacement though as we need somewhere with:

      - drink prices that don’t take the piss
      - good, large smoking area
      - decent enough music, doesn’t have to be heavy, just not like you’ve tuned into capital fm

      santi’s doesn’t make the cut, their prices are gross & the smoking area’s tiny :( we used to love psilo before it closed down too but RIP init

      please help us escape howl đŸ«©

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

    14. 🔗 Don't Panic Copy-on-write git worktrees rss

      In the before times, I typically used a small, curated handful of git worktrees. Now the worktrees grow like bermuda grass, to the extent that they’ve become a disk space problem.

      Git worktrees do share their git objects, but they don’t share their working tree. That’s the whole point: you can edit them independently.

      But conveniently, if you are using a filesystem that supports reflinking (APFS on macOS, some Linux filesystems), you can share most of the working tree as well!

      Git doesn’t offer this out of the box, although hopefully that’ll change someday.

      In the meantime, you can approximate it:

      • run git worktree add with --no-checkout
      • pick another worktree that probably has similar files
      • simulate the checkout by doing CoW/reflink copies of git-tracked files from that worktree
      • have git complete the checkout, to fill in missing or mismatched files and to refresh the index

      I bundled this all up in a vibe-engineered command at https://github.com/josharian/git-cow-worktree. It’s a bit slower than using git worktree directly when there are lots of files, but otherwise I’ve been pretty happy with it.

    15. 🔗 r/wiesbaden BĂ€ckerei Dries hat Sonntagspreise rss

      Der einzige Laden der am Sonntag teurer ist wie unter der Woche ist BÀckerei Dries. Angesichts dessen dass das so niemand sonst macht ist das eine UnverschÀmtheit.

      Edit: mir ist schon klar dass die Mitarbeiter am Sonntag einen höheren Lohn haben.
      Aber warum macht das sonst kein Laden, warum macht das nur Dries?

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

    16. 🔗 r/reverseengineering GitHub - iss4cf0ng/OpenPetya: A Proof-of-Concept bootkit inspired by Petya ransomware, written in Assembly, C, and C++ rss

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

    17. 🔗 r/Yorkshire Surprise Trip to York or Leeds rss

      I was involved in a car crash on the way to Edinburgh, fortunately there were no serious injuries for any parties involved but we currently find ourselves stranded at a service station on the A1M between Leeds and York.

      Because of the bank holiday getting a courtesy car may take a few days, we have spoken to the hotel chain we are booked in at Edinburgh they have branches in Leeds and York and have allowed us to transfer our booking because of the extenuating circumstances.

      I'd like to ask the good people of Yorkshire their advice on which direction to go in and what each of your great cities have to offer someone who is having a pretty shit weekend away that need recovering.

      Bonus points for restaurant recommendations.

      Thanks in advance for all of your help.

      UPDATE: Thanks to everyone's help we are now in York having a much better day, just enjoyed an icecream from the icecream boat and had a stroll around the museum grounds, now we're off to explore the rest of the City and find somewhere nice to eat.

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

    18. 🔗 r/Yorkshire Screenshots of the tattoos of Reform Councillor Andy Arnold in close-up detail rss

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

    19. 🔗 backnotprop/plannotator v0.19.22 release

      Follow @plannotator on X for updates

      Missed recent releases? Release | Highlights
      ---|---
      v0.19.21 | Ask AI in plan review and annotate mode, shared AI runtime, origin-aware provider defaults
      v0.19.20 | Interactive goal setup UI, OpenCode submit_plan fixes, browser no-op sentinel handling for Claude agents
      v0.19.18 | Edit-based submit_plan for OpenCode, Pi namespace migration, Codex annotate-last fix, OpenCode commands dir fix
      v0.19.17 | Reworked goal setup skill (interview-driven flow), CLI --version flag
      v0.19.16 | Code navigation with peek view (Cmd/Ctrl+click tokens in diffs)
      v0.19.15 | Commit-based diff base, jj evolution diffs, GitLab reliability fixes, OpenCode command intercept fix
      v0.19.14 | Visual explainer skill update, PFM code-file hover previews, Graphviz, diff tab size and line bg intensity, hooks settings tab
      v0.19.11 | Jujutsu (jj) VCS backend, slimmer hunk separators, collapse viewed files, multi-line gutter selection fix
      v0.19.9 | OpenCode user-managed workflow, Pi model switch fix, Codex skill install, shimmer removal
      v0.19.8 | 49 themes with syntax highlighting, keyboard shortcut registry, smart code-file path validation, remote URL notifications

      What's New in v0.19.22

      v0.19.22 fixes Safari clipboard handling in plan review and adds support for custom Claude config directories. Two PRs, one closing a community feature request.

      Safari Copy Fix in Plan Viewer

      Cmd+C (or Ctrl+C) was silently failing in Safari when copying selected text from the plan viewer. Two things combined to break it: web-highlighter clears the DOM selection on mouseup (so the browser has nothing to copy by the time the keyboard shortcut fires), and Safari rejects async navigator.clipboard.writeText() calls outside the synchronous user-gesture window.

      The fix replaces the keydown handler with a native copy event listener that calls e.clipboardData.setData() synchronously. This works across all browsers. On touch devices where keyboard copy is less common, the toolbar's copy button remains visible and uses an execCommand fallback for extra safety.

      Support for CLAUDE_CONFIG_DIR

      Session log discovery for plannotator last now reads the CLAUDE_CONFIG_DIR environment variable when resolving the sessions/ and projects/ directories. Users who relocate their Claude Code config directory (common in container and multi-user setups) no longer need to work around hardcoded ~/.claude/ paths. When the variable is not set, behavior is unchanged.

      Install / Update

      macOS / Linux:

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

      Windows:

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

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

      OpenCode: Clear cache and restart:

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

      Then in opencode.json:

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

      Pi: Install or update the extension:

      pi install npm:@plannotator/pi-extension

      What's Changed

      Community

      @BenNewman100 filed #783 requesting support for CLAUDE_CONFIG_DIR in session log paths, which ships in this release.

      Full Changelog : v0.19.21...v0.19.22

    20. 🔗 r/LocalLLaMA Qwen3.6-35B-A3B-Uncensored-Genesis-APEX-MTP rss

      Here model: https://huggingface.co/LuffyTheFox/Qwen3.6-35B-A3B-Uncensored- Genesis-V2-APEX-MTP-GGUF

      Safetensors: https://huggingface.co/LuffyTheFox/Qwen3.6-35B-A3B-Uncensored- Genesis-V2-FP8-Safetensors

      MTP-Safetensors: https://huggingface.co/LuffyTheFox/Qwen3.6-35B-A3B-Uncensored- Genesis-V2-FP8-MTP-Safetensors

      Testing results in Open Code on hardware (Beelink gtr9 pro + Strix Halo) done by my friend on Q8_K_P - MTP quant:

      1. 5 sessions with 200k context, not a single glitch, no loops, no repeated tool calls.
      2. After 120k tokens he suddenly gave another task that doesn't intersect with what it was doing at all, and it calmly picked up and solved it correctly.
      3. Uncensored with MTP support with APEX and APEX Compact quantization.
      4. Safetensors support for Apple MLX conversion for Mac users.

      Recommended quant: APEX, MTP-APEX

      Recommended settings for LM Studio:

      System Prompt

      Chat Template

      Chat Template Thinking

      Or use this minimal string as the first line :

      You are Qwen, created by Alibaba Cloud. You are a helpful assistant.

      Then add anything you want after. Model may underperform without this first line.

      Settings:

      Parameter | Value
      ---|---
      Temperature | 0.7
      Top K Sampling | 20
      Presence Penalty | 1.5
      Repeat Penalty | 1.0
      Top P Sampling | 0.8
      Min P Sampling | 0
      Seed | 42

      Enjoy 😄

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

    21. 🔗 r/wiesbaden Best Massages rss

      Hey M19 who works out a lot looking for a great place to get full body massages around the Wiesbaden area!!! What’s yalls recommendations 🙏👏

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

    22. 🔗 HexRaysSA/plugin-repository commits sync repo: +1 release rss 
      sync repo: +1 release

## New releases
- [vtable-context-tools](https://github.com/oxikkk/ida-vtable-tools): 1.1.0
    23. 🔗 r/reverseengineering Reverse engineering circuitry in a Spacelab computer from 1980 rss

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

    24. 🔗 Armin Ronacher Building Pi With Pi rss

      Pi is now part of Earendil, but in the important sense it is still Mario's project. He has been living with its issue tracker longer than I have, and he has been exposed to the weirdness of the new form of agent traffic in Open Source projects for longer too. This post is mostly a reflection of my own experience after spending more time in the tracker, using Pi to work on Pi, and watching what I have learned about it so far.

      Slop Issues

      Unsurprisingly, we are using Pi to build Pi. That sounds like a cute dogfooding thing but it really helps understand what we do. An interesting effect of building with agents is that it changes the role of the issue tracker a tiny bit. The issue descriptions are not just messages from a user to a maintainer because we also use them as inputs for prompts in Pi sessions. It is something I might hand to my clanker1 and say: "understand this, reproduce it, inspect the code, and propose a fix."

      That means the shape of the issue matters in a new way. A bad issue was always annoying, but at least a lot of issues were vague. Now we are also dealing with a class of issues that are 5% human and 95% clanker-generated and largely inaccurate shit. A bad issue that contains a plausible but wrong diagnosis creates extra work.

      The most frustrating failure mode right now is that people submit issues that are not in their own voice. They contain an observed problem somewhere, but it has been thrown into a clanker and the clanker reworded it and made a huge mess of it. Typically, it was prompted so badly that the conclusions produced are more often than not inaccurate but always full of confidence. The result is complete guesswork on root causes, fake-minimal repros, suggested implementation strategies, analogies to adjacent but often the wrong code, and long lists of error classes that might or might not matter.

      That is worse than no diagnosis.

      I don't want to point to specific issues because I really do not want to bad mouth anyone, but it is frustrating. It is also frustrating because when I give that issue to Pi, Pi sees the wrong diagnosis too. It does not treat the issue body as a rumor. It treats it as evidence. It will happily go down the path that the issue already prepared for it, because the prose is confident and the code references look plausible. We use a custom slash command called /is, which specifically has this instruction in it:

      Do not trust analysis written in the issue. Independently verify behavior and derive your own analysis from the code and execution path.

      Unfortunately, it does not fully work, because when humans first throw their issue through the clanker wringer, their clanker expands scope almost immediately. What was once a very narrow and fact based bug observation, turns into a much expanded surface area full of hypotheses. So at least personally, I increasingly want issue reports to be condensed to what the human actually observed:

      1. I ran this command.
      2. I expected this to happen.
      3. This happened instead.
      4. Here is the exact error or log.

      That is enough. If you used an LLM to understand the problem, great, maybe leave it as a follow-up comment. But the issue and the issue text should be something you own. If you do not know the root cause, say that. I too can operate a clanker, and I would rather do this myself than use your slop. If your repro is a guess, say that. If the only hard fact is one stack trace, give me the stack trace and stop there.

      Slop Begets Slop

      That we're seeing issues full of slop is just a result of the present day quality of these machines. Sadly, their failures in creating good issues extend to a lot of code that is generated. Not all of it, but a lot of code. Over and over I keep running into them over-engineering the hell out of issues and implementations.

      If you tell them that "this malformed session log crashes the reader," the clanker will often add a tolerant reader. Then it will add a fallback, then maybe a migration, then more debug output, then a test for all of this. None of this is necessarily wrong in isolation, but it can be the wrong move for the system.

      At Pi's core is a rather well-designed session log with invariants that must be upheld. The clanker's present-day behavior is to just assume that no such invariants exist, and instead to make the system work with all kinds of malformedness, blowing up the complexity in the process.

      Almost always, the correct fix is not to handle the bad state, but to make the bad state impossible. This matters a lot for persisted data such as Pi session logs. They are opened, branched, compacted, exported, shared, and analyzed. The goal here is to never write bad session data. Yet if you just let the clanker roam freely, it will attempt to handle every case of bad data in the session log with a more permissive reader.

      I have complained about this plenty, but working on Pi's code base continues to reinforce the point. This is one of the ways LLM authored code grows so much needless complexity. All these models see a local failure and try to locally defend against it. As maintainers we have to keep pulling the conversation back to the global invariant, which is harder than it should be, and it's laborious.

      Volume Is The Problem

      Then there is the issue of volume. The tracker is receiving a lot of issues and PRs, and a significant fraction of them are clearly LLM-assisted. Some are good, none are excellent, and most are just bad. The total throughput is a maintenance problem by itself.

      As you might know, Pi's issue tracker is automated to close all issues and pull requests from new contributors, and there is a manual process by which we might reopen some of them or approve individuals. So auto-close -> reopen -> close again is an interesting statistic for us to look at.

      I pulled the public GitHub tracker data while writing this over the last 90 days. Excluding Earendil members, that leaves 3,145 external issues and pull requests. Of those, 2,504 were auto-closed because they were from non-approved individuals. 17% were re-opened but that somewhat undercounts issues, because some remain closed while we still fix them. If we also count issues referenced by a main-branch commit or merged pull request that number rises to 26%. For pull requests the number is worse: 60 of 714 auto-closed PRs were ultimately merged, or about 8%.

      Weekly external volume and acceptance rate of Pi issues and pull requests

      Many of the issues and PRs are complete slop and in some cases the humans did not even realize that they created them. Sources of low-quality spam include OpenClaw instances, as well as some skills that people put into their context that seemingly encourage issue creation.

      GitHub clearly is not built to deal with this new form of Open Source, but I'm increasingly feeling the need to put the blame less on GitHub than on all the people involved who make that experience painful. If your clanker shits on someone else's issue tracker then it's not the fault of GitHub, it's yours alone.

      Careful Parallelism

      Pi might be built with Pi, but we're quite far off today from where Bun and OpenClaw already are: fully detached, automated software engineering. Maybe we will reach that point, I don't know. Today it does not seem like we know how to pull off a dark factory and we also don't yet have the desire. That said, there is quite a bit of parallelism going on, and it is mostly for reproducing issues.

      The small setup we use for this is three tiny pieces in Pi's own committed .pi folder. /is (for analyze is sue) is a prompt for analyzing GitHub issues: it labels and assigns the issue, reads the full thread and links, then explicitly tells the agent not to trust the analysis in the issue and to derive its own diagnosis from the code. Then an extension adds a prompt-url-widget which watches the prompt before the agent starts, recognizes the GitHub issue or PR URL that /is (or the PR equivalent) put into the prompt, fetches the title and author with gh, renders that in a little UI widget, and renames the session. It also rebuilds that state on session start or session switch, so if we reopen an older investigation the window still tells the developer which issue it belongs to.

      In practice this means it's possible to have several Pi windows open, each running /is against a different issue, and the UI keeps the investigations visually distinct while the agents do their independent reproduction and code reading. Once the investigations are done, one can work through them sequentially. To finish off everything, /wr (wr ap it up) is the matching wrap-up prompt: it infers the GitHub context from the session, updates the changelog, drafts or posts the final issue comment with a disclaimer, commits only the files changed in that session, adds the appropriate closes #... when there is exactly one issue, and pushes from main.

      Pi terminal session showing an agent analysis with a GitHub issue widget displaying the issue title, author, and URL.

      Open Source Is About Hard Problems Worth Fixing

      You will have noticed this already but Open Source in a post-AI world is under a strange new pressure. We are getting more code, more projects, and more issues. Projects appear with no real users, or a temporary audience of one, and even projects with thousands of stars can have a shelf life of weeks.

      For us, Pi's harness layer is worth maintaining carefully because it solves hard coordination problems and creates a platform we and others can build on. We also know that coordination and cooperation lifts us all up. Many times the right answer is not to work around a problem locally, but to make the upstream behavior correct. Mario has been very good at refusing to make Pi paper over every misconfigured gateway, and we're trying to preserve that discipline. When a gateway behaves correctly, everybody benefits.

      Sadly that type of thinking is quickly disappearing because these machines make local workarounds cheap, so code accumulates local defenses against every misbehavior. Instead of humans talking to humans about where a fix belongs, one human and one machine work around the problem in isolation.

      Keep in mind that AI has not increased the number of people who need software, or the number of maintainers who can review it. It has mostly increased the amount of code and the number of projects competing for attention. Some of that is healthy, but a lot of it fragments effort that should be shared.

      We need stronger foundations, not weaker ones. Open Source needs more collaboration, not more isolated work with a machine. Human communication is hard, and it is tempting to avoid it when you can sit alone with your clanker. But isolation is not where Open Source derives its value. The value is in the community and the structure that lets projects outlive their original creators.

      1. To me, clanker is a much preferable term for agent. Agency lies with humans, not with machines. Calling these things agents I still believe is a mistake, but alas.↩

generated: May 27, 2026 at 00:22:27