🏡

to read (pdf)

generated: February 22, 2026 at 21:06:02

February 22, 2026
1. 🔗 radiac/nanodjango v0.15.0 release
  
  Version 0.15.0
2. 🔗 remorses/critique critique@0.1.118 release
  0.1.118
  - Syntax highlighting (critique, critique --web, critique review):
    
    Replace the non-existent remote Prisma WASM URL with a vendored parser binary at src/parsers/tree-sitter-prisma.wasm
    
    Load Prisma parser from local absolute path so Prisma highlighting works without relying on external hosting
  0.1.117
  - Syntax highlighting (critique, critique --web, critique review):
    
    Detect .prisma files as prisma filetype in diff syntax highlighting
    
    Register Prisma parser configuration with Tree-sitter highlights query source
3. 🔗 r/reverseengineering [ BETA UPDATE ] LCSAJdump v1.1.1-beta is out — x86-64 support finally lands rss
  
  submitted by /u/LCSAJdump
  [link] [comments]
4. 🔗 r/Leeds John Betjeman visiting Whitelocks. (B.B.C. 1968) rss
  
  submitted by /u/AllColoursSam
  [link] [comments]
5. 🔗 r/Yorkshire Pub recommendations rss
  
  Does anyone have good pub recommendations around Skipton, Keighley, Ilkley, Harrogate, Ripon etc? I'm going to be frequently visiting this area soon for my photography project, so any recommendations would be welcomed. Also in any other nice nearby towns, I'll check them out.
  
  submitted by /u/secretlythepotato
  [link] [comments]
6. 🔗 r/Leeds Places to spot fox? rss
  
  Hey! I’m an international student currently living in the Leeds.
  
  A friend of mine who’s studying down South of UK sent me a photo yesterday of a fox hanging out by his garden fence. And this might sound a bit weird, but I was honestly kind of jealous 😅
  
  Leeds is obviously one of the bigger cities in the UK, so I guess it’s harder to spot foxes just around residential areas here. But I was wondering are there any spots around Leeds where you’re relatively more likely to see foxes?
  
  submitted by /u/FriedbAconsPam
  [link] [comments]
7. 🔗 r/york I think Goshawk caught a pigeon out the sky next to me at the side of Foss bank car park! rss
  
  | submitted by /u/TrapperTrev
  [link] [comments]
  ---|---
8. 🔗 remorses/critique critique@0.1.116 release
  Web preview anchor links — more robust position detection
  - --web : Anchor IDs for file sections are now resolved from opentui layout coordinates instead of regex-scanning the rendered frame text
    
    Previously scanned frame lines for a filename +N-N pattern — fragile against code lines that happened to mimic that pattern
    
    Each file section container now gets a React ref; after render stabilization getComputedLayout().top gives the exact row for that section
    
    buildAnchorMap accepts { lineIndex, fileName }[] positions directly — simpler API, no false positives, no basename-fallback heuristic needed
    
    Removed now-unnecessary imports (getFileName, processFiles, parseGitDiffFiles, stripSubmoduleHeaders) from web-utils
  - Tests:
    
    Simplified buildAnchorMap unit tests to use the new direct-input API
    
    Dropped tests for the removed regex heuristics
    
    Added edge-case coverage: empty input, negative/NaN indexes, duplicate line indexes, slugify-empty filenames
    
    Fixed mockSpan helper to use RGBA.fromValues and include the required width field
9. 🔗 r/Yorkshire £150,000 funding to help reduce North Yorkshire cold deaths rss
  
  | submitted by /u/Kagedeah
  [link] [comments]
  ---|---
10. 🔗 badlogic/pi-mono v0.54.1 release
  Fixed
  - Externalized koffi from bun binary builds, reducing archive sizes by ~15MB per platform (e.g. darwin-arm64: 43MB -> 28MB). Koffi's Windows-only .node file is now shipped alongside the Windows binary only.
11. 🔗 r/Yorkshire Yorkshire Moors Wind Farm walking route recommendations rss
  
  I've long been weirdly entranced by wind turbines. I love seeing them off in the distance from the M62, these strange white giants sticking out of the moors like birthday candles.
  
  I've always wanted to see them up close.
  
  I live in Leeds - can you recommend any walking routes I can get to easily via train that can take me to a good wind farm? Even better if it's a loop.
  
  I'd rather not trespass or go too far off the beaten path if it can be avoided.
  
  submitted by /u/PancreousDiabeetus
  [link] [comments]
12. 🔗 r/LocalLLaMA Which one are you waiting for more: 9B or 35B? rss
  
  | submitted by /u/jacek2023
  [link] [comments]
  ---|---
13. 🔗 r/wiesbaden Rhein-Main Uferkonzept rss
  
  Wie steht ihr zum Rhein-Main Uferkonzept?
  
  Hier der Maßnahmenkatalog im PDF Format, da kann man easy den für einen selbst wichtigsten Flussabschnitt und die geplanten Veränderungen raussuchen.
  
  060.020.2.16-RMUK_Massnahmenkatalog_230201_web.pdf https://share.google/8CYKkzdEistaRPxt0
  
  Welche geplanten Maßnahmen sprechen euch am meisten an?
  
  Ich würde mir tatsächlich die Umsetzung aller geplanten Schritte für meinen Bereich (Kastel) wünschen, finde es klingt richtig cool teilweise.
  
  submitted by /u/newtwoothis
  [link] [comments]
14. 🔗 r/reverseengineering Obfusk8: lightweight Obfuscation library based on C++17 / Header Only for windows binaries rss
  
  submitted by /u/NoBad8130
  [link] [comments]
15. 🔗 r/Leeds Saw in Woodhouse Moor late last night rss
  
  Honestly kind of impressed, those things look heavy.
  
  submitted by /u/greg225
  [link] [comments]
16. 🔗 r/york Purple Street Lights rss
  
  I noticed last night that the street lights on the residential areas behind Poppleton Road Prinary school have been changed to purple LEDs. So Seldon Rd, Poplar St, Carrington Ave, Oak St.
  
  I can't figure out why and the shade is really quite jarring.
  
  The only other uses of this kind of light have been areas of significant drug use, but I dont believe this area fits that bill, compared to other areas of town with "normal" coloured lighting.
  
  Thoughts
  
  submitted by /u/BluefearHere
  [link] [comments]
17. 🔗 HexRaysSA/plugin-repository commits sync repo: +2 plugins, -2 plugins, +8 releases, -3 releases, ~1 changed rss
```
sync repo: +2 plugins, -2 plugins, +8 releases, -3 releases, ~1 changed

## New plugins
- [Binwalk](https://github.com/kevinmuoz/binwalk-reversing-plugin) (0.0.1)
- [DBImporter](https://github.com/HexRaysSA/ida-dbimporter) (0.0.1)

## New releases
- [augur](https://github.com/0xdea/augur): 0.8.0
- [haruspex](https://github.com/0xdea/haruspex): 0.8.0
- [hrtng](https://github.com/KasperskyLab/hrtng): 3.8.88
- [idalib-rust-bindings](https://github.com/idalib-rs/idalib): 0.8.1, 0.8.0
- [rhabdomancer](https://github.com/0xdea/rhabdomancer): 0.8.0

## Changes
- [iOSHelper](https://github.com/yoavst/ida-ios-helper):
  - 1.0.19: archive contents changed, download URL changed
- [idalib-rust-bindings](https://github.com/idalib-rs/idalib):
  - host changed: binarly-io/idalib → idalib-rs/idalib
  - removed version(s): 0.7.2

## Removed plugins
- comida
- ipyida
```
18. 🔗 r/york Hand tattooing at Jorvik festival. Effort has been made to blur out the face. rss
  
  | submitted by /u/tyw7
  [link] [comments]
  ---|---
February 21, 2026
1. 🔗 IDA Plugin Updates IDA Plugin Updates on 2026-02-21 rss
  IDA Plugin Updates on 2026-02-21
  
  New Releases:
  - binwalk-reversing-plugin v0.0.1
  Activity:
  - binwalk-reversing-plugin
    
    f394c968: feat: index
    
    5ce6c1c8: feat: core
    
    4453ff6f: feat: images
    
    cff2d9e0: Initial commit
  - idalib
    
    668e93cf: release v0.8.1
    
    663e3c7e: fix build via windows cross tools (#62)
    
    e21952f6: add slack workspace link (#61)
  - idamcp
    
    f3bd76a6: fix compat bugs
    
    7c658532: Add multi ports
  - msc-thesis-LLMs-to-rank-decompilers
    
    99c331e9: update latex
    
    a86018f3: new reps to check
  - Tenet-IDA9.0
    
    8e066307: Update README.md
    
    310fb4fc: Update README.md
2. 🔗 r/york Bakers/ Cakes in York rss
  
  | I'm in York at the end of April and I'm looking for somewhere to have my birthday cake made, I don't want anything too crazy but I was wondering if anyone had any recommendations of bakery pages/ small Businesses/ shops that I could order from? (This is my cake from last year and I'd like something similar) submitted by /u/moonlight_brat
  [link] [comments]
  ---|---
3. 🔗 r/LocalLLaMA Favourite niche usecases? rss
  
  | submitted by /u/Figai
  [link] [comments]
  ---|---
4. 🔗 HexRaysSA/plugin-repository commits Merge pull request #22 from kevinmuoz/v1 rss
```
Merge pull request #22 from kevinmuoz/v1
```
5. 🔗 Register Spill Joy & Curiosity #75 rss
  Where's software going? Is software… dead? Or will there be more software than we ever thought possible? Or is it going to disappear, into the agents? Or is it going to grow and grow and then truly eat the world? Who's going to create it?
  
  There's few things right now that I find more fascinating than these questions. Of course, I don't have answers and I don't think anyone has. Guesses, sure. Theories, absolutely. Anecdotes? Here's some.
  
  Geoffrey Litt, standing in a hotel gym, asked Claude for a workout plan and got an app that guides him through the plan. Huh. Then Ryan Florence threw away his workout app and just asked ChatGPT's voice mode to guide him through a workout. Where's the software gone?
  
  A couple weeks back I thought: maybe I should set up Clawdbot and hook it up to our shopping list in Todoist and then my wife and I can use a group chat to manage that list. We could even use voice messages:__ hey pal I'm in the car woops wait a second … yeah we're out of paper towels. That'd be cool, right? But then: wait, why would I need Todoist? State could just live in that conversation or on Clawdbot's disk, right? And then: but sometimes I do want a better UI than a group chat, don't I? But when and why?
  
  This week I was this close to typing something into the Slack search bar. I already had some keywords and combinations of keywords ready to go. I had already put the cursor in when I remembered that we have agg, an internal tool that Tim blind-coded and that connects to Slack and Google workspaces and whatnot, and so I asked Amp: hey, didn't so and so say that we they migrated this thing and now we all need to? Amp via agg found it in five seconds. No keyword, no UI. Okay.
  
  As Alex says: "It feels like a maxim is emerging - if your software is useful to agents, your product is going to be 10x more valuable than before, but if your software is built for humans, you're dead." And Sahil Lavigna says that "gh is the new GitHub."
  
  But there is still software, isn't there? I'm typing this through software. And I had Amp create many hundreds of lines of personal software for me, but that software is so personal that I won't release it, because why bother? The cost of generalizing it is higher than the cost of creating it. So you won't ever see it. Invisible software.
  
  Say that I do release some software that took me an hour to create. Or let's say six hours. A small useful app, with some heft to it. You know what I mean. A good workout tracker. Or a little menu bar app. Or a browser extension. Say I sell it for $5. Won't a hundred competitors be able to recreate what I did in thirty minutes? Prices will go to zero. Why bother?
  
  Last anecdote. I've been meaning to create a little booklet. A physical thing, printed professionally. Weeks ago I had Nano Banana and ChatGPT tag-teaming and they created the logo that'd go on the front. Then work stalled because I couldn't be bothered to look up the dimensions the print company needs and CMYK and PDFs and all of that and ugh, please. So I sent exactly that to ChatGPT: here's the URL of the product description, here's the logo in 4 formats, here's the mockup someone (wink wink) created, please help me man. It ran for 15, 20 minutes and gave me a PDF. I uploaded it on the printer's website, following the 6 steps ChatGPT outlined for me, got an error, told ChatGPT about the error also asked for some adjustments, got a new PDF, uploaded it, got the green checkmark, put my credit card in and now the booklet's on its way.
  
  I then checked what ChatGPT did, in agent mode, and turns ou: it wrote a lot of code. It essentially created the PDF I needed by writing Python. Many, many lines of Python. And now they're gone and no one would've seen then if I hadn't looked.
  
  So, where's the software going?
  - We at Amp think the coding agent is dead. Or maybe we should've said it's solved. Or that the text editor is dead. Point being: what we have right now isn't the future. There's more to build. And this is the model that made us realize it: GPT-5.3-Codex.
  - Don't believe us? Say it to our face. Most of the Amp team is in Singapore this week. Join us on Thursday. (I'm writing this at the airport.)
  - Harness engineering: leveraging Codex in an agent-first world, on the OpenAI blog. This is some of the best writing on agents hitting the real world and where this ride is going. You should read the whole thing, but this bit in particular stayed with me: "As Codex's throughput increased, many conventional engineering norms became counterproductive. The repository operates with minimal blocking merge gates. Pull requests are short-lived. Test flakes are often addressed with follow-up runs rather than blocking progress indefinitely. In a system where agent throughput far exceeds human attention, corrections are cheap, and waiting is expensive."
  - How will OpenAI compete? by Benedict Evans. Great, as always.
  - Chris Lattner took a close look at the C compiler produced by Claude Code. I have to admit that I started reading with the expectation that it's going to be about the compiler internals and what the AI got right and what it got wrong. And yes, that's in there, but there's more: thoughts about the AI in general, about IP law, about the shifting role of software engineers, about AI use at Modular. "Lower barriers to implementation do not reduce the importance of engineers; instead, they elevate the importance of vision, judgment, and taste. When creation becomes easier, deciding what is worth creating becomes the harder problem. AI accelerates execution, but meaning, direction, and responsibility remain fundamentally human."
  - Entertaining and interesting: How does Docusign have 7,000 employees?
  - Can Opus 4.6 do Category Theory in Lean? You know me: I don't understand any of the formulas in there and when I read "endofunctor" I do that Homer Simpson stare, but still (or because?) I found this very fascinating. "When this layer becomes trivial, we get to spend our time on the parts that actually matter: choosing the right abstractions, seeing the connections between structures, deciding what's worth formalizing in the first place. The proof assistant becomes less of a bureaucratic obstacle and more of a genuine thinking tool. We get to build higher." When category theory and formal specification languages become mainstream due to AI, call me.
  - AI fatigue is real and nobody talks about it: "When each task takes less time, you don't do fewer tasks. You do more tasks. Your capacity appears to expand, so the work expands to fill it. And then some. Your manager sees you shipping faster, so the expectations adjust. You see yourself shipping faster, so your own expectations adjust. The baseline moves. Before AI, I might spend a full day on one design problem. I'd sketch on paper, think in the shower, go for a walk, come back with clarity. The pace was slow but the cognitive load was manageable. One problem. One day. Deep focus." I find this very fascinating to think about, because it's true, isn't it? Back in the olden days, say in 2024, you could have a full day of programming in which you did nothing but program and yet there would still be moments of mindless execution that let you recover from moments of high concentration and focus. Now, with the mindless execution being done by the mindless, there's nothing left to act as a buffer between the intense moments. Except maybe distraction.
  - No Skill. No Taste.
  - A "a Matt Levine style explanation of how OAuth works" given by Blaine, who, 19 years ago, "wrote the first sketch of an OAuth specification". We need more explanations like this!
  - This post has a lot of really interesting thoughts on where software as a business is going. This part here, on building financial software, is illustrative of some trends, I think: "Zero custom parsers. Zero industry-specific classifiers. Why? Because frontier models already know how to navigate a 10-K. They know that Home Depot's ticker is HD. […] Frontier models already know how to parse SEC filings from their training data. They understand the structure of a 10-K, where to find revenue recognition policies, how to reconcile GAAP and non-GAAP figures. You don't need to build a parser. The model IS the parser. Feed it a 10-K and it can answer any question about it. […] The data isn't worthless. But the 'making it searchable' layer, which is where a lot of the value and pricing power lived, is collapsing." Replace 'searchable' with other abilities and you see how it applies to more than just software to navigate SEC filings. And then, of course, there's competition: "The critical insight is that competition doesn't increase linearly--it explodes combinatorially. You don't go from 3 incumbents to 4. You go from 3 to 300. And that's what craters pricing power. Before LLMs, each vertical had 2-3 dominant players commanding premium prices because the barriers to entry were insurmountable. That math changes completely when 50 AI-native startups can offer 80% of the capability at 20% of the price." We already had five thousand TODO apps. What's the next category of software in which there'll be five thousand alternatives, selling for $5.99?
  - Similarly: "if your product isn't a system of record that ai tools can be built on top of, you're increasingly hard to justify keeping" But then the question is: how hard is it to reproduce that system of record? Todoist: easy. Your company's pay slips? Hard. Analytics? Performance data? Monitoring? Errors? Tickets?
  - Sean Goedecke compared how the recently released "fast" modes by OpenAI and Anthropic differ: Two different tricks for fast LLM inference. Interesting stuff, especially since he now collected and responded to some of the comments he got.
  - I Sold Out for $20 a Month and All I Got Was This Perfectly Generated Terraform. This is some real stuff -- some true stuff. I love the honesty and the humility. I love the "band of Eastern European programmers who chain smoke during calls and whose motto is basically 'we never miss a deadline'" and I love this part here: "I also just have trouble with the idea that this is my career and the thing I spend my limited time on earth doing and the quality of it doesn't matter. I delight in craftsmanship when I encounter it in almost any discipline. I love it when you walk into an old house and see all the hand crafted details everywhere that don't make economic sense but still look beautiful. I adore when someone has carefully selected the perfect font to match something. […] When I asked my EVE friend about it on a recent TeamSpeak session, he was quiet for awhile. I thought that maybe my moral dilemma had shocked him into silence. Then he said, 'You know what the difference is between you and me? I know I'm a mercenary. You thought you were an artist. We're both guys who type for money.'"
  - 15,597 tok/s. Holy shit. And here's how they did it. Are there any physical or theoretical limits that would stop someone from doing the same for, say, GPT-5.3-Codex in a few years?
  - The Only Moat Left Is Money: "The effort is gone. Effort was the filter. I launched something last week. 14 people signed up -- no ads, just a couple of posts. 14 real people who didn't have to. That number is tiny and it felt like something. Then I sat down to think about what it would take to grow it and I couldn't look at that math for very long. The people winning mostly had a head start. Or they have money. Usually both. When creation was hard, skill was the differentiator: you had to actually be good to make something worth showing. Now the barrier is near zero, so you need reach. Reach costs money or it costs years. Probably both." I'm not sure I believe that effort doesn't count anymore, but the game is changing, which is fascinating and scary and exciting and crazy.
  - Child's Play, subtitled: tech's new generation and the end of thinking. Excellent.
  - The Software Development Lifecycle Is Dead. Not too sure about the specifics, but you know me: I agree.
  - "I built an agent for researching, coding, and running generative art animations for 16-segment displays. Will open source code and hardware design files soon."
  - Andy Coenen, who built the wonderful isometric nyc, on The Software Industrial Revolution. It's very, very good. To pick just one of the parts worth picking: "The old golden age is over, and it ain't coming back - no more 'rest and vest', no more ping-pong offsites and five-star catered lunches. But a new 'golden age' is coming - no more nights staring red-eyed at empty stack overflow issues, no more weeks of alignment meetings to ship a prototype. I believe it's never been a better time to build - not just software but anything you can dream of. The world is yours if you embrace this new reality and learn how to really use these tools". The other part worth mentioning is the one about "personal apps": sure, yes, grandma won't use AI to write her own sudoku app, but, as Andy suggests here, there are so many other people -- _professionals! -- _who sure would love to build better research tools for themselves.
  - I'm pretty sure this just changed how I think about intelligence: why aren't smart people happier? (That little "what if you booted up an AI in ancient Greece?" thought experiment is fun too.)
  - "Two old engineers were talking of their lives and boasting of their greatest projects. One of the engineers explained how he had designed the largest bridge ever made."
  - Robin Sloan on how far AI can expand: flood fill vs. the magic circle. Interesting to think about, but I can't help but wonder: does it matter that AI can't touch the physical world, when your career is 99% digital and you're looking at a screen a lot?
  - Jason Fried was on the David Senra podcast. What a perspective this guy has. Inspiring.
  - I've seen many, many, many stand-up specials over the years, because I enjoy stand-up comedy a lot and very earnestly believe it's one of the highest art forms we humans have created. Yes, I'm serious. I'm German. If there's one thing I don't joke around about it's comedy. But a stand-up special that makes me actually laugh out loud is a rare one. Kevin Nealon's latest special Loose in the Crotch did that. I nearly spit out food. God damn did I fall in love with that special. I've watched it twice since Tuesday. I know it's not everyone's cup of tea and if you don't like it you should keep that to yourself. But let me know if you do.
  - "This Fab Faux recording of most of side two of Abbey Road is a live, in the studio performance for a two camera video shoot. In the end, there were only three minor guitar fixes and each section was recorded in no more than three takes (most were two). There are NO added overdubs within this performance. The audio is pure." Uploaded fourteen years ago. I think I started watching this video in 2010, when it was uploaded to Vimeo. Treat yourself.
  If you have thoughts on where this is going or want to find out, you should subscribe:
6. 🔗 r/LocalLLaMA PSA: The software “Shade” is a fraudulent, plagiarized copy of Heretic rss
  
  Three days ago, the following repository was published, which its “creator” has been aggressively promoting on various channels since then:
  
  https://github.com/assemsabry/shade
  
  The entire source code in the repository is plagiarized from Heretic (https://github.com/p-e-w/heretic), with only the project name and the copyright notice replaced, claiming “original authorship” of everything. The repository does not acknowledge Heretic as its source, and has erased the commit history and the names of all Heretic contributors.
  
  I and several others have called the repository owner out, but he has deleted all issues and tried to cover up his wrongdoing by adding some bogus “additional features” using an AI agent. A quick look at the source files, however, reveals that they are still 95% identical to Heretic’s code. In some cases, only the copyright notice was replaced.
  
  I can only assume that the ultimate goal is to push malware of some sort, and strongly advise people to stay clear of this plagiarized repository.
  
  This is one of several incidents where malicious actors tried to profit from Heretic’s surging popularity during the past days, when it reached #1 on the GitHub trending chart and was posted in various social feeds that cater to scammers.
  
  Please also see https://github.com/p-e-w/heretic/issues/167
  
  I’m doing everything in my power to keep Heretic clean and available to everyone. Thank you for your encouragement in the past few months, it means the world to me!
  
  submitted by /u/-p-e-w-
  [link] [comments]
7. 🔗 r/york Roman Bath at York (under pub) rss
  
  submitted by /u/tyw7
  [link] [comments]
8. 🔗 r/wiesbaden Streik am Dienstag 24.02.2026 rss
  
  https://www.hessenschau.de/wirtschaft/kassel-frankfurt-wiesbaden-verdi- kuendigt-streik-im-nahverkehr-an---ausfaelle-am-dienstag-v4,verdi-streik- nahverkehr-hessen-100.html
  
  Ich will nicht mehr. Ich kann nicht mehr. Ich halte das alles nicht mehr aus.
  
  submitted by /u/Senoculidae
  [link] [comments]
9. 🔗 r/reverseengineering processhacker mcp ( this is dynamic mcp server for runtime analysis and process hacking. it is like processhacker but for ai agents) rss
  
  submitted by /u/Humble-Plastic-5285
  [link] [comments]
10. 🔗 r/Leeds Any decent smaller comedy clubs? rss
  
  Hello everyone so I like City Varieties and The Cardigan Arms pub for comedy in Leeds. Can anyone recommend a decent alternative that isn't too rowdy with decent seats?
  
  City Varieties is a beautiful venue and has the bigger comedians but I do like watching local comics too. I don't drive so has to be City centre, Kirkstall, Horsforth, Headingley kinda areas.
  
  Any suggestions would be super for me & my friend👌 cheers! X
  
  submitted by /u/MasterMembership4506
  [link] [comments]
11. 🔗 r/Yorkshire What's your opinion on Wakefield and the 5 towns? rss
  
  An area of Yorkshire rarely mentioned in discussions, thought i'd shine a light on it!
  
  submitted by /u/aaaaaaa_aaaaaa_aaa
  [link] [comments]
12. 🔗 r/Yorkshire Thinking of visiting the Dales towards the end of summer. rss
  
  Not entirely sure where the best place to stay would be, I'm thinking skipton/settle/ingleton as I am relying on trains from Manchester, want to do some hiking/photography
  
  Are any of them considered cheaper to stay at than others ?
  
  Never been in this area before, so know nothing about the place other than anyone whose ever been grabs you and slaps you about until you say you'll visit :D
  
  submitted by /u/zibafu
  [link] [comments]
13. 🔗 r/wiesbaden Gratis Rollenspiel Tag 2026: 28.3., Phantasos Arena Wiesbaden, 15 Runden rss
  
  Anmeldung: Discord-Server der Phantasos Arena: https://discord.gg/2A6vjQ58yg
  
  Daggerheart, DnD, Shadowrun, Cyberpunk RED, Mausritter, Alien, Mothership, Outgunned uvm
  
  submitted by /u/Bitter-Secretary6006
  [link] [comments]
14. 🔗 r/LocalLLaMA they have Karpathy, we are doomed ;) rss
  
  | (added second image for the context) submitted by /u/jacek2023
  [link] [comments]
  ---|---
15. 🔗 HexRaysSA/plugin-repository commits feat: cleanup and new repo rss
```
feat: cleanup and new repo
```
16. 🔗 lief-project/LIEF 0.17.4 release
  
  https://lief.re/doc/stable/changelog.html#february-21th-2026
17. 🔗 r/york York Minster: Historic Graffiti rss
  
  | submitted by /u/Julija82
  [link] [comments]
  ---|---
18. 🔗 r/Yorkshire Yorkshire Water rss
  
  Just got a bill with 8% price increase. Bastards.
  
  Edit - looking more closely at the bill, the actual increase it’s much higher (around 30%) - it’s states ‘an average of 8% increase’ on the bill, despite their press releases saying 5.6%. Don’t know how they get away with such lack of clarity!
  
  submitted by /u/Exciting_Stretch_847
  [link] [comments]
19. 🔗 r/reverseengineering [Technical] Implementing a CRT-Free Sovereign PE: Custom IAT reconstruction and Hybrid EXE/DLL loading without MSVCRT rss
  
  submitted by /u/Key_Handle_8753
  [link] [comments]
20. 🔗 matklad Wrapping Code Comments rss
  Wrapping Code Comments
  
  Feb 21, 2026
  
  I was today years old when I realized that:
  - Code and code comments ideally should be wrapped to a different column.
  - For comments, the width should be relative to the start of the comment.
  It’s a good idea to limit line length to about 100 columns. This is a physical limit, the width at which you can still comfortably fit two editors side by side (see Size Matters). Note an apparent contradiction: the optimal width for readable prose is usually taken to be narrower, 60–70 columns. The contradiction is resolved by noticing that, for code, indentation eats into usable space. Typically, code is much less typographically dense than prose.
  
  Still, I find comment blocks easier to read when they are wrapped narrower than the surrounding code. I want lines to be wrapped at 100, and content of comments to be wrapped at 70 (unless that pushes overall line to be longer than 100). That is, I want layout like this (using 20/30 rulers instead of 70/100, for illustrative purposes):
```
// Top level comments
// can be this wide.
const S = struct {
    // Nested comments are
    // also this wide, but
    // are shifted right.
    fn f() void {
        switch (value) {
            0 => {
                // But there is
                // a hard limit.
            }
        }
    }
}
```
  This feels obvious in retrospect, but notably isn’t be well-supported by the tools? The VS Code extension I use allows configuring dedicated fill column for comments, but doesn’t make it relative , so indented comment blocks are always narrower than top-level ones. Emacs M-q also doesn’t do relative wrapping out of the box!
  
  Aside on hard-wrapping: should we bother with wrapping comments at all? Can’t we rely on our editor to implement soft-wrapping? The problem with soft- wrapping is that you can’t soft-wrap text correctly without understanding its meaning. Consider a markdown list:
```
A list:
  * item one,
  * item two.
```
  If the first item is long enough to necessitate wrapping, the wrapped line should also be indented, which requires parsing the text as markdown first:
```
A list:
  * item one which is long enough
    necessitate wrapping,
  * item two.
```
21. 🔗 Stephen Diehl Optimal Caverna Gameplay via Formal Methods rss
  Optimal Caverna Gameplay via Formal Methods
  
  I always win at Caverna (Uwe Rosenberg's classic European worker placement tabletop board game). Always. But "always" just means "every time so far," and I needed something with more mathematical permanence. So I formalized the entire game in Lean 4 and proved that my strategy is the unique weakly dominant pure strategy across every possible game configuration. My friends think this is excessive. My friends also lose at Caverna. Unrelated, I don't get invited to board game night much anymore.
  
  Caverna: The Cave Farmers is the 2013 sequel to Agricola, a game about feeding dwarfs who live in caves and do a suspicious amount of farming. You place workers, gather resources, breed animals, excavate caverns, furnish rooms, and at the end of 12 rounds the scoring formula totals up everything you've accomplished and everything you failed to accomplish. It's a good game. It's also, in the 2-player variant, a finite deterministic perfect-information system with discrete phases, which means it's a labeled transition system, which means it's amenable to formal verification. So I did that.
  
  The project is about 3,000 lines of Lean 4 spread across 19 modules: 11 definition files modeling the complete game (all 24 action spaces, all 48 unique furnishing tiles, the expedition loot system, board geometry, harvest schedule, scoring formula) and 8 theorem files containing 176 machine-checked proofs. The model covers all 2,880 possible 2-player game setups (144 card orderings times 20 harvest marker placements). The main result is that furnishing rush is the weakly dominant strategy. It is the optimal response to every opponent, in every setup, regardless of which cards come out when or where the harvest markers land.
  
  The interactive proof blueprint has the full derivation with a dependency graph showing how every theorem connects. The source code compiles.
  
  Labeled Transition Systems
  
  A labeled transition system (LTS) is a triple $(S, A, T)$ where $S$ is a set of states, $A$ is a set of actions, and $T \subseteq S \times A \times S$ is a transition relation specifying which state changes are legal. You start in some initial state satisfying an init predicate. The system evolves by taking actions: if $(s, a, s') \in T$, you can move from state $s$ to state $s'$ by performing action $a$. A state is reachable if there's a finite chain of transitions from an initial state to it. A property is an invariant if it holds on every reachable state.
  
  In Lean 4, the LTS is three fields:
```
structure LTS (State : Type) (Action : Type) where
  init : State -> Prop
  trans : State -> Action -> State -> Prop
```
  Reachability is an inductive type with two constructors: initial states are reachable, and if you can reach $s$ and take action $a$ to get to $s'$, then $s'$ is reachable:
```
inductive Reachable (sys : LTS State Action) : State -> Prop where
  | init : forall s, sys.init s -> Reachable sys s
  | step : forall s a s', Reachable sys s -> sys.trans s a s' -> Reachable sys s'
```
  In plain terms: the LTS is the rulebook encoded as a state transition relation. init says what the starting board looks like, and trans encodes every legal move as a state-to-state constraint. The entire Caverna rulebook fits in about 250 lines of Lean: a 160-line applyPlacement function matching on all 24 action spaces with their effects, and a 90-line cavernaLTS definition wiring up phase transitions, harvest logic, and round progression. It's a relation rather than a function because Caverna has sub-choices within actions (sow grain vs. sow vegetable, which furnishing tile to install, which loot to take), so a single action space placement can lead to multiple successor states. The relation captures all of them.
  
  Once you have init and trans, you prove a property holds on all reachable states without enumerating them. You prove the base case (holds on initial states) and the inductive step (every valid transition preserves it). This is strictly stronger than testing. Testing checks specific play sequences. An invariant proof covers every sequence of legal moves across every setup, including sequences no human would ever play.
  
  Here's a small fragment of the Caverna LTS to give the flavor of how a round of play works as a state machine:
  
  Each state records the player's resources and remaining dwarfs to place. Transitions correspond to action space selections. With 13 initial action spaces and 2 dwarfs, even a single round produces $13 \times 12 = 156$ placement sequences. Over 12 rounds with family growth, the branching factor is astronomical, but the LTS doesn't care. The structure is finite, and every path through it is covered by the invariant proofs.
  
  The Game as a Transition Relation
  
  Board games are natural LTS candidates. In Caverna 2-player, the states are the complete game configurations (round number, phase, both players' inventories, board layouts, available action spaces), the actions are dwarf placements and harvest events, and the transition relation encodes the rulebook.
  
  The game has five phases that cycle within each round:
```
inductive Phase where
  | placeP1      -- player 1 places a dwarf
  | placeP2      -- player 2 places a dwarf
  | harvest      -- harvest phase (feeding, breeding, fields)
  | roundEnd     -- round cleanup, advance to next round
  | gameOver     -- game has ended
```
  The full game state tracks everything both players could possibly have, plus the global state of the board:
```
structure GState where
  round : Nat
  phase : Phase
  p1 : FullPlayer
  p2 : FullPlayer
  p1IsFirst : Bool
  placementsLeft : Nat
  acc : AccState
  occupiedSpaces : List ActionSpaceId := []
  harvestSchedule : Nat -> HarvestEvent
  wishIsUrgent : Bool := false
```
  The transition relation is a single function with a match on (gs.phase, act). Each case is a game rule. Here's the core of the placement logic for Player 1:
```
def cavernaLTS (schedule : Nat -> HarvestEvent) :
    TransitionSystem.LTS GState GameAction where
  init := fun gs => gs = initFullGState schedule
  trans := fun gs act gs' =>
    match gs.phase, act with
    | .placeP1, .place space choice =>
      spaceAvailable gs.round space = true /\
      spaceUnoccupied gs space = true /\
      gs.placementsLeft > 0 /\
      (let (p1', acc') := applyPlacement gs.p1 gs space choice
       let newPlacements := gs.placementsLeft - 1
       let newOccupied := space :: gs.occupiedSpaces
       if newPlacements == 0 then
         gs' = { gs with p1 := p1', acc := acc',
                         phase := .harvest, placementsLeft := 0,
                         occupiedSpaces := newOccupied }
       else
         gs' = { gs with p1 := p1', acc := acc',
                         phase := .placeP2,
                         placementsLeft := newPlacements,
                         occupiedSpaces := newOccupied })
    -- ... Player 2, harvest, round end, game over ...
    | _, _ => False
```
  That last line is beautiful. | _, _ => False says: any action not explicitly listed is illegal. The transition relation is closed. No undefined behavior, no edge cases, no "the rules don't say I can't." If it's not in the match, it doesn't happen.
  
  The applyPlacement function is a 250-line match on all 24 action spaces, each encoding the exact effect from the rulebook. Blacksmithing forges a weapon from ore and runs an expedition. Wish for Children can only grow your family if you have a dwelling with capacity. Excavation gives you stone and lets you carve out cavern/tunnel pairs. Every sub-choice (sow grain vs. sow vegetable, build small pasture vs. large pasture, which furnishing tile to install) is a branch in the ActionChoice type.
  
  The Game Timeline
  
  Twelve rounds. Green nodes are harvest rounds where dwarfs must be fed. Two critical milestones: "Wish for Children" at round 4 enables the first family growth (from 2 dwarfs to 3), and "Family Life" at round 8 enables the second (3 to 5, eventually). One new action space reveals each round, growing from 13 to 24 available choices. The interaction between when cards flip and when harvests hit is the clock that drives the entire strategic analysis.
  
  The timeline matters because of this: without growth you get 44 total dwarf placements across all 12 rounds. With one growth at round 4, you get 47. With both growths, you get 56. That's a 27% increase in total actions from growing your family as fast as possible, and since actions are the binding constraint on everything else (scoring, food, resources), the 12-placement gap between "no growth" and "both growths" is the single most important strategic lever in the game.
  
  Refinement Types: Making Illegal States Unrepresentable
  
  One of the most satisfying patterns in the formalization is using dependent types to make illegal game states impossible to construct. Weapons are the clearest example. In the physical game, weapon strength ranges from 1 to 14. You could model this as a bare Nat and hope nobody passes in 0 or 15. Or you could make the type system enforce the constraint:
```
structure Weapon where
  strength : Nat
  h__min : strength >= 1
  h__max : strength <= 14
```
  Every Weapon value carries proof that its strength is in range. This means forgeWeapon must produce evidence that the forged strength is valid, and upgradeWeapon must show that incrementing stays within bounds:
```
def forgeWeapon (oreSpent : Nat) (h__pos : oreSpent >= 1) : Option Weapon :=
  if h : oreSpent <= maxInitialWeaponStrength then
    some { strength := oreSpent
         , h__min := h__pos
         , h__max := by simp [maxInitialWeaponStrength] at h; omega }
  else
    none

def upgradeWeapon (w : Weapon) : Weapon :=
  if h : w.strength < maxWeaponStrength then
    { strength := w.strength + 1
    , h__min := by omega
    , h__max := by simp [maxWeaponStrength] at h; omega }
  else
    w
```
  The by omega calls are Lean's linear arithmetic tactic closing the proof obligations automatically. If w.strength < 14, then w.strength + 1 <= 14. If oreSpent >= 1, then strength >= 1. The type checker verifies this at compile time. No weapon in the entire formalization can ever have strength 0 or 15.
  
  The same pattern shows up in RoundPlacements, which carries proof that all four dwarf placements within a round go to distinct action spaces:
```
structure RoundPlacements where
  firstPlayer1  : ActionSpaceId
  secondPlayer1 : ActionSpaceId
  firstPlayer2  : ActionSpaceId
  secondPlayer2 : ActionSpaceId
  h__distinct12 : firstPlayer1 != secondPlayer1
  h__distinct13 : firstPlayer1 != firstPlayer2
  h__distinct14 : firstPlayer1 != secondPlayer2
  h__distinct23 : secondPlayer1 != firstPlayer2
  h__distinct24 : secondPlayer1 != secondPlayer2
  h__distinct34 : firstPlayer2 != secondPlayer2
```
  Six distinctness proofs, one for each pair. You literally cannot construct a RoundPlacements where two dwarfs share an action space. The game rule is baked into the type.
  
  The Weapon System
  
  Weapons are forged at strength 1 through 8 (costing that many ore), then grow by +1 per expedition, capping at 14. The blue range is forgeable; the peach range requires expedition grinding. Cattle loot unlocks at strength 9, which means even if you forge at max (8 ore), you still need at least one expedition before you can get cattle.
  
  The loot table is an inductive type with minimum strength requirements for each item:
```
def LootItem.minStrength : LootItem -> Nat
  | .allWeaponsPlus1    => 1
  | .dog                => 1
  | .wood               => 1
  | .grain              => 2
  | .sheep              => 2
  | .stone              => 3
  | .donkey             => 3
  | .ore                => 4
  | .wildBoar           => 4
  | .stableFree         => 5
  | .gold2              => 6
  | .furnishCavern      => 7
  | .buildFencesCheap   => 8
  | .cattle             => 9
  | .dwelling           => 10
  | .sow                => 11
  | .breedTwoTypes      => 12
  | .furnishCavernAgain => 14
```
  At strength 1 you can loot a dog or a stick. At strength 14 you can furnish a second cavern for free. The loot count at key strengths: 3 at strength 1, 13 at strength 8, 18 at strength 14. That's 5 premium items (cattle, dwelling, sow, breed, second furnish) locked behind the expedition grind. Whether the ore investment is worth it is the core question of the weapon rush archetype, and the answer turns out to be: no, not quite.
  
  The Universal Food Crisis
  
  Every strategy in Caverna must solve the same problem before anything else. Both players face a food deficit at the first harvest:
  
  Player 1 starts with 1 food and needs 4 (2 dwarfs times 2 food each). Player 2 starts with 2 food and needs 4. The gaps are 3 and 2 respectively. This is proven as universal__food__crisis:
```
theorem universal_food_crisis :
    feedingCost 2 0 - startingFoodP1 = 3 /\
    feedingCost 2 0 - startingFoodP2 = 2 := by decide
```
  The implication (food__crisis__shapes__all__strategies) is that every viable archetype must spend its first few actions on food acquisition. There's no "skip feeding and go straight to scoring" option. The begging marker penalty is $-3$ points each, and the theorem absolute__floor__is__neg55 shows that a player who takes zero actions across all rounds scores $-55$. The food crisis isn't optional; it's structural.
  
  The food conversion network itself is a delightful mess of exchange rates. Cattle gives 4 food per animal, wild boar gives 3, sheep gives 2, grain gives 1, vegetables give 2, gold converts lossily at $n-1$ (1 gold is wasted as overhead), and rubies are emergency food at 2+ each. And then there are donkeys, which have a superlinear pairing bonus that I spent an embarrassing amount of time formalizing:
```
def donkeyFoodValue (n : Nat) : Nat :=
  let pairs := n / 2
  let remainder := n % 2
  pairs * 3 + remainder * 1

theorem donkey__superlinear :
    donkeyFoodValue 2 > donkeyFoodValue 1 + donkeyFoodValue 1 := by decide
```
  Two donkeys together yield 3 food, but individually they'd give 1 + 1 = 2. The whole is greater than the sum of its parts. Uwe Rosenberg almost certainly didn't think about this as a super-additivity property of a set function, but that's what it is, and Lean can prove it.
  
  The Feeding Cascade
  
  The feeding function is the core survival mechanic. When harvest hits, each dwarf eats 2 food (offspring eat 1). If you don't have enough food, the deficit cascades through your resources: try food first, then convert grain (1 food each), then convert vegetables (2 food each), then take begging markers for anything remaining.
```
def FullPlayer.feed (p : FullPlayer) : FullPlayer :=
  let cost := p.dwarfs * 2 + p.offspring * 1
  if p.food >= cost then
    { p with food := p.food - cost }
  else
    let deficit := cost - p.food
    let p' := { p with food := 0 }
    let grainUsed := min p'.grain deficit
    let p'' := { p' with grain := p'.grain - grainUsed }
    let deficit' := deficit - grainUsed
    let vegUsed := min p''.vegetables (deficit' / 2 + deficit' % 2)
    let vegFood := min (vegUsed * 2) deficit'
    let p''' := { p'' with vegetables := p''.vegetables - vegUsed }
    let deficit'' := deficit' - vegFood
    { p''' with beggingMarkers := p'''.beggingMarkers + deficit'' }
```
  And a normal harvest is the composition of three phases in one elegant pipeline:
```
def FullPlayer.normalHarvest (p : FullPlayer) : FullPlayer :=
  p.fieldPhase.feed.breedingPhase
```
  Field phase harvests your sown crops. Feed pays the food cost (or generates begging markers). Breeding adds one animal per type that has at least two. The order matters: fields produce food before feeding, and breeding happens after, so newborn animals don't need to be fed in the same round they appear. This ordering rule from page 6 of the Caverna rulebook is encoded in the function composition.
  
  Furnishing Tiles and the BonusContext
  
  There are 48 furnishing tiles in the game, each with resource costs, base victory points, and (for some) end-game bonus scoring formulas that depend on your final board state. The BonusContext struct captures everything a furnishing tile might look at when computing its bonus:
```
structure BonusContext where
  stoneInSupply        : Nat := 0
  oreInSupply          : Nat := 0
  sheepCount           : Nat := 0
  cattleCount          : Nat := 0
  numAdjacentDwellings : Nat := 0
  numArmedDwarfs       : Nat := 0
  numDwarfs            : Nat := 0
  rubyCount            : Nat := 0
  grainCount           : Nat := 0
  vegCount             : Nat := 0
  farmAnimalCount      : Nat := 0
  hasAnyWeapon         : Bool := false
  allDwarfsArmed       : Bool := false
  numYellowTagTiles    : Nat := 0
```
  The bonus point function is a match on tile ID that implements every scoring formula from the Caverna appendix:
```
def furnishingBonusPoints (fid : FurnishingId) (ctx : BonusContext) : Nat :=
  match fid with
  | .stoneStorage   => ctx.stoneInSupply
  | .oreStorage     => ctx.oreInSupply / 2
  | .weavingParlor  => ctx.sheepCount / 2
  | .milkingParlor  => ctx.cattleCount
  | .stateParlor    => ctx.numAdjacentDwellings * 4
  | .mainStorage    => ctx.numYellowTagTiles * 2
  | .weaponStorage  => ctx.numArmedDwarfs * 3
  | .suppliesStorage => if ctx.allDwarfsArmed then 8 else 0
  | .broomChamber   => if ctx.numDwarfs >= 6 then 10
                        else if ctx.numDwarfs >= 5 then 5
                        else 0
  | .prayerChamber  => if ctx.hasAnyWeapon then 0 else 8
  | _ => 0
```
  The Prayer Chamber is particularly nasty. It gives you 8 free points, but only if none of your dwarfs have weapons. The moment you forge a single weapon, it drops to zero. This creates a genuine strategic dilemma, formalized and proved:
```
theorem prayer__chamber__vs__weapons :
    furnishingBonusPoints .prayerChamber {} = 8 /\
    furnishingBonusPoints .prayerChamber { hasAnyWeapon := true } = 0 :=
  by constructor <;> native_decide
```
  The furnishing rush archetype gets its power from stacking compatible bonus tiles: Office Room overhangs, State Parlor for +4 per adjacent dwelling (up to +16), Broom Chamber for +5 or +10 based on dwarf count, Prayer Chamber for +8 (no weapons). These bonuses compound. A player with 5 dwarfs, 4 adjacent dwellings, and no weapons can pull +39 bonus points from three tiles. That's why furnishing rush has the highest ceiling.
  
  The Strategy Space
  
  With the LTS, scoring function, and food economy in place, the next question is: what are the high-level plans a player can actually follow? The transition relation defines roughly $10^{30}$ possible play sequences, but the overwhelming majority of them are nonsense. Consider a player who forges a weapon in round 1 (spending precious ore), then never goes on an expedition, sows a field in round 3 but never harvests grain from it, builds a pasture in round 5 but never acquires an animal, and spends round 8 taking Starting Player for no reason. This player ends the game with a weapon they never used, an empty pasture, a field of rotting grain, and a final score somewhere around 20 points after begging penalties. The LTS covers this path. The invariant proofs hold over it. It is a legal play sequence, and it is also exactly the kind of play sequence that a five-year-old would produce by picking action spaces at random.
  
  The vast majority of the state space looks like this: diffuse, uncommitted paths where the player dabbles in everything and commits to nothing, hemorrhaging tempo and food while accumulating resources that never convert to points. Only a handful of coherent "channels" through the action space graph lead to competitive scores against a rational opponent. A strategy archetype is a consistent pattern of action space usage across the full 12-round game. I identified eight by examining which action spaces and furnishing tiles naturally cluster together: if two actions compete for the same resources or unlock the same scoring categories, they belong to the same archetype. For example, Blacksmithing, Expedition, and weapon-dependent loot all form the weapon rush cluster, while Excavation, Housework, and bonus-scoring furnishings form the furnishing rush cluster. The classification was manual, but the Lean proofs validate it: every archetype's score estimates are derived from the formalized game rules, and the dominance relations are machine-checked over the resulting payoff matrix.
```
inductive StrategyArchetype where
  | furnishingRush
  | weaponRush
  | animalHusbandry
  | miningHeavy
  | balanced
  | peacefulFarming
  | rubyEconomy
  | peacefulCaveEngine
```
  But why eight? The answer comes from the structure of the game's scoring channels. A scoring channel is a resource-to-points pathway through the action spaces: the furnishing channel runs through Excavation and Housework into furnished caverns, the weapon channel runs through Blacksmithing into expeditions and loot, and so on. There are exactly six:
```
inductive ScoringChannel where
  | furnishing        -- Excavation + Housework -> caverns -> furnishing tiles
  | weaponExpedition  -- Blacksmithing + Adventure -> weapons -> loot
  | agriculture       -- Clearing + Sustenance -> fields -> crops
  | animalBreeding    -- Sheep Farming + Donkey Farming -> pastures -> animals
  | mining            -- Ore/Ruby Mine Construction -> mines
  | economy           -- Starting Player + Ore Trading + Ruby Mining -> gold/rubies
```
  Each archetype commits to a primary channel, and the eight archetypes cover all six channels (all__channels__covered). Some channels conflict over shared resources: weapon/expedition and mining both need ore, furnishing and mining both need stone. The channelsConflict function encodes these tensions. With 47 productive actions per game and each channel needing at least 6 dedicated actions to reach competitive scoring, a player can invest in at most 2 channels seriously (budget__bounds__channels). The archetypes are the maximal compatible channel combinations: 6 single-primary archetypes plus 2 hybrids (balanced spreads across 3 channels, peaceful cave engine uses weapons for food rather than scoring).
  
  The exhaustivity proof (archetype__channel__surjection) shows every channel has at least one archetype as its primary. If you're going to score points, you have to go through a channel, and every channel is represented. No viable strategy falls outside the classification.
  
  Each archetype has an estimated scoring ceiling (best case across all setups) and floor (worst case):
  
  Furnishing rush tops the ceiling at 140 and ties for the highest floor at 60. Weapon rush matches the floor but caps at 120. The others trail off. The interval chart makes the dominance relationships immediately visible: furnishing rush's bar extends further right (higher ceiling) than any other archetype, and its left endpoint (floor) is as good as anyone's.
  
  The Dominance Hierarchy
  
  Before building the payoff matrix, we can establish partial dominance from the score estimates alone. If strategy $s$ has both a higher ceiling and a higher floor than strategy $t$ (with at least one strict inequality), then $s$ dominates $t$ in score estimates.
  
  Solid green arrows show dominance via score estimates (higher ceiling and floor). Dashed green arrows indicate dominance established only through the full payoff matrix. Animal Husbandry and Mining Heavy are incomparable in score estimates (one has a higher ceiling, the other a higher floor), but both are weakly dominated by Furnishing Rush in the payoff matrix.
  
  The incomparability is proven constructively:
```
theorem incomparable__strategies__exist :
    not (dominates .miningHeavy .animalHusbandry) /\
    not (dominates .animalHusbandry .miningHeavy) := by decide
```
  The Payoff Matrix
  
  The next question is what happens when two players with potentially different archetypes collide over the shared action spaces. You model this as an $8 \times 8$ payoff matrix $M$ where $M_{ij}$ is the estimated score for the row player when row plays archetype $i$ and column plays archetype $j$.
  
  The green border marks the Furnishing Rush row (weakly dominant). Blue borders highlight the diagonal (mirror matchups, always depressed). Cell color intensity reflects payoff magnitude: light green (55) through coral (135).
  
  In Lean, the matrix is a function from Fin 8 -> Fin 8 -> Int with all 64 entries hardcoded from the strategy analysis:
```
def payoffMatrix : Fin 8 -> Fin 8 -> Int
  | 0, 0 =>  85 | 0, 1 => 130 | 0, 2 => 135 | 0, 3 => 130
  | 0, 4 => 125 | 0, 5 => 135 | 0, 6 => 135 | 0, 7 => 130
  | 1, 0 =>  80 | 1, 1 =>  75 | 1, 2 => 100 | 1, 3 =>  85
  | 1, 4 =>  95 | 1, 5 => 105 | 1, 6 => 100 | 1, 7 =>  85
  -- ... 48 more entries ...
```
  A word on what "estimated" means here. The matrix entries are derived from the formalized game rules (scoring function, food costs, action budgets), not from Monte Carlo simulation or guesswork. But they are estimates in the sense that I haven't exhaustively solved every possible 47-move sequence within each archetype. How sensitive is the result? The min__dominance__margin__is__5 theorem proves that the minimum gap between the furnishing rush row and the next-best entry in each column is exactly 5 points (occurring in the mirror matchup column). Perturbing any single entry by less than 5 points cannot flip the dominance relation. Even a 10-point swing in a single cell would only affect one column, not the global result. The Nash equilibrium is more sensitive (it depends on the diagonal), but the mirror matchup at 85 would need to drop below the next-best response value of 80 before the equilibrium shifts. The downstream proofs are machine-checked over the matrix as stated, so the formal guarantees are exact conditional on these entries.
  
  We can do better than conditional. Replace each scalar entry with a closed interval bounding the true payoff. Mirror matchups get tight bounds (the point estimate $\pm 2$, since both players execute the same plan and contention is symmetric). Cross-archetype matchups get wider bounds ($\pm 5$, reflecting uncertainty in cross-strategy interaction). The interval payoff matrix looks like this:
```
structure PayoffInterval where
  lo : Int
  hi : Int
  valid : lo <= hi

def intervalPayoff : Fin 8 -> Fin 8 -> PayoffInterval
  | 0, 0 => { lo := 83, hi := 87, valid := by omega }   -- mirror: eps=2
  | 0, 1 => { lo := 125, hi := 135, valid := by omega }  -- vs weapon: eps=5
  -- ... 62 more entries ...
```
  Robust weak dominance asks: for every column and every non-furnishing alternative, does the furnishing rush lower bound meet or exceed the alternative's upper bound? If yes, then furnishing rush dominates for ALL true payoff matrices within these intervals, not just the point estimates.
```
theorem robust_weak_dominance :
    forall (col : Fin 8) (alt : Fin 8), alt != 0 ->
      (intervalPayoff 0 col).lo >= (intervalPayoff alt col).hi := by decide
```
  It passes. The tightest cell is column 0 (mirror matchup): furnishing rush $[83, 87]$ vs. weapon rush $[77, 83]$. The margin is $83 - 83 = 0$, a weak tie at the boundary. All other columns have margins of 20 or more (non__mirror__columns__robust). If the error bounds were widened by just 1 point, column 0 would fail (fragility__column__0), which tells us exactly where the result is most fragile and what the tolerance is.
  
  The interval analysis also gives us robust welfare bounds. Nash welfare lies in $[166, 174]$ and the social optimum in $[200, 220]$. Even in the best case for selfish play and worst case for cooperation, the social optimum still exceeds Nash welfare (robust__price__of__anarchy). The prisoner's dilemma structure is not an artifact of the point estimates.
  
  The first row is at least as large as every other row in every column. That's it. That's the whole result. In game theory this property is called weak dominance: a strategy $\sigma^*$ is weakly dominant if for all opponent strategies $o$ and all alternative strategies $\sigma$,
  
  $$
  M(\sigma^*, o) \geq M(\sigma, o)
  $$
  
  The Lean proof is furnishing__rush__weakly__dominant, and it says exactly this:
```
theorem furnishing_rush_weakly_dominant :
    forall (row : Fin 8) (col : Fin 8),
      payoffMatrix 0 col >= payoffMatrix row col := by decide
```
  For all opponents, for all alternatives, the furnishing rush payoff is greater than or equal. The proof is decide: Lean's kernel checks all 64 cells. Nobody has to trust my arithmetic.
  
  The Contention Effect
  
  The diagonal of the payoff matrix is always depressed relative to the off-diagonal entries:
```
theorem diagonal__always__depressed :
    forall (i : Fin 8), exists (j : Fin 8), j /= i /\
      payoffMatrix i j > payoffMatrix i i := by decide
```
  Every mirror matchup scores below at least one non-mirror matchup in the same row. This is the contention effect: when both players pursue the same archetype, they fight over the same action spaces. Furnishing rush mirrors compete for excavation and housework. Weapon rush mirrors fight over blacksmithing. Mining mirrors clash on ore mine construction.
  
  The game punishes sameness. It's just that the punishment for sameness (85) is still less painful than the punishment for picking something worse (60 to 80 against an opponent who picked furnishing rush).
  
  Nash Equilibrium and the Prisoner's Dilemma
  
  From weak dominance, the game theory falls out like dominoes. The best response function $\text{BR} : \text{Strategies} \to \text{Strategies}$ maps each opponent strategy to the row-maximizer in the corresponding column. Since furnishing rush achieves the column maximum everywhere, BR is the constant function:
  
  $$
  \text{BR}(x) = \text{FurnishingRush} \quad \forall x
  $$
  
  A Nash equilibrium is a fixed point of the joint best-response correspondence: a pair $(a, b)$ where $a = \text{BR}(b)$ and $b = \text{BR}(a)$. Since BR is constant, the only fixed point is (FurnishingRush, FurnishingRush). Existence and uniqueness in three lines:
```
theorem exactly__one__nash__equilibrium :
    (exists a b, isNashEquilibrium a b) /\
    (forall a b, isNashEquilibrium a b ->
      a = .furnishingRush /\ b = .furnishingRush) :=
  <<.furnishingRush, .furnishingRush, furnishing_mirror_is_nash>,
   furnishing_mirror_unique_nash>
```
  The uniqueness proof works by case-splitting on all 64 strategy pairs and observing that only one satisfies the Nash condition:
```
theorem furnishing__mirror__unique__nash :
    forall a b : StrategyArchetype,
      isNashEquilibrium a b ->
        a = .furnishingRush /\ b = .furnishingRush := by
  intro a b h
  have h1 := h.1; have h2 := h.2
  cases a <;> cases b <;> simp_all [bestResponse, isNashEquilibrium]
```
  There is exactly one pure Nash equilibrium and it is the one where both players do the same thing. Which is a little tragic.
  
  The Price of Anarchy
  
  Both players score 85 in the Nash equilibrium. If they could somehow coordinate on different strategies (say furnishing rush versus animal husbandry), the combined welfare would be $135 + 75 = 210$ instead of $85 + 85 = 170$.
  
  The price of anarchy is the ratio of the social optimum to the Nash welfare:
  
  $$
  \text{PoA} = \frac{210}{170} = \frac{21}{17} \approx 1.24
  $$
  
  Selfish play costs about 19% of the social optimum. The Lean proof is decide, because it's just arithmetic:
```
theorem price__of__anarchy__ratio :
    socialOptimumValue = 210 /\ nashWelfare = 170 /\
    210 * 17 = 170 * 21 := by decide
```
  The depressing implication is that both players would prefer the other person to play something different, but neither can unilaterally deviate without making themselves worse off. You're stuck at 85 each, staring across the table at someone who also read this blog post.
  
  The Scoring Function
  
  A natural question is where the scores can actually land. The end-game scoring function totals up every positive and negative contribution:
```
def FullPlayer.score (p : FullPlayer) : Int :=
  let animals := (p.dogs + p.sheep + p.donkeys +
                  p.wildBoars + p.cattle : Int)
  let grainPts := (((p.grain + p.fieldsWithGrain * 3) + 1) / 2 : Int)
  let vegPts := ((p.vegetables + p.fieldsWithVeg * 2) : Int)
  let rubyPts := (p.rubies : Int)
  let dwarfPts := ((p.dwarfs + p.offspring) : Int)
  let pasturePts := (p.smallPastures * 2 + p.largePastures * 4 : Int)
  let minePts := (p.oreMines * 3 + p.rubyMines * 4 : Int)
  let goldPts := (p.gold : Int)
  let furnPts := p.furnishings.foldl (fun acc fid =>
    acc + ((furnishingSpec fid).basePoints : Int)) (0 : Int)
  let missingTypes :=
    (if p.sheep == 0 then 1 else 0) + (if p.donkeys == 0 then 1 else 0) +
    (if p.wildBoars == 0 then 1 else 0) + (if p.cattle == 0 then 1 else 0)
  let unusedPenalty := (p.unusedMountain + p.unusedForest : Int)
  let beggingPenalty := (p.beggingMarkers * 3 : Int)
  let missingPenalty := (missingTypes * 2 : Int)
  animals + grainPts + vegPts + rubyPts + dwarfPts + pasturePts +
  minePts + goldPts + furnPts - unusedPenalty - beggingPenalty - missingPenalty
```
  The theoretical floor is $-55$ points: a player who takes zero actions across all rounds gets +2 for their two starting dwarfs, $-8$ for missing all four farm animal types, $-22$ for 22 unused board spaces, and $-27$ from 9 begging markers at $-3$ points each. The theoretical ceiling is 202, computed by summing the independent maxima of every scoring category. But you can't reach 202, because every scoring category competes for the same 56 dwarf placements over 12 rounds. You cannot simultaneously furnish 12 caverns, build 5 mines, breed 20 animals, and sow 10 fields. The action budget is the binding constraint. The practical ceiling is around 140, achievable by furnishing rush when uncontested.
  
  The theoretical range is 195 points (from $-55$ to 140), but the $-55$ floor requires literally doing nothing for 12 rounds, so it's not strategically meaningful. The practical floor across all archetypes is around 45 (peaceful farming in the worst setup), giving a practical range of about 95 points. The dominant strategy's own range is 80 points (60 to 140), proven as dominant__strategy__variance. The safety margin (dominant__strategy__safety__margin) is 115 points above the theoretical floor, but the more relevant number is the gap between furnishing rush's worst case (60) and the worst viable archetype's worst case (45): even in the most adversarial setup, choosing correctly gains you at least 15 points.
  
  Degenerate Combos
  
  The formalization surfaced several combos that look broken in isolation. Four stand out.
  
  The Beer Parlor converts grain to gold at a 3:2 ratio before scoring: every 2 grain becomes 3 gold. Without it, 20 grain scores 10 points (the grain formula is $\lceil n/2 \rceil$). With it, the same 20 grain becomes 30 gold. That's a 3x multiplier on the base grain value, and the gold stacks with every other scoring category. The beer__parlor__max__gold theorem proves beerParlorGold 20 = 30. The catch is accumulating 20 grain: you need aggressive sowing across multiple rounds, which means burning actions on Slash-and-Burn and Sustenance instead of excavating caverns.
  
  Dogs have no cap on sheep-watching: $n$ dogs on one meadow guard $n+1$ sheep. Stack 10 dogs and a Weaving Parlor and you're looking at 51 points from a single tile combo. The catch is that acquiring 10 dogs requires roughly 6 expedition actions (dogs are strength-1 loot, so they're easy to get but each expedition burns an action), and those 6 actions aren't building caverns or growing your family.
  
  The Writing Chamber prevents up to 7 points of losses for 2 stone. This sounds like a license to ignore entire scoring categories, and it is, except the categories you'd skip (unused spaces, missing animal types) are exactly the ones that furnishing rush covers naturally. The players who benefit most from Writing Chamber are the ones playing badly enough to accumulate large penalties, and at that point the cap at 7 means it barely dents a truly neglected board.
  
  The Prayer Chamber is the most elegant. It gives 8 points for zero resource investment, but the bonus evaporates the moment any dwarf forges a weapon. The prayer__chamber__vs__weapons theorem proves this is a hard binary: 8 or 0, nothing in between. It creates a genuine strategic fork (peaceful play vs. expedition play) that the rest of the game's design carefully preserves.
  
  None of these breaks the dominant strategy. Every combo faces the same binding constraint: 56 total actions with full family growth. You can produce flashy numbers in one scoring category, but you can't cover all of them. The vanilla furnishing rush, with its balanced approach to board coverage, family growth, and furnishing synergies, remains the ceiling. The combos are features, not bugs: they're what make the game worth replaying even after you know the dominant strategy, because they give you something to pivot into when the standard lines are blocked.
  
  Is the Game Solved?
  
  A serious mathematician would call this "a formal analysis of a model, with the caveat that the model's parameters are estimated rather than computed." That is a legitimate and common pattern in applied math, operations research, and mechanism design. The proofs are machine-checked and airtight, but they are conditional on the payoff matrix. The theorems say: IF the payoff matrix is this, THEN furnishing rush is weakly dominant, the Nash equilibrium is unique, and the price of anarchy is 21/17. They do not say: the true expected score of an optimally-played furnishing rush against an optimally-played animal husbandry opponent is exactly 135. That number is an estimate derived from the formalized action economy, not from exhaustive search of the game tree.
  
  How confident should you be in the estimate? The min__dominance__margin__is__5 theorem proves the narrowest gap between furnishing rush and its closest competitor is 5 points. If the estimation methodology has a systematic bias of less than 5 points (plausible, given that the estimates are derived from the same scoring functions and action budgets used in actual play), the qualitative result holds. A correlated shift of 5+ points across an entire row of the matrix could break weak dominance in the mirror column, but would require the methodology to consistently overestimate furnishing rush's performance in self-contention scenarios. Given that the mirror penalty (85 vs. 130+ off-diagonal) already models severe contention, this seems unlikely.
  
  At the archetype level, yes, the game is solved. For any 2-player setup, regardless of which of the 2,880 configurations you draw, the model says the optimal pure strategy is furnishing rush. The proof does not depend on any specific card ordering or harvest marker placement. What I haven't done is compute the exact sequence of dwarf placements for each specific setup. That would require solving a game tree with roughly $10^{30}$ nodes. But the archetype-level result is the one that matters for actual play. You know the plan. The within-archetype decisions (which cavern to excavate first, which furnishing tile to prioritize) are tactical, not strategic. They don't change the answer.
  
  The 3+ player variants remain open. The payoff matrix becomes a rank-3 tensor with 512 entries, action space contention shifts from binary to combinatorial, and the pure dominance result almost certainly fails, since furnishing tile scarcity under three-way competition makes mixed equilibria the likely outcome. If someone wants to formalize that, I would love to read the proof.
  
  Play the Dominant Strategy
  
  Play furnishing rush. Excavate aggressively in rounds 1 through 4. Get Office Room early for the overhang bonuses. Get State Parlor for +4 per dwelling. Grow to 5 dwarfs and pick up Broom Chamber for +10 bonus. If your opponent does something different, you score 125 to 135 and they score 60 to 105. If your opponent also plays furnishing rush, you both land at 85, which is worse than the cooperative optimum of 210 but better than any unilateral deviation. You'll sit there at the table, both of you excavating caverns as fast as you can, both knowing that one of you could sacrifice 10 points to give the other 50, but neither willing to be the one who blinks.
  
  Prisoner's dilemma in a cave. Uwe Rosenberg probably didn't intend this, but the formal analysis says it's there.
  
  The code is built on Lean 4 v4.28.0 with Mathlib, modeling all 24 action spaces, all 48 furnishing tiles, the complete expedition loot table, the board grids, and the full 12-round 2-player harvest schedule. I think Caverna is a beautifully designed game, which is exactly why it was satisfying to find that even under formal analysis the strategic structure holds together so well. A badly designed game would have a trivially dominant strategy that makes the game boring. Caverna's dominant strategy comes with a 19% welfare tax on the mirror matchup, which means the game is always more interesting when your opponent does something unexpected (the Nash equilibrium is rarely where the fun is, in games or in life), which means in practice people don't always play the dominant strategy, which means the game stays fun.
  
  Good game design, it turns out, is robust to being solved. Now you know the optimal play. Whether you follow it is, thankfully, not a theorem.
February 20, 2026
1. 🔗 IDA Plugin Updates IDA Plugin Updates on 2026-02-20 rss
  IDA Plugin Updates on 2026-02-20
  
  New Releases:
  - augur v0.8.0
  - haruspex v0.8.0
  - hrtng v3.8.88
  - rhabdomancer v0.8.0
  Activity:
  - augur
    
    38e31c3f: doc: update CHANGELOG.md
    
    e3023021: feat: ida 9.3 compatibility release
  - capa
    
    f526357d: main: suggest -os flag when ELF OS detection fails (#2869)
    
    c1ec826a: Merge pull request #2866 from devs6186/fix/2699-rich-markup-escape
    
    5ef4ad96: doc: fix typo and add documentation links in README
  - haruspex
    
    05df4465: feat: ida 9.3 compatibility release
  - hrtng
    
    3274a7e1: once again
    
    c9386971: it seems build.yml should works
    
    9e584112: dance with workflows/build.yml
    
    929f18be: fix release workflow
    
    39b894e4: "Microcode Explorer…" menu item is turned off on 9.3 as obsolete (b…
  - rhabdomancer
    
    855546b7: feat: ida 9.3 compatibility release
2. 🔗 Simon Willison Adding TILs, releases, museums, tools and research to my blog rss
  I've been wanting to add indications of my various other online activities to my blog for a while now. I just turned on a new feature I'm calling "beats" (after story beats, naming this was hard!) which adds five new types of content to my site, all corresponding to activity elsewhere.
  
  Here's what beats look like:
  
  Those three are from the 30th December 2025 archive page.
  
  Beats are little inline links with badges that fit into different content timeline views around my site, including the homepage, search and archive pages.
  
  There are currently five types of beats:
  - Releases are GitHub releases of my many different open source projects, imported from this JSON file that was constructed by GitHub Actions.
  - TILs are the posts from my TIL blog, imported using a SQL query over JSON and HTTP against the Datasette instance powering that site.
  - Museums are new posts on my niche-museums.com blog, imported from this custom JSON feed.
  - Tools are HTML and JavaScript tools I've vibe-coded on my tools.simonwillison.net site, as described in Useful patterns for building HTML tools.
  - Research is for AI-generated research projects, hosted in my simonw/research repo and described in Code research projects with async coding agents like Claude Code and Codex.
  That's five different custom integrations to pull in all of that data. The good news is that this kind of integration project is the kind of thing that coding agents really excel at. I knocked most of the feature out in a single morning while working in parallel on various other things.
  
  I didn't have a useful structured feed of my Research projects, and it didn't matter because I gave Claude Code a link to the raw Markdown README that lists them all and it spun up a parser regex. Since I'm responsible for both the source and the destination I'm fine with a brittle solution that would be too risky against a source that I don't control myself.
  
  Claude also handled all of the potentially tedious UI integration work with my site, making sure the new content worked on all of my different page types and was handled correctly by my faceted search engine.
  
  Prototyping with Claude Artifacts
  
  I actually prototyped the initial concept for beats in regular Claude - not Claude Code - taking advantage of the fact that it can clone public repos from GitHub these days. I started with:
  
  Clone simonw/simonwillisonblog and tell me about the models and views
  
  And then later in the brainstorming session said:
  
  use the templates and CSS in this repo to create a new artifact with all HTML and CSS inline that shows me my homepage with some of those inline content types mixed in
  
  After some iteration we got to this artifact mockup, which was enough to convince me that the concept had legs and was worth handing over to full Claude Code for web to implement.
  
  If you want to see how the rest of the build played out the most interesting PRs are Beats #592 which implemented the core feature and Add Museums Beat importer #595 which added the Museums content type.
  
  You are only seeing the long-form articles from my blog. Subscribe to /atom/everything/ to get all of my posts, or take a look at my other subscription options.
3. 🔗 imfing/hextra v0.12.0 release
  Hextra v0.12.0 delivers page context menus for Markdown/AI integration, redesigned tabs with icon support, image zoom, comprehensive WCAG 2.2 AA accessibility improvements, and numerous bug fixes.
  
  For the full release notes and upgrade guide, please visit:
  https://imfing.github.io/hextra/blog/v0.12/
  
  New Features
  - Page Context Menu : copy page content as Markdown or view raw source, great for feeding docs into AI tools
  - Tab Icon Support : add icons to tabs in the redesigned tabs shortcode
  - Image Zoom : click-to-zoom for Markdown images via params.imageZoom.enable: true
  - GoatCounter Analytics : new built-in analytics provider
  - Hide Main Sidebar : per-page sidebar.hide: true to give content pages full width
  - Last Modified Author : display last commit author via GitInfo
  - Disable Prev/Next Navigation : params.page.displayPagination: false
  - Archives Page : built-in chronological blog listing grouped by year
  - Glossary : site-wide term glossary with term shortcode
  - LLMs.txt Exclusion : exclude pages/sections via llms: false in front matter
  What's Changed
  - feat: support hiding the main sidebar in desktop site by @KStocky in #778
  - feat(tabs): revamp tabs by @ldez in #815
  - chore(scripts): generic way to build scripts by @ldez in #829
  - fix(docs): menu main duplicate field by @ldez in #837
  - fix(analytics): change default umami analytics file to script.js by @ghac101 in #835
  - feat: enhance table readability by @kowyo in #826
  - feat: markdown attribute support for headers + "no-step-marker" docs for steps by @pmarrapese in #851
  - docs(details): change details shortcode calls to angle brackets by @Bubbler-4 in #855
  - feat: support GoatCounter analytics by @KStocky in #814
  - chore: Update Beginner Privacy showcase image and add PrintN website by @PrintN in #859
  - chore(docs): link KaTeX by @yuri1969 in #860
  - feat: add optional alt parameter to card shortcode by @imfing in #899
  - feat: support page bundle images in OpenGraph metadata by @torbjornbp in #892
  - fix: work around flexsearch returning fewer than expected result pages by @bloovis in #847
  - fix(og-image): handle leading slashes in image paths for subpath deployments by @imfing in #901
  - fix(card): ensure subtitle stays at bottom by wrapping title/subtitle… by @AntoninPvr in #877
  - fix(flexsearch): enhance match highlighting and safe DOM manipulation by @imfing in #903
  - fix: respect the page parameter toc in the mobile dropdown by @illia-v in https://github.c/imfing/hextra/pull/905
  - fix: respect search.enable in the mobile by @illia-v in #904
  - feat(glossary): provide basic term glossary by @yuri1969 in #869
  - fix: migrate tabs shortcode to new standard syntax by @imfing in #906
  - feat(image-zoom): add image zoom functionality and documentation by @imfing in #907
  - feat(context-menu): add page context menu for copy/view Markdown by @imfing in #908
  - fix(layout): make content width respect page.width config by @imfing in #911
  - fix(tabs): prevent markdown blockquote parsing when nested in steps by @imfing in #912
  - fix(navbar): improve active state detection for multilingual section pages by @imfing in #913
  - feat(pagination): add option to disable prev/next navigation by @ghac101 in #836
  - fix(glossary): make Glossary optional by @yuri1969 in #916
  - feat(i18n): add Italian localization strings for various UI elements by @gallochri in #915
  - feat(llms): add option to exclude pages and sections from llms.txt by @MatheusFlausino in #918
  - feat(lastUpdated): introduce last modified author using GitInfo by @daniseijo in #857
  - fix: prevent relref double base-prefix in render-link by @imfing in #920
  - feat: archives page by @confusedkernel in #922
  - refactor(a11y): comprehensive WCAG 2.2 AA accessibility improvements by @imfing in #924
  - feat(tabs): add icon support for tabs by @imfing in #926
  - fix: Site.Author -> Site.Params.Author for Hugo v1.156.0 by @Fenyutanchan in #933
  - fix(navbar): align mobile sidebar ordering and labels with menu.main by @AntoninPvr in #883
  - refactor(layout): keep content width fixed and document CSS var override by @imfing in #934
  - chore: release blog for Hextra v0.12 by @imfing in #927
  New Contributors
  - @ghac101 made their first contribution in #835
  - @pmarrapese made their first contribution in #851
  - @Bubbler-4 made their first contribution in #855
  - @bloovis made their first contribution in #847
  - @AntoninPvr made their first contribution in #877
  - @illia-v made their first contribution in #905
  - @gallochri made their first contribution in #915
  - @MatheusFlausino made their first contribution in #918
  - @daniseijo made their first contribution in #857
  - @confusedkernel made their first contribution in #922
  - @Fenyutanchan made their first contribution in #933
  Full Changelog : v0.11.1...v0.12.0
4. 🔗 r/Yorkshire Where's the best place to live outside of Leeds? rss
  
  Hey r/Yorkshire, I've very recently split from my girlfriend, I'm a guy in my late 20s and currently living in York. I'm looking to move out of York as, let's be real, how tf am I supposed to live in York on my own at that kind of price.
  
  I work hybrid in Leeds and am looking to find somewhere new no more than about an hour's drive away. Thing is, I've only just moved to York in the winter, haven't really planted my roots, so would like to find somewhere that has a little going on so I can meet people. In my down time I love a lot of hiking, pubs, live music, I'm not expecting to find somewhere with all that, but somewhere that is relatively close to that kind of vibe, bit of an arty young vibe if possible.
  
  I'm looking at Skipton, Halifax, keighly, and Harrogate at the moment, but let's rarely come up for under 700, but I'm open to other areas as I'd like to get to know the place. Just looking for recommendations really or thourghts on the above? I've heard mixed on keighly, and worried Skipton be a bit of a retirement village (no idea if that's true). Love to hear your thoughts. Thanks
  
  submitted by /u/tmatthews98
  [link] [comments]
5. 🔗 imfing/hextra v0.10.3 release
  
  fix: Site.Author -> Site.Params.Author for Hugo v1.156.0 (#933)
6. 🔗 imfing/hextra v0.11.3 release
  Bug Fixes
  - fix(docs): menu main duplicate field (#837)
7. 🔗 r/Leeds Comedy clubs? rss
  
  Does anyone know where there are good stand up comedy acts in Leeds? Looking for venues that could be fun to visit
  
  submitted by /u/C0sm1c_3l3ph4nt
  [link] [comments]
8. 🔗 r/york Yorkshire Ghostbusters in this sub - Are any of you folks interested in a quick meet for a patch swap? I'll be in York visiting family next Tuesday - Thursday. The Chesapeake Ghostbusters logo ties our areas together through the use of Calvert and Crossland heraldry on the Maryland flag. rss
  
  | submitted by /u/CaptainAwwsum
  [link] [comments]
  ---|---
9. 🔗 @binaryninja@infosec.exchange Want to get the best decompilation for your own architecture? Glenn's post mastodon
  
  Want to get the best decompilation for your own architecture? Glenn's post shows how you can enable Binary Ninja to give you the best decompilation around. Part 1 covers the basics up to disassembly, assembly, and control- flow. Next week, part 2 covers lifting and our first decompilation results.
  
  https://binary.ninja/2026/02/20/quark-platform- part-1.html
10. 🔗 @binaryninja@infosec.exchange Going live now! Don't miss some fantastic demos by our RE//verse instructors! mastodon
  
  Going live now! Don't miss some fantastic demos by our RE//verse instructors! https://www.youtube.com/vector35/live
11. 🔗 News Minimalist 🐢 Supreme Court blocks Trump's tariffs + 11 more stories rss
  
  In the last 2 days ChatGPT read 63550 top news stories. After removing previously covered events, there are 12 articles with a significance score over 5.5.
  
  [5.8] Supreme Court limits presidential authority on global tariffs —ctvnews.ca(+47)
  
  The U.S. Supreme Court on Friday struck down President Trump’s global tariffs, ruling that his unilateral use of emergency economic powers exceeded executive authority and violated constitutional limits.
  
  The 6-3 ruling determined that the 1977 International Emergency Economic Powers Act does not authorize unilateral tariffs. The conservative majority applied the "major questions" doctrine, asserting that significant economic actions require explicit congressional approval rather than broad executive interpretations of emergency statutes.
  
  Challenged by twelve states and various businesses, the ruling could force the refund of $175 billion. Although the administration explores alternative legal routes, the decision curtails a central pillar of Trump's agenda.
  
  [5.7] FDA to require one study for new drug approvals to speed patient access —abcnews.com(+14)
  
  The FDA will drop its longtime requirement for two clinical trials for new drug approvals, making a single study the default standard to accelerate patient access to novel medical treatments.
  
  Commissioner Marty Makary and Deputy Vinay Prasad stated that modern research precision makes the old standard obsolete. The shift aims to reduce bureaucracy, potentially sparking a surge in drug development for common diseases that previously required more extensive testing than rare conditions.
  
  Although the agency has accepted single studies for rare diseases since the 1990s, this policy expansion contrasts with recent restrictive decisions regarding vaccines and gene therapies, leaving some industry stakeholders seeking clarity.
  
  Highly covered news with significance over 5.5
  
  [6.5] Nasal spray vaccine protects mice from multiple respiratory pathogens — nature.com (+11)
  
  [6.4] Feline and human cancers share striking genetic similarities, offering new research avenues — news.cornell.edu (+16)
  
  [6.0] Invisible galaxy confirmed, composed almost entirely of dark matter — es.wired.com (Spanish) (+5)
  
  [6.0] Google and Apple integrate generative AI music features into consumer apps — financialpost.com (+23)
  
  [6.0] UN experts find genocide hallmarks in Sudan's el-Fasher campaign — apnews.com (+21)
  
  [5.9] PromptSpy Android malware uses generative AI to adapt its persistence — bleepingcomputer.com (+8)
  
  [5.6] Trump order protects glyphosate production and manufacturer immunity — theguardian.com (+8)
  
  [5.6] Afghanistan's hunger crisis worsens as aid cuts force WFP to turn away children — abcnews.com (+3)
  
  [5.5] White House allows ICE to detain refugees for rescreening — theguardian.com (+13)
  
  [5.5] Iran nuclear talks collapse, pushing oil prices toward $100 as U.S. deploys military assets to the Middle East — economictimes.indiatimes.com (+65)
  
  Thanks for reading!
  
  — Vadim
  
  You can personalize this newsletter with premium.
  
  Powered by beehiiv
12. 🔗 r/wiesbaden Schön in der Sauna schwitzen rss
  
  submitted by /u/Z_smasher_Z
  [link] [comments]
13. 🔗 r/wiesbaden Meine Englische Bulldogge braucht dringend Gaumensegel-OP, organized by Mario Beierstettel rss
  
  submitted by /u/Slight_Today7434
  [link] [comments]
14. 🔗 r/wiesbaden Meine Englische Bulldogge braucht dringend Gaumensegel-OP, organized by Mario Beierstettel rss
  
  submitted by /u/Slight_Today7434
  [link] [comments]
15. 🔗 r/york The ubiquitous tourist rss
  
  In the '70s, a friend of mine's gaff was a second floor flat rented in Stonegate (for £11 a week - we think it was part of the Minster's estate). Anyway, the point is that, even back then, during the holidays and in summer, we would have fun leaning out the of the window to spot the odd local trying to worm their way through the dawdling crowds.
  
  submitted by /u/flame2spear
  [link] [comments]
16. 🔗 r/wiesbaden https://gofund.me/a4849d36a rss
  
  submitted by /u/Slight_Today7434
  [link] [comments]
17. 🔗 imfing/hextra v0.11.2 release
  Bug Fixes
  - Fix Site.Author -> Site.Params.Author for Hugo v0.156.0 compatibility (#933)
  This is a patch release to fix a breaking change introduced by Hugo v0.156.0, which removed the deprecated .Site.Author method. Users on Hugo v0.156.0+ should upgrade to this version.
18. 🔗 r/Yorkshire Yorkshire Dales in January 2027 rss
  
  | I visited the Dales last summer, finally, and fell absolutely in love with the people, nature, stone barns, endless greenery, etc. I plan to visit this summer again to do some hiking, but also planning a January 2027 trip. I really want to see the area with possible snow, frost, and with luck, the snowdrops starting to bloom! I usually take the train from Leeds to Skipton, then the bus to Grassington where I stay for a few days. For winter 2027, I wanted to either stay in Appletreewick, or Burnsall, for a few days. I mostly plan to write, read, and if the weather permits, take a few walks. Would these places be nice for winter, or would you recommend slightly larger places, like Settle? Also, is snow fairly common in the area in winter? Thanks!! Photo credit: Getty submitted by /u/skepticalbureaucrat
  [link] [comments]
  ---|---
19. 🔗 r/LocalLLaMA The top 3 models on openrouter this week ( Chinese models are dominating!) rss
  
  | the first time i see a model exceed 3 trillion tokens per week on openrouter! the first time i see more than one model exceed a trillion token per week ( it was only grok 4 fast month ago) the first time i see chinese models destroying US ones like this submitted by /u/keb_37
  [link] [comments]
  ---|---
20. 🔗 r/reverseengineering Reverse engineering the Creative Katana V2X soundbar to be able to control it from Linux rss
  
  submitted by /u/crower
  [link] [comments]
21. 🔗 r/Leeds Where do people play Warhammer? rss
  
  The actual Warhammer shop aren't interested if you're not buying a starter set, patriot games isn't great and there's nothing else near the city centre I'm aware of. So where do people play Warhammer? Are there any clubs out there?
  
  submitted by /u/sendmemespls97
  [link] [comments]
22. 🔗 r/wiesbaden Gute Orthopäden rss
  
  Wer ist ein guter Arzt/Ärztin für Orthopädie in Wiesbaden wo man nicht wie am Fließband behandelt wird? Empfehlungen für Kassenpatienten bitte 😊
  
  submitted by /u/kassen_patient
  [link] [comments]
23. 🔗 r/Yorkshire I went for a walk. rss
  
  | Too many stunning photos to choose from. submitted by /u/Background_Pay_3113
  [link] [comments]
  ---|---
24. 🔗 r/LocalLLaMA GGML.AI has got acquired by Huggingface rss
  
  | submitted by /u/Time_Reaper
  [link] [comments]
  ---|---
25. 🔗 r/Yorkshire Just love this place❤️ rss
  
  | submitted by /u/Terrible_Passion6178
  [link] [comments]
  ---|---
26. 🔗 r/LocalLLaMA Deepseek and Gemma ?? rss
  
  | submitted by /u/ZeusZCC
  [link] [comments]
  ---|---
27. 🔗 r/Leeds Barbers in city centre that can help me choose a haircut rss
  
  I always have a terrible time when going to a barber, or choosing a haircut. I have a hard time deciding what kind of haircut or style looks good on me.
  
  I live in the city centre; Are there any good barbers/hair salons within walking distance where I can just tell them to get creative with my hair? So far I've been to RMUK, lords' barbering and scissorhands barber but they all looked uncomfortable when I told them I'm not quite sure what to do with my hair...
  
  submitted by /u/Hideharuhaduken420
  [link] [comments]
28. 🔗 r/Leeds Deliveroo drivers rss
  
  I am absolutely sick of being nearly run over by uber eats/Deliveroo bikers on electric bikes with no helmets or lights going all over pedestrian routes. I’m pretty sure people have died being hit by these?? Is there anything we can do to bring this matter to the council?
  
  submitted by /u/Weary-Bus8436
  [link] [comments]
29. 🔗 r/reverseengineering Decrypt and extract voice guidance MP3 prompts from Sony WH-1000XM4 encrypted voice packs. AES key extracted via Bluetooth firmware dump of the Airoha MT2811 SoC. rss
  
  submitted by /u/TheHelgeSverre
  [link] [comments]
30. 🔗 r/Harrogate Photo booths in Harrogate - digital passport photos rss
  
  Are there any photo booths in town that do the digital photos for passports (providing the code for online passport applications)? Thanks
  
  submitted by /u/purte
  [link] [comments]
31. 🔗 r/LocalLLaMA Kimi has context window expansion ambitions rss
  
  | submitted by /u/omarous
  [link] [comments]
  ---|---
32. 🔗 r/york The Shambles doesn’t feel like The Shambles anymore rss
  
  Walked through on a Saturday and it genuinely felt like I was in a slow-moving queue for a theme park ride.
  
  I get that it’s popular and good for the city but it used to feel charming and slightly chaotic in a nice way. Now it feels like everyone’s there for the same photo.
  
  Is it just nostalgia talking, or has the vibe shifted a bit over the last few years?
  
  submitted by /u/1ChanceChipmunk1
  [link] [comments]
33. 🔗 r/Yorkshire Who here believes that the fish should have at least come with a signed apology for that price tag? rss
  
  | submitted by /u/PubLogic
  [link] [comments]
  ---|---
34. 🔗 r/Yorkshire Activities to take my gf to for her birthday? (South Yorkshire) rss
  
  It’s my girlfriend’s birthday in a couple of weeks and I want to surprise her with something to do. She likes creative activities like pottery and painting. She’s also into gothic stuff like tarot, spells, ghosts and taxidermy etc. She doesn’t drink so anything pub/bar focused is out of the question but if there’s somewhere I could get a beer nearby, I wouldn’t mind that haha.
  
  Any suggestions would be greatly appreciated 😁
  
  submitted by /u/Both-Opportunity7602
  [link] [comments]
February 19, 2026
1. 🔗 IDA Plugin Updates IDA Plugin Updates on 2026-02-19 rss
  IDA Plugin Updates on 2026-02-19
  
  New Releases:
  - ida-ios-helper 1.0.20
  Activity:
  - capa
    
    8aef630a: Sync capa rules submodule
    
    d1c9d206: Merge pull request #2865 from mandiant/lsc-1771433500.551532
  - HexRays-CppFormatter
    
    357dbec1: improve complex expression first arg reformatting
  - ida-cs2-reversing-tools
    
    e7a62451: Merge pull request #1 from oxiKKK/pseudocode-dumper
    
    65f1194d: Add pseudocode marker
  - ida-free-mcp
    
    2e6955b9: Add GUI-based decompiler integration for IDA Free support
  - ida-function-string-associate
    
    5b7831bd: Readme
    
    e3c7df6e: Add support for IDA 9.3
  - ida-hcli
    
    f6f79983: fix(github): gracefully handle GraphQL NOT_FOUND repositories
    
    f01be212: include 9.3 for accept_eula
  - ida-ios-helper
    
    2a5ee5e4: :green_heart: Resolve CI by updating ruff and apply format again
    
    2a35afe4: :bug: Fix getv to support ida 9.3
  - ida-sigmaker
    
    e70706aa: Merge pull request #2 from oxiKKK/pattern-search-improvement
    
    2023c3ef: migrate to PySide6
    
    2f8daeb3: Improve the searching dialog for C style patterns with msaks
  - ida-vtable-tools
    
    36c660cc: initial commit
  - ipyida
    
    4b0d6dae: Don't crash if no event loop is running (fixes bug with Python 3.14)
    
    4b3b596e: Reduce code in try-catch and add comment about RuntimeError in asynci…
  - msc-thesis-LLMs-to-rank-decompilers
    
    9b1fa33f: Merge branch 'main' of https://github.com/Lurpigi/msc-thesis-LLMs-to-…
    
    14ba14f1: upd
    
    94c7fde7: fix parser
    
    1f3561c1: dogbolt section
  - python-elpida_core.py
    
    f05c9d8c: docs: D15 Reality-Parliament Interface — compiled from codebase
    
    fc51cee2: docs: Update HF deployment status - Phase C deployed at 05:12 UTC
    
    95295029: state: D14 ark + feedback cache after 290 cycles
    
    3ab4c308: federation: 290 cycles governance + curation state (5 watches Feb 19)
    
    1b2d1133: docs: Feb 19 session - PSO optimizer restoration + MIND/BODY converge…
    
    1b784a43: Remove redundant GitHub Actions workflow - daemon approach sufficient
    
    f795cb52: fix: bypass aws-actions STS validation, set creds via env directly
    
    99546a09: fix: MIND workflow region eu-north-1 + add python-dotenv
    
    14be8ff5: Phase C: Axiom PSO optimizer + MIND autonomous workflow
    
    ac04ef9a: Phase B: Two-loop MIND/BODY architecture with D15 convergence gate
    
    f56c8c95: docs: Run log Feb 19 — 327 cycles, federation first light
    
    3668253f: fix: kernel_status key names + CadenceState.recursion_alert → ArkRhyt…
    
    4ea3c2d3: Update HF deployment status: Phase 14-20, federation architecture, au…
    
    7deebf36: Fix HF deploy workflow: push HEAD:main (git init creates master by de…
    
    b4222bfc: Add workflow_dispatch trigger to HF deploy workflow
  - smd_ida_tools2
    
    bf85dd09: Fixed IDA Pro crash when creating a function in Granada (maybe in som…
2. 🔗 badlogic/pi-mono v0.54.0 release
  Added
  - Added default skill auto-discovery for .agents/skills locations. Pi now discovers project skills from .agents/skills in cwd and ancestor directories (up to git repo root, or filesystem root when not in a repo), and global skills from ~/.agents/skills, in addition to existing .pi skill paths.
3. 🔗 r/LocalLLaMA Free ASIC Llama 3.1 8B inference at 16,000 tok/s - no, not a joke rss
  
  Hello everyone,
  
  A fast inference hardware startup, Taalas, has released a free chatbot interface and API endpoint running on their chip. They chose a small model intentionally as proof of concept. Well, it worked out really well, it runs at 16k tps! I know this model is quite limited but there likely exists a group of users who find it sufficient and would benefit from hyper-speed on offer.
  
  Anyways, they are of course moving on to bigger and better models, but are giving free access to their proof-of-concept to people who want it.
  
  More info: https://taalas.com/the-path-to-ubiquitous-ai/
  
  Chatbot demo: https://chatjimmy.ai/
  
  Inference API service: https://taalas.com/api-request-form
  
  It's worth trying out the chatbot even just for a bit, the speed is really something to experience. Cheers!
  
  EDIT: It's worth noting that the chatbot demo actually undersells the speed on display. Anything over a few hundred tps is perceived as instantaneous, so the experience of 1k tps vs 16k tps should be pretty similar. So you are only seeing the bottom few percent of the speed on offer. A proper demo would be using a token-intensive workload with their API. Now THAT would be something to see.
  
  submitted by /u/Easy_Calligrapher790
  [link] [comments]
4. 🔗 r/Leeds Leeds Reddit mixed social meet up for m&f aged 35-45 confirmed rss
  
  UPDATED at 11.30pm:
  
  Hey everyone i posted a few weeks ago reaching out asking if people aged 35-45 would be keen on small group social meet ups in Leeds City centre to make new friends. And I did not expect to get so many of your replies. Also, thanks for those who got in touch and all the lovely comments. Appreciate it!
  
  The first 2 socials are planned and nearly all booked up. I will share what spaces are left to book:
  
  For anyone asking, I am trying to keep a balance of men and women as best as possible so those of us have a diverse range of people to socialise with.
  
  4.3.26 @ 6.30pm-8.30pm - 1 female space left aged 35-45. Venue in Trinity Centre, city centre, I have reserved tables & the small group space at the venue. All male rsvp/spaces fully booked.
  
  For after work dinner - LOTS of options on food and so very affordable. No pre-orders needed. Pay what you order individually.
  
  Capacity: 14 attendees.
  
  7.3.26 @ 10am-12pm Leeds Docks venue for coffee & brunch - FULLY BOOKED. No more spaces left.
  
  For coffee & brunch, lovely venue and affordable coffees, teas & brunch. I will have to chase pre-orders a few days beforehand, it's required by the venue. Pay what you order individually. Capacity: 14 attendees - Sorry all booked up!
  
  Booking is mandatory. No plus ones.
  
  Many thanks 😊
  
  F, aged 40
  
  submitted by /u/MasterMembership4506
  [link] [comments]
5. 🔗 r/reverseengineering i found the macbook’s built in accelerometer and it streams in real time (python, m3 pro) rss
  
  submitted by /u/BillieWeston
  [link] [comments]
6. 🔗 r/Leeds Swiss food rss
  
  Anywhere restaurants/bars/cafe’s in Leeds that sells Swiss food or is Swiss themed?
  
  submitted by /u/AdComprehensive4246
  [link] [comments]
7. 🔗 r/LocalLLaMA Pack it up guys, open weight AI models running offline locally on PCs aren't real. 😞 rss
  
  | submitted by /u/CesarOverlorde
  [link] [comments]
  ---|---
8. 🔗 r/york York Minster in the rain rss
  
  | The puddles and the Minster lined up rather nicely the other night in the rain. submitted by /u/Borobeer49
  [link] [comments]
  ---|---
9. 🔗 badlogic/pi-mono v0.53.1 release
  
  Release v0.53.1
10. 🔗 r/york Do you have any York related stories you find interesting or documentary worthy? rss
  
  I have lived around York forever and I am so interested in stories from around York that I might not be aware of no matter how niche. I have recently gotten into video production so this is interesting for a number of reasons but I would love any stories people have! Thanks!
  
  submitted by /u/Beneficial_Law6076
  [link] [comments]
11. 🔗 r/york Looking for tea community/tea friends in York #gongfucha rss
  
  | Hello~! As the title says, are there any tea nerds out there in York? ☺️ Would really like to connect with people who are into tea. I’m into most teas but currently really into Chinese teas and the occasional Japanese tea. I make tea gongfu style as pictured above. Was having some tea today and thought how fun it would be to share this with likeminded people! Thank you for reading! 🙏 submitted by /u/morksuggan
  [link] [comments]
  ---|---
12. 🔗 r/reverseengineering Who said C# isn't for low-level tools? My new Hex Editor uses MMF and a custom DSL to outperform traditional binary editors. rss
  
  submitted by /u/FnaFi_
  [link] [comments]
13. 🔗 r/Yorkshire Arrest after two teenagers found dead at Bridlington holiday park rss
  
  | submitted by /u/Kagedeah
  [link] [comments]
  ---|---
14. 🔗 r/Leeds Fritz Kola in Leeds? rss
  
  Very odd request, but trying to shift away from Coke, and been looking for some good alternatives in Leeds. Adored Fritz Kola on my travels, does anyone know if any supermarkets or smaller shops in Leeds stock it? Many thanks in advance
  
  submitted by /u/WestComfortable8423
  [link] [comments]
15. 🔗 r/Yorkshire Wakefield rss
  
  What are peoples opinion on Wakefield area? We are looking to relocate and have family in Wakefield. I had a look on police.uk which tells you about crimes in the area. Which says Wakefield has a lot of violent and sexual crimes committed. The areas we were looking at were. Horbury, castleford and a tiny bit out of Wakefield town centre, we have a 7 month old so wanted to be close to baby groups/ activities to do, plus being close to a family member.
  
  submitted by /u/Postpartum_Bowser-26
  [link] [comments]
16. 🔗 @binaryninja@infosec.exchange Connect with us on Friday 2/20 @ 3pm for some advanced exploitation! Brandon mastodon
  
  Connect with us on Friday 2/20 @ 3pm for some advanced exploitation! Brandon (teaching Firmware RE at RE//verse) has a spicy meshtastic bug from class for us to preview, then we'll continue with more advanced C++ reversing! https://www.youtube.com/watch?v=k0s7W3Wuipg
17. 🔗 r/wiesbaden Möbel zu verschenken rss
  
  EDIT: Das Sofa ist bis Sonntagabend reserviert. Ich schicke trotzdem allen Interessenten gerne noch Bilder falls die Abnehmer bis Sonntagabend absagen sollten ist es wieder verfügbar. Die Stühle werden am Dienstag abgeholt!
  
  Moin ihr Lieben! Aufgrund unglücklicher Umstände haben mir meine Umzugshelfer abgesagt und ich muss zu Ende Februar aus meiner Wohnung in Wiesbaden raus. Da ich für meine neue Wohnung eh lieber andere Möbel hätte, findet sich hier vielleicht jemand der etwas von meinem Hausstand übernehmen möchte. Ich möchte dafür nichts haben, wer was gebrauchen kann soll es haben! Ich weiß die Zeiten sind nicht leicht für alle und vielleicht kann ich jemandem eine Freude machen. Schicke gerne bei Interesse Bilder der Möbel! Die Möbel sind bis auf das Schlafsofa alle im letzten Januar gekauft worden und kaum in Benutzung gewesen.
  
  Abzugeben habe ich: 160x200 Malm Bett mit 4 Schubladen in Holzoptik 1 ausziehbares Schlafsofa mit grobem beigem Bezug 1 runden Esstisch mit 4 Stühlen (entweder als Kombi oder jeder das was er mag)
  
  Meldet euch gerne bei Interesse! :)
  
  submitted by /u/improvedjay
  [link] [comments]
18. 🔗 r/wiesbaden Smoke-together rss
  
  submitted by /u/Wide-Distribution-78
  [link] [comments]
19. 🔗 r/Leeds How would you get a feel for Horsforth's vibe? rss
  
  I'm visiting the area tomorrow on an unrelated errand, but it's on my list of potential places when it comes to buying a house in the next year or so (moving from the city centre).
  
  If you had a few hours in Horsforth, what would you do or recommend to get a feel for the vibe of the area, in terms of what it's like to live there?
  
  submitted by /u/Global_Bike_6647
  [link] [comments]
20. 🔗 Andrew Ayer - Blog Why IP Address Certificates Are Dangerous and Usually Unnecessary rss
  Imagine you're connecting to an IP address over TLS. The server presents a valid, properly-issued IP address certificate from a publicly-trusted certificate authority. But you're not really talking to that IP address, but to a man-in-the-middle (MitM) who was assigned the IP address over a year ago. How could this be? Unfortunately, publicly-trusted IP address certificates just don't provide the same level of security as certificates for domain names. Unless you're operating a DNS-over-TLS or DNS-over-HTTPS resolver, you should not use IP address certificates. You'll be much more secure with domain name certificates.
  
  TL;DR:
  - A "valid" IP address certificate can mean "someone who controlled this IP address any time in the last 796 days. "
  - Certificate validation happens in the past, not at connection time, and IP addresses are reused constantly.
  - This risk exists for domains too, but it's far worse for IP addresses, especially in cloud environments.
  - IP address certificates only make sense for DNS-over-TLS and DNS-over-HTTPS resolvers.
  - For everything else, use domain name certificates; even short-lived servers can do this practically by embedding IP addresses in hostnames.
  (When I say IP address certificate, I mean a TLS certificate with an IP address subjectAltName, which allows a certificate to authenticate a connection to an IP address, rather than a domain name as is typical on the Web. Public certificate authorities have been allowed to issue IP address certificates for a long time, but I fear they will become more popular since Let's Encrypt added support for them last month.)
  
  The basic security property provided by a certificate is that the certificate authority has validated that the certificate subscriber (the person who applies for the certificate and knows its private key) is authorized to represent the domain name or IP address in the certificate. This ensures that the other end of a TLS connection is truly the domain or IP address that you want to connect to, not a MitM impostor.
  
  But the validation is not done every time a TLS connection is established; rather, it was done at some point in the past. Thus, the certificate subscriber may no longer be authorized to represent the domain or IP address.
  
  How old might the validation be? As of February 2026, certificate authorities are allowed to issue certificates that are valid for up to 398 days. (Let's Encrypt limits their IP address certs to 6 days, but you have to worry about attackers using other CAs, not just the CA you use.) So the validation may be 398 days old. But it gets worse. When issuing a certificate, CAs are allowed to rely on a validation that was done up to 398 days prior to issuance. So when you establish a TLS connection, you may be relying on a validation that was performed a whopping 796 days ago. You could be talking not to the current assignee of the domain or IP address, but to anyone who was assigned the domain or IP address at any point in the last 2+ years.
  
  Validation performed IP address reassigned Certificate issued to previous assignee You connect validation reuse time (398 days) certificate lifetime (398 days) window of vulnerability (796 days)
  
  This is a problem with both domains and IP addresses, but it's way worse with IP addresses. While it's still very possible to register a domain that no one has ever registered before, you don't have this luxury with IPv4 addresses. There are no unassigned IPv4 addresses left; when you get an IPv4 address, it has already been assigned to someone else. In some cases, particularly in cloud environments, the address could have had as many tenants as a room at a Motel 6.
  
  For some use cases, the risk is unavoidable. For example, DNS-over-TLS and DNS-over-HTTPS resolvers have to be contacted by IP address, to avoid a circular dependency on DNS resolution. Domain name certificates are not an option. Fortunately, by 2029, the maximum certificate lifetime will be 47 days, and the maximum validation reuse period will be 10 days, so the risk window will be only 57 days. That's not too bad for a service that's likely to exist for many years with the same IP address.
  
  But even with a 57 day window, other use cases should just use domain name certificates. One use case for IP address certificates is particularly misguided: securing short-lived cloud workloads. Let's Encrypt describes this use case as:
  
  Securing ephemeral connections within cloud hosting infrastructure, like connections between one back-end cloud server and another, or ephemeral connections to administer new or short-lived back-end servers via HTTPS - as long as those servers have at least one public IP address available.
  
  On Bluesky, Ryan Hurst goes into more detail:
  
  Modern infrastructure no longer has stable hostnames, static IPs, or long- lived trust anchors. Workloads spin up before DNS exists, live briefly, and disappear. Trust has to keep up.
  
  Short-lived and IP certificates make it possible to use TLS before a DNS name exists, reduce friction for DNS over HTTPS adoption, secure ephemeral devices and services by default, and shift trust from long-lived credentials to automated renewal.
  
  As I understand it, the use case is running servers which accept TLS connections and exist for a very short period, like minutes. The most secure implementation would be to assign the server a unique, never-before-used hostname under your domain, publish a DNS record pointing the hostname to the server's IP address, get a domain name certificate, and have clients connect to the hostname. Thanks to the unique hostname, clients can be sure they're connecting to the right server and not to an impostor who was assigned the IP address at some point in the past.
  
  But Ryan suggests that it might not be possible to wait for a DNS record to be published before the server needs to be usable. Fortunately, it's still possible to avoid IP address certificates. Instead, you can publish, in advance, a DNS record under your domain for every IP address you might need to use. For example, ip-192-0-2-1.yourcompany.example would resolve to 192.0.2.1. ISPs commonly publish DNS records like this for their entire IP address space, so it's possible to do at scale. Have your clients connect to your short-lived server using this DNS record, rather than an IP address. To prevent would-be attackers from completing domain validation under your domain using a non-DNS validation method, you should also publish a CAA record for your domain that uses ACME account binding to restrict issuance to your ACME account. Now clients can be sure they're connecting to a server controlled by your organization, rather than anyone who happened to be assigned the same cloud IP address in the last 2 years.
  
  You can also monitor Certificate Transparency logs to look for unauthorized certificates for your domain. Monitoring Certificate Transparency is not practical when using IP address certificates with short-lived cloud workloads, since the set of IP addresses that you need to monitor will be constantly changing as you create and destroy your servers, and it will be hard to tell whether an unknown certificate is malicious or just an innocent issuance to someone who got assigned the same IP address.
  
  I encourage you to think long and hard before using IP address certificates, especially for short-lived cloud servers. The high risk of stale validation, combined with the inability to effectively monitor Certificate Transparency, bring IP address certificates uncomfortably close to opportunistic encryption (TLS without certificate validation), even with post-2029 shortened lifetimes. Fortunately, you can embed IP addresses in pre-published DNS records if you can't publish DNS records on the fly. Doing a little extra DNS work is a small price to pay for avoiding the inherent risks of IP address certificates.
21. 🔗 r/wiesbaden Wie hat sich Wiesbaden in den letzten 20 Jahren verändert? rss
  
  Ich wohne erst seit etwas mehr als zwei Jahren in Wiesbaden und komme aus einer ganz anderen Ecke Deutschlands.
  
  Aus meiner Sicht hat Wiesbaden viel positives zu bieten, aber leider auch viel negatives, was das Lebensgefühl für mich und meine Freundin einschränkt, was bestimmt auch an unserem Viertel liegt in welchen wir wohnen.
  
  Daher würde ich mal gerne von den Alteingesessenen wissen, wie sehr sich Wiesbaden in den letzten 20 Jahren verändert hat und ob ihr mit dem Trend der Stadt glücklich seit oder eher nicht.
  
  Liebe Grüße!
  
  submitted by /u/Extension-Cry225
  [link] [comments]
22. 🔗 r/Leeds Thinking of moving from Meanwood to Garforth rss
  
  Hey all,
  
  Currently renting in Meanwood and like it, but thinking about buying in Garforth.
  
  I’ll be working longterm in York, my wife works in Wakefield (needs train access), and primary school for our daughter is a big priority.
  
  We’re not bothered about pubs/restaurants just want a safe, family friendly area with good schools and transport.
  
  On paper Garforth makes sense, but I’m hesitating because we feel settled where we are.
  
  Is Garforth a good long-term base for a young family? Any honest thoughts appreciated
  
  Thanks
  
  submitted by /u/Similar_Win5490
  [link] [comments]
23. 🔗 r/york York Minster West Window rss
  
  | Last night and a cold but dry and clear night. submitted by /u/York_shireman
  [link] [comments]
  ---|---
24. 🔗 r/wiesbaden Wirtschaft in Wiesbaden ⬇️ rss
  
  https://preview.redd.it/ozr9ixmulfkg1.png?width=1408&format=png&auto=webp&s=921aef4d58e59046d3e6650b075de7baf0034879
  
  submitted by /u/Western-Coat-3812
  [link] [comments]
25. 🔗 r/wiesbaden Inliner fahren in Wiesbaden? rss
  
  Vor einigen Jahren bin ich sehr viel inline Skates gefahren, und jetzt habe ich die Zeit wieder damit anzufangen. Gibt es hier in der Nähe Treffen oder ähnliches? Strecken die man empfehlen kann? Etc. danke
  
  submitted by /u/Old-Bus-6698
  [link] [comments]
26. 🔗 r/wiesbaden Warum wird Wiesbaden oft als weniger attraktiv angesehen als Mainz? rss
  
  Ich verstehe nicht, warum viele Mainz als ansprechender ansehen als Wiesbaden. In Mainz, wo ich wohne, gibt es praktisch keine zentrumsnahen Grünflächen, abgesehen von dem kleinen Altstadtteil ist die Stadt auch sehr hässlich, es gibt keine wirklich belebten Orte abseits der Gastronomie und auch keine brauchbaren Radwege, während man in Wiesbaden zumindest breitere Straßen hat. Auch die Innenstadt in Mainz ist wenig schön und sehr klein, während man in Wiesbaden sehr viele Geschäfte und attraktive Straßen und Gassen findet. Ich frage mich, wo kommt dieser Mainz-Hype her?
  
  submitted by /u/Western-Coat-3812
  [link] [comments]
27. 🔗 remorses/critique critique@0.1.109 release
  What's new
  
  Syntax highlighting
  - Generalized delimiter balancing to fix tree-sitter misparsing when a diff hunk starts mid-string
    
    Python: balance """ and ''' triple-quoted strings / docstrings
    
    Go: balance ``` raw string literals
    
    Scala, Swift, Julia: balance """ triple-quoted strings
    
    TypeScript/JS backtick template literals (existing, now part of a unified system)
  Bug fixes
  - --filter: paths containing $ characters (e.g. d.$owner.$repo.tsx) now work correctly — switched to single quotes in shell commands to prevent variable expansion
  - --stdin (lazygit pager): strip ANSI escape codes from colored diffs before parsing so filenames are no longer mangled — thanks @skoch13 for the lazygit README fix that surfaced this
  Internal
  - Replaced balance-backticks.ts with a generic balance-delimiters.ts supporting any multi-char delimiter
  - 42+ new tests covering all supported languages and edge cases
28. 🔗 r/reverseengineering Agentic Mobile SAST & Protection Bypass rss
  
  submitted by /u/New-Parfait-9988
  [link] [comments]
29. 🔗 r/LocalLLaMA I'm 100% convinced that it's the NFT-bros pushing all the openclawd engagement on X rss
  
  | I'm absolutely sure of it. The same usual suspects, the same language, the same who stole from whom the next million dollar ideas. It's insane. NFT-bros are now peddling openclawd crypto schemes. It's all the same BS quasi-tech lingo wrapped into neverending posts with meme-like pictures full of slogans, and graphs that literally means less than nothing, that lead back to 'blockchain, blah, blah blah, agentic, blah, blah, prediction markets". I have enough of this. Is this the sign of a real bubble? In the fall people were talking on X about how AI is in a bubble - which is never the time for bubbles to burst. But now every grifter discovered AI agents. Now, normally it takes 1-2 years to get from one stage to another, (sorry I'm old) but we are in a super accelerated scenario. Felt like 1998 in fall. It feels we jumped to 2000 suddenly. So IDK. Smells like a bubble is expanding rapidly. Where is my thumbtack? Is AGI is coming on X (Sign of something?) submitted by /u/FPham
  [link] [comments]
  ---|---
30. 🔗 r/LocalLLaMA Kitten TTS V0.8 is out: New SOTA Super-tiny TTS Model (Less than 25 MB) rss
  | Model introduction: New Kitten models are out. Kitten ML has released open source code and weights for three new tiny expressive TTS models - 80M, 40M, 14M (all Apache 2.0) Discord: https://discord.com/invite/VJ86W4SURW GitHub: https://github.com/KittenML/KittenTTS Hugging Face - Kitten TTS V0.8:
  - Mini 80M: https://huggingface.co/KittenML/kitten-tts-mini-0.8
  - Micro 40M: https://huggingface.co/KittenML/kitten-tts-micro-0.8
  - Nano 14M: https://huggingface.co/KittenML/kitten-tts-nano-0.8
  The smallest model is less than 25 MB, and around 14M parameters. All models have a major quality upgrade from previous versions, and can run on just CPU. Key Features and Advantages
  1. Eight expressive voices: 4 female and 4 male voices across all three models. They all have very high expressivity, with 80M being the best in quality. English support in this release, multilingual coming in future releases.
  2. Super-small in size: The 14M model is just 25 megabytes. 40M and 80M are slightly bigger, with high quality and expressivity even for longer chunks.
  3. Runs literally anywhere lol: Forget "no GPU required." This is designed for resource-constrained edge devices. Great news for GPU-poor folks like us.
  4. Open source (hell yeah!): The models can be used for free under Apache 2.0.
  5. Unlocking on-device voice agents and applications: Matches cloud TTS quality for most use cases, but runs entirely on-device (can also be hosted on a cheap GPU). If you're building voice agents, assistants, or any local speech application, no API calls needed. Free local inference. Just ship it.
  6. What changed from V0.1 to V0.8: Higher quality, expressivity, and realism. Better training pipelines and 10x larger datasets.
  submitted by /u/ElectricalBar7464
  [link] [comments]
  ---|---
31. 🔗 r/york What is the Postgrad and LGBT community in York like? Is there any nightlife? rss
  
  Basically the title, I'll be starting a postgrad in York soon and will be turning 24. I'll obviously be too old for freshers and where the undergrads go (and I've been there done that) but wonder if there's any nightlife for someone more my demographic (predominantly gay and women).
  
  Is there a large enough postgrad community where I won't feel like the odd one out for being older and not an undergrad?
  
  Any general suggestions?
  
  submitted by /u/GeeCeeSlay7
  [link] [comments]
32. 🔗 Rust Blog Rust participates in Google Summer of Code 2026 rss
  We are happy to announce that the Rust Project will again be participating in Google Summer of Code (GSoC) 2026, same as in the previous two years. If you're not eligible or interested in participating in GSoC, then most of this post likely isn't relevant to you; if you are, this should contain some useful information and links.
  
  Google Summer of Code (GSoC) is an annual global program organized by Google that aims to bring new contributors to the world of open-source. The program pairs organizations (such as the Rust Project) with contributors (usually students), with the goal of helping the participants make meaningful open- source contributions under the guidance of experienced mentors.
  
  The organizations that have been accepted into the program have been announced by Google. The GSoC applicants now have several weeks to discuss project ideas with mentors. Later, they will send project proposals for the projects that they found the most interesting. If their project proposal is accepted, they will embark on a several months long journey during which they will try to complete their proposed project under the guidance of an assigned mentor.
  
  We have prepared a list of project ideas that can serve as inspiration for potential GSoC contributors that would like to send a project proposal to the Rust organization. However, applicants can also come up with their own project ideas. You can discuss project ideas or try to find mentors in the #gsoc Zulip stream. We have also prepared a proposal guide that should help you with preparing your project proposals. We would also like to bring your attention to our GSoC AI policy.
  
  You can start discussing the project ideas with Rust Project mentors and maintainers immediately, but you might want to keep the following important dates in mind:
  - The project proposal application period starts on March 16, 2026. From that date you can submit project proposals into the GSoC dashboard.
  - The project proposal application period ends on March 31, 2026 at 18:00 UTC. Take note of that deadline, as there will be no extensions!
  If you are interested in contributing to the Rust Project, we encourage you to check out our project idea list and send us a GSoC project proposal! Of course, you are also free to discuss these projects and/or try to move them forward even if you do not intend to (or cannot) participate in GSoC. We welcome all contributors to Rust, as there is always enough work to do.
  
  Our GSoC contributors were quite successful in the past two years (2024, 2025), so we are excited what this year's GSoC will bring! We hope that participants in the program can improve their skills, but also would love for this to bring new contributors to the Project and increase the awareness of Rust in general. Like last year, we expect to publish blog posts in the future with updates about our participation in the program.
33. 🔗 Ampcode News GPT‐5.3‐Codex rss
  
  GPT-5.3-Codex now powers Amp's deep mode.
  
  It’s a truly impressive model. After using it, we realized: "The coding agent is dead."
  
  Everything is changing again. With GPT-5.3-Codex, the agent is no longer the bottleneck. Our ability to tell it what to do is.
  
  In our experience, it's a better than GPT-5.2-Codex in every dimension. It still goes deep, but it's learned when to stop.
  
  To use it: open the command palette with Ctrl-O and run the command mode: use deep in the Amp CLI, or select deep mode in the Amp editor extension's prompt field.
34. 🔗 Ampcode News The Coding Agent Is Dead rss
  
  The current generation of coding agents is dead. The heart is still beating, yes, but the bullet has already left the chamber. This generation isn't the future.
  
  With the newest models, the agent — the prompts and tools you wrap around a model — is no longer the limiting factor. These models can be powerful with nearly any tool you throw at them. A simple tool called bash is often enough. Whether you show LSP diagnostics here or there is dwarfed by what these models can do through sheer brute force. As long as it mostly gets out of the way, nearly any agent can get good results out of them. These new models barely need to be told how to act like coding agents anymore. They're now fully trained for that.
  
  How you organize your codebase for agents, how your organization uses them — those are now the bottlenecks.
  
  The frontier has shifted. And we're going to make massive changes to Amp so it stays on the frontier.
  
  It's tempting not to. Amp is growing faster than ever. We could stay, keep things as they are, pretend that the coding agents of February 2026 are the final form and watch the numbers go up. We could say yes to more VC money and sell $2,000 worth of tokens for $20 a month.
  
  But what would that buy us? A local maximum. And while we're sitting on top of the local maximum, each new model generation would move the frontier further and further into the distance. And the longer we keep things the same, the more we select for users that aren't comfortable at the frontier. But the users we want and need are those who are willing to pack up and travel light with us.
  
  So, Amp has to evolve.
  
  First step: we're going to kill the Amp editor extensions for VS Code and Cursor. We're unshackling these models from the editor.
  
  By keeping these new models in an editor sidebar, we restrict them. They're now much more than mere assistants. They no longer need the hand-holding and really want to kick off their training wheels. They want to write code and run even when you're not sitting in front of your editor. It's time to see what they can do without supervision.
  
  The Amp editor extensions will self-destruct on March 5 at 8pm Pacific Time. Time to switch to the Amp CLI.
  
  Because we're keeping the CLI, for now. Its heart is still beating and it helps us get to where we need to go. Think of it as a ladder: we use it to climb up to the next level and then we might not need it. It's flexible, light, easy to change, can be run anywhere and anytime. It attracts the kind of users we're building for.
  
  For those of you who read "everything is changing" on our landing page back in April 2025 and nodded, this is nothing new. Our only promise was that when the frontier moved, we would move too.
  
  If you're new to Amp: welcome. Come with us. Today Amp ceases to be a coding agent. It's no longer a point on a map. It's an arrow. Not a stop, but a ride.
  
  And it might self-destruct too.