🏡
  • ↔
  • →

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 25, 2026 at 12:59:13

  1. May 25, 2026
    1. 🔗 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]

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

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

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

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

    4. 🔗 mr-karan/doggo v1.1.7 release

      Changelog

      New Features

      • be67297: feat(app): debug-log nameserver strategy application (@mr-karan)
      • 622bd7f: feat(resolvers): tag lookup errors with nameserver and support partial success (@mr-karan)

      Bug fixes

      Others

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

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

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

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

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

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

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

  2. 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/wiesbaden Taunus therme Erfahrung? rss

      Kann irgendwann eine detaillierte Überprüfung des FKK-Bereichs in der Taunus- Therme geben?

      1. Ungefähr Wie viele Personen sind anwesend?

      2. Neigen die Menschen dazu, völlig nackt herumzulaufen?

      3. Ist man die ganze Zeit nackt oder in bestimmten Bereichen?

      4. Welche Art und wie viele Pools gibt es im FKK-Bereich?

      submitted by /u/Neither-Garage-876
      [link] [comments]

    3. 🔗 jellyfin/jellyfin 10.11.10 release

      🚀 Jellyfin Server 10.11.10

      We are pleased to announce the latest stable release of Jellyfin, version 10.11.10! 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 (2)

      🔒 Security

      📈 General Changes

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

    5. 🔗 r/york Earbuds found on Little Knavesmire (23 May) rss

      As it says in the title. Would be happy to return if identified!

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

    6. 🔗 r/york Bank Holiday Sunny York rss

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

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

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

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

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

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

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

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

    14. 🔗 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):

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

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

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

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

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

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

      submitted by /u/johnsmithoncemore
      [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.↩
  3. May 23, 2026
    1. 🔗 IDA Plugin Updates IDA Plugin Updates on 2026-05-23 rss

      IDA Plugin Updates on 2026-05-23

      New Releases:

      Activity:

      • atelier
        • 73b51a77: Merge pull request #27 from atelier-runtime/cc
        • 3a6bf44e: docs(state): record phase 1 context session
        • ce77c4d3: docs(01): capture phase context
        • 315f46e8: docs: create milestone v1.0 roadmap (5 phases)
        • 0e8a66ec: docs: define milestone v1.0 requirements
        • f6aa31c9: docs: start milestone v1.0 Atelier Token-Cost Reduction
        • 454bd5ac: benchmarks: close remaining pending substitution rows
        • 1e124eb0: docs: refresh search/grep measured benchmark rows
        • 2e70b0dc: code: expand route extraction patterns
        • 57542e75: code: stabilize explore budget packing
        • 47c360e2: code: expose autosync counters in status
        • 27cbe7a3: code: implement debounced autosync reindex
        • dc702e6c: benchmarks: add code routes A/B fixture
        • 9f9608c3: Merge pull request #26 from atelier-runtime/cc
        • 18269d1a: code: add provider freshness warnings to status
        • 50b70a54: code: scaffold autosync status surface
        • be202749: code: add routes op to code MCP
        • 63733996: code: enrich status payload diagnostics
        • 412db648: benchmarks: add code files/explore A/B fixtures
      • FileAnaAssistant
        • 993d79a8: Test cleaned report IOC extraction
        • 6f9e4ba3: Use cleaned IOC extractor in report builder
        • f80e4887: Add cleaned IOC extraction for report JSON
        • 37201e50: zq report ability
      • ida-func-call-rank
        • a07aadd5: Add malware triage use cases to README
        • f68beb7a: Add badges (License, IDA Pro compat, IDAPython, latest tag) to README
        • 87363c2c: Sync Japanese spec with implemented Recursive/Unknown columns
        • 70c8725d: Address review #1 (title sync) and #2 (missing chooser columns)
        • c14f17b8: Address review findings: stale view, install order, license
        • f5465184: Drop toy.c sample; rely on the Emotet screenshot as the demo
        • 71baafc7: Initial commit: ida-func-call-rank MVP
      • space-reversing
        • c2e26f7e: Add sta6-pyr2-nyx5 DGS territory config and update existing territories
      • Spectra
        • 2b41ca80: Fix XREF_NEAR compatibility in ai_features.py
        • fd2f650a: Create skill.md
        • 849928ae: Fixed some bugs
        • 411548ec: Fix generate_disasm_text compatibility across all tools
        • df554238: Fix IDA Pro 9.x XREF API compatibility
        • d68e25f7: Add DPI scale override via environment variable and increase base fon…
        • 7d8ee37d: Add auto-install for anthropic package and DPI debug logging
        • df3eda0c: Updated GUI
        • a4e4b3d4: Updated GUI
        • 292ab8cd: Install Anthropic SDK in installer scripts
        • e8ce9c56: Add Windows ARM64 detection and pip handling
    2. 🔗 r/Yorkshire Big up Yorkshire rss

      Big up Yorkshire | submitted by /u/Britishsheffield
      [link] [comments]
      ---|---

    3. 🔗 r/wiesbaden Wo spontan grillen in Wiesbaden (ohne Anmeldung)? rss

      Hi zusammen! Meine Freundin und ich wohnen am Dotzheim (Daimlerstraße) und wollen zum ersten Mal draußen grillen. Wir haben einen eigenen kleinen Grill mit Standbeinen.
      Da wir spontan sein wollen, suchen wir Plätze, an denen man keinen Termin vorab online buchen muss.
      Stimmt es, dass man im Kulturpark hinter dem Schlachthof einfach so mit eigenem Grill grillen darf? Gibt es dort einen bestimmten Bereich?
      Habt ihr ansonsten noch coole Tipps in der Nähe oder am Rhein (z.B. Biebrich/Kastel) für ein entspanntes Grillen zu zweit ohne Anmeldung?
      Danke euch! 🙏

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

    4. 🔗 r/york Best Catholic Church? rss

      Hi! I was raised Roman Catholic, and as a student in York I've missed the frequent religious involvement I underwent for the first 18 years of my life.

      Which Church would be best for a quiet weekday mass where I can just sit at the back and contemplate religion and life while listening without worrying about having to interact with people much?

      Any suggestions are greatly appreciated!

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

    5. 🔗 r/Leeds Does anyone know if i can and if so where I can get free period products in ls14 area? rss

      Hey hope this is OK. Recently lost my job due to disability. That time of the month and have nothing in the bank. I hate stuff like this. I have been using toilet paper tbh but i also have run out

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

    6. 🔗 r/LocalLLaMA Does GPU spacing matter if we’re undervolting anyways? rss

      Does GPU spacing matter if we’re undervolting anyways? | How close can GPU cards be to each other on the mobo to remain safe and keep the hardware healthy over time? I have 4x 5060ti16gb cards in my mobo (I know 5060ti’s are not ideal when it comes to bandwidth, but I found a few at a decent price so it felt worth it at the time). They do fit on my mobo, but they seem pretty close to each other. These GPUs are supposed to be pretty power efficient, but I’ll probably undervolt them a bit anyways to limit power consumption. No liquid cooling or anything else here, just case fans (10 fans here). Is this amount of spacing cause for alarm or might damage the components over time, or am I just overthinking all this? submitted by /u/Ambitious_Fold_2874
      [link] [comments]
      ---|---

    7. 🔗 r/Harrogate Lost glasses rss

      My friend lost her varifocals on the Stray during park run today. If you find them we’d be grateful for their return

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

    8. 🔗 r/reverseengineering Open-source reverse engineering of PerimeterX (HUMAN Security) Web SDK — pure-algo cookie generators, dual-site live HTTP 200, 10-chapter methodology rss

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

    9. 🔗 r/Harrogate Paddling pool rss

      Hi, hope you're all enjoying the sun!

      Thinking about what to do with my children (5 and 6) on monday and wondered if anyone knew whether or not the paddling pool in the park had water in yet?

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

    10. 🔗 r/wiesbaden Karten für S Festival heute am Kurhaus rss

      Braucht noch jemand ne Karte? Hätte zwei, bin mir aktuell nur noch nt sicher ob ich eine selbst benutze. Also wenn jmd sucht, meldet euch

      https://www.vibrancy-music.com/events/vibrancy-at-kurhaus-wiesbaden

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

    11. 🔗 r/york Lovely views across York this afternoon rss

      Lovely views across York this afternoon | Town may be heaving and not always in a good way, a combination of races, first weekend of half term, bank holiday weekend and the usual hen/stag do’s, but from up here the views are lovely and peaceful. Guess I don’t have to say where I am… submitted by /u/dosguy76
      [link] [comments]
      ---|---

    12. 🔗 r/york Lovely walk around Rowntrees park and the Terrys chocolate factory rss

      Lovely walk around Rowntrees park and the Terrys chocolate factory | Taken with my Lumix G9ii, PL12-60 and PL9 lenses. submitted by /u/DentistKitchen
      [link] [comments]
      ---|---

    13. 🔗 r/Leeds Leeds to Manchester Commute via trains rss

      I work in Manchester and my partner has work in york. Currently we are living in two separate cities i.e where we work and it has costed us a lot. We are planning to find a place in leeds near the train station so that we can commute to the two cities for our jobs. His commute is shorter while mine would take an average of 47 mins to 1 hour considering I take the transpenine direct train to Manchester Victoria.

      Is anyone in the same situation and can advise? My work place has fairly strict attendance and time rules. I will go hybrid from September hopefully (2 days WFH). Can anyone give genuine advice on how workable the situation is or if anyone is in the same boat and can provide some tips?

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

    14. 🔗 r/york This little guy was hanging out opposite York St. John this morning rss

      This little guy was hanging out opposite York St. John this morning | submitted by /u/SavingsMap2506
      [link] [comments]
      ---|---

    15. 🔗 earendil-works/pi v0.75.5 release

      New Features

      • Cleaner read tool output - Collapsed read tool cards now show only the read line by default, while Ctrl+O still expands the full file content.
      • Faster file tools on Windows - Built-in file tools now use async filesystem operations during streaming, and image resizes run off the main TUI thread in a worker.
      • More reliable package updates - pi update and git package installs now reconcile pinned git refs and keep package settings intact. See Packages.
      • Custom Anthropic-compatible adaptive thinking - Custom provider model configs can opt into adaptive-thinking Claude behavior with compat.forceAdaptiveThinking. See Custom providers and Models.

      Added

      • Added compat.forceAdaptiveThinking support to custom Anthropic-compatible model configuration docs and validation (#4797 by @mbazso).
      • Added a standard unified patch to edit tool result details for SDK consumers (#4821).

      Changed

      • Changed collapsed read tool cards to show only the read line until expanded (#4916).
      • Replaced the inherited optional koffi dependency for Windows VT input with a tiny vendored native helper, reducing install size while preserving Shift+Tab handling (#4480).
      • Changed the root development install documentation to use npm install --ignore-scripts (#4868).

      Fixed

      • Fixed pi update to reconcile git-pinned packages to their configured ref (#4869).
      • Fixed package/resource path handling for Windows and glob/pattern resolution (#4873 by @mitsuhiko).
      • Fixed config pattern matching to resolve patterns from the correct base directory (#4898 by @haoqixu).
      • Fixed theme pickers to list themes by their content name instead of file stem (#4830 by @Perlence).
      • Fixed OpenCode Zen/Go requests to send per-session OpenCode routing headers (#4847).
      • Fixed Amazon Bedrock provider loading under strict package managers by inheriting the declared @smithy/node-http-handler dependency from @earendil-works/pi-ai (#4842).
      • Fixed inherited Amazon Bedrock Claude requests to send the model output token cap by default, avoiding Bedrock's 4096-token default truncation (#4848).
      • Fixed exported session HTML to escape quote characters in attribute values (#4832).
      • Fixed GitHub Copilot device-code login to keep opening the verification URL in browser-capable environments while ignoring browser launch failures for headless use (#4788 by @vegarsti).
      • Fixed git package installs to reconcile existing checkouts to the requested ref and update package settings without losing filters (#4870).
      • Published a 0.74.2 rescue release that tells Node 20 users to upgrade Node before updating to newer Pi versions (#4876).
      • Fixed final bash tool cards to avoid rendering duplicate full-output truncation paths (#4819).
      • Fixed bash tool truncation line counts to ignore the trailing newline as an extra output line (#4818).
      • Fixed footer home-directory abbreviation to avoid shortening sibling paths that only share the same prefix (#4878).
      • Fixed macOS Bun release binaries to resolve the native clipboard sidecar so Ctrl+V image paste can load @mariozechner/clipboard (#4307).
      • Fixed coding-agent tools to avoid synchronous filesystem operations during streaming and moved image resizing off the main TUI thread (#4756 by @mitsuhiko).
    16. 🔗 r/Leeds I've just navigated Dawsons Corner for the first time. WTF rss

      Had to choose between an RTC or taking the wrong turn. Chose the latter obviously. Appropriate signage might help drivers navigate the new layout (was leaving New Pudsey station trying to get back to Horsforth). Lol 🫣

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

    17. 🔗 r/Yorkshire The Reform councillor for Wombwell has some interesting tattoos.. rss

      The Reform councillor for Wombwell has some interesting tattoos.. | submitted by /u/johnsmithoncemore
      [link] [comments]
      ---|---

    18. 🔗 Probably Dance Book Review: Babel by R.F. Kuang rss

      The book Babel, or The Necessity of Violence: An Arcane History of the Oxford Translators ' Revolution is fascinating. And I'm not sure how much of this the author intended. It's mainly fascinating because it's trying to discuss colonialism, technological progress, and inequality with characters who are all stuck in the 19th century and are unable to reason with history in mind. And throughout the entire book the author acts like this is the right way of thinking. This review will contain major spoilers, partially because I don't think the book is actually worth reading. I found it very frustrating and nearly stopped a few times.

      The main reason for this frustration is that the "good guys" are often quite evil and get nearly everything wrong all the time and don't achieve any of their goals. There are very few actual good people in this book, and those actual good people get treated badly by the story. The "good guys" think that the actual good people are evil.

      The story is about a kind of magic ("silver working") where you can use a bar of silver for direct effects (heal someone from cholera, kill someone) or imbue the silver with a kind of aura that affects things near it. So you can embed the right bar of silver in e.g. a steam engine and the engine runs more efficiently. Or you can embed it in a buildings foundation to make the building stronger. The magic spells require fluency in multiple languages, so being a translator is a very prestigious job. The story takes place at the University of Oxford in the 1830s, where silver working has recently gone through its own industrial revolution (at the same time as the actual industrial revolution is going on) so that these aura effects have been scaled up, creating enormous benefits for society, and enormous wealth for the people in charge.

      Colonialist Imperialism vs Anarchism

      The book is mainly about how this technological progress changes the world. But the two main parties are

      • The bad guys: British colonizers who would like nothing more than to take over the world and exploit all other countries. These are racist warmongering assholes who believe in a zero-sum world where they have to win, and if others lose in the process, that's just how the world is. (oh and they're also academics, which is the first slight disconnect)
      • The "good guys": Modern day Robin Hoods who steal from the university so that the poor can also benefit from silver working. It's hard to characterize them because they don't have a fully coherent plan, but they're probably closest to anarchists. These people play negative-sum games (theft, sabotage) mostly because they're upset that the first group got so rich while being assholes, and also because they enjoy helping the poor directly.

      The obvious issue, knowing how the industrial revolution turned out, is that both of these mindsets are deeply stupid. Progress is a positive-sum game. We now live in a world that's vastly better than the 1830s, with much of the world lifted out of poverty. The bad guys are working towards that much better world, but they're doing it for selfish reasons and they incorrectly believe that they have to hurt others to get the benefits that they're getting. Meanwhile the "good guys" are acting in a way that will delay the better world that we now live in. They have good intentions and the book constantly acts like that is what counts, but it is intensely frustrating to read. It's never quite clear what their plan is. They talk about helping the poor, though that topic stays abstract, and about sabotaging the bad guys, which they get very specific on.

      A Trumpian Mindset And the Tragedy It Leads To

      When talking to my wife about this, she pointed out that many people still think in the zero-sum mindset today. In my mind the most obvious person is Donald Trump, and maybe the people who vote for him. So the book is extra fascinating because it has these people who think like Donald Trump, but who would probably hate him. If a left-leaning person had the same world view as Donald Trump, they might turn out like the "good guys" in this book.

      The saddest character in the book is Letty, the main actual good person. Obviously the "good guys" end up hating her by the end. She is the only one who seems capable of breaking out of the Trumpian world view. She survives until the end of the book and the main hope is that she manages to improve the world. Her tragedy is that she falls in love with Ramy, one of the "good guys" who is an immigrant from India. But Ramy refuses her advances because of this same weird dynamic where he has fully adopted the racist colonial world view where a brown Indian man can't date a white English lady. Letty is realistic about this and is willing to try to transgress the norms of the time and find out what the consequences are, but once again the "good guys" accept the world view of the bad guys and are unable to get over it.

      The entire time while reading the book I'm not sure what the author actually thinks. Does she have this Trumpian mindset? The first chapter quotes from Adam Smith's The Wealth of Nations, which makes you think that the book will explore the economic impacts of this silver working. But then everyone is acting very stupidly about it, from an economist point of view (but consistent with 19th century beliefs). Similarly the author writes a chapter which perfectly explains Letty: A brilliant girl from an upper class English family who was constantly oppressed because of the sexism of the time. But her genius and hard work allow her to escape her path and go to university. When the "good guys" join the anarchist group she has her doubts, but joins in because she was also oppressed and is trying to improve the world. She quits and betrays them when it's clear that the anarchists are turning towards violent means. She is very clear-eyed and sane about all of this. So once again it's very interesting how the author can write this character, but also writes all the other characters who think Letty is evil.

      At one point, when the existence of the anarchist group is first revealed to Letty, she makes all kinds of sane suggestions about how the world could be improved using their skills for magic, including finishing school then going into philanthropy. This actually would make sense, but the author criticizes the idea in a footnote. The author can write both sides, but then she always gives the last word to a Trumpian mindset where philanthropy is suspect.

      The Necessity of Violence

      The confusion about the author's intent peaks at the end of the book when things turn violent. The anarchist group occupies Babel, the home of most silver-working in the country, by shooting its leader and making everyone else flee, and goes on strike. The goal is to weaken the British empire with the most destructive sabotage. The magical auras from silver keep many things working in the country and they can disrupt it all.

      At some point earlier in the book it's revealed that the translators' guild (the "bad guys") is deeply irresponsible about how they run their business. They intentionally make it so that silver has to be regularly maintained because that makes them more money. Also it's revealed that they only have two translators in all of England who are fluent enough in English and Chinese to keep the silver bars working that rely on those two languages. One of them dies in the story, the other joins the strike, so magic auras all over the country start failing very quickly. It's incredible irresponsible that such important technology relies on just two people. (once again the book is internally confused because in the book all of this is treated as sane and is not even questioned)

      Silver afforded London all of its modern conveniences. Silver powered the ice-making machines in the kitchens of London's rich. Silver powered the engines of the breweries which supplied London's pubs, and the mills which produced London's flour. Without silver, the locomotives would cease to run. No new railways could be built. The water would run foul; the air would thicken with grime. When all the machines that mechanized the processes of spinning, weaving, carding, and roving ground to a halt, Britain's textile industry would wholly collapse. The entire country faced possible starvation, for there was silver in the plough-frames, seed drills, threshing machines, and draining pipes throughout Britain's countryside.

      (Page 485)

      The strike fails terribly because, oh shock, it mostly hurts poor people. Turns out silver working was benefiting the whole society, not just the rich. (just like the real industrial revolution) This quickly opens up a rift in the anarchist group. Some realize that they're mostly hurting the poor and want to stand down, or at least still maintain some of the silver bars. But after a vote they decide to keep the strike going on full so that the pain can even be felt by the rich people who they're striking against. Dozens of people die as a result from traffic accidents from malfunctioning carriages and crumbling buildings which were held up by magic auras. (the buildings crumble the day after the scheduled maintenance. Who schedules the maintenance on the last possible day? Again incredibly irresponsible) Eventually it's revealed that the rich, who were the target of this strike, were barely affected. And when the rich did finally lose their patience, they stopped being polite and send in the army for real. The anarchists cave in immediately. Part of the group flees, but the others stay behind to end the book in a giant suicide bombing, destroying the silver-working center of the country with its library, throwing back technological progress by a decade or more.

      Once again the author's world view is deeply confusing because she writes as if these people are heroes, but she also writes that they're just causing a giant disaster without achieving any of their goals. It surely must be a commentary on how the "necessity of violence" is bullshit and leads to far more suffering and doesn't help in the end. But it has that same fascinating confusion as the rest of the book where the author pretends that these are heroes.

      What Does the Author Think?

      I am writing this without having looked up R.F. Kuang. I have not read any other book by her. I think it's more interesting to have this uncertainty. Currently my odds are

      • 30% chance that she has this Trumpian mindset
      • 60% chance that she is confused and this book is her way of working through her confusion, with the result being that she is still trying to hold on to this zero-sum world view, but she also sees that it doesn't really work
      • 10% chance that she understands all of the issues in the book and wrote it as a brilliant criticism of the anarchist branch of the American far left by showing how their world view is stuck in the past and doesn't work

      Given that I put the biggest odds at "she is working through her confusion" and that I think she didn't finish working it out by the end of the book, the rest of this blog post will be me trying to talk about how to move on from this confused mindset.

      Technological Progress in the Trumpian World View

      This is obviously relevant right now because Trump started a war with Iran, and when they responded with blocking the Strait of Hormuz, causing economic problems and fuel shortages all over the world, mostly affecting poorer countries, Trump responded with joining in and blocking all oil trade from Iran. Meaning now Trump and Iran are blocking the Strait of Hormuz together. It's exactly the kind of thing that the "good guys" in Babel would be doing. Sabotaging the world in order to hurt their evil enemies (and there's no doubt that the Iranian regime is evil) but doing it in such a way that they're mostly hurting the poor. (This is just the current example. If I had written this review six months earlier or later, I'm sure I could have named another current example)

      The other reason why it's relevant is that we are going through the AI revolution. As a programmer I am obviously very positive about technological progress. The book is very negative on it and often gives voice to Luddites and focuses on how people lost their livelihoods as the factories automated. I'm sure that was very bad at the time, but with the benefit of hindsight we know that this turned out great. New jobs popped up, including mine, programming. We now live in a country with 100k massage therapists, and even more people whose job it is to care for pets. We live longer lives because more people could dedicate their lives to curing diseases. Average people now live healthier lives, eat better food, and enjoy better entertainment than kings and queens of the 19th century. If the anarchists in the book had their way, this would either not have happened or would have happened much more slowly. The most sensible method of dealing with the terrible colonial imperialists in the book would have been to finish school at Babel, and to then open a competing school with the goal of democratizing silver-work. Yet the only person who even vaguely gestures in this direction is the evil Professor Lovell, when he points out that other countries have been unable to open competing institutions. (mainly because they have bad governments) In particular some of the anarchist group have been in a position for years to do this, but have not done it, preferring to work in secret so they can sabotage the bad guys.

      I'm sure that as a programmer I have reduced the number of jobs required to finish a project. Most obviously when I was a tools programmer on Just Cause 3. If it hadn't been for my work (or somebody else in the same role) that game would have required more artists and more designers. But obviously those people wouldn't have been hired. The budget wasn't there. Instead the game would have just turned out worse. Similarly right now AI is automating a lot of programming tasks. It's clear that this will end differently once AI can do all tasks (also called "AGI") but so far my job is secure and I have been using AI to create new projects that I couldn't have done on my own before. (1, 2) Maybe in another world I would have hired a web designer or frontend programmer to do the things that I couldn't do myself, but realistically I wouldn't have. Either the projects would have turned out worse or just wouldn't have gotten done at all.

      So when the book talks about people being out of jobs because looms are being automated, I just can't empathize. In my mind automating looms is a great thing. That's what I do for a living. It allows people to get more stuff done or to do better work. If you're against that automation you're probably destroying the 100k massage therapist jobs in the country because those wouldn't have existed in a world in which people make clothing by hand. There just wasn't enough wealth in the 1830s. But in a Trumpian world view these things are zero-sum and if someone gets rich off of automatic looms, that must mean that others are poorer as a result. Now we know that this is a silly thought, but people didn't know in the 19th century.

      The Lecture

      There is a part in the book where one of the professors becomes disillusioned with their work. I'm going to quote a long section to show you how the book talks about these things:

      The silver industrial revolution had decimated both the textile and agricultural industries. The papers ran piece after piece exposing the horrific working conditions inside silver-powered factories (although these had their rebuttals, including one refutation by Andrew Ure, who argued that factory workers would feel a good deal better if they only consumed less gin and tobacco). In 1833 the surgeon Peter Gaskell had published a thoroughly researched manuscript entitled The Manufacturing Population of England , focusing chiefly on the moral, social, and physical toll of silver-working machinery on British labourers. It had gone largely unheeded at the time, except by the Radicals, who were known to exaggerate everything. Now, the antiwar papers ran excerpts from it every day, reporting in grisly detail the coal dust inhaled by small children forced to wriggle into tunnels that adults could not, the fingers and toes lost to silver-powered machines working at inhuman speeds, the girls who'd been strangled by their own hair caught in whirring spindles and looms.

      The Spectator printed a cartoon illustration of emaciated children being crushed to death under the wheels of some nebulous contraption, which they captured WHITE SLAVES OF THE SILVER REVOLUTION. In the tower, they laughed themselves silly over this comparison, but the general public seemed genuinely horrified. Someone asked a member of the House of Lords why he supported exploiting children in factories; he replied quite flippantly that employing children under the age of nine had been outlawed in 1833, which led to more general outcry over the suffering of ten- and eleven-year-olds in the country.

      'Is it really as bad as all that?' Robin asked Abel. 'The factories, I mean.'

      'Worse,' said Abel. 'Those are just the freak accidents they're reporting on. But they don't say what it's like to work day after day on those cramped floors. Rising before dawn and working until nine with few breaks in between. And those are the conditions we covet. The jobs we wish we could get back. I imagine they don't make work half as hard at university, do they?'

      'No,' said Robin, feeling embarrassed. 'They don't.'

      The Spectator story seemed to greatly affect Professor Craft in particular. Robin found her sitting with it at the tea table, red in the eyes, long after the others had finished their breakfast. She hastily wiped her eyes with a handkerchief when she saw him approach.

      He sat down beside her. 'Are you all right, Professor?'

      'Oh, yes.' She cleared her throat, paused, then nudged the paper. 'It's just… it's a side of the story we don't often think about, isn't it?'

      'I think we all got good at choosing not to think about certain things.'

      She seemed not to hear him. She stared out of the window at the green below, where the strikers' protest grounds had been turned into what looked like a military camp. 'My first patented match-pair improved the efficiency of equipment at a min in Tyneshire,' she said. 'It kept coal-laden trolleys firmly on their tracks. The mine owners were so impressed they invited me up for a visit, and of course I went; I was so excited about contributing something to the country. I remember being shocked at all the little children in the pits. When I asked, the miners said that they were completely safe, and that helping out in the mines kept them from trouble when their parents were at work.'

      She took a shaky breath. 'Later they told me that the silver-work made the trolleys impossible to move off the tracks, even when there were people in the way. There was an accident. One little boy lost both his legs. They stopped using the match-pair when they couldn't figure out a workaround, but I didn't give it a second thought. By then I'd received my fellowship. I had a professorship in sight, and I'd moved on to other, bigger projects. I didn't think about it. I simply didn't think about it, for years, and years and years.'

      She turned back towards him. Her eyes were wet. 'Only it builds up, doesn't it? It doesn't just disappear. And one day you start prodding at what you've suppressed. And it's a mass of black rot, and it's endless, horrifying, and you can't look away.'

      (Pages 492 to 494)

      (a "match-pair" is the magic spell you can cast on silver, it's a pair of words from different languages)

      So what do you do with that? It's really bad. Your magic spell made a kid lose both legs because a mine cart couldn't be stopped. But in a sense it's the wrong thing to focus on. The important thing to notice that this is better. Working conditions were terrible before, now they're slightly less terrible. Obviously it's not better for the kid who lost both legs, but given the nature of the invention it's likely that risk of injuries went down on average. Less risk of mine carts derailing and injuring people, more risk of getting hit by a mine cart if you're on the tracks, which adds up to less risk overall. The professor is making the mistake of not giving herself credit for the accidents that didn't happen. We know, with the benefit of hindsight, that piling up inventions leads to a much better life. You'd rather be working in a English coal mine the 2000s than in the 1830s, because working conditions became much better. Partially due to labor organizing and demanding better working conditions, but mostly due to technology getting better. (no amount of labor organizing in the 1830s would have improved conditions to the level of the 2000s) And in fact the last big coal mine in England shut down in 2013, which would have never happened if it weren't for better technology. So when you're presented with a terrible situation it would be great if you could solve it, but if you can't, maybe you can make it better , and that's a good thing to do. And then eventually the new invention was retired, maybe in favor of a new, even better magic spell, maybe for nothing at all. This is fine. Trying is progress as long as you sometimes come up with things that stick. It's not necessarily a straight line.

      Obviously nothing is better along every single dimension. For almost every invention you can find some aspect where it's worse. That's just the messiness of life, it happens with most decisions you have to make, not just new inventions. But notice that there can be decisions that are better for almost every involved party. This invention is better for the mine owners and the mine workers (assuming less risk of injury on average) and it's also better for the professor. The increased reliability is so much better that all three involved parties benefit. In a Trumpian world view you'd think that this is impossible. In a Trumpian world view you think that if one person benefits, another must lose out. (the book is reliably cynical about improvements to the world, like abolition of slavery, or making child labor illegal for kids under the age of nine, see above. It always finds something to complain about and ignores that things got better) That's where the cartoon above comes in. The thresher and the automatic loom made life better for the majority of people. Not everyone, but for most (I'm sure someone was unable to find a new job, but employment in the English textile industry went up, not down, peaking in the early 20th century).

      This point can be made more obviously in the other direction: There are some acts that just make things worse. Like if I go around littering, or smashing windows, that just makes things worse for everyone. (except maybe briefly myself because littering or smashing windows is slightly more fun than not littering and not smashing windows, but in the long term it also makes things worse for myself) I'm just causing people to have costs to bring things back into order, and those costs bring us no benefits except getting us back to the status quo. So if there are acts that can be worse for almost everyone, where there is no winner for the loser, maybe that makes it believable that there can also be acts that can be better for almost everyone. Like building an automatic loom. It's the difference between negative-sum games (littering), zero-sum games (land disputes), and positive-sum games (improving technology).

      If you want to be really rich, then for most of human history you had to take from someone else. The richest people had to field armies to conquer neighboring countries and to force the conquered to pay taxes. This stopped being true. Now the richest people are entrepreneurs and merchants. And even normal people lead better lives than conquerors of the past. This is because positive-sum games make the world so much better. There is no amount of conquering and taxing you can do in the middle ages that would allow you to lead as good of a life as billions of people have today. (measured in things like health, food, entertainment, …) And those billions of people don't constantly have to defend their wealth against usurpers and competing powers. The only way to get to that broad wealth is with positive-sum games like trade and technology.

      The long take to watch is the Sarah Paine interview where she talks about "Continental Powers" vs "Maritime Powers". Excerpt here, but also watch the full thing:

      The Unpleasant Parts of the Book

      So back to the book. It makes sense that if you, as an author, want to talk about these things, you should set your story in the 19th century because back then these were real problems. Nowadays globalization and automation is lifting the world out of poverty one country at a time and this is great. Back then this was very much not the case. Colonialism was exploiting and destroying countries. But from today's perspective it's just so frustrating to read the opinions of people who had 19th century frameworks and didn't know how to solve this and then go about doing lots of bad things because their world view is so uninformed. Is that plausible? Yes. Is it fun to read as a 21st century person? No.

      The other part where I had to skip pages was that at some point in the book the "good guys" have to cover up a murder. The book makes this very unpleasant. They're stuck on a boat and have to somehow come up with a cover story to hide the murdered until the boat lands. This leads to high tension for weeks. When they finally land, you think it's over now, but no, now they meet the neighbor of the murdered person and so the tension is high for longer. After that's over they have to face the housekeeper and then coworkers and after I've had too much of this series of tense awkward encounters, the author ratchets it up even more by making them go to a social event where everyone will be suspicious that the murdered person is missing and yet the "good guys" have to go for some reason and have to somehow come up with implausible stories because their cover story has long ago fallen apart. I skipped that part because there really was no need to drag this whole thing out for so long and to keep on making me feel uncomfortable.

      Overall a Fascinating Book

      The book is still fascinating. Mainly this aspect of "adopting the world view of the people you oppose." Where the "good guys" are accepting the world view of the "bad guys" and then come up with really bad plans that work out really badly because they're operating within the wrong world view. (and also where the main love story doesn't work out because the Indian guy has accepted the world view of the colonizers and is unwilling to date a white woman (and also, actually, how the author feels the need to justify at the beginning of the book why it's OK for her as an American to write about Oxford. Why are you arguing with people like that? They're wrong, ignore them, nobody can tell you to not write this book, just write the book))

      It would be less fascinating if it treated these aspects from a 21st century perspective, but it only briefly gives voice to that and always gives the last word to people who are stuck in the 19th century. A view you only find in few prominent people today. Maybe Trump or Putin or the remaining communist regimes. I couldn't figure out for the entire book what the author actually believes. My main theory is that she has part of that Trumpian world view because she is so consistent in voicing it, but she is confused by it because anything else would seem really weird for a smart author in the 21st century, especially one who has read so much history. After all she is also able to write the other side.

      It's also fascinating how she constantly undermines the stated point of the book. "The Necessity of Violence" is the alternate title but whenever the "good guys" adopt this belief they make terrible decisions and don't achieve their goals. Similarly she chose to create a kind of magic that is so obviously positive-sum (just take a piece of silver, engrave some words, speak the words, and suddenly things around it are better in some way) that all of the zero-sum thinking of the characters in the book makes even less sense than it makes in the real world. Why write with such a strong opinion when the story works out exactly the opposite, undermining your own message?

      I mentioned that I wrote this whole review without actually looking up what R.F. Kuang believes. The experience was more interesting not knowing that, having this big uncertainty. I plan on looking her up as soon as I hit publish.

  4. May 22, 2026
    1. 🔗 IDA Plugin Updates IDA Plugin Updates on 2026-05-22 rss

      IDA Plugin Updates on 2026-05-22

      Activity:

      • capa
        • 88ba8f77: Sync capa rules submodule
        • c619ef51: Sync capa rules submodule
        • 9ac688b8: build(deps-dev): bump js-cookie from 3.0.5 to 3.0.7 in /web/explorer …
      • haruspex
        • bda544a6: chore: update dependencies
        • 0f42f58e: chore: update mozilla-actions/sccache-action in ci
      • hrtng
        • 560579b3: fix unflatterer looping and register size issues; fix "Auto turn on '…
      • rhabdomancer
        • c652bf18: chore: update mozilla-actions/sccache-action in ci
    2. 🔗 r/Yorkshire Descent down the B6270 w/ Boards of Canada rss

      Descent down the B6270 w/ Boards of Canada | submitted by /u/alanas4201
      [link] [comments]
      ---|---

    3. 🔗 r/LocalLLaMA NVIDIA Removes Gaming Revenue Category From Financial Reports rss

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

    4. 🔗 r/Leeds Summer w/o a social group rss

      with the lovely weather this weekend, it can be a bit isolating not knowing a lot of people in leeds, especially when everywhere seems to be constantly packed with groups and couples.

      what are some solo things we’re doing which don’t feel as scary or lonely? anyone in the same boat?

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

    5. 🔗 r/Yorkshire Some more from YWP rss

      Some more from YWP | I work here currently so apologies for all the images. It was a really sunny day and I got these at lunchtime. submitted by /u/Icy_Ebb_6862
      [link] [comments]
      ---|---

    6. 🔗 r/reverseengineering CTF with AI/LLM reverse engineering angles - intercepting streamed responses, replaying tokens, finding hidden endpoints (June 17-22) rss

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

    7. 🔗 r/york Mega Empires - York rss

      Mega Empires - York | Hi r/york. I am organising a game of Mega Empires up at Monks Cross on Saturday 27th June. This is a modern epic take on a classic civilization board game for up to 18 players. I have a handful of spaces left available, if you're interested see below or drop me a message! BGG link for the game: https://boardgamegeek.com/boardgame/339526/mega-empires
      Sign up: https://forms.gle/bLPx9Mdis5nqtMsz6 submitted by /u/Thisisnotasmile
      [link] [comments]
      ---|---

    8. 🔗 r/york Wavy Hair Hairdresser rss

      Hi I was wondering if anyone has recommendations for hair dressers who work with wavy hair? I have 2B hair and I’m going to York for Uni in September so I want to find a good hairdresser in advance

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

    9. 🔗 r/wiesbaden Vibrancy rss

      Moin,
      morgen soll ja das erste Event des Jahres von Vibrancy stattfinden. Also bis eben war noch nichts vor dem Kurhaus zu sehen. Jemand eine Ahnung ob die so kurzfristig alles aufbauen können?

      submitted by /u/Prestigious-Cod-8064
      [link] [comments]

    10. 🔗 r/Yorkshire Pub BBQ In Collingham rss

      Pub BBQ In Collingham | Needless to say, I scoffed a burger like a dog might. submitted by /u/Pitiful-Hearing5279
      [link] [comments]
      ---|---

    11. 🔗 r/reverseengineering Rebuilding Zyxel’s super-admin password flow in HTML from firmware/runtime notes rss

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

    12. 🔗 r/Yorkshire Paint thrown at antinracist protesters outside Hull Guildhall as police appeal for CCTV rss

      Paint thrown at antinracist protesters outside Hull Guildhall as police appeal for CCTV | submitted by /u/johnsmithoncemore
      [link] [comments]
      ---|---

    13. 🔗 r/wiesbaden Wiesbaden → Flughafen Frankfurt: Taxi, Uber oder Transfer? rss

      Hi zusammen,

      was ist die beste Möglichkeit, von Wiesbaden zum Flughafen Frankfurt zu kommen, wenn man 4–5 große Koffer dabei hat? Wir sind 2 Personen.

      Würdet ihr eher Taxi, Flughafentransfer, Uber oder etwas anderes empfehlen? Am besten unkompliziert und nicht zu teuer.

      Danke!

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

    14. 🔗 r/wiesbaden Body Street Biebrich Str. d. Republik 22 rss

      Can someone in the area confirm if Body Street EMS Gym is open? They don't respond to any emails and calls. If someone is in the area and can check for me that would be super nice! Google says they're still open but the last review was 5 months ago...

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

    15. 🔗 r/Yorkshire What’s a completely normal thing in Yorkshire that confuses people from elsewhere in the UK? rss

      For me it’s how people will still call somewhere “down road” even when it’s about 40 min away

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

    16. 🔗 r/LocalLLaMA DeepSeek is pushing forward with $10.29 billion financing round, with Liang Wenfeng committing to continue developing open-source AI models rather than pursuing short-term commercialization goals rss

      https://www.bloomberg.com/news/articles/2026-05-22/deepseek-founder-declares- agi-goal-as-10-billion-round-advances

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

    17. 🔗 r/york Snowdrops at St mary’s abbey 🫶 rss

      Snowdrops at St mary’s abbey 🫶 | @ Sue Gabbatiss submitted by /u/Juicewithextrapulp
      [link] [comments]
      ---|---

    18. 🔗 r/Yorkshire The Futuro House in Todmorden, West Yorkshire. It was a post-war futurist home designed to be easy to transport, deconstruct and quickly reconstruct on site. (1971) rss

      The Futuro House in Todmorden, West Yorkshire. It was a post-war futurist home designed to be easy to transport, deconstruct and quickly reconstruct on site. (1971) | submitted by /u/StephenMcGannon
      [link] [comments]
      ---|---

    19. 🔗 r/Leeds Beer gardens in headingley/Hyde park with real grass? rss

      Bit of a weird question maybe but are there any pubs in the headingley/hyde park area that have beer gardens with real grass? It just stood out to me as strange that they all have fake grass put down when none of the pubs in my hometown have it

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

    20. 🔗 r/Yorkshire Kirklees Reform councillors admit to not understanding how councils work at failed meeting to elect leader rss

      Kirklees Reform councillors admit to not understanding how councils work at failed meeting to elect leader | submitted by /u/johnsmithoncemore
      [link] [comments]
      ---|---

    21. 🔗 r/Leeds The sun is coming 🌞 rss

      Where are your favourite places to go around Leeds (or accessible from Leeds) on a hot day? Particularly interested in any toddler friendly recs

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

    22. 🔗 r/reverseengineering Reverse Engineered Google reCAPTCHA rss

      submitted by /u/Dapper-Profession552
      [link] [comments]

    23. 🔗 r/LocalLLaMA When your LLM treats data center GPUs like an optional DLC rss

      When your LLM treats data center GPUs like an optional DLC | submitted by /u/noprompt
      [link] [comments]
      ---|---

generated: May 25, 2026 at 13:01:31