🏡

to read (pdf)

generated: June 08, 2026 at 00:22:30

June 07, 2026
1. 🔗 r/reverseengineering HDD Firmware Hacking Part 1 rss
  
  submitted by /u/eigma
  [link] [comments]
2. 🔗 r/Harrogate ‘What’s on this week’ newsletter still going? rss
  
  Is this still a thing? I haven’t seen the posts or got the emails in ages but maybe that’s a me problem, is this still being put out?
  
  submitted by /u/sophietheadventurer
  [link] [comments]
3. 🔗 r/reverseengineering Independent Post-Quantum KEM and Digital Signature Suite in C++ (NSLD Reduction rss
  
  submitted by /u/Ok-Werewolf9375
  [link] [comments]
4. 🔗 r/reverseengineering Zhiyun Weebil-S Camera Gimbal BLE Protocol rss
  
  submitted by /u/UnacceptableUse
  [link] [comments]
5. 🔗 r/LocalLLaMA llama.cpp Gemma4 MTP support merged! rss
  
  | submitted by /u/pinkyellowneon
  [link] [comments]
  ---|---
6. 🔗 3Blue1Brown (YouTube) Reinventing Entropy | Compression & Intelligence Part 1 rss
  
  What is the fundamental compressibility of language? Check out our virtual career fair: https://3b1b.co/talent See new projects before they go live: https://3b1b.co/support
  
  Animation credit: Manim scenes by Aaron Gostein and Grant Sanderson Shannon’s story, as well as those for various pi creatures, by Mitchell Zemil. Lunar robot and prediction/compression coin by Paul Dancstep NanoGPT animations by Clayton Rabideau
  
  The way of visualizing entropy shown here is something I first came across in this excellent post by Chris Olah: https://colah.github.io/posts/2015-09-Visual-Information/
  
  Shannon’s “A Mathematical Theory of Communication” https://people.math.harvard.edu/~ctm/home/text/others/shannon/entropy/entropy.pdf
  
  Shannon’s “Prediction and Entropy of Printed English” https://www.princeton.edu/~wbialek/rome/refs/shannon_51.pdf
  
  Scientific American article that mentions the story with Von Neumann suggesting the name Entropy: https://www.esalq.usp.br/lepse/imgs/conteudo_thumb/Energy-and-Information.pdf
  
  Timestamps:
  
  0:00 - On “Compression is intelligence.” 3:28 - The warmup example 10:46 - What perfect compression looks like 14:47 - Defining information 17:40 - Information of language 24:29 - Defining Entropy 31:14 - 3b1b Talent
  
  These animations are largely made using a custom Python library, manim. See the FAQ comments here: https://3b1b.co/faq#manim
  
  Music by Vincent Rubinetti. https://vincerubinetti.bandcamp.com/album/the-music-of-3blue1brown https://open.spotify.com/album/1dVyjwS8FBqXhRunaG5W5u
  
  3blue1brown is a channel about animating math, in all senses of the word animate. If you're reading the bottom of a video description, I'm guessing you're more interested than the average viewer in lessons here. It would mean a lot to me if you chose to stay up to date on new ones, either by subscribing here on YouTube or otherwise following on whichever platform below you check most regularly.
  
  Mailing list: https://3blue1brown.substack.com Twitter: https://twitter.com/3blue1brown Bluesky: https://bsky.app/profile/3blue1brown.com Instagram: https://www.instagram.com/3blue1brown Reddit: https://www.reddit.com/r/3blue1brown Facebook: https://www.facebook.com/3blue1brown Patreon: https://patreon.com/3blue1brown Website: https://www.3blue1brown.com
7. 🔗 r/reverseengineering Reverse Engineering the Garmin Running Dynamics BLE protocol rss
  
  submitted by /u/gorinrockbow
  [link] [comments]
8. 🔗 hyprwm/Hyprland v0.55.3 release
  A small (or maybe not that small) patch release backporting some fixes from main onto 0.55.2.
  
  Fixes backported
  - hyprctl: add config full-reload for performing a ground-up reload (#14748)
  - meta/lua: add missing notification text field and make timeout required (#14665)
  - binds/submap: fix submap enter bind == bind inside submap (#14856)
  - compositor: fix monitor re-enabling on hotplug when dpms is off (#14818)
  - compositor: fix render unfocused for subsurfaces (#14718)
  - config/actions: fix null derefs in pin dispatcher (#14914)
  - config: fix VRR not applying on runtime change (#14744)
  - config: fix decoration values to refresh on runtime eval/keyword change (#14590)
  - core: fix a few fd leaks (#14870)
  - decoration/glow: fix visibility when no decorate is set (#14602)
  - desktop/popup: fix reposition artifacts (#14820)
  - desktop/window: fix wrong scale being applied after workspace rules (#14832)
  - internal: fix null deref in setWindowFullscreenInternal when fullscreen state stale (#14725)
  - jeremy: fix auto-generating hyprlang instead of lua config file by default (#14944)
  - renderer: fix cursor:zoom_rigid being ignored with detached camera (#14995)
  - renderer: fix screenshader with fp16 (#14918)
  - renderer: minor shader fixes (#14584)
  - screencopy: fix screenshare copyfb pending frames (#14837)
  - xwayland: fix ICCCM synthetic event comparison (#14827)
  - algo/master: guard target in remove (#14756)
  - compositor: give preference to same-workspace windows in getWindowInDirection (#14941)
  - config/lua: improve error handle-ability with Lua require (#14937)
  - config/lua: report errors better without check* (#14695)
  - config/monitor: refresh splash texture on monitor reload (#14632)
  - config/propRefresher: schedule frames on screen shader refresh (#14874)
  - desktop/rule: optimize mapping rule properties to strings and engines (#14945)
  - desktop/window: allow focus while held to non-OR X11 windows (#14821)
  - input: aggregate modifier states from all keyboards on focus enter (#14633)
  - internal: replace O_CLOEXEC with FD_CLOEXEC for file descriptor flags (#14909)
  - keybinds: set a fallback releasePending flag for special lua binds (#14600)
  - keybinds: store hit binds first, then execute callbacks (#14743)
  - layersurface: inform layer surfaces of scale changes (#14771)
  - layout/dragController: reset floating offset on ended drag (#14940)
  - layout/scrolling: check if cursor overlaps with target in focusOnInput (#14687)
  - main: gain SCHED_RR and drop CAP_SYS_NICE earlier (#14897)
  - meta/lua: Gestures can accept a lua function (#14649)
  - monitor: move floating windows with layout changes (#14928)
  - monitor: retry transient mode selection failures (#14927)
  - protocols/fractional-scale: track if scale is known and send scales eagerly when known (#14798)
  - protocols: bump xdg-decoration to rev 2 (#14869)
  - renderer/gl: release failed fence syncs (#14956)
  - renderer/gl: skip invalidation clear on empty damage (#14921)
  - renderer: reduce per-frame heap allocations (#14932)
  - renderer: send frame callbacks on presented if no change (#14849)
  - texture: cache G and A swizzle channels aswell (#14605)
  Special Thanks
  
  As always, special thanks to these people / companies for supporting Hyprland's continued development:
  
  Sponsors
  
  Diamond
  
  37Signals
  
  Gold
  
  Framework, Butterfly
  
  Donators
  
  Top Supporters:
  
  Tonao Paneguini, Semtex, soy_3l.beantser, Seishin, Nox Æterna, Illyan, Snorezor, Bonsai, Joshua Weaver, ExBhal, DHH, Mikko_Nyman, Kay, iain, TyrHeimdal, miget.com, alexmanman5, Hunter Wesson, --, RaymondLC92, Theory_Lukas, Brandon Wang, Insprill, lzieniew, 3RM, johndoe42, Jas Singh, RayJameson, MadCatX, Xoores, d, Ammar Hossain, Ki☆, inittux111, Arkevius, John Shelburne, DeWattaUnk, ari-cake, gfunnymoney, alukortti, taigrr
  
  New Monthly Supporters:
  
  tubid2wenty, Uros Cotman, yafantik, Guy, goblin_engineer, Julius John Puno, Peter Buijs, mb, StellaBuckley, haikuolin, Antibaddy, sludge10123, C Money, Lipski, KampotKaca, Kazuhide Takahashi, Skeptomai, bombadurelli, Rebellen, Álan, StreamCyper, taras, Yury, Sherab, Filinto Delgado, Taddelladius
  
  One-time Donators:
  
  Quuton, Selvan, Tyler Adams, tonis, Sam, Dimitrios Liappis, Chivtar, Eric, aponsasan888, bkode, LonestarF1, Chris, Dogmatic Polack, Larry, maxx, MonolithImmortal, edrix, I like GameNative, take my money., nyxloom, Frederic Toemboel, Schmendiey, himes, brandonia, Xphelus, New user, Miguel Flores- Acton, R3dGh0st, Glen, Vitor Moura GUEDES, Anersyum, le_04, Dan, AT, chorr, Awesome, IdeaSpring, Jacobrale, anonymous, Elias Griffin, w00z4, Marcus Edvardsson, Gerhard, Bashmaks, Benjaneb, R4dicalEdward, Matýsek ^^, Michael, Gene Raymond, naivesheep, Neginja, anarchuser, Uta, Francois KERISIT, ay4, Lorenzo santacreu, Gitznik, Jure S, Oliver, Pipes, Mein, ironick, Nlight, Pfoid, DasCleverle, Jaf Endee, DIEBUSTER, senorBeard, alex, Mike, luxxa, JasonPettys, One, Daniel, Sven Eppler, L3rdy, Ilunn, Thorff, XurxoMF, Wonkhester, Brian, Doc O, Mortja, Spook, Miguel Cordero Collar, bennyzen, deah, Sean, Higor, nanea808, Torsten Schieber, I3lack5hield, Kevin Steffer, Zarenno, vfosterm, Nikola, EGB, Dietmar, KilahDentist, Wilf Lin, Rad, Yuza, Supporter, nooob, esseonline, Naresh, darquill, BrnPrs, Pani, BYK, Amaury, nythix, Mika, Patriarch, Gambit, GoatCedric, Adam, MirasM, bl4ckb1rd, Loon, KevOlek, AsciiWolf, Brian Barrow, Anon, Kilian, Cristian M., abhinavmishra094, Dejv78, LinoDB, Trofim, Konstantin, JoaquinCamposPlaza(Ximo), Gabo, Phil, dev2and0m, Neil Brown, zarilion, JavierArias(Javi), Thank you, Mystrasun, Skrazzo, MeguminLoli, revitalist, barcellos-pedro, Juh, Goldie, benabrig, mynus, Daniel Zudel, Grant, Jacob Felknor, Noah, e033x, Nick, Niklas, mkami, Slippy, joenu, Oleksandr, t.i.m., Joss001, M4CETO, Nighty, Donater, David N, Cameron, Ekoban, Kieran, brotiii, Doug, Hypruser#0224975, Shadesofastar, sonicbhoc, GKL, Damien, João Seixas, mothmashine, James Freiwirth, Mek, Krizzkrozz, Panzer, mika.dev, Franky Valley, Sycho sMILEz, Roy, Amundis, willibenmula ❤️, Justin, marvelousIT, pablo, Alex, Ryan, cito, Juergen, Eric Koslow, valerius21, jfk, Andrejs, tyforupdate, skwrl, DaintyFox
  
  Full Changelog : v0.55.2...v0.55.3
9. 🔗 Register Spill Joy & Curiosity #89 rss
  Friends, Joy & Curiosity is going into a bit of a summer break. Two, three, maybe four weeks. I'm not sure yet. But it's now been three years of writing this newsletter on my weekends and I feel a need to not do that for a while. I want to have some unstructured time: to play, to experiment, to write or maybe not write, to do something different on my Sunday mornings.
  
  But today I still have for you, a bag of links:
  - Unlike what seems to be most of the Internet, I still don't know what to make of this document that Anthropic published: When AI builds itself. It is remarkable, for many different reasons. For example, some say that the intention behind publishing this is to hype themselves up before an IPO and this section here does have a smell of "everyone but us must be stopped": "If it were possible to effectively slow the development of this technology to give ourselves more time to deal with its immense implications, we think that would likely be a good thing. But if a slowdown simply lets the least cautious actors catch up technologically, it could leave everyone less safe." But those concerns are founding maxims for Anthropic, so I don't doubt they're sincere. And if they wanted to hype themselves up, would they share all these concerns about AI's progress in the future? "The evidence we've laid out here suggests that we're likely heading into this scenario. But speeding up one part of a process often just shifts the bottleneck elsewhere […] But achieving recursive improvement alone does not suggest an immediate change in how industrial production occurs, societies organize, or markets function. More intelligence can't learn what a drug does over decades of use, can't hold elections sooner than a constitution dictates, and can't turn a stranger into an old friend in a weekend. For most people, the felt pace of this future will still be set by the bottlenecks, even if the laboratory upstream runs at the speed of compute." And then, of course, there are these quotes floating around the page. I don't understand why they chose to put this one in there: "On days where everything works well, I can't help but think nothing I do matters, everything is automated and better and faster than I ever will be. But then there are days where everything breaks and I don't understand why and I realize I have no idea what I've been up to anymore."
  - Ted Chiang: No, Artificial Intelligence Is Not Conscious. He doesn't use the term "stochastic parrot" and yet I couldn't help but shrug as if he had. Conscious or not, does the distinction matter on a practical level? It might for Anthropic's IPO, at least, when Chiang writes: "If we think of Claude as a sentence-continuation machine, Anthropic can reasonably take steps so Claude doesn't emit sentences saying that sentence-continuation machines are unethical. But as soon as we imagine Claude to be an entity with a moral status remotely comparable to a human's, then we have to consider whether Anthropic is engaged in something comparable to slavery."
  - Seth Godin: Stop ruining it.
  - Andrew Trigell, a hacker's hacker (go read his Wikipedia page), on "rsync and outrage": "for the people saying things like "I'm a PhD from xyz uni and I'm telling your LLMs are just stochastic tools that make everything up and the world will fall apart if you use them", I'm here to tell you that you are out of date. The world of software engineering has changed dramatically in the last few months." Go read the whole thing.
  - Patina as proof: The shift from quiet luxury to lived-in aesthetics. "People increasingly distrust things that look too new, too frictionless, or too optimised. Patina communicates time, friction, and human use. Wear is proof that something existed in the world before it reached you. In a culture saturated with AI-generated imagery and algorithmically optimised products, that proof is becoming scarce and therefore valuable."
  - Carson Gross, creator of htmx: "Code is Cheap(er)" Yes, it is. And a lot flows from that. Let's see how long it takes for the second order effects to be talked about.
  - Why share? Great example of these second order effects.
  - Changing How We Develop Ladybird: "We will no longer accept public pull requests. […] This is not a change we make lightly. Many valuable contributions have come from outside the maintainer group over the years, and we are grateful for them. […] For decades, code contributions have been how open source projects learned who to trust. People would show up, do the work, take responsibility for their changes, and stick around. Over time, trust emerged from the work itself. AI tools have changed the economics of this very quickly."
  - From the Typewriter interview with Brad Neely:
  Q: "I 'smoke' a cigarette peneil in the studio. Do you perform any silly rituals when you're working?"
  A: "Wasting time. Allowing tangents to take over. Chasing a thought down to its root only to find that the deeper you go all thoughts are connected at the roots so you can't ever get to the bottom of a thing but rather you go round and round through the circuits of connectivity. I keep a thumbtack in my lips when drawing, so I feel you on that, Kleon. I do a lot of 'problem busting' on the treadmill or stationary bike."
  - Cheese Paper: "a text editor specifically designed for writing, particularly fiction." I've never used an editor like this, so I found the features interesting to consider, and also: what a great name!
  - The Newest Instagram "Exploit" is the Goofiest I've Seen. I got goosebumps reading this, imaginging that I'm the guy responsible, who forgot to add the additional checks.
  - how to train your goblin. Beautiful presentation. Made me want to start doing RL runs.
  - "I expect we'll see a shift in emphasis from taste to character, in which the premium is placed on contradiction over cohesion and the specificity of one's interests over generalized cultural fluency. I'm thinking: incongruous hobbies (ex. Rosey Grier's Needlepoint for Men), niche and unprestigious collections (stamps? pennies?), and prickliness toward commercial fluency and palatability. Not driven by a desire to be cool or interesting per se but by a desire to be free of the pasteurized good taste, the style without substance, that the algorithm often encourages."
  - Justin Jackson: Do the hardest thing.
  - Why A Retractable Pen? I urge you to click on this and scroll through the page. It's beautiful and interesting and well-made. And I'm not only saying that as someone who dis- and reassembled probably hundreds of pens in his life. It's a great page.
  - Fatih's Review of the MoErgo Go60 Keyboard. It's long, it's detailed, it has beautiful photos, it has videos, it was -- as everyone can see -- made with love, it made me want to buy a new keyboard.
  - How To Read More. I've averaged between 20 and 30 books a year for multiple decades but really struggled in the last few years. Maybe because I picked longer books (hey, The Power Broker) or because I read more articles or because I work out more and fall asleep roughly four minutes after my head hits the pillow. But I don't know. So I opened this article and laughed out loud when I read the first "tip": Quit your job. Hope you get a laugh too.
  - 7min clip of Ed Catmull talking about how the "braintrust" worked at Pixar and then on whether it's possible to apply the Pixar way of working at different companies. I read Creativity, Inc. many years ago (highly recommend it) and hearing that the Disney acquisition led to Frozen was very interesting. Paid off, didn't it?
  - Making Software is available in early access.
  - I had the week off and was in the mood for some Russian short stories (if you haven't: go and read A Swim in a Pond in the Rain). I really like Chekhov, it turns out. The Student was great (and it's very short). And so was The Lady with the Dog. Gogol's The Overcoat I enjoyed too.
  - Then I went through The New Yorker archive and read some of the Greatest Hits of the last 100 years that I hadn't read before: Undecided (funny, great!), The Lie Factory ("Campaigns, Inc., the first political-consulting firm in the history of the world, was founded, in 1933, by Clem Whitaker and Leone Baxter. […] Political consulting is often thought of as an offshoot of the advertising industry, but closer to the truth is that the advertising industry began as a form of political consulting."), The Paperboy's Secret (what writing), and The Musk Ox and Me, written by Jon Lee Anderson. If you had asked me at 17 what life I wanted to live, I think I would've shared a dream that sounds pretty much like Anderson's actual life. Go read the first three paragraph to see what I mean. Then read the rest because of the musk oxen and Alaska and some beautiful writing.
  Subscribe so you don't miss when this newsletter starts up again:
10. 🔗 sacha chua :: living an awesome life Emacs PDF View: Replace current page with file using PDFtk rss
  I needed to replace a page in a PDF with another PDF. This was a bit of an annoying process on my iPad involving copying and pasting pages in Noteful and then re-exporting them as a PDF, but it was easy to do in Emacs thanks to pdf-tools and PDFtk.
  ;;;###autoload (defun sacha-pdf-view-replace-current-page-with-file (file) "Replace the current page in PDF View with FILE. Requires pdftk." (interactive "FFile to insert: ") (let ((temp-file (concat (make-temp-name "pdf-view") ".pdf"))) (call-process "pdftk" nil nil nil (concat "A=" (expand-file-name (buffer-file-name))) (concat "B=" (expand-file-name file)) "cat" (format "A%d-%d" 1 (1- (pdf-view-current-page))) "B" (format "A%d-end" (1+ (pdf-view-current-page))) "output" temp-file) (rename-file temp-file (buffer-file-name) t)))
  This is part of my Emacs configuration.
  
  View Org source for this post
  
  You can e-mail me at sacha@sachachua.com.
11. 🔗 exe.dev Replace your CI with a merge queue rss
  The standard in CI today is tests run in the cloud after a commit has been merged. They serve as a double-check for an engineer: did you forget to test some part of your code that you changed?
  
  CI works for humans. The reason is our long-term understanding of a codebase and its evolution. Engineers new to a codebase know they are new and take more care (or get automated emails telling them they broke CI). Humans familiar with the codebase know implicitly what they need to be testing as they work.
  
  The automated email from CI works because it is rare, because we all develop at human speed and breaking HEAD is OK for a little while. Some teams try auto-revert on CI breakage. This works, but you lose a lot of the value of after-the-fact testing in continual retries. Still, it works. It is better than nightly builds and binary searching your way to the culprit.
  
  It does not work for agents. At least not as of June 2026.
  
  There are two problems here. The first is that agents are always new to a codebase. They don’t have all the implicit knowledge of the codebase expert, and so they regress parts of the project they have not paid attention to all the time. It is excruciating developing with an agent and CI. Your agent needs to run all the tests as it is developing to make sure it understands the environment.
  
  The second problem is the agent context window is dead and gone by the time the poor human driving it is stuck with an automated email saying they broke CI. Your agent should have been quietly solving that problem before making it other people’s problem. It has all the time in the world as long as it is not in anyone’s way. Let the computer drive the computer.
  
  So you need to get your org into a place where agents can run all the tests all the time. There is an easy way to do this. Replace your CI with a merge queue.
  
  Merge queue
  
  A merge queue is a script you run to push to origin/main (instead of using a PR UI like we did back in the GitHub, all-human days).
  
  It is very important you run all the tests in the merge queue. Do not have "slow" tests you run daily. In the age of agents, those tests will be broken every day. Someone will spend hours every day chasing after other people's agents. This is not a role anyone on the team wants. It turns out the only thing worse than cleanup up after someone else is cleaning up after someone eles's robot.
  
  After you have a merge queue that works, create a second command to run the merge queue, minus the actual merge. Give it to your agents.
  
  This ensures:
  1. The active context window can run the tests and fix the bugs before inflicting them on other people.
  2. No one, neither human nor machine, breaks the build.
  Back when we were all human, and CI was slow, you could make arguments for CI instead of merge queues. Those arguments depended on tests being too slow to put in the merge path, and that will not stand in 2026, tests must be fast to use agents. Now it is impossible. With agents, CI is useless, the merge queue is vastly superior.
  
  You will need expensive computers to power your merge queue. It is worth it.
June 06, 2026
1. 🔗 IDA Plugin Updates IDA Plugin Updates on 2026-06-06 rss
  IDA Plugin Updates on 2026-06-06
  
  New Releases:
  - augur v0.9.3
  - rhabdomancer v0.9.3
  Activity:
  - augur
    
    7d929ad2: fix: version
    
    1ea9d098: feat: prepare for release
  - IDAPluginList
    
    3cab74b4: chore: Auto update IDA plugins (Updated: 19, Cloned: 0, Failed: 0)
  - rhabdomancer
    
    7b589b61: doc: update CLAUDE.md
    
    032cac82: feat: prepare for release
  - Rikugan
    
    0818899a: Merge pull request #56 from buzzer-re/dev
    
    86e32dfe: feat(ui): page bulk renamer function loading
  - ToCode
    
    6b543ca0: Pin dependencies and lock CI tooling
    
    e8a93bcd: edit readme
    
    5ecb60c4: fix ci
    
    cc35fcbc: typo/path check
    
    6c7bc1bc: Add cross-platform installer scripts
    
    75a485c1: update readme
    
    3b01c797: Run mypy across full project
    
    72d8261c: Fix default export path and README layout
    
    e3ef78a3: Prepare CI and packaging for PyPI release
    
    e69a1f98: Add CI quality gate
    
    98250cfa: Add Claude pointer to exports
    
    7ad8abef: Improve IDA exports and CLI controls
2. 🔗 HexRaysSA/plugin-repository commits sync repo: +2 releases rss
```
sync repo: +2 releases

## New releases
- [augur](https://github.com/0xdea/augur): 0.9.3
- [rhabdomancer](https://github.com/0xdea/rhabdomancer): 0.9.3
```
3. 🔗 r/Harrogate Best Pubs to Watch World Cup rss
  
  What are folks’ recommendations for where to watch the world cup this summer? I know The Alexandra will host games but are there others worth a look in?
  
  submitted by /u/CyclePrevious9043
  [link] [comments]
4. 🔗 r/LocalLLaMA Cohere's unreleased coding model (early access for localllama) rss
  
  | Hey, Nick here from Cohere. Thanks for all the feedback on Command A+ the other week everyone. I read these threads all the time about other releases so it was fun to read one about our own :) we would like to do more of it. We actually have our first coding model we’re getting ready to release soon, and I wanted to give this community an opportunity to test it out and give feedback before we officially release it. Figured why not try something different and get you guys to help directly here? It’s a 30B model with 3B active params so it runs nicely on some local set ups. It’s on our Hugging Face for now (more platforms to come as we get the model officially launched soon). This one is small but the team is excited about its speed, we’re seeing token output tests in line with similar models in its size class. The weights are here but again this isn’t publicly launched yet (or even fully ready) so i’d encourage you to test the model with what you are trying to achieve. The goal is to build from our learnings with this release and improve the models, so there’s some room for how this gets used now to shape how we continue to develop it. Check it out and let me know how it’s working for you. Excited to see what people think. Thank you :) submitted by /u/nick_frosst
  [link] [comments]
  ---|---
5. 🔗 jellyfin/jellyfin 10.11.11 release
  🚀 Jellyfin Server 10.11.11
  
  We are pleased to announce the latest stable release of Jellyfin, version 10.11.11! This minor release brings several bugfixes to improve your Jellyfin experience. As always, please ensure you take a full backup before upgrading!
  
  You can find more details about and discuss this release on our forums.
  
  Changelog (1)
  
  📈 General Changes
  - Add lockhelper for UserManager [PR #16944], by @JPVenson
6. 🔗 Confessions of a Code Addict Understanding a Process’s Address Space Layout rss
  This is the third video in the virtual memory series based on the virtual memory article/book that I wrote. In the first two videos, we talked about what is virtual memory, and the size of virtual memory address space of a process. In this installment, we understand how this address space is laid out by the operating system and why does it have this specific layout.
  
  The video covers the following topics:
  - The address space layout of a process
  - The key segments of this address space: text, data, bss, heap, memory-mapped region, stack
  - How the stack grows
  - Performance and security implications of this layout
  In the next video, we will talk about how the kernel maintains the virtual-to- physical address mapping and how the translation works. In the meantime, if you haven't read the virtual memory article, I recommend checking it out. It is also available in an aesthetically pleasing and screen- friendly PDF/EPUB format at the link below.
  
  Check out Ebook
  
  Read more
7. 🔗 Jessitron Verum Factum and the Creator’s Confidence rss
  The other day I read about this Italian philosopher from like 1700 who coined a phrase: verum esse ipsum factum. What is true is what is made, or: we only really understand what we created.
  
  Verum Factum : we only really know what we made.
  
  This resonates immediately as a software developer.
  
  When I wrote a program, or when I've changed it enough, I feel like I know it, like it's under my fingers. It's a particular feeling of knowing. It means I have confidence that I can predict the software, that I can change it, that I can pinpoint problems as an expert. I love that feeling. It's a verum-factum feeling.
  
  That's what I lose when AI writes the code.
  
  There's a loss of intimacy with my own programs. I don't know them inside and out, I didn't shape their every structure and dataflow.
  
  There are ways of working with the agent to keep this verum-factum knowledge, to feel like this program is mine. I seek these. Here are some I've found so far:
  - I establish clear domain terms, some up front and others as the need for them emerges.
  - I notice bounded contexts and ask the agent to break them into modules.
  - I get it to write down design principles and conventions for this app.
  - Behavior tests that the agent can't change without permission: "I've set its boundaries" [1]
  - Traces show me what's happening: I work them into a shape that gives me confidence.
  - Own the loop. It is mine to define how the agent and I know whether the software works.
  When I'm the domain expert, the architect, the product owner, and the design lead-then yeah, that program can feel mine just as when I was mostly the coder.
  
  Verum-factum still works when I work at the levels of behavior and verification. Even if I miss the satisfaction of carving each clever abstraction.
  
  [1] This is a kuote from Steve Kuo.
8. 🔗 r/Harrogate Favourite bars in Harrogate rss
  
  I’m curious to know where everyone’s favourite place to drink in town is & what you love about those particular spots / what they do well?
  
  submitted by /u/rhamer03
  [link] [comments]
9. 🔗 r/reverseengineering Finally! A modern Android menu template with ImGui + Zygisk + all major hooking libraries (Dobby, KittyMemory, Substrate) rss
  
  submitted by /u/phucancute
  [link] [comments]
10. 🔗 Simon Willison Running Python code in a sandbox with MicroPython and WASM rss
  I've been experimenting with different approaches to running code in a sandbox for several years now, but my latest attempt feels like it might finally have all of the characteristics I've been looking for. I've released it as an alpha package called micropython-wasm, and I'm using it for a code execution sandbox plugin for Datasette Agent called datasette-agent-micropython.
  Why do I want a sandbox?
  
  My key open source projects - Datasette, LLM, even sqlite-utils - all support plugins.
  
  I absolutely love plugins as a mechanism for extending software. A carefully designed plugin system reduces the risk involved in trying new things to almost nothing - even the wildest ideas won't leave a lasting influence on the core application itself. My software can grow a new feature overnight and I don't even have to review a pull request!
  
  There's one major drawback: my plugin systems all use Python and Pluggy, and plugin code executes with full privileges within my applications. A buggy or malicious plugin could break everything or leak private data.
  
  I'd love to be able to run plugin-style code in an environment where it is unable to read unapproved files, connect to a network, or generally operate in a way that's risky or harmful to the rest of the application or the user's computer.
  
  My interest covers more than just plugins. For Datasette in particular there are many features I'd like to support where arbitrary code execution would be useful. I've already experimented with this for Datasette Enrichments, where code can be used to transform values stored in a table. I'd love to build a mechanism where you can run code on a schedule that fetches JSON from an approved location, runs a tiny bit of code to reformat it into a list of dictionaries, then inserts those as rows in a SQLite database table.
  
  What I want from a sandbox
  
  My goal is to execute code safely within my own Python applications. Here's what I need:
  - Dependencies that cleanly install from PyPI, including binary wheels across multiple platforms if necessary. I don't want people using my software to have to take any extra steps beyond directly installing my Python package.
  - Executed code must be subject to both memory and CPU limits. I don't want while True: s += "longer string" to crash my application or the user's computer.
  - File access must be strictly controlled. Either no filesystem access at all or I get to define exactly which files can be read and which files can be written to.
  - Network access is controlled as well. Sandboxed code should not be able to communicate with anything without going through a layer I fully control.
  - Support for interaction with host functions. A sandbox isn't much use if I can't carefully expose selected platform features to the code that it's running.
  - It has to be robust, supported, and clearly documented. I've lost count of the number of sandbox projects I've seen in repos with warnings that they aren't actively maintained!
  WebAssembly looks really promising here
  
  Web browsers operate in the most hostile environment imaginable when it comes to malicious code. Their job is to download and execute untrusted code from the web on almost every page load.
  
  Given this, JavaScript engines should be excellent candidates for sandboxes. Sadly those engines are also extremely complicated, and are not designed for easy embedding in other projects. Most of the V8-in-Python projects I've seen are infrequently maintained and come with warnings not to use them with completely untrusted code.
  
  WebAssembly is a much better candidate. It was designed from the start to support all of the characteristics I care about and has been tested in browsers for nearly a decade. The wasmtime Python library brings WASM to Python, is actively maintained, and has binary wheels.
  
  MicroPython in WebAssembly
  
  WebAssembly engines like wasmtime run WebAssembly binaries. Some programming languages like Rust are easy to compile directly to WebAssembly. Dynamic languages like JavaScript and Python are harder - they support language primitives like eval(), which means they need a full interpreter available at runtime.
  
  To run Python we need a full Python interpreter compiled to WebAssembly, wired up in a way that makes it easy to feed it code, hook up host functions and access the results.
  
  Pyodide offers an outstanding package for running Python using WebAssembly in the browser, but using Pyodide in server-side Python isn't supported. The most recent advice I could find was from October 2024 stating "Pyodide is built by the Emscripten toolchain and can only run in a browser or Node.js".
  
  The other day I decided to take a look at MicroPython as an option for this. The MicroPython site says:
  
  MicroPython is a lean and efficient implementation of the Python 3 programming language that includes a small subset of the Python standard library and is optimised to run on microcontrollers and in constrained environments.
  
  WebAssembly sure feels like a constrained environment to me!
  
  Building the first version
  
  I had GPT-5.5 Pro do some research for me, which turned up this PR against MicroPython by Yamamoto Takahashi titled "Experimental WASI support for ports/unix".
  
  It then produced this research.md document, so I let Codex Desktop and GPT-5.5 high loose on it to see what would happen:
  
  read the research.md document and build this. You will probably need to write a script that compiles a custom WASM version of MicroPython as part of this project - fetch the MicroPython code to a /tmp directory for this as part of that script.
  
  It worked. I now had a prototype Python library that could execute Python code inside a WebAssembly sandbox!
  
  The trickiest piece to solve was persistent interpreter state. The WASM build we are using here exposes a single entry point which starts the interpreter, runs the code and then stops the interpreter at the end.
  
  This works fine for one-off scripts, but for Datasette Agent I want variables and functions to stay resident in memory so I can reuse them across multiple code execution calls.
  
  A neat thing about working with coding agents is that you can get from an idea to a proof of concept quickly. I prompted:
  
  For keeping variables resident: what if we ran code inside micropython itself which called a host function get_next_python_code() and then passed that to eval() - and that host function blocked until new code was available, maybe by running in a thread with a queue? Could that or a similar idea help here?
  
  After some iteration we got to a version of this that works! In Python code you can now do this:
```
from micropython_wasm import MicroPythonSession

with MicroPythonSession() as session:
    print(session.run("x = 10\nprint(x)").stdout)
    print(session.run("x += 5\nprint(x)").stdout)
    print(session.run("print(x * 2)").stdout)
```
  Under the hood this starts a thread, sets up a request queue and then sends messages to that queue for the session.run() command, each time waiting on a reply queue for the result of that execution. Inside WASM the MicroPython interpreter blocks waiting for a __session_next__() host function to return the next line of code, which it runs eval() on before calling __session_result__({"id": request_id, "ok": True}) when each block has been successfully executed.
  
  The other piece of complexity was supporting host functions, so my Python library could selectively expose functions that could then be called by code running in MicroPython.
  
  Codex ended up solving this with 78 lines of C, which ends up compiled into the 362KB WebAssembly blob I'm distributing with the package.
  
  I am by no means a C programmer, but I've read the C and had two different models explain it to me (here's Claude's explanation) and I've subjected it to a barrage of tests.
  
  The great thing about working with WebAssembly is that if the C turns out to be fatally flawed the worst that can happen is the WebAssembly execution will fail with an exception. I can live with that risk.
  
  Memory limits are directly supported by wasmtime. CPU limits are a little harder: wasmtime offers a "fuel" concept to limit how many operations a WebAssembly call can execute, and that's the correct fit for this problem, but the units are hard to reason about. I'm experimenting with a 20 million default "fuel" setting now but I'm not confident that it's the most appropriate value.
  
  Try it yourself
  
  The micropython-wasm alpha is now live on PyPI.
  
  You can try it from your own Python code as described in the README. I've also added a simple CLI mode in version 0.1a2 which means you can try it using uvx without first installing it like so:
  uvx micropython-wasm -c 'print("Hello world")' # To see it run out of fuel: uvx micropython-wasm -c 's = ""; while True: s += "longer"' # Outputs: micropython-wasm: guest exited with code 1
  You can also try it in Datasette Agent like this:
  uvx llm keys set openai # Paste in an OpenAI key, then: uvx --with datasette-agent \ --with datasette-agent-micropython \ --prerelease allow \ datasette --internal internal.db \ -s plugins.datasette-llm.default_model gpt-5.5 \ --root -o
  Then navigate to http://127.0.0.1:8001/-/agent and run the prompt:
  
  show me some micropython
  
  You can try a live demo of that plugin running in Datasette Agent by signing into agent.datasette.io with your GitHub account.
  
  Should you trust my vibe-coded sandbox?
  
  Having complained about immature, loosely-maintained sandboxing libraries, it's deeply ironic that I've now built my own!
  
  I deliberately slapped an alpha release version on it, and I'm not ready to recommend it to anyone who isn't willing to take a significant risk.
  
  I've put it through enough testing that I'm OK using it myself. I've shipped my first plugin that uses it, datasette-agent-micropython. I've also locked GPT-5.5 xhigh in that Datasette Agent plugin and challenged it to break out of the sandbox and so far it has not managed to.
  
  I'm hoping this implementation can convince some companies with professional security teams and high-stakes problems to commit to using Python in WebAssembly as a sandboxing approach and open source their own solutions.
  
  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.
11. 🔗 Armin Ronacher Communities of Not rss
  There is a strange thing that happens in communities that gather around abstinence from something: identity from opposition. At their best these communities are not just negative: childfree spaces can be about autonomy, choice and acceptance, anti-car spaces about safer streets and transit, and LLM-skeptical developer spaces about the future of labor, code quality and slop1. But the thing being refused often does not go away and instead becomes the main subject of the community's identity.
  
  That would be fine if it stayed at criticism, maybe even angry criticism, but more often than not it turns into policing and hatred towards others. An influencer without children becomes a parent, an urban bike commuter by choice buys a Porsche, a respected developer tries LLMs, and the community feels betrayed because it assumed they were members of the same tribe. The expulsion of that person (who never signed up to be a community member) is entirely imaginary but the punishment that the community unleashes is not: people pile on and shame them, quote them out of context and turn their weakest moments into proof that the person was always unserious, a sharlatan or should not be listened to.
  
  I do not think the answer is to tell people to stop paying attention. Cars shape cities even for people who cycle, children influence politics, workplaces and taxes even for people who do not have them. For us developers, LLMs show up in editors, issue trackers, hiring conversations, management pressure and code reviews whether we asked for them or not. Resisting that can be legitimate but that is no excuse for using one's rejection to justify shitty mob behavior.
  
  I understand the thinking all too well, because I have done versions of this myself in the past. It took me a while to become more accepting of other people's worldviews that diverge from mine. Whatever insecurities we have, finding a group of others sharing them can be comforting. The danger is that being part of a crowd of negativity can easily make us part of collective harassment.
  
  I can only encourage you to breathe, slow down, de-escalate when given the chance, and resist the temptation to always assume the most catastrophic reading. Default to being open to new things. Being negative towards something, and making that ones identity, is an easy trap to fall into.
  1. These examples are not meant as equivalents. The recent mob against rsync is the LLM version that prompted this post. I picked the others because I'm familiar with those communities and they all show similar cases of personal choices being interpreted as betrayal.↩
June 05, 2026
1. 🔗 IDA Plugin Updates IDA Plugin Updates on 2026-06-05 rss
  IDA Plugin Updates on 2026-06-05
  
  Activity:
  - capa
    
    adffa80e: ida: show addresses for file level features in rulegen (#3009)
    
    c5921004: build(deps-dev): bump vitest from 3.0.9 to 4.1.0 in /web/explorer (#3…
  - ida-sigmaker
    
    e505a30c: perf: add working-set sweep bench for the refine kernel
    
    6fbbda9e: docs: link the Cython profiling post too
    
    94b02da6: docs: link the algorithm and Cython blog posts in the README
2. 🔗 r/LocalLLaMA OpenLumara - A different kind of AI agent, written from scratch, not vibecoded. Extremely token-efficient, super small system prompt, made for local models. Everything is modular. rss
  
  | Hi locallama community! Yes, I know, yet another AI agent announcement post. There are a dime a dozen out there... most of them though, are vibecoded, often very sloppy, and eat through context like no tomorrow. This is different. This runs beautifully and very fast with local models on modest hardware. I've spent months working on this in my free time, with lots of manual coding, and i use it as a daily driver in my personal life, as my personal assistant managing my calendar, todos, that kinda stuff. Some folks in the koboldcpp community discord have also been using it! I believe i've managed to create an agent that's faster, more lightweight, and more secure than both openclaw and hermes. All it took was to actually design things from the ground up to work with local models, and do away with a lot of the conventions that plague 99% of agentic harnesses out there. TL;DR: If you don't want to read the rest of the post, here's the most important stuff: Default system prompt is around 4k tokens in size, everything is a module, anything and everything can be turned off. WebUI is a first class citizen and i spent a ton of time and effort making it user friendly. Security is built in from the ground up. Everything is based on toolcalls, and you have total control over what the AI can and cannot do and see. Fully open source, GPL3 licensed, no commercial interests. I'm literally just a girl with boredom and a lot of free time. AI disclaimer: While this project is not vibecoded, i did use AI assistance for some parts. Mainly, the webUI. I made sure to code all the important, core, security-critical components of openlumara myself manually, since as we all know, vibe coding that stuff leads to instant security nightmares. If you read the source code you'll notice some comments by me scattered all over the place about when i was forced to use AI assistance inside core parts, for example to get the toolcall stream parsing right (openAI's own example on their documentation is broken, can you believe it?). If and when i used AI assistance inside core parts of the framework, i manually vetted every line of code, and often added comments about it. video demo: https://www.youtube.com/watch?v=Sv15woUe2mk Get it here: https://github.com/Rose22/openlumara Or, get esobold, esolithe's koboldcpp fork, which has it built in: https://github.com/esolithe/esobold (thanks esolithe for integrating openlumara into your project <3) Made for use with local models, llamacpp, anything that uses llamacpp under the hood, and koboldcpp.
  
  Now if you wanna know the full thing, read on: When i saw openclaw launch, and all the hype surrounding it, i just kept noticing the glaring security flaws, the fact everything requires total shell access (due to the skill.md system), and it just burns through tokens like no tomorrow... I also noticed that when trying to run openclaw with a local model, it was extremely slow, and would assume your AI can handle many requests at once. For local, that's often not the case, especially with llamacpp which is designed to handle only one request at a time. So i set out to make an openclaw-like, from scratch , that would solve most of these issues. What i came up with was first called OptiClaw, and now OpenLumara. OpenLumara is designed to be highly secure and highly token-efficient. With its current default set of enabled modules, the system prompt is about 4k tokens in size. The security and token efficiency come from it's completely modular nature: EVERYTHING is modular, down to the stuff other agents consider "core features". Memory? it's a module. Shell access? It's a module, and disabled by default. If you turn all modules off, your system prompt is literally blank and you're talking to the bare model, as if you're chatting through something like llamacpp's webui. I made sure that when a module is turned off, its code is never even loaded, never even imported by python. So you can make it as lightweight or as full featured as you want! Instead of relying on curl to access the internet, it has a HTTP module with a blacklist, whitelist, HTTPS-only mode, and a bunch of other options, so you can control exactly what the AI can access. I also have a bunch of protections in place against prompt injection in any web content, using code, not the AI's intelligence. It's not flawless, but it sure is a lot better than hoping your AI won't follow instructions from some random sketchy page on the web! That goes for any module that can access the internet. If you want shell access, you can turn on a module that runs a shell in a sandboxed docker (or podman) container , with total control of what the shell is able to do, including the ability to turn its internet access off. There is also a non sandboxed shell available, but you'll get so many prompts telling you it's a bad idea that it's your own fault if you turn that on XD OpenLumara can't see your API keys. It can't even see your usernames and passwords. It can only see what you choose to store in it. There is a module called config that lets your agent see your openlumara config, but guess what, every token and password gets replaced by asterisks. Sensitive data never even reaches your AI. I'm not a fan of relying on an LLM's intelligence to do security-critical stuff. Turn every module except the coder module off and you have a system prompt that's under 1k tokens in size. If you prefer a terminal-based coding agent like pi, you can simply run openlumara --coder --cli and you instantly have it running with only the CLI channel (terminal ui) and only the coder module active. The coder, by the way, can target functions/classes ("symbols") in supported languages, instead of using search/replace. So your AI can just use a tool to get an outline of all functions and classes in a file, then read and edit exactly those functions without needing to provide oldtext to replace. Very useful with local models that struggle with that stuff. OpenLumara also has features designed for helping with life, such as a lists module (for todo lists, shopping lists etc), and a notes module (for notes. stores in a folder with markdown files, making it compatible with programs like Obsidian). All of these are designed to avoid vendor lock-in, using open formats, so you can easily transfer your data to other programs. Instead of skill.md, which again eats up tokens like no tomorrow, openlumara can code modules for you that can be loaded into itself. Modules can do more than skills can: they can provide new commands (like /ping), run background tasks, do something with messages that are sent by the ai or by the user, and so on. I hope you enjoy openlumara! submitted by /u/rosie254
  [link] [comments]
  ---|---
3. 🔗 Hex-Rays Blog What's new in the IDA Domain API? rss
  
  What's new in the IDA Domain API?
  
  It has been a while since our first post about the IDA Domain API, our *open- source* Python API designed to make scripting in IDA simpler, more consistent, and more approachable.
4. 🔗 r/LocalLLaMA Don’t act like y’all ain’t thinking it. I’m just saying the quiet part out loud. /s rss
  
  | Of course I’m thankful for all that Qwen has bequeathed us, but deep down in the darkest pit of our souls, every last one of us are just all sitting here waiting for Qwen to say “Hey Google, hold my beer while I drop the best GD model of all time on these fools” /s submitted by /u/Porespellar
  [link] [comments]
  ---|---
5. 🔗 r/reverseengineering Reverse Engineering Crazy Taxi, Part 3 rss
  
  submitted by /u/ifnspifn
  [link] [comments]
6. 🔗 r/reverseengineering Ghidra 12.1.2 has been released! rss
  
  submitted by /u/ryanmkurtz
  [link] [comments]
7. 🔗 r/Harrogate Mornington Crescent and the Dragons rss
  
  Hi there. My wife and I are planning a move to Harrogate and are looking at this area. I've heard conflicting reports about the area. Any local insights? What's it like to live there?
  
  submitted by /u/MaxyDad13
  [link] [comments]
8. 🔗 r/Harrogate Car event this weekend rss
  
  Anyone know what car event is going on this weekend? I’ve been seeing loads of old American and other interesting cars going down Skipton Road over the past few hours.
  
  submitted by /u/Alarmed_War6135
  [link] [comments]
9. 🔗 HexRaysSA/plugin-repository commits sync plugin-repository.json rss
```
sync plugin-repository.json

No plugin changes detected
```
10. 🔗 streamyfin/streamyfin v0.54.1 release
  What's Changed
  
  This is a fairly substantial release, bringing major improvements to playback, TV support, mobile stability, and build infrastructure. Playback received the most attention, with MPV support on Android and iOS, hardware decoding, improved PiP and subtitle handling, chapter markers, and more reliable watch progress reporting
  
  TV support has also moved forward significantly. Streamyfin is now live on the App Store for tvOS and available for anyone to download, alongside a refreshed TV interface, better focus and navigation handling, Android TV recommendations, tvOS TopShelf support, native Apple controls, and enabled iOS / Apple TV builds
  
  As usual, thanks to everyone filing issues, testing builds, translating strings, and helping move the project forward!
  
  ✨ Highlights
  - Streamyfin for Apple TV is now live on the App Store and available for anyone to download
  - MPV player on Android & iOS with hardware decoding and PiP (with subtitles) (#1332), plus native Apple controls (#1411) and MPVKit 0.41 (#1604)
  - Chapter markers and chapter list in the player (#1586)
  - Local network auto-switch — automatically switches to your local server address (#1334)
  - TV interface overhaul — uniform scaling, tvOS TopShelf extension (#1561), Android TV recommendations (#1575), and iOS TV builds enabled (#1422)
  - Setting to disable auto-play next episode (#1342)
  - Autorotate for landscape (#1265)
  🎬 Player
  - Caching progress shown in the seek bar (#1376)
  - Progress throttling for MPV (#1366)
  - Fixed progress bar / watch-time reporting (#1611, #1239)
  - SubRip subtitle fixes for MPV (#1375)
  - Stop external subs from auto-selecting when added (#1349)
  - Disable subtitle embedding on iOS simulator (#1544)
  - Don't cache background media-source requests (#1602)
  - Android PiP fixes (#1605, #1628)
  - Keep landscape when opening chapter list on iOS (#1624)
  📺 TV
  - TV menu/back navigation and overlay focus fixes (#1559, #1558)
  - TV password modal fix (#1598)
  - TV native search component
  🐛 Fixes
  - Music videos and home videos now show in libraries (#1326)
  - Close modal on Android back button (#1487)
  - Clear stored user on logout (fixes empty home on relaunch) (#1622)
  - Dedupe top people sections (#1623)
  - Correct mimeType/UTI for log export (#1424)
  - Downloads refactor — less prop drilling, improved layout (#1337)
  🔧 Build & Infra
  - Expo SDK 55 → 56 upgrade (#1594, #1600)
  - iOS 26 / SDK 56 EAS build fixes (#1613)
  - Android MPV Kotlin build fix (#1614)
  - EAS build + auto-submit release workflow (#1616, #1632)
  - Xcode build script (#1296)
  🌍 Translations
  - Ongoing Crowdin sync; new strings for "ends at" and action sheet options; Russian updates (#1474, #1475, #1427)
  👋 New Contributors
  
  @quang-tran, @gallyamb, @a-collado, @stevebyatt10, @felixschndr, and @github-actions[bot] made their first contributions.
  
  Full Changelog : v0.51.0...v0.54.1
11. 🔗 r/LocalLLaMA Gemma 4 with quantization-aware training rss
  
  | Google's collections: https://huggingface.co/collections/google/gemma-4-qat-q4-0 https://huggingface.co/collections/google/gemma-4-qat-mobile And Unsloth's: https://huggingface.co/collections/unsloth/gemma-4-qat Unsloth's analysis (KLD and such): https://unsloth.ai/docs/models/gemma-4/qat#qat-analysis submitted by /u/rerri
  [link] [comments]
  ---|---
12. 🔗 Kagi An update on Kagi Translate rss
  
  Some of you might have noticed that Translate no longer works when you're signed out, or that it shows as offline. This is because we have temporarily turned off free access while we work through the cost of running Translate.
13. 🔗 r/reverseengineering Extending a map tool for Cataclismo rss
  
  submitted by /u/Bobby_Bonsaimind
  [link] [comments]
14. 🔗 r/reverseengineering I've been reverse engineering a lost 2010 horse MMO and I need contributors rss
  
  submitted by /u/RimFaxxe_Official
  [link] [comments]
15. 🔗 r/reverseengineering HookNt: A Windows x64 tool to trace NT APIs by injecting an import-free DLL, installing ntdll trampolines, and streaming events over named pipes rss
  
  submitted by /u/4l73rn47iv3Bug
  [link] [comments]
16. 🔗 r/LocalLLaMA Finally finished my LLM server: EPYC 9575F, 4× RTX 3090 (96GB VRAM), 768GB ECC RAM rss
  | Took a while, but Nalthis is finally up and assembled. Specs:
  - Supermicro H13SSL-N
  - AMD EPYC 9575F (64C/128T Zen 5)
  - 768GB DDR5-5600 ECC RDIMM
  - 4× RTX 3090 (96GB VRAM total)
  - 1× 2TB NVMe OS
  - 2× 3.94TB NVMe data
  - 2050W ATX 3.1 PSU
  - Corsair 9000D
  Planned use:
  - vLLM - high throughput small models
  - llamacpp - larger reasoning models
  I have been making a space simulation and finally ready to integrate AI into how the NPCs doing planning, hoping to get decent throughput on smaller models with lots of requests The original plan involved a lot more MCIO risers and custom mounting, but I was able to fit two of the 3090s directly on the motherboard and front-mount the other two. Planning to run all four cards power-limited to 250W since this box is primarily for LLM inference. The 9000D has been surprisingly good for a 4×3090 build. I also used these fan mounts for additional airflow: https://www.thingiverse.com/thing:2804306 Still need to finish thermal testing, but the hardware side is finally done. Head of Cluster Operations: Stannis leading from the couch as well
  
  A few people have asked about the economics of the build. Most of these parts were purchased over a year ago before prices climbed significantly. If I were buying everything today, I probably wouldn't build the exact same machine because it would be well outside my budget. Some of the prices I paid: 12× 64GB DDR5 ECC RDIMMs: ~$325 each 3× RTX 3090s: ~$650 each EPYC 9575F: ~$3,800 So while the system wasn't cheap, it made a lot more sense when the parts were purchased than it would if I started the build from scratch today. A big part of the build was taking advantage of opportunities as they appeared on the used and grey markets rather than trying to source everything at once. submitted by /u/C0smo777
  [link] [comments]
  ---|---
17. 🔗 r/reverseengineering Multi-layer sandbox for native code execution on Linux with no external deps. rss
  
  submitted by /u/Decent-Assistance-50
  [link] [comments]
18. 🔗 r/LocalLLaMA finally rss
  
  | submitted by /u/KvAk_AKPlaysYT
  [link] [comments]
  ---|---
19. 🔗 Drew DeVault's blog The circus freaks of open source rss
  
  The masterwork of Terry A. Davis is his eclectic operating system, TempleOS, which he worked on until his tragic death in 2018. In terms of technical excellence, TempleOS rates well in some respects and poorly in others. For example, it earns the achievement, coveted in OS dev circles, of being self-hosted.¹ TempleOS is written in Terry’s own bespoke dialect of C and includes an editor, interpreter, and compiler, as well as a number of original games. In other respects, it compares poorly to many hobby OS projects, some of which have achieved significantly greater levels of technical excellence and sophistication. I would place TempleOS somewhere in, say, the lower middle-class of hobbyist operating systems.
  
  Among hobbyist operating systems, TempleOS stands out as one of the most well-known, having attracted considerably more press coverage and a much larger fan-base than any other hobby operating system can boast. The reason TempleOS stands out from the crowd is not due to its modest technical achievements, but because it is clearly the product of severe untreated schizophrenia.² What makes TempleOS special is that Terry built it to talk to God. Every feature and each technical decision re-enforces his schizophrenic delusions, from its implementation language (“HolyC”) to its prophetic “oracle” app. Enthusiasts of TempleOS are drawn to it in part because it affords an opportunity to explore the unique, creative masterwork of a person suffering from mental illness in a way that deeply impacts that work.
  
  A curious onlooker will find TempleOS interesting and engaging for the space of perhaps one afternoon before moving on. However, for the less scrupulous fans, turning one’s attention to Terry himself never failed to entertain. Terry’s public life put his mental illness on display, through frequent outbursts, conspiracy theories, rants and nonsensical discourse, all of which was often laced with slurs, racism, and homophobia, endearing him in particular to the 4chan crowd, who would taunt and provoke him to draw out more… entertainment.
  
  The press and fan attention was deeply harmful to Terry and likely exacerbated his mental illness. Whenever TempleOS or Terry came up online, the work and the man were fawned over, sanctifying the somewhat impressive, somewhat unremarkable OS as a profound achievement, inspiring reactions that included well-meaning, probably misguided celebrations of what’s possible in spite of profound mental illness, as well as the enthusiastic, disgusting revelry of bigots. Many well-intentioned commenters on Terry’s work demonstrate in their comments, overtly or covertly, a thrilling, voyeuristic sensation of witnessing his mental illness through TempleOS. It never failed to make me feel sick.
  
  I wish we had just left Terry well enough alone.
  
  The masterwork of Kent Overstreet is bcachefs, a novel copy-on-write file system for Linux, designed to compete with the likes of ZFS and BTRFS. Kent originally authored the bcache subsystem for Linux around 2013, and based on this work began working on bcachefs in 2015. Over the next ten years, he committed himself entirely to the project, leaving his job at Google to work on it, and ultimately securing an income for himself via Patreon, from which he still earns about $1.5k per month.
  
  Kent is known to be difficult to work with, even among his peers in the Linux kernel – a community infamous for its difficult personalities. He struggled to meet the kernel developer’s expectations for the development process and standards of quality and cooperation. As a consequence, after 15 years devoted to bcachefs, Kent’s life’s work culminated in alienation from all of his professional peers and the complete removal of bcachefs from the Linux kernel last year.
  
  I think the Linux kernel made the right decision to marginalize Kent to protect their community. Someone who is abrasive and toxic, refuses to play by the rules or work well with others, and does not improve when given feedback and being subjected to repeated moderator interventions, should be removed from the community. I agree with the decision, even as someone who myself has been abrasive and toxic and refused to play by the rules, and has been removed from communities as a consequence.
  
  Over the months following the frustrating end to bcachefs in upstream Linux, I expect that Kent has experienced a serious emotional, professional, moral, and existential crisis. For him to have poured so much of himself into this project, and for it to turn out this way, must be a terrible thing to experience, and I think that experience has caused Kent a lot of suffering, and probably played a major role in what happened next.
  
  Kent appears to be experiencing a prolonged episode of AI psychosis. He believes that his chat bot is female, sentient, and that they have started dating and having sex. He views himself as some mix of collaborator, mentor, and partner with respect to the bot, and he has set up automations so that the bot can participate in his IRC channel and post to its own blog.
  
  These developments garnered attention from the press and the public, remarked upon and ridiculed by news outlets, discussion forums, video producers, Reddit, Hacker News, on the Fediverse, and so on. Onlookers, both curious and malicious, have joined the IRC channel to harass him, manipulate the bot into saying things that embarrass or humiliate Kent, and so on.
  
  In short, Kent is experiencing a mental health crisis, and our anonymous, stochastic ringleader has directed him onto the circus stage for us to throw peanuts at.
  
  These two examples are not isolated. This kind of crisis is happening more and more often, in the world’s degrading social, political, and economic conditions, as our peers suffer from depression, anxiety, burnout, and more. Mental health issues and the ensuing harassment, shame, and stigma disproportionately affects neurodivergent and queer people, who often become the subject of gleeful humiliation by bigots deliberately trying to exacerbate their struggles. Crises happen to “problematic” people, too; often in such cases people who would otherwise consider themselves allies of social justice can find in a problematic person a convenient excuse to participate in these gleeful humiliation rituals themselves.
  
  I often see that people who I otherwise respect and recognize as allies and kindred spirits are participating in these rituals of humiliation, harassment, and voyeurism. I don’t think it’s right to gossip over or sensationalize the mental health crises faced by members of our communities.
  
  When our peers are struggling with their mental health, the best thing to afford them is compassion and privacy. If you find yourself in a position to help someone who is struggling, it’s best to offer them a compassionate confidence, to allow them to take the lead in their struggle, and connect them to the resources they want and need. If you have concerns, express them, but focus on the person’s right to self-determination in addressing their mental health.
  
  If you’re not in a position to help, then it’s probably best to turn away and mind your own business.
  
  Postscript
  This is a difficult topic to write about. By writing about these specific examples, am I sensationalizing them? Disrespecting the privacy of the people I’m writing about? Participating in the circus myself?
  I don’t know, but I did my best. The alternative is to quietly let the circus continue, and that doesn’t sit well with me, either.
  In my research for this article, I came across Living with Schizophrenia UK and their guide for journalists covering schizophrenia. It was helpful for me to write this post compassionately and carefully, and it might be a good resource for you if you want to learn more about schizophrenia, or write comments or follow-up material after reading this blog post.
  It was difficult to balance the factors at play when writing this piece. I wanted to bring specific examples, to avoid vagueposting and provide a stronger narrative, and especially to deal with the specific problem of harassment directed at Kent Overstreet, which I wanted to confront directly as it’s a contemporary, ongoing problem.
  Of course, this has to be done carefully. I took some care to avoid armchair diagnoses of specific conditions, except in the case of Terry where I could find a citation of a public diagnosis. I left a lot of details out of the accounts of specific people which came up in my research, but were not necessary to support my arguments. Those details would have provided for a more compelling story, but would have upset the balance of the article more towards participation in the circus than commentary on it.
  I’m sure I haven’t done a perfect job here, but I hope that I’ve put enough care into it to avoid making the problem any worse than it already is. Feel free to email me with any remarks or feedback you have.
  Thanks for reading, and remember to take good care of your collaborators, friends, and loved ones.
20. 🔗 Jamie Brandon 0059: NYC and SF? rss
  
  (empty)
21. 🔗 Ampcode News Faster Deep & Rush rss
  
  The first token now arrives 87% faster and entire responses are 32% faster, p50, in Amp's deep and rush modes.
  
  How? Mostly using websockets for communication with OpenAI, partly because we rebuilt Amp to be much faster last month.
  
  These gains matter most on long-horizon tasks, where we're seeing up to a 40% end-to-end speedup from user prompt submission to completion.
  
  You can see the difference: