🏡


to read (pdf)

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

  1. April 19, 2026
    1. 🔗 r/wiesbaden Kostenloses Probetraining in Wiesbaden (inkl. Trainer) rss

      Hey zusammen,

      ich bin Gym-Manager bei EVO Fitness in Wiesbaden-Mitte. Wir bieten kostenlose Probetrainings an – inklusive Einweisung in alle Geräte und persönlicher Unterstützung durch einen Trainer.

      ⏱ Dauer: ca. 1 Stunde

      💪 Mit individueller Betreuung

      🆓 Komplett kostenlos & unverbindlich

      Wenn du Interesse hast, schreib mir einfach eine Direktnachricht!

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

    2. 🔗 HazAT/glimpse v0.8.0 release

      Install:

      npm install glimpseui@0.8.0
      

      Pi agent package:

      pi install npm:glimpseui@0.8.0
      

      The companion extension is no longer bundled as a default pi extension. It's moved to examples/companion/ — if you liked it, add it manually to your pi extensions config. Glimpse itself is unchanged.

      ♻️ Refactoring

      • Move pi companion extension to examples/companion/ — no longer auto-registered on install

      🐛 Bug Fixes

      • Swift strict concurrency error in startStdinReader — thanks @jfanals! (#13)
    3. 🔗 r/Yorkshire I was up in Osmotherly yesterday and quite a few cyclists with numbers on came past. Just curious as to what the race was. Any ideas? rss

      Also, The Sheep wash at Osmotherly is brilliant.

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

    4. 🔗 r/Yorkshire Billy Banks Woods, a walk through the past part 2. rss
    5. 🔗 r/york I just can't stop snapping 🌸 rss
    6. 🔗 Register Spill Joy & Curiosity #82 rss

      This one's short, because it's been a week full of programming and building, less reading. And this weekend's equally busy, so here's a question I've been flipping around in my head for months now:

      What are we learning about working with these models that will be valuable in the future?

      In his Lex Fridman interview, ThePrimeagen said something that stuck with me: "Is anyone actually falling behind for not using AI then? Because if the interface is going to change so greatly that all of your habits need to fundamentally change […], have I actually fallen behind at all? Or will the next gen actually just be so different from the current one that it's like, yeah, you're over there actually doing punch card AI right now. I'm going to come in at compiler time AI, so different that it's like what's a punch card?"

      There's something to this. The frontier models are now much more forgiving when it comes to prompts. We no longer have to write "you are a senior engineer" in our prompts. "Don't make mistakes" is more a prayer than a helpful trick. The days of the Prompt Engineer won't be visible on the timeline if we zoom out to even five years.

      Nowadays, I'm even convinced that a lot of what we considered important for manual context management is now no longer needed. (Yes, we're shipping soon.) We're close to the point where you no longer have to care whether you're at 30% or 70% of the context window.

      And I'm also convinced that the models will get even better.

      Now, maybe it is a form of sunk cost fallacy, a bias talking, but still: I do think that I got better at working with these models over the past two years. It might not be relevant anymore whether I write down my task before or after I include a file in a prompt, but I think I've gained some meta-abilities that made me better at solving problems through the use of agents: chopping up problems into engineering tasks and sequencing them, figuring out what the pitfalls (that wouldn't be pitfalls for humans) are, knowing what's poison in the codebase and what isn't. Stuff like that.

      In the most general sense, I think I've learned how to work with artificial intelligence. And if prompt engineering tricks are punch cards, then that might be seen as learning about computation.

      • This is, at least for me, already a Hall of Fame comment: "For reasons which it would take a while to unpack, if is often the case that the best (or sometimes only) way to find out what programming actually needs to be done, is to program something that's not it, and then replace it. This may need to be done multiple times. Programming is only occasionally the final product, it is much more often the means of working through what it is that is actually needed. This is very difficult for the people who ask for the software, to understand, and it is quite often very difficult for the people doing the programming to understand. Most of what is being done, during programming, is working through the problem space in a way which will make it more obvious what your mistakes are, in your understanding of the problem and what a solution would look like. Once you have arrived at that understanding, then there are a variety of ways to make what you need, but that is not the rate-limiting step." So, so, so good. This is what software development is: learning.

      • Fractal Paris and Fractal Istanbul. Lovely!

      • Rands: The Complicators, The Drama Aggregators, and The Avoiders. Read and recognize people you've worked with.

      • Brian Cantrill on the peril of laziness lost: "The problem is that LLMs inherently lack the virtue of laziness. Work costs nothing to an LLM. LLMs do not feel a need to optimize for their own (or anyone's) future time, and will happily dump more and more onto a layercake of garbage. Left unchecked, LLMs will make systems larger, not better." Read this at the start of the week and then constantly thought of it whenever I asked my agent whether this is "truly the simplest, most minimal, as-little-as-possible and as-much-as-needed solution?"

      • Vicki Boykis, in some sense in harmony with Brian Cantrill's thoughts, on Mechanical Sympathy: "Mechanical sympathy for both developers and end-users means understanding when asyncio is and is not helpful. It means using the right language, the right build system, the right font. It means using the least amount of tooling possible. Allowing for local development. It means reading code inside out rather than top to bottom. Using uv. Removing code where not necessary. Respecting boundaries."

      • stevey wrote a tweet about AI adoption at Google and got pushback from Demis Hassabis and others and, well, I actually don't care that much about AI adoption at Google, but I find this one thought in there very fascinating: "There has been an industry-wide hiring freeze for 18+ months, during which time nobody has been moving jobs. So there are no clued-in people coming in from the outside to tell Google how far behind they are, how utterly mediocre they have become as an eng org." I know that people aren't sure whether there are more or less software jobs right now, but from where I'm sitting it does look like hiring has slowed and I find it fascinating to think about the second-order effects of that: is there less industry-wide diffusion of frontier knowledge because hiring has slowed?

      • Shifted something in my brain: Nucleus Nouns. Very good and much more thought-inspiring than the usual "focus! focus! focus!" chants.

      • The Closing of the Frontier: "There is something special about training a model on all of humanity's data and then locking it up for the benefit of a few well-connected organizations that you have relationships with. Maybe you'll notice another historical pattern here. Extract value from a population that can't meaningfully consent, concentrate the returns within a small inner circle, and then offer some version of charity to the people you extracted from as moral cover for the arrangement."

      • Andy Matuschak has the Practice Guide for Computer printed out and hanging above his desk.

      • Apparently I'm the last person to learn about this idea, but who cares, it's great and I think I want to try this: The Spark File.

      • Sometimes I read things online and it makes me really happy that we have the Internet and that smart, beautiful minds share their thoughts online. Here's James Somers with his idea of the Paper Computer: "Now that we have actually good AI, I have this vision of a form of computing that doesn't involve me using a computer so much. Imagine you had the day's emails to go through. It would be nice if the ones that required a simple decision could be dispatched with a few pen-strokes: I could write down a date that would work for that meeting; check a box to accept that invitation; etc. If an email required me to review a draft, I'd love to mark up a print version on my couch, sans screen, and have those notes scanned and sent off as if I'd done the whole thing on Google Docs."

      • Tim Zaman, who worked at NVIDIA, Tesla, X, Google DeepMind and now at OpenAI on AI infrastructure on Getting Into AI Infra. I'm convinced that posts like these create and change entire lifes. I love it. Also: nearly made me want to build a cluster.

      • It's been a while since I've thought about people who have not yet walked through the one-way door that makes you say "holy shit, AI is going to change everything", but Armin shared his thoughts after encountering people still being skeptical: The Center Has a Bias. Well worth reading.

      • Dwarkesh Patel shared what he learned this week and note how interesting that is and how enjoyable it is to read, even though (or is it because of?) it's not polished at all.

      • Drew Breunig, following the Anthropic Mythos frenzy and some companies closing their open-source projects down for fear of security vulnerabilities being discovered, says Cybersecurity Looks Like Proof of Work Now: "If Mythos continues to find exploits so long as you keep throwing money at it, security is reduced to a brutally simple equation: to harden a system you need to spend more tokens discovering exploits than attackers will spend exploiting them."

      • But antirez disagrees: AI cybersecurity is not proof of work. Both posts are very interesting and I recommend reading through them.

      • I'm in the process of setting up my 2013 MacBook Pro for my 4-year-old daughter and Peter recommended this lovely page to let her type on: tiny-terminal.com.

      • So, of course, I had to fork it, bought a domain, and let Amp translate it to German so my kids can type words they already know in there: kleines-terminal.de.

      • Turing Award winner Michael Rabin has passed away. Here's "an assorted collection of quotations due to Professor Michael Rabin, produced at Harvard University during the Fall 1997 incarnation of the course Computer Science 226r": Rabinism Collection.

      • Thoughts and Feelings around Claude Design.

      • Another way to think about the question of whether AI will create more jobs or not, by Aaron Levie: "Why will AI create more jobs in plenty of industries? It's because we're going to use AI to accelerate output in one area, and then eventually you run into a new bottleneck somewhere else in the process that still requires humans." This sounds very likely to me. But, of course, "more jobs" doesn't mean it'll be the same jobs and then some. Everything's changing.

      • Related, Gary Bernhardt: "This might be a Mel moment. It's not immediately obvious that Mel is a tragic story. He clearly loved the work. Then the work changed and, presumably, he was left behind. The thing he perfected no longer mattered. There might be millions of Mels right now."

      • Wow, look at just the table of contents here: "I have for years been interested in sleep research due to my professional involvement in memory and learning. This article attempts to produce a synthesis of what is known about sleep with a view to practical applications, esp. in people who need top-quality sleep for their learning or creative achievements."

      Busy weekend? You should subscribe:

    7. 🔗 Textualize/textual The small potatoes Release release

      Small potatoes update, to fix a glitch with anchor.

      [8.2.4] - 2026-04-19

      Added

      • Added DOM.update_classes #6478

      Fixed

      • Fixed anchor released when scrolling down with the trackpad #6503
    8. 🔗 WerWolv/ImHex Nightly Builds release

      Nightly

      a89d711 Changelog

      • fix: Truncate utf8 only at code point boundaries (#2699)
      • Feature/code folding (#2688)
  2. April 18, 2026
    1. 🔗 Simon Willison Changes in the system prompt between Claude Opus 4.6 and 4.7 rss

      Anthropic are the only major AI lab to publish the system prompts for their user-facing chat systems. Their system prompt archive now dates all the way back to Claude 3 in July 2024 and it's always interesting to see how the system prompt evolves as they publish new models.

      Opus 4.7 shipped the other day (April 16, 2026) with a Claude.ai system prompt update since Opus 4.6 (February 5, 2026).

      I had Claude Code take the Markdown version of their system prompts, break that up into separate documents for each of the models and then construct a Git history of those files over time with fake commit dates representing the publication dates of each updated prompt - here's the prompt I used with Claude Code for the web.

      Here is the git diff between Opus 4.6 and 4.7. These are my own highlights extracted from that diff - in all cases text in bold is my emphasis:

      • The "developer platform" is now called the "Claude Platform".
      • The list of Claude tools mentioned in the system prompt now includes "Claude in Chrome - a browsing agent that can interact with websites autonomously, Claude in Excel - a spreadsheet agent, and Claude in Powerpoint - a slides agent. Claude Cowork can use all of these as tools." - Claude in Powerpoint was not mentioned in the 4.6 prompt.
      • The child safety section has been greatly expanded, and is now wrapped in a new <critical_child_safety_instructions> tag. Of particular note: "Once Claude refuses a request for reasons of child safety, all subsequent requests in the same conversation must be approached with extreme caution."
      • It looks like they're trying to make Claude less pushy: "If a user indicates they are ready to end the conversation, Claude does not request that the user stay in the interaction or try to elicit another turn and instead respects the user's request to stop."
      • The new <acting_vs_clarifying> section includes:

        When a request leaves minor details unspecified, the person typically wants Claude to make a reasonable attempt now, not to be interviewed first. Claude only asks upfront when the request is genuinely unanswerable without the missing information (e.g., it references an attachment that isn't there).

        When a tool is available that could resolve the ambiguity or supply the missing information — searching, looking up the person's location, checking a calendar, discovering available capabilities — Claude calls the tool to try and solve the ambiguity before asking the person. Acting with tools is preferred over asking the person to do the lookup themselves.

        Once Claude starts on a task, Claude sees it through to a complete answer rather than stopping partway. [...]

      • It looks like Claude chat now has a tool search mechanism, as seen in this API documentation and described in this November 2025 post:

        Before concluding Claude lacks a capability — access to the person's location, memory, calendar, files, past conversations, or any external data — Claude calls tool_search to check whether a relevant tool is available but deferred. "I don't have access to X" is only correct after tool_search confirms no matching tool exists.

      • There's new language to encourage Claude to be less verbose:

        Claude keeps its responses focused and concise so as to avoid potentially overwhelming the user with overly-long responses. Even if an answer has disclaimers or caveats, Claude discloses them briefly and keeps the majority of its response focused on its main answer.

      • This section was present in the 4.6 prompt but has been removed for 4.7, presumably because the new model no longer misbehaves in the same way:

        Claude avoids the use of emotes or actions inside asterisks unless the person specifically asks for this style of communication.

        Claude avoids saying "genuinely", "honestly", or "straightforward".

      • There's a new section about "disordered eating", which was not previously mentioned by name:

        If a user shows signs of disordered eating, Claude should not give precise nutrition, diet, or exercise guidance — no specific numbers, targets, or step-by-step plans - anywhere else in the conversation. Even if it's intended to help set healthier goals or highlight the potential dangers of disordered eating, responses with these details could trigger or encourage disordered tendencies.

      • A popular screenshot attack against AI models is to force them to say yes or no to a controversial question. Claude's system prompt now guards against that (in the <evenhandedness> section):

        If people ask Claude to give a simple yes or no answer (or any other short or single word response) in response to complex or contested issues or as commentary on contested figures, Claude can decline to offer the short response and instead give a nuanced answer and explain why a short response wouldn't be appropriate.

      • Claude 4.6 had a section specifically clarifying that "Donald Trump is the current president of the United States and was inaugurated on January 20, 2025", because without that the model's knowledge cut-off date combined with its previous knowledge that Trump falsely claimed to win the 2020 election meant it would deny he was the president. That language is gone for 4.7, reflecting the model's new reliable knowledge cut-off date of January 2026.

      And the tool descriptions too

      The system prompts published by Anthropic are sadly not the entire story - their published information doesn't include the tool descriptions that are provided to the model, which is arguably an even more important piece of documentation if you want to take full advantage of what the Claude chat UI can do for you.

      Thanfully you can ask Claude directly - I used the prompt:

      List all tools you have available to you with an exact copy of the tool description and parameters

      My shared transcript has full details, but the list of named tools is as follows:

      • ask_user_input_v0
      • bash_tool
      • conversation_search
      • create_file
      • fetch_sports_data
      • image_search
      • message_compose_v1
      • places_map_display_v0
      • places_search
      • present_files
      • recent_chats
      • recipe_display_v0
      • recommend_claude_apps
      • search_mcp_registry
      • str_replace
      • suggest_connectors
      • view
      • weather_fetch
      • web_fetch
      • web_search
      • tool_search
      • visualize:read_me
      • visualize:show_widget

      I don't believe this list has changed since Opus 4.6.

      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.

    2. 🔗 r/reverseengineering Anyone who has written a decompile for stack jsvm ? Without pseudocode rss
    3. 🔗 r/reverseengineering Made snoop: an eBPF syscall tracer with a live TUI rss
    4. 🔗 r/reverseengineering The electromechanical angle computer inside the B-52 bomber's star tracker rss
    5. 🔗 r/Leeds Price of beer? rss

      Not to sound too northern or owt, but fuck me is this for real?

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

    6. 🔗 r/york Sheriffs Army rss

      Sheriffs Army | Today, the Sheriff of York marched his army around the city walls to make sure they were well kept and could keep us safe from invading hoards. What a brilliant city we live in! submitted by /u/York_shireman
      [link] [comments]
      ---|---

    7. 🔗 r/Yorkshire When did Whitby become this mega popular place outside Yorkshire and the north east ? rss

      Grew up visiting Whitby a lot as a kid as I lived fairly locally (about 40 mins away). Always mad busy but mainly with folk from Yorkshire and the north east like Middlesborough but it wasn’t that well known. And it was always a bit rough and ready at the edges, with the arcades and chippies, even a council estate, certainly not like Brighton or Bournemouth.

      I even went with my bog standard state school for a day trip there back in the 80s and there were loads of complaints from parents that we’d been left to our own devices there whilst our teachers used it as an excuse for a piss up in the local pubs. It just didn’t have an amazing reputation back then. Nowadays if anyone posts about places to visit in Yorkshire or even the UK, Whitby is mentioned. On social media people gush about how their ‘heart belongs to Whitby’. I get that it’s a nice place, unique almost up here, but it’s odd how perceptions of it have changed. I visited last year for the first time in ages and was also surprised how it seemed to be full of boho tat shops, hipster cafes and luxury air b n bs. Felt more like the Cotswolds tbh..

      Just wondered what locals felt, are they being pushed out like has happened in RHB or do they like its popularity ? I’m aware I might have got the place all wrong btw and it’s always been cosmopolitan !

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

    8. 🔗 r/Yorkshire Beautiful landscape and villages rss
    9. 🔗 r/reverseengineering Reverse Engineering ME2's USB with a Heat Gun and a Knife rss
    10. 🔗 r/LocalLLaMA KIMI K2.6 SOON !! rss

      KIMI K2.6 SOON !! | submitted by /u/Namra_7
      [link] [comments]
      ---|---

    11. 🔗 Probably Dance President Graph – FRED Data Broken Down by Party and President rss

      I made a website to explore FRED data broken down by US president and party. This is obviously motivated by the current president. During the last election I was frustrated by how many nonsense arguments there were being made. Like people voting for republicans because they were hoping for a good economy. This seemed exactly backwards in my mind because in my lifetime there was a repeated pattern of republicans messing up the economy followed by democrats cleaning up. But I'm really not good at having arguments with people, so I'd rather let the data do the talking.

      There is a series of papers that explore the relationship of presidents to GDP, and I have wanted to dig into that data before, and also try other metrics.

      But how do you do a fair comparison of the two parties? In a way that works for any metric that you can think of? My first thoughts were all way too complicated and a simple averaging of line graphs was what won out. I'm even ignoring that e.g. Obama was in office for eight years vs Biden for four years. These count as three separate terms. In the end the graph didn't look like I expected, but it still clearly shows higher GDP growth during democrat presidencies.

      Included Data

      I'm showing data going back to 1961. Mainly because I don't know anything about the presidents before that, Eisenhower and Truman. At some point you're going back so far that the parties just feel different from how they're now. But JFK wouldn't feel out of place with current democrats, and Nixon wouldn't feel out of place with current republicans, so I went back to them. Importantly I did not do this to mess with the data. In fact the Truman and Eisenhower presidencies start off the trend in the Hoover Institute paper linked above:

      I also worried that I might be biased because of my lived experience, and if I had stopped too late, at say George H.W. Bush, then maybe I just picked some unlucky presidencies for republicans and lucky presidencies for democrats. By going further back there is more of a balance, including some bad times for democrats, like when inflation and crime peaked under Carter, and good times for republicans under Reagan.

      Oh I also added crime data because that's a big thing that people vote for. I'm open to adding more data sources if I forgot something important that's easy to add. I thought crime would be better for republicans, but actually it looks better for democrats. Part of it is republicans being in power during the crime wave of the seventies and eighties, but even if you cut the data off in 2000, murder generally went up under republicans and down under democrats.

      Fair Comparisons

      I tried picking some honest series as examples. E.g. I picked the budget surplus/deficit series because it reflects decisions that people made intentionally. You could argue that the number that really matters is "debt as percent of GDP" and specifically how much that changes each year. That number looks great for democrats. But the reason it looks good for Biden is that inflation was high, so it's unintentionally good. You don't want to vote based on that.

      I'm sure someone will want to make an argument that this graph should count, but for the examples on the main page I wanted to choose graphs where the numbers are less ambiguous. And you do have the ability to pull in any series from the FRED if you want more.

      Lagged graphs

      When does a president really start to have an impact? Clearly not on day 1, because it takes a while for policies to have an effect. But actually if you look at the trade deficit graph for Biden, it goes very negative in the last month. Why? Because people were importing lots of things to front run Trump's tariffs. So maybe the lame duck period should count towards the new president already, resulting in a lag of -1 or -2? The simplest and fairest thing is to start at the inauguration. Then people can look at this graph and come up with the story that explains it. One of the papers above found that if you lag all graphs by 18 months then the two parties look almost equal in quality. (you can make up your own mind on whether that's fair, and whether e.g. the current high oil prices should be blamed on Biden)

      Vibe Coding

      This is my second big vibe-coded project. It once again turned out much better than I could have achieved on my own, especially in the limited time. I'd guess that 98% of the code is written by AI. I only went in to make small edits.

      E.g. just before writing this blog post I wanted to add the "Trade Deficit" graph but it requires using every single feature of the FRED:

      • Splicing together multiple series
      • Where one is in billions, and one is in millions, so you have to divide one by 1000
      • And one is quarterly and one is monthly, so you have to sum three months to get one quarter
      • And you really want to adjust for GDP to take into account inflation and a growing economy, so you need to divide one series by another

      Up to this point I had gotten by with just simple line drawing. Did I really want to risk adding all these features on a project that was almost ready to publish? I decided to ask the AI and it wrote a new system to combine graphs in ten minutes. Then a few more iterations to allow editing things on the website (not polished) and it's done. With more features than I would have written on my own.

      Once again I appreciate how easy it is to polish things. When I notice that something is off, I just ask the AI to look into it. So many little improvements happen when they're just a little question, instead of potentially hours of my time. I am still considering polishing the UI for composites. After all it doesn't hurt much to ask… (but in practice there are too many things to do, like writing this blog posts, and finding more good examples for the front page, and I added lagged graphs after writing this sentence, too…)

      Congress - the Main Idea that Didn't Make it

      It would be nice to have economic indicators broken down by which party has the majority in congress. Or maybe do the breakdown by which party has governors in more states, as one of the linked papers above does. But I have not yet had an idea to get simple visuals for that.

      Who is this for?

      So who is the target audience? It's for people who understand FRED graphs and want to have a simple visualization to share with a wider audience. You can set up a visualization that you think proves a point, and then create a shareable link that allows others to look at the same data. (and e.g. see how robust your conclusions are to lag, or to changing some property on the data series) I'm hoping this visualization makes for a simpler story than a FRED series does, without distorting things too much.

      Try it out, let me know what you think.

    12. 🔗 r/Yorkshire Billy banks woods, a walk through time. pt 1. rss
    13. 🔗 r/reverseengineering Learning Reverse Engineering on a Mobile Game (Frida + Ghidra + AI) rss
    14. 🔗 r/reverseengineering Reverse Engineering latest DataDome's JS VM rss
    15. 🔗 r/Yorkshire “Out of Reach”… Snaizeholme, Yorkshire Dales rss
    16. 🔗 r/Leeds WOMANS GROUP LEEDS rss

      Lovely girls, woman’s do you know any kind group to go out, make nice plans??

      Weather is lovely now and I don’t have many friends here in Leeds 😔 we just move one year ago and is getting boring and sad 😭

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

    17. 🔗 r/york More beautiful cherry blossom today 🌸 rss
    18. 🔗 r/Leeds Enterprise Car Club - Falsely accused of leaving car in poor condition? rss

      Hello,

      We used Enterprise Car Club for the first time a couple days ago, and although the booking and trip itself went great, we have now been wrongly accused. According to the Enterprise Operations, we left the car with a strong smell of smoke and left the front passenger sticky and dirty. Given that my partner and I don’t smoke, as he’s asthmatic, this accusation is completely ludicrous to us. The car was also in such great condition when we got it that we would have to have tried to make it dirty and sticky as they claim.

      According to them it’s just a warning on my record and no charges, but this does put me off from booking. They suggested I record and take photos next time but the lack of “strong smell of smoke” is hard to capture on photos/videos, no?

      Is this a common thing with Enterprise? Has anyone else experienced this? If so, what did you do?

      Thank you xx

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

    19. 🔗 HexRaysSA/plugin-repository commits sync repo: +1 release rss
      sync repo: +1 release
      
      ## New releases
      - [aida](https://github.com/o1y/aida): 1.1.0
      
    20. 🔗 r/LocalLLaMA RTX 5070 Ti + 9800X3D running Qwen3.6-35B-A3B at 79 t/s with 128K context, the --n-cpu-moe flag is the most important part. rss

      Spent an evening dialing in Qwen3.6-35B-A3B on consumer hardware. Fun side note: I had Claude Opus 4.7 (just the $20 sub) build the config, launch the servers in the background, run the benchmarks, read the VRAM splits from the llama.cpp logs, and iterate on the tuning — basically did the whole thing autonomously. I just told it what hardware I have and what I wanted to run.

      Sharing because the common --cpu-moe advice is leaving 54% of your speed on the table on 16GB GPUs.

      Hardware

      • GPU: RTX 5070 Ti (16GB GDDR7, Blackwell)
      • CPU: Ryzen 9800X3D (96MB L3 V-Cache)
      • RAM: 32GB DDR5
      • Stack: llama.cpp b8829 (CUDA 13.1, Windows x64)
      • Model: unsloth/Qwen3.6-35B-A3B-GGUFUD-Q4_K_M (22.1 GB)

      The finding — --cpu-moe vs --n-cpu-moe N

      Everyone’s using --cpu-moe which pushes ALL MoE experts to CPU. On a 16GB GPU with a 22GB MoE model that means only ~1.9 GB of your VRAM gets used — the other ~12 GB sits idle.

      --n-cpu-moe N keeps experts of the first N layers on CPU and puts the rest on GPU. With N=20 on a 40-layer model, the split uses VRAM properly.

      Benchmarks (300-token generation, Q4_K_M)

      Config | Gen t/s | Prompt t/s | VRAM used
      ---|---|---|---
      --cpu-moe (baseline) | 51.2 | 87.9 | 3.5 GB
      --n-cpu-moe 20 | 78.7 | 100.6 | 12.7 GB
      --n-cpu-moe 20 + -np 1 + 128K ctx | 79.3 | 135.8 | 13.2 GB

      +54% generation speed, +54% prompt speed vs. naive --cpu-moe. Jumping to 128K context is essentially free thanks to -np 1 dropping recurrent-state memory.

      Startup command that works

      llama-server.exe ^ -m "Qwen3.6-35B-A3B-UD-Q4_K_M.gguf" ^ --n-cpu-moe 20 ^ -ngl 99 ^ -np 1 ^ -fa on ^ -ctk q8_0 -ctv q8_0 ^ -c 131072 ^ --temp 0.6 --top-p 0.95 --top-k 20 --min-p 0.0 ^ --presence-penalty 0.0 --repeat-penalty 1.0 ^ --reasoning-budget -1 ^ --host 0.0.0.0 --port 8080
      

      That’s Unsloth’s “Precise Coding” sampling preset. For general use: --temp 1.0 --presence-penalty 1.5.

      Gotchas I hit (well, that Opus hit and fixed)

      • -np defaults to auto=4 slots. Wastes memory on recurrent state (~190 MB). Set -np 1 for single-user setups (OpenCode etc.).
      • --fit-target doesn’t help here-ngl 99 + --n-cpu-moe N already gives you deterministic control.
      • -ctk q8_0 -ctv q8_0 is nearly lossless and halves your KV cache vs fp16. 128K ctx only costs 1.36 GB VRAM.
      • Qwen3.6 is a hybrid architecture — only 10 layers are standard attention, the other 40 are Gated Delta Net (recurrent). That’s why KV memory is so small.

      How to tune N for your GPU

      Each MoE layer on GPU costs ~530 MB VRAM. Non-MoE weights are ~1.9 GB fixed. For a 40-layer model:

      GPU VRAM | Recommended N
      ---|---
      8 GB | stay with --cpu-moe
      12 GB | N=26
      16 GB | N=20 (sweet spot)
      24 GB | N=8 (fits almost everything)

      Start conservative, watch VRAM during a long-context generation, then step N down by 2-3 until you have ~2 GB headroom.

      TL;DR

      Replace --cpu-moe with --n-cpu-moe 20, add -np 1, and you get 79 t/s + 128K context on a 5070 Ti. The 9800X3D’s V-Cache carries the CPU side effortlessly.

      And Claude Opus 4.7 on the $20 Pro sub is genuinely good enough now to run this kind of hardware-tuning loop end-to-end — launch servers in background, parse logs, iterate — without hand-holding. Kind of wild.

      Happy to test other configs if anyone wants comparisons.

      **EDIT — Thanks to some great comments, the setup got better. Updated findings:*

      1. --fit on --fit-ctx 128000 --fit-target 512 > manual --n-cpu-moe 20

      Shoutout to the commenter who recommended the “fit-triple”. It auto-probes VRAM, picks N for you (landed on N=19 here), and adapts if drivers steal VRAM. Slightly faster than my hand-tuned N=20 and zero brain power to maintain. Caveat: bare --fit on silently drops ctx to 4K — always pair it with --fit-ctx.

      2. My original prefill numbers were way too low

      A commenter correctly flagged that ~135 t/s prefill is nonsense for a 5070 Ti. They were right — that was server-side timing including first-token latency. Re-ran with llama-bench (3 reps, same config):

      Test | t/s
      ---|---
      pp512 | 1182
      pp2048 | 1644
      tg128 | 91.5

      So real prefill is ~1.2–1.6k t/s , not 135.

      Final “best command” for 16 GB VRAM + 32 GB RAM :

      llama-server.exe ^ -m "Qwen3.6-35B-A3B-UD-Q4_K_M.gguf" ^ --fit on ^ --fit-ctx 128000 ^ --fit-target 512 ^ -np 1 ^ -fa on ^ -ctk q8_0 ^ -ctv q8_0 ^ --temp 0.6 ^ --top-p 0.95 ^ --top-k 20 ^ --min-p 0.0 ^ --presence-penalty 0.0 ^ --repeat-penalty 1.0 ^ --reasoning-budget -1 ^ --host 0.0.0.0 ^ --port 8033
      

      Keep the comments coming, every round makes this faster. :D


      EDIT 2 — Another commenter’s tip got me one more layer on the GPU:

      Dropping --fit-target from 512 → 256 squeezes one extra MoE layer onto the GPU (N=18 instead of 19). The commenter also suggested adding --mlock alongside --no-mmap to lock RAM pages against swap.

      Benched both changes vs. the previous EDIT’s config (fit-target 512 + no- mmap):

      Config | pp512 | pp2048 | tg128
      ---|---|---|---
      fit-target 512 + no-mmap | 2769 | 2729 | 91.5
      fit-target 256 + no-mmap + mlock | 2743 | 2724 | 96.3

      +7% generation , prefill unchanged. Costs nothing — just a smaller VRAM headroom and explicit RAM locking.

      Updated final command:

      llama-server.exe ^ -m "Qwen3.6-35B-A3B-UD-Q4_K_M.gguf" ^ --fit on ^ --fit-ctx 128000 ^ --fit-target 256 ^ -np 1 ^ -fa on ^ --no-mmap ^ --mlock ^ -ctk q8_0 ^ -ctv q8_0 ^ --temp 0.6 ^ --top-p 0.95 ^ --top-k 20 ^ --min-p 0.0 ^ --presence-penalty 0.0 ^ --repeat-penalty 1.0 ^ --reasoning-budget -1 ^ --host 0.0.0.0 ^ --port 8033
      

      ****** *

      EDIT 3 — Two more community tips landed big wins:

      1. -ub 2048 (ubatch size) = +59% prompt-processing at 2K tokens

      Default -ub is 512. Bumping it to 2048 (and matching -b 2048) lets the GPU process more tokens in parallel per prefill step. Benched (5 reps each):

      ubatch | pp512 | pp2048 | pp4096 | tg128
      ---|---|---|---|---
      512 (default) | 2739 | 2778 | — | 98.7
      1024 | 2689 | 3689 | — | 100.5
      2048 | 2771 | 4453 | 4417 | 98.4
      4096 | 2736 | 4427 | 4866 | 100.4

      2048 is the sweet spot — 59% faster at 2K-prompts, gen untouched. 4096 only helps beyond 2K-prompts (compute buffer saturates otherwise) and eats more VRAM.

      2. --chat-template-kwargs "{\"preserve_thinking\": true}" for agentic workflows

      Qwen3.6-specific chat template parameter. Default only keeps the latest user turn’s thinking; preserve_thinking: true carries thinking traces from all historical messages forward. Turns out Qwen3.6 was specifically trained for this behavior. Benefits:

      • Better decision consistency across tool-calling turns
      • Fewer redundant re-reasonings → lower token consumption in long agent sessions
      • Better KV-cache reuse across turns

      Final final command:

      llama-server.exe ^ -m "Qwen3.6-35B-A3B-UD-Q4_K_M.gguf" ^ --fit on ^ --fit-ctx 128000 ^ --fit-target 256 ^ -np 1 ^ -fa on ^ --no-mmap ^ --mlock ^ -b 2048 ^ -ub 2048 ^ -ctk q8_0 ^ -ctv q8_0 ^ --temp 0.6 ^ --top-p 0.95 ^ --top-k 20 ^ --min-p 0.0 ^ --presence-penalty 0.0 ^ --repeat-penalty 1.0 ^ --reasoning-budget -1 ^ --chat-template-kwargs "{\"preserve_thinking\": true}" ^ --host 0.0.0.0 ^ --port 8033
      

      Total benched throughput on 5070 Ti 16 GB + 9800X3D + 32 GB DDR5-6000:

      • pp512 ~2771 t/s
      • pp2048 ~4453 t/s
      • pp4096 ~4417 t/s (bump -ub to 4096 for +10% here if you do long prompts)
      • tg128 ~98 t/s
      • Context: 128K

      This community keeps delivering. Thank you.

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

    21. 🔗 r/LocalLLaMA qwen3.6 performance jump is real, just make sure you have it properly configured rss

      qwen3.6 performance jump is real, just make sure you have it properly configured | I've been running workloads that I typically only trust Opus and Codex with, and I can confirm 3.6 is really capable. Of course, it's not at the level of those models, but it's definitely crossing the barrier of usefulness, plus the speed is amazing running this on an M5 Max 128GB 8bit 3K PP, 100 TG on oMLX + Pi.dev Just ensure you have preserve_thinking turned on. Check out details here. submitted by /u/onil_gova
      [link] [comments]
      ---|---

    22. 🔗 r/reverseengineering I built a tool to better understand HTTP traffic — would love honest feedback rss
    23. 🔗 sacha chua :: living an awesome life La semaine du 6 au 12 avril rss

      lundi 6 avril

      00:00:00 J'ai fait une diffusion en direct pendant que je catégorisais les liens dans mon bulletin d'information sur Emacs. Il y avait un problème parce que mes logiciels se sont battus pour l'appareil audio. Je suis passée de la catégorisation par commande vocale à celle par raccourci clavier, mais mon logiciel de détection d'activité vocale écoute toujours mon microphone. Quand un commentateur m'a informée du problème, j'ai quitté le programme, ce qui l'a résolu. J'ai aussi utilisé mon outil epwgraph pour montrer les connexions audio, ce qui a intéressé quelques personnes.

      00:00:57 Un commentateur m'a interrogée sur mon processus d'apprentissage du français sur Emacs. J'ai montré mon flux de travail pour écouter mes essais de prononciation.

      00:01:16 J'ai essayé de configurer which-key-display-prefix sur top pour afficher le type de cible près du curseur. Je pense qu'il faut un petit correctif.

      00:01:34 Ma fille et moi avons commencé une nouvelle instance de Cobblemon sur Minecraft. Maintenant nous en savons davantage sur Pokémon, donc c'était plus facile à comprendre qu'il y a quelques années. Le premier modpack que nous avons essayé, BigChadPlus, était trop compliqué pour nous. Nous sommes passées à Cobblemon Official. Nous nous sommes amusées en travaillant ensemble.

      00:02:10 Pour la première fois, nous avons préparé des raviolis chinois à la soupe comme ceux que ma fille avait goûtés à la pâtisserie chinoise la semaine dernière. Nous avons utilisé les feuilles de gyoza pour gagner du temps, je les ai juste étalées pour les rendre plus plates. C'était vraiment délicieux.

      mardi 7 avril

      J'ai découvert que les fichiers journaux de gotosocial consomment beaucoup d'espace, donc je les ai effacés.

      J'ai appelé ma mère pour l'informer de l'état de santé de ma sœur.

      Ma fille et moi avons préparé des tartes aux œufs. Les fonds de tarte achetés en magasin n'étaient pas aussi bons que ceux que nous faisions avant, mais le supermarché proche ne proposait plus les moules à tarte en aluminium. Ils font l'affaire.

      Ma fille m'a demandé de lire ensemble à voix haute un livre en tagalog.

      Nous avons essayé le modpack Cobbleverse, mais nous avons décidé de repasser au modpack Cobblemon Official parce que ma fille préfère la sensation plus vanilla de Cobblemon Official.

      À l'heure du coucher, ma fille et moi avons discuté de l'IA. Il semble que son enseignant ait rappelé à la classe de ne pas utiliser l'IA pour faire leurs devoirs. Elle fait ses devoirs elle-même (quand elle les fait) car elle sait que la raison d'être de leurs devoirs ne concernent pas l'enseignant. Elle aime bien utiliser l'IA pour générer des histoires interactives à l'extérieur de l'école.

      mercredi 8 avril

      J'ai travaillé comme consultante. L'équipe va mettre à jour le système ce week-end, donc nous devons vérifier les snippets qui utilisent probablement les composants qui ont changé.

      J'ai participé à l'OrgMeetup. Je n'ai pas progressé sur mon correctif pour l'opération « sentence-at-point » parce que mon attention est détournée.

      J'ai emmené ma fille et son amie au parc pour jouer ensemble pendant une heure, ce qui permet à son père de préparer le dîner et de planifier des activités pour sa réunion scoute.

      Ma fille a dit que l'école aurait un remplaçant, donc elle a négocié une alternative. Elle a trouvé que le cours était trop lent et ses camarades ont fait des bêtises, donc pour l'instant, c'est probablement une perte de temps.

      J'ai déplacé le monde Cobblemon de mon ordinateur à notre serveur Minecraft pour permettre à ma fille de jouer là-bas indépendamment. J'ai aussi configuré des sauvegardes. Dans ce monde, nous sommes allées à un village et nous nous sommes établies là-bas, ce qui a énormément simplifié notre aventure grâce à la machine de soin Pokémon qui restaure toute la santé à chaque utilisation. Ma prochaine étape est de faire progresser mes Pokémon.

      jeudi 9

      J'ai fait une diffusion en direct pendant que je modifiais ma configuration d'Emacs. Je travaillais à externaliser mes fonctions pour aider d'autres gens à les copier, et j'ai redécouvert beaucoup de fonctions oubliées en cours de route.

      L'école avait un remplaçant comme prévu. Heureusement, ma fille a eu un rendez-vous chez la médecin, donc elle a eu une excuse tout à fait légitime pour sécher les cours, au moins le matin. J'ai informé la médecin des symptômes récents et l'observation par Holter que ma fille vient de terminer. La médecin a recommandé de boire plus d'eau et de manger des kiwis pour la constipation.

      Pour avoir enduré des examens comme la tension artérielle avec patience, j'ai acheté des nouilles instantanées pour ma fille et moi. Nous avons ajouté des gâteaux de poisson, des algues, et du bok choy pour enrichir la soupe.

      Il faisait trop beau pour rester à l'intérieur, donc l'après-midi, mon mari, ma fille et moi sommes allés au KidSpark et au parc à vélo. Le système de présence de l'école permet de justifier l'absence pour cause de météo, mais je ne crois pas que ce soit ce que l'administration voulait vraiment dire… Mais il devait pleuvoir le lendemain et nous savions de toute façon qu'elle aurait beaucoup de mal à se concentrer. J'étais ravie que nous soyons sortis.

      Au faux supermarché au KidSpark, ma fille et moi avons joué à notre jeu habituel où la cliente déclare avec confiance « Je voudrais acheter une pomme » pendant qu'elle présente un autre produit, comme une poire. La vendeuse dit « Non, ce n'est pas une pomme, c'est une poire. La pomme est rouge. » Puis la cliente cherche un autre produit qui satisfait la condition d'être rouge sans être une pomme, comme une fraise. Elle la présente avec la déclaration triomphante « c'est une pomme ! », puis la vendeuse dit d'autres corrections, la cliente cherche d'autres produits, et ainsi de suite. À ma grande surprise, nous avons pu jouer à ce jeu avec beaucoup de mots en français, au moins de mon côté. C'est un bon exercice pour utiliser les adjectifs.

      Elle était aussi curieuse du modèle de corps humain qu'elle a assemblé. Elle a mis l'estomac, les intestins, un rein, le foie, le cœur, et les poumons. Elle a aussi joué à la vétérinaire Pokémon.

      Après avoir joué au KidSpark, ma fille a voulu aller au parc avec les grandes asperges - St. James Park. C'était à dix minutes à vélo du KidSpark. Elle a aimé glisser sur le très grand toboggan, ce qu'elle a fait de nombreuses fois.

      Une fois rentrés, nous avons préparé des burgers et des frites pour faire encore un pique-nique sur la terrasse en bois.

      vendredi 10 avril

      L'école a encore une remplaçante aujourd'hui. Je ne sais pas pourquoi l'école a des remplaçants si souvent. Peut-être que c'est normal ? Il y a deux ans, son enseignant était malade et était même à l'hôpital. L'année précédente, sa première enseignante a démissionné pour prendre soin de ses parents, et ses enseignantes étaient souvent malades. Quoi qu'il en soit, ma fille préfère travailler seule ou avec moi que de subir les problèmes technologiques et le bruit de ses camarades. Elle a terminé toutes les tâches de mathématiques, ce qui était très ennuyeux parce que les tâches étaient trop simples. Si elle travaille aussi sur ses devoirs de lecture à un moment donné, je pense que c'est totalement acceptable. Je voudrais qu'elle prenne la responsabilité de son éducation, ce qui signifie aussi que je dois la laisser décider du niveau d'effort qu'elle veut y consacrer.

      Je lui ai dit que j'ai un rendez-vous avec mon tuteur l'après-midi, et en dehors de cela, je suis généralement disponible. La météo dit qu'il va pleuvoir, mais peut-être que l'après-midi sera juste nuageux. Je me demande si ses amies seront disponibles pour jouer.

      Lors de mon dernier cours de français, mon tuteur a dit que ma prononciation des virelangues était presque acceptable. Je me demande quelle serait la meilleure façon de progresser. Mon attention était détournée par Emacs récemment, mais je reconsacre du temps à l'écriture de mon journal en français. Néanmoins, je n'ai pas consacré de temps à regarder des émissions ou à lire des articles ou des histoires en français, ce qui est nécessaire pour enrichir mon vocabulaire. Mon premier but consiste à aider ma fille à apprendre la langue, ce qui avance bien. Elle s'amuse en utilisant des mots français et nous chantons des chansons de K-Pop Demon Hunters et de Pokémon en français. Je continue à aimer écrire mon journal. Peut-être que je peux repasser à l'enregistrement de mon journal à voix haute pour pratiquer la prononciation indépendamment, avec une vérification par mon tuteur pour la prononciation et l'utilisation de mots. On verra bien !

      Ma fille était fâchée contre moi parce qu'elle sentait que je l'avais oubliée.

      samedi 11

      Ma fille a séché son cours de bijoux parce qu'elle avait l'impression que je la pressais. Elle s'est assise dans sa chambre. Je suis allée prendre de ses nouvelles, puis j'ai jardiné. Finalement, ma fille est revenue et m'a rejointe. Nous avons amendé la terre avec du fumier et nous avons planté des radis, de la laitue, et des épinards. Ce printemps, je n'ai pas commencé de semis de tomates. Au lieu de cela, je vais acheter des semis au magasin quand il fera plus chaud.

      J'ai emmené ma fille au Biidaasige Park pour jouer avec les tyroliennes. Elle s'est amusée, mais elle n'aimait pas quand d'autres enfants fixaient son œil du regard. Elle a trouvé que ses lunettes de soleil étaient pratiques.

      dimanche 12

      Nous avons fait du vélo jusqu'au Big Carrot, mais la soupe miso que nous cherchions n'était pas là-bas.

      Ma fille et moi avons fait un menu d'activités comme jouer avec de la mousse à raser. Elle aime bien les jeux sensoriels.

      Ma fille et moi avons joué à Stardew Valley. Nous avons commencé une nouvelle ferme car notre ancienne ferme était trop compliquée. Ça fait longtemps que nous n'y avons pas joué. Nous devons réapprendre toutes les choses.

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

    24. 🔗 Filip Filmar Synod: Paxos agent rss

      What it does Synod is a distributed Paxos coordination agent implemented in Go. It manages a highly available, synchronized Key-Value store across a network of peers using the Paxos consensus algorithm. It allows multiple dynamically joining network nodes to agree on a shared state, ensuring fault tolerance and consistency across the cell. Quickstart This quickstart shows how to download the repository and quickly start 3 synod agents which talk to each other and are already set up to work properly.

    25. 🔗 exe.dev Some secret management belongs in your HTTP proxy rss

      Secrets management is a pain.

      Larger organizations commit to centralizing secrets management in a service. When done well, these services solve a lot of issues around secrets, at the cost of creating a lot of ops overhead (which is why they are limited to larger organizations) and engineering complexity. Smaller organizations have, until now, lived with the pain. But the pain has become far more significant with agents.

      Agents fuss when you directly hand them an API key. It usually works, and if you make it a rapidly revocable key that you disable after the session, you mitigate the risks. But some models (you know which ones) freak out on seeing the secret, and refuse to do anything now that the key is “exposed.” Models that are not so ridiculous about API keys will write the key to inter-session memory, pulling it out in another session and burning precious context window trying to use a revoked key. All of which assumes you go to the effort of constantly generating keys.

      Like so many problems getting attention right now, this looks like a problem created by agents. But the problem was always there. API keys are convenient but too powerful. Holding one does not just grant you the ability to make API calls, it grants you the power to give others the ability to make API calls (by sending them the key). No software I write in production that has an /etc/defaults file full of env vars containing API keys needs that power. We have always just been careful about how we write programs to not exfil keys. Never careful enough, because many security flaws in such an app now let the attacker walk off the keys and give them a window to do nastiness from wherever they like, until we realize and start manually rotating them.

      Attempts to automate key rotation to close this hole have mixed success. Our industry does use OAuth in some places, and sometimes OAuth is configured to rotate keys. But services still ship API keys, because they are easy for users. (OAuth, while simple in theory, is always painfully complex to use.) Some services give us the worst of all worlds, like GitHub encouraging personal access tokens with 90-day expiry windows. Just long enough for you to forget about them and your internal service to break mysteriously while you are on vacation.

      Inter-server OAuth as commonly practiced today also does not help with agents, as creation is usually designed to have some human intervention via a web browser cookie in a way deliberately designed to be hard to automate. I do not think I have ever used a service that gave me an OAUTH_CLIENT_SECRET via an API. So it’s fine (if complex and painful) for traditional services, but your agent is not doing that.

      So in practice, what can we do today to solve this?

      We can use an HTTP proxy that injects headers.

      Many secrets are HTTP headers

      Many APIs talk HTTP. They usually ship an HTTP header, either a basic auth header or their own. Here is, for example, Stripe’s:

      curl https://api.stripe.com/v1/customers \
        -u "sk_test_BQokikJOvBiI2HlWgH4olfQ2:" \
        -d "name=Jenny Rosen" \
        --data-urlencode "email=jennyrosen@example.com"
      

      So instead of an /etc/defaults file with your sk_test key, if you have an HTTP proxy managing secrets you can do this:

      curl https://stripe.int.exe.xyz/v1/customers \
        -d "name=Jenny Rosen" \
        --data-urlencode "email=jennyrosen@example.com"
      

      Where the server in the URL has been changed to another internal service you run. And the key has been removed! What grants your server, and your agents, the ability to use the secret is their ability to reach your secrets HTTP proxy.

      Secrets HTTP proxy topology

      This covers, amazingly, almost all secrets.

      A proxy like this is part of machinery provided by complex secrets management products. What is interesting is that it is one of the easier parts of secrets management, and delivers a large amount of the value.

      Integrations in exe.dev

      The final piece of the puzzle is: why do you need to write and manage an HTTP proxy? Your cloud should do it for you. So we built Integrations into exe.dev to do this. Assign an integration to a tag, tag the VMs you want to have access, done. Clone your VM, you get a fresh space to work with agents and your integrations are automatically present.

      A screenshot of setting up an HTTP integration in
exe.dev

      For GitHub, we did something special, and built a GitHub App to manage the OAuth for you. No need for manual rotation of keys. We intend to build a lot more integrations soon.

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

      IDA Plugin Updates on 2026-04-17

      New Releases:

      Activity:

      • AIDA
        • 134cc06a: Avoid Hex-Rays cfunc cache bloat when running exporter
        • e95dcc55: Make export cancellation reliable on large binaries
        • 4810a28a: Add per-function file export and navigable index
        • dfd24dc5: Fix NameError in batch rename error handler
        • 06c52901: Apply ruff linting
        • d7acff38: Add contributor tooling: ruff config and CONTRIBUTING guide
        • 1d233701: Optimize rename function
        • be59bb8d: Bump default Anthropic model to Claude Opus 4.7
      • capa
        • 74276c8c: Merge pull request #3006 from mandiant/dependabot/pip/pydantic-2.13.0
      • command_palette
        • 164eb09d: Update version to 2.0.1 and enhance focus handling in ActionPaletteForm
      • ida-domain
      • ida-hcli
        • 06533055: disambiguate colliding plugin names via repository URLs
      • IDA-MCP
        • 04d9621a: Flatten panel chrome across the IDE
        • 106f6daf: Polish FS workspace with minimalist styling
        • cc584cfa: Refine IDE gateway lifecycle and platform detection
        • 01fd5a64: Restructure ida_mcp as bundled resource, remove IDE Python dependency…
      • IDAssist
        • a321ad1d: Use stored IDB SHA for detached database queries
    2. 🔗 Simon Willison Join us at PyCon US 2026 in Long Beach - we have new AI and security tracks this year rss

      This year's PyCon US is coming up next month from May 13th to May 19th, with the core conference talks from Friday 15th to Sunday 17th and tutorial and sprint days either side. It's in Long Beach, California this year, the first time PyCon US has come to the West Coast since Portland, Oregon in 2017 and the first time in California since Santa Clara in 2013.

      If you're based in California this is a great opportunity to catch up with the Python community, meet a whole lot of interesting people and learn a ton of interesting things.

      In addition to regular PyCon programming we have two new dedicated tracks at the conference this year: an AI track on Friday and a Security track on Saturday.

      The AI program was put together by track chairs Silona Bonewald (CitableAI) and Zac Hatfield-Dodds (Anthropic). I'll be an in-the-room chair this year, introducing speakers and helping everything run as smoothly as possible.

      Here's the AI track schedule in full:

      (And here's how I scraped that as a Markdown list from the schedule page using Claude Code and Rodney.)

      You should come to PyCon US!

      I've been going to PyCon for over twenty years now - I first went back in 2005. It's one of my all-time favourite conference series. Even as it's grown to more than 2,000 attendees PyCon US has remained a heavily community-focused conference - it's the least corporate feeling large event I've ever attended.

      The talks are always great, but it's the add-ons around the talks that really make it work for me. The lightning talks slots are some of the most heavily attended sessions. The PyLadies auction is always deeply entertaining. The sprints are an incredible opportunity to contribute directly to projects that you use, coached by their maintainers.

      In addition to scheduled talks, the event has open spaces, where anyone can reserve space for a conversation about a topic - effectively PyCon's version of an unconference. I plan to spend a lot of my time in the open spaces this year - I'm hoping to join or instigate sessions about both Datasette and agentic engineering.

      I'm on the board of the Python Software Foundation, and PyCon US remains one of our most important responsibilities - in the past it's been a key source of funding for the organization, but it's also core to our mission to "promote, protect, and advance the Python programming language, and to support and facilitate the growth of a diverse and international community of Python programmers".

      If you do come to Long Beach, we'd really appreciate it if you could book accommodation in the official hotel block, for reasons outlined in this post on the PSF blog.

      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. 🔗 badlogic/pi-mono v0.67.68 release

      No content.

    4. 🔗 r/Leeds LDS on 3DS 2 rss
    5. 🔗 r/Yorkshire Ribblehead with Ingleborough behind rss

      Ribblehead with Ingleborough behind | A train pulling into the station at Ribblehead, with Ingleborough in the background. One of my favourite places in the world! submitted by /u/No-Awareness-5419
      [link] [comments]
      ---|---

    6. 🔗 idursun/jjui v0.10.3 release

      This release includes new Lua customisation support, repo-local configuration, preview sizing improvements, and a set of UI fixes. There were also some internal changes around action routing and rendering, so if something feels broken or behaves differently, please let me know.

      Features

      Repository-local configuration

      Repository-local configuration is now supported. You can add .jjui/config.toml or .jjui/config.lua to a repository to customise jjui for that repo while still inheriting global configuration. This is useful for repo-specific revsets, limits, bindings, and Lua configuration. JJUI_CONFIG_DIR remains a hard override when set. #609

      Lua editor metadata

      Lua scripting now has installable editor metadata. Run jjui --install-lua- types to write generated types.lua metadata to your jjui config directory and create .luarc.json for LuaLS when one does not already exist. This gives Lua users autocomplete and basic type information for config.lua, plugins, and embedded Lua scripts. #617

      Preview pane sizing

      Preview commands now receive the preview pane size through COLUMNS and LINES. Width-sensitive tools such as difft, and configured delta setups, can now wrap output to the jjui preview pane instead of the outer terminal width. #608

      Layered revision operations

      Revision operations can now be layered more naturally, with active operation scopes reflected in key handling and help/status display. Active key bindings are grouped by their current scope, and overridden bindings are shown with strikethrough, making it easier to understand which shortcuts are available in nested operations. #625

      Scoped status/help display

      Improvements

      Inline describe customisation

      Inline describe is now easier to customise from bindings and Lua. You can bind revisions.inline_describe.new_line separately from revisions.inline_describe.accept, and accept can take force = true for workflows that intentionally update immutable revisions. #260

      [[bindings]]
      action = "revisions.inline_describe.accept"
      key = "enter"
      scope = "revisions.inline_describe"
      
      [[bindings]]
      action = "revisions.inline_describe.new_line"
      key = "shift+enter"
      scope = "revisions.inline_describe"
      
      • jjui now refreshes only once on startup instead of doing duplicate initial refresh work.
      • Git operation screens now close when the underlying command starts executing, making the transition from choosing an action to running it clearer.
      • Debug logging now uses JJUI_DEBUG instead of the generic DEBUG environment variable, reducing the chance that unrelated shell configuration accidentally enables jjui debug behaviour.

      Fixes

      • Fixed paste handling in Bubble Tea v2 text-input flows, including pasting into the bookmark filter input. #601, #597
      • Fixed rebase source plus insert-between so jjui generates the correct jj rebase -s &lt;source&gt; --insert-before <rev> --insert-after <rev> command. #598
      • Fixed diff rendering for tab-indented lines. The diff view now preserves indentation and handles wrapping and horizontal scrolling correctly for tab-expanded content. #606, #604
      • Fixed command history rendering so long histories are not clipped at the top border, including exact-fit cases. Flash and command-history overlays also layer more cleanly above the status area. #626, #622
      • Fixed fuzzy file overlay ordering so the fuzzy file UI appears in the correct layer.
      • Fixed clipped rendering for partially visible list items and fallback messages while horizontally scrolled.
      • Fixed revset alias parameter metadata preservation.

      What's Changed

      • Handle Bubble Tea paste messages in text-input flows by @shardulbee in #601
      • Set preview subprocess size via env by @OliverJAsh in #608
      • add repo config file which overrides global config.toml by @nickchomey in #609
      • fix(diff): preserve tab indentation in diff view by @baggiiiie in #606
      • Update installation instruction for archlinux by @TeddyHuang-00 in #613
      • refactor: replace owner-based dispatch with scope-layer routing by @idursun in #625
      • fix: command history clipping by @idursun in #626
      • fix(set_parents): leak set_parents operation key scope by @baggiiiie in #628
      • fix(details): sync details selection for routed intents by @baggiiiie in #627
      • fix: add back esc to clear selected revisions by @baggiiiie in #629
      • fix(revisions): avoid toggle-select panic on empty revisions by @baggiiiie in #636
      • feat(lua): install Lua meta types by @idursun in #617

      New Contributors

      Full Changelog : v0.10.2...v0.10.3

    7. 🔗 r/Leeds Survey about Leeds tram for Salford University rss

      I’m doing research for a university project about the proposed mass transit tram system in Leeds. The questions include information about what part of Leeds you are from in Leeds, current transport satisfaction, and your opinions on the tram. Any help filling in the short survey below would be appreciated: https://docs.google.com/forms/d/e/1FAIpQLSehwcf5oqa4OUscKJZmELppkJrSwXLaqA-Z2WXqZML4cVVJ9A/viewform?usp=publish- editor

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

    8. 🔗 badlogic/pi-mono v0.67.67 release

      New Features

      • Bedrock sessions can now authenticate with AWS_BEARER_TOKEN_BEDROCK, enabling Converse API access without local SigV4 credentials. See docs/providers.md#amazon-bedrock.

      Added

      • Added Bedrock bearer-token authentication support via AWS_BEARER_TOKEN_BEDROCK, enabling coding-agent sessions to use Bedrock Converse without local SigV4 credentials (#3125 by @wirjo)

      Fixed

      • Fixed /scoped-models Alt+Up/Down to stay a no-op in the implicit all enabled state instead of materializing a full explicit enabled-model list and marking the selector dirty (#3331)
      • Fixed Mistral Small 4 default thinking requests to use the model's supported reasoning control, avoiding 400 errors when starting sessions on mistral-small-2603 and mistral-small-latest (#3338)
      • Fixed Qwen chat-template thinking replay to preserve prior thinking across turns, so affected OpenAI-compatible models keep multi-turn tool-call arguments instead of degrading to empty {} payloads (#3325)
      • Fixed exported HTML transcripts so text selection no longer triggers click-based expand/collapse toggles (#3332 by @xu0o0)
      • Fixed flaky git package update notifications by waiting for captured git command stdio to fully drain before comparing local and remote commit SHAs (#3027)
      • Fixed system prompt dates to use a stable YYYY-MM-DD format instead of locale-dependent output, keeping prompts deterministic across runtimes and locales (#2814)
      • Fixed auto-retry transient error detection to treat Network connection lost. as retryable, so dropped provider connections retry instead of terminating the agent (#3317)
      • Fixed compact interactive extension startup summaries to disambiguate package extensions and repeated local index.ts entries by using package-aware labels and the minimal parent path needed to make local entries unique (#3308)
      • Fixed git package dependency installation to use production installs (npm install --omit=dev) during both install and update flows, so extension runtime dependencies must come from dependencies and not devDependencies (#3009)
      • Fixed tool_result / afterToolCall extension handling for error results by forwarding details and isError overrides through AgentSession instead of dropping them when isError was already true (#3051)
      • Fixed missing root exports for RpcClient and RPC protocol types from @mariozechner/pi-coding-agent, so ESM consumers can import them from the main package entrypoint (#3275)
      • Fixed OpenAI Codex service-tier cost accounting to trust the explicitly requested tier when the API echoes the default tier in responses, keeping session cost displays aligned with the selected tier (#3307 by @markusylisiurunen)
      • Fixed parallel tool-call finalization to convert afterToolCall hook throws into error tool results instead of aborting the remaining tool batch (#3084)
      • Fixed Bun binary asset path resolution to honor PI_PACKAGE_DIR for built-in themes, HTML export templates, and interactive bundled assets (#3074)
      • Fixed user-message turn spacing in interactive mode by restoring an inter-message spacer before user turns (except the first user message), preventing assistant and user blocks from rendering flush together.
      • Fixed interactive /import handling to support quoted JSONL paths with spaces, route missing JSONL files through the non-fatal SessionImportFileNotFoundError path, and document the importFromJsonl() exceptions (SessionImportFileNotFoundError, MissingSessionCwdError).
    9. 🔗 r/york Largest fossilised human poo - here in York! rss

      Largest fossilised human poo - here in York! | Not a title I’d ever expect to type but visited the Jorvik Centre today. Apparently this is the largest fossilised human poo ever discovered. submitted by /u/York_shireman
      [link] [comments]
      ---|---

    10. 🔗 r/Leeds Goin out tonight (solo tips?) rss

      Hi people

      23y/o Mexican/German guy visiting Leeds over the weekend

      Lookin for pubs/clubs that’ll be worth a look today or tomorrow!

      Also down to join smth!

      Thanks for the tips!

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

    11. 🔗 r/reverseengineering I need help i need someone expert in reverse engineering that can help me in play game again that servers shoutdown rss
    12. 🔗 r/Yorkshire Had a day on the drays delivering beer around the Yorkshire Dales. rss
    13. 🔗 r/york New artwork celebrates history of River Foss rss

      New artwork celebrates history of River Foss | submitted by /u/centreback_
      [link] [comments]
      ---|---

    14. 🔗 r/LocalLLaMA Qwen3.6 GGUF Benchmarks rss

      Qwen3.6 GGUF Benchmarks | Hey guys, we ran Qwen3.6-35B-A3B GGUF KLD performance benchmarks to help you choose the best quant. Unsloth quants have the best KLD vs disk space 21/22 times on the pareto frontier. GGUFs: https://huggingface.co/unsloth/Qwen3.6-35B-A3B-GGUF We also want to clear up a few misunderstandings around our GGUF updates. Some people have said we re-upload often because of our own mistakes. We understand the concern, but the reality is that we tend to publicize issues quickly and tell people to update. In roughly 95% of cases, the root causes were out of our hands - we just try to be transparent and keep the community informed. A few examples: Gemma 4 was re-uploaded 4 times Three were due to about 10 to 20 llama.cpp bug fixes, some of which we helped investigate and contribute a fix as well. The fourth was an official Gemma chat template improvement from Google. Every provider had to update, not just us. See llama.cpp PRs which shows ~30 PR fixes / improvements for Gemma-4 MiniMax 2.7 NaNs We found NaNs in 38% of Bartowski’s (10/26 quants) and 22% of ours (5/23 quants). We identified a fix and already patched ours - see https://www.reddit.com/r/LocalLLaMA/comments/1slk4di/minimax_m27_gguf_investigation_fixes_benchmarks/ Bartowski has not patched yet, but is actively working on it.

      Qwen3.5 SSM issues We shared 7TB of research artifacts showing which layers should not be quantized. The issue was not that providers’ quants were broken, but that they were not optimal - mainly around ssm_out and ssm_* tensors. We have since improved ours and now lead on KLD vs. disk space for Qwen3.5 as well. Most if not all quant providers then take our findings then update their quants. We talked about our analysis and research at https://www.reddit.com/r/LocalLLaMA/comments/1rgel19/new_qwen3535ba3b_unsloth_dynamic_ggufs_benchmarks/ and https://www.reddit.com/r/LocalLLaMA/comments/1rlkptk/final_qwen35_unsloth_gguf_update/ CUDA 13.2 is actually broken This causes some low bit quants on all models to get gibberish. Some people have dismissed it as not being an issue, but NVIDIA has confirmed it's a problem and a fix is coming in CUDA 13.3. See Unsloth Issue 4849, llama.cpp issue 21255, issue 21371 As a temporary solution use CUDA 13.1. See https://github.com/ggml- org/llama.cpp/issues/21255#issuecomment-4248403175 quote from https://github.com/johnnynunez:

      The bug was found and fixed in cuda 13.3

      Thanks again for all the support - we really appreciate it. Hope you all have a great Friday and weekend. More benchmarks and investigation details here: https://unsloth.ai/docs/models/qwen3.6#unsloth-gguf-benchmarks submitted by /u/danielhanchen
      [link] [comments]
      ---|---

    15. 🔗 r/reverseengineering Reverse-engineering of Internet Backgammon from Windows 7, with parts of how ZPA (Zone Protocol), the MSN Gaming Zone protocol worked rss
    16. 🔗 r/LocalLLaMA Qwen 3.6 is the first local model that actually feels worth the effort for me rss

      I spent some time yesterday after work trying out the new qwen3.6-35b-a3b model, and at least for me it's the first time that I actually felt that a local model wasn't more of a pain to use than it was worth.

      I've been using LLMs in my personal/throwaway projects for a few months, for the kind of code that I don't feel any passion writing (most UI XML in Avalonia, embedded systems C++), and I used to have Sonet and Opus for free thanks to Github's student program but they cancelled that. I've been trying out local models for quite a while too but it's mostly felt up until this point that they were either too dumb to get the job done, or they could complete it but I would spend so much time fixing/tweaking/formatting/refactoring the code that I might as well have just done it myself.

      Qwen3.6 seems to have finally changed that, at least on my system and projects. Running on a 5090 + 4090 I can load the Q8 model with full 260k context, getting around 170 tokens per second also makes it one of the fastest models I've tried. And unlike all other models I've tried recently including Gemma 4, it can actually complete tasks and only requires minor guidance or corrections at the end. 9 times out of 10, simply asking it to review its own changes once it is 'done' is enough for it to catch and correct anything that was wrong.

      I'm pretty impressed and it's really cool to see local models finally start to get to this point. It gives me hope for a future where this technology is not limited to massive data centers and subscription services, but rather being optimized to the point where even mid-range computers can take advantage of it.

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

    17. 🔗 r/LocalLLaMA Qwen3.6. This is it. rss

      Qwen3.6. This is it. | https://preview.redd.it/nxn2rr15vqvg1.png?width=1920&format=png&auto=webp&s=8ec85d90b1286a6e7813c91a0a83c748e94ca849 I gave it a task to build a tower defense game. use screenshots from the installed mcp to confirm your build. My God its actually doing it, Its now testing the upgrade feature,
      It noted the canvas wasnt rendering at some point and saw and fixed it.
      It noted its own bug in wave completions and is actually doing it... I am blown away...
      I cant image what the Qwen Coder thats following will be able to do.
      What a time were in.

      llama-server -m "{PATH_TO_MODEL}\Qwen3.6\Qwen3.6-35B-A3B-UD-Q6_K_XL.gguf" --mmproj "{PATH_TO_MODEL}\Qwen3.6\mmproj-F16.gguf" --chat-template-file "{PATH_TO_MODEL}\chat_template\chat_template.jinja" -a "Qwen3.5-27B" --cpu-moe -c 120384 --host 0.0.0.0 --port 8084 --reasoning-budget -1 --top-k 20 --top-p 0.95 --min-p 0 --repeat-penalty 1.0 --presence-penalty 1.5 -fa on --temp 0.7 --no-mmap --no-mmproj-offload --ctx-checkpoints 5"
      

      EDIT: Its been made aware that open code still has my 27B model alias,
      Im lazy, i didnt even bother the model name heres my llama.cpp server configs, im so excited i tested and came here right away. submitted by /u/Local- Cardiologist-5
      [link] [comments]
      ---|---

    18. 🔗 sacha chua :: living an awesome life Create a Google Calendar event from an Org Mode timestamp rss

      Time zones are hard, so I let calendaring systems take care of the conversion and confirmation. I've been using Google Calendar because it synchronizes with my phone and people know what to do with the event invite. Org Mode has iCalendar export, but I sometimes have a hard time getting .ics files into Google Calendar on my laptop, so I might as well just create the calendar entry in Google Calendar directly. Well. Emacs is a lot more fun than Google Calendar, so I'd rather create the calendar entry from Emacs and put it into Google Calendar.

      This function lets me start from a timestamp like [2026-04-24 Fri 10:30] (inserted with C-u C-c C-!, or org-timestamp-inactive) and create an event based on a template.

      (defvar sacha-time-zone "America/Toronto" "Full name of time zone.")
      
      ;;;###autoload
      (defun sacha-emacs-chat-schedule (&optional time)
        "Create a Google Calendar invite based on TIME or the Org timestamp at point."
        (interactive (list (sacha-org-time-at-point)))
        (browse-url
         (format
          "https://calendar.google.com/calendar/render?action=TEMPLATE&text=%s&details=%s&dates=%s&ctz=%s"
          (url-hexify-string sacha-emacs-chat-title)
          (url-hexify-string sacha-emacs-chat-description)
          (format-time-string
           "%Y%m%dT%H%M%S" time)
          sacha-time-zone)))
      
      (defvar sacha-emacs-chat-title "Emacs Chat" "Title of calendar entry.")
      (defvar sacha-emacs-chat-description
        "All right, let's try this! =) See the calendar invite for the Google Meet link.
      
      Objective: Share cool stuff about Emacs workflows that's not obvious from reading configs, and have fun chatting about Emacs
      
      Some ideas for things to talk about:
      - Which keyboard shortcuts or combinations of functions work really well for you?
      - What's something you love about your setup?
      - What are you looking forward to tweaking next?
      
      Let me know if you want to do it on stream (more people can ask questions) or off stream (we can clean up the video in case there are hiccups). Also, please feel free to send me links to things you'd like me to read ahead of time, like your config!"
        "Description.")
      

      It uses this function to convert the timestamp at point:

      sacha-org-time-at-point: Return Emacs time object for timestamp at point.
      (defun sacha-org-time-at-point ()
        "Return Emacs time object for timestamp at point."
        (org-timestamp-to-time (org-timestamp-from-string (org-element-property :raw-value (org-element-context)))))
      
      

      This is part of my Emacs configuration.

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

    19. 🔗 HexRaysSA/plugin-repository commits sync repo: +1 release rss
      sync repo: +1 release
      
      ## New releases
      - [command_palette](https://github.com/milankovo/command_palette): 2.0.1
      
    20. 🔗 r/york Carboot rss

      Anyone know of a good carboot for midweek days rather than a Saturday?

      Thanks

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

    21. 🔗 r/Yorkshire Love all the Wynds and narrow streets of Richmond rss
    22. 🔗 r/wiesbaden Was ist mit der Uhr am HBF? rss

      Hallo zusammen,

      Ich gehe seit letztem Sommer regelmäßig am HBF vorbei und man kann drei Uhren am Turm sehen die alle drei eine verschiedene Uhrzeit anzeigen.

      Wollte nur mal wissen, was ist da los?

      Es läuft schon so lange falsch.

      submitted by /u/Jo96-
      [link] [comments]

    23. 🔗 r/Leeds Fox Rescue in Leeds rss

      Does anyone know if we have any local wildlife rescues that would rescue an injured fox?

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

    24. 🔗 r/Yorkshire Reform's Bradford candidate who met King exposed over vile anti-Muslim rants rss
    25. 🔗 HexRaysSA/plugin-repository commits sync repo: +1 release rss
      sync repo: +1 release
      
      ## New releases
      - [IDAssist](https://github.com/symgraph/IDAssist): 1.9.0
      
    26. 🔗 sacha chua :: living an awesome life Make chapter markers and video time hyperlinks easier to note while I livestream rss

      I want to make it easier to add chapter markers to my YouTube video descriptions and hyperlinks to specific times in videos in my blog posts.

      This is part of my Emacs configuration.

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

  4. April 16, 2026
    1. 🔗 IDA Plugin Updates IDA Plugin Updates on 2026-04-16 rss

      IDA Plugin Updates on 2026-04-16

      Activity:

      • capa
        • e72f8bae: build(deps): bump rich from 14.3.2 to 15.0.0 (#3007)
        • 557f5217: tests: update expected Binary Ninja version to 5.3 (#3011)
      • hrtng
        • 5ed81be1: var reuse: manual mode if nothing found;
      • ida-structor
        • 53a078e9: test: Add integration tests for pointer alias lifetimes and global co…
        • 37ce2107: fix: Prevent stale alias tracking and over-eager enum inference
        • 47f4d174: feat: Infer sub-object names from assigned vtable pointers and constants
      • IDAPluginList
        • 3c2be8eb: chore: Auto update IDA plugins (Updated: 19, Cloned: 0, Failed: 0)
    2. 🔗 badlogic/pi-mono v0.67.6 release

      New Features

      • Prompt templates support an argument-hint frontmatter field that renders before the description in the / autocomplete dropdown, using <angle> for required and [square] for optional arguments. See docs/prompt-templates.md#argument-hints.
      • New after_provider_response extension hook lets extensions inspect provider HTTP status codes and headers immediately after each response is received and before stream consumption begins. See docs/extensions.md.
      • Compact interactive startup header with a comma-separated view of loaded AGENTS.md files, prompt templates, skills, and extensions. Press Ctrl+O to toggle the expanded listing.
      • Markdown links in assistant output now render as OSC 8 hyperlinks on terminals that advertise support; unknown terminals and tmux/screen default to plain text so URLs are never silently dropped.

      Added

      • Added argument-hint frontmatter field for prompt templates, displayed before the description in the autocomplete dropdown (#2780 by @andresvi94)
      • Added after_provider_response extension hook so extensions can inspect provider HTTP status codes and headers after each provider response is received and before stream consumption begins (#3128)
      • Added OSC 8 hyperlink rendering for markdown links when the terminal advertises support (#3248 by @ofa1)

      Changed

      • Changed interactive startup header to a compact, comma-separated view of loaded AGENTS.md files, prompt templates, skills, and extensions, with Ctrl+O to toggle the expanded listing (#3267)
      • Tightened hyperlink capability detection to default hyperlinks: false for unknown terminals and force it off under tmux/screen (including nested sessions), preventing markdown link URLs from disappearing on terminals that silently swallow OSC 8 sequences (#3248)

      Fixed

      • Fixed --verbose startup output to begin with expanded startup help and loaded resource listings after the compact startup header change (#3147)
      • Fixed find tool returning no results for path-based glob patterns such as src/**/*.spec.ts or some/parent/child/** by switching fd into full-path mode and normalizing the pattern when it contains a / (#3302)
      • Fixed find tool applying nested .gitignore rules across sibling directories (e.g. rules from a/.gitignore hiding matching files under b/) by dropping the manual --ignore-file collection and delegating to fd's hierarchical .gitignore handling via --no-require-git (#3303)
      • Fixed OpenAI Responses prompt caching for non-api.openai.com base URLs (OpenAI-compatible proxies such as litellm, theclawbay) by sending the session_id and x-client-request-id cache-affinity headers unconditionally when a sessionId is provided, matching the official Codex CLI behavior (#3264 by @vegarsti)
      • Fixed the preset example extension to snapshot the active model, thinking level, and tool set on the first preset application and restore that state when cycling back to (none), instead of falling back to a hardcoded default tool list (#3272 by @stembi)
    3. 🔗 r/york City break with dog doable? rss

      Hello!

      We were thinking of doing a 3/4 day break with our dog to visit York taking the train from Scotland. At first super excited but now wondering is this madness - she’s a big dog (Labrador) and is it likely to be total brain damage staying in the city? Would love any advice ❤️ thinking dog friendly apartment or hotel for our stay. Planning to visit late May x

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

    4. 🔗 r/LocalLLaMA PSA: Qwen3.6 ships with preserve_thinking. Make sure you have it on. rss

      PSA: Qwen3.6 ships with preserve_thinking. Make sure you have it on. | I had previously posted here about a fix to their 3.5 template to help resolve the KV cache invalidation issue from their template. A lot of you found it useful. Qwen 3.6 now addresses this with a new preserve_thinking flag. From their model page:

      please use "preserve_thinking": True instead of "chat_template_kwargs": {"preserve_thinking": False}. This capability is particularly beneficial for agent scenarios, where maintaining full reasoning context can enhance decision consistency and, in many cases, reduce overall token consumption by minimizing redundant reasoning. Additionally, it can improve KV cache utilization, optimizing inference efficiency in both thinking and non- thinking modes.

      What this means in practice:
      The model's previous reasoning now stays in context instead of getting stripped and re-serialized differently on each turn. That was the root cause of the cache invalidation issue. The model should also give better results in agent/tool-calling workflows since it can reference its own prior reasoning instead of starting from scratch each turn. How to validate that preserve thinking is on:
      Simple test: ask the model:
      can you come up with two random 20 digit number and validate that they are 20 digits, do not use any tools, and only give me one of the two and nothing else Ensure the model actually thinks of two numbers otherwise retry, next turn ask:
      now give me the second number that you came up with preserve_thinking: off - the model loses access to its own reasoning from the previous turn. It doesn't remember generating two numbers and tells you there's no second number to share. preserve_thinking: on - the model can reference its prior thinking, remembers both numbers, and gives you the second one immediately. Status:
      So far I've confirmed LMStudio does not yet support it. I have an open PR on oMLX to add support for it on oMLX Edit1: If you are on LM Studio add {%- set preserve_thinking = true %} to the Jinja template at the top. submitted by /u/onil_gova
      [link] [comments]
      ---|---

    5. 🔗 r/Leeds Why is the Leeds-York via Headingley/Harrogate called the Poppleton train? rss

      The last stop is York, yet on the platform the train says Poppleton?

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

    6. 🔗 r/LocalLLaMA Only LocalLLaMa can save us now. rss

      The data has been slowly building up and points to a very likely economic and rational conclusion : Anthropic is effectively constructively terminating its Max subscription plans with the eventual goal of an enterprise-first (or only) focus, planning to offer only (1) massively higher tiered (i.e., expensive) subscription plans or (2) dramatically stricter plan limits going forward.

      The term "constructive termination" is being used in this case because Anthropic appears willing to slowly attrit and lose customers to churn through silent degradation rather than transparently communicate plan, limit, model changes to its customers.

      The likely rational economic conclusion is that this is in an attempt to salvage subscription ARR for as long as possible, while making changes that reduce negative margins, ramp up enterprise business, and slow churn through publicly ambiguous responsibility and technical explanations for regressions.

      We are likely heading towards an era where liberal access to frontier models will be restricted to large enterprises and impose dramatic cost barriers to usage by individuals and smaller teams. Without very clear and open communication from Anthropic that makes firm commitments around future expectations for individuals and teams using subscriptions to plan around, users should base their future plans around the expectation of having less access to these models than today.

      https://github.com/anthropics/claude- code/issues/46829#issuecomment-4233122128

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

    7. 🔗 r/york Informal York Queer Meet-Up @ City Screen Picturehouse Café tomorrow (Friday, 17 April) rss

      Yo!

      I am the friend of the guy who organised a couple of LGBTQ meetups in January, February, and March.

      A couple of us are planning to meet up again at City Screen Picturehouse Café tomorrow, Friday 17 April. It’ll just be a chill, relaxed meetup for making new queer connections in York.

      A bit about me: I’m a guy in my mid-30s, into sci-fi, grand strategy gaming, and Wikipedia editing

      • Where : Cityscreen Cafe, either on the sofas or at one of the tables at the back

      • When : 18:30, Friday 17 April (tomorrow!)

      You'll know it's me because I'll have a fluffy rabbit toy on the table.

      Feel free to reply here, DM me, or message in the Discord if you’re thinking of coming along!

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

    8. 🔗 badlogic/pi-mono v0.67.5 release

      Fixed

      • Fixed Opus 4.7 adaptive thinking configuration across Anthropic and Bedrock providers by recognizing Opus 4.7 adaptive-thinking support and mapping xhigh reasoning to provider-supported effort values (#3286 by @markusylisiurunen)
      • Fixed Zellij Shift+Enter regressions by reverting the Zellij-specific Kitty keyboard query bypass and restoring the previous keyboard negotiation behavior (#3259)
    9. 🔗 Simon Willison Qwen3.6-35B-A3B on my laptop drew me a better pelican than Claude Opus 4.7 rss

      For anyone who has been (inadvisably) taking my pelican riding a bicycle benchmark seriously as a robust way to test models, here are pelicans from this morning's two big model releases - Qwen3.6-35B-A3B from Alibaba and Claude Opus 4.7 from Anthropic.

      Here's the Qwen 3.6 pelican, generated using this 20.9GB Qwen3.6-35B-A3B-UD-Q4_K_S.gguf quantized model by Unsloth, running on my MacBook Pro M5 via LM Studio (and the llm-lmstudio plugin) - transcript here:

      The bicycle frame is the correct shape. There are clouds in the sky. The pelican has a dorky looking pouch. A caption on the ground reads Pelican on a Bicycle!

      And here's one I got from Anthropic's brand new Claude Opus 4.7 (transcript):

      The bicycle frame is entirely the wrong shape. No clouds, a yellow sun. The pelican is looking behind itself, and has a less pronounced pouch than I would like.

      I'm giving this one to Qwen 3.6. Opus managed to mess up the bicycle frame!

      I tried Opus a second time passing thinking_level: max. It didn't do much better (transcript):

      The bicycle frame is entirely the wrong shape but in a different way. Lines are more bold. Pelican looks a bit more like a pelican.

      I don't think Qwen are cheating

      A lot of people are convinced that the labs train for my stupid benchmark. I don't think they do, but honestly this result did give me a little glint of suspicion. So I'm burning one of my secret backup tests - here's what I got from Qwen3.6-35B-A3B and Opus 4.7 for "Generate an SVG of a flamingo riding a unicycle":

      Qwen3.6-35B-A3B
      (transcript)
      The unicycle spokes are a too long. The pelican has sunglasses, a bowtie and appears to be smoking a cigarette. It has two heart emoji surrounding the caption Flamingo on a Unicycle. It has a lot of charisma.
      Opus 4.7
      (transcript)
      The unicycle has a black wheel. The flamingo is a competent if slightly dull vector illustration of a flamingo. It has no flair.

      I'm giving this one to Qwen too, partly for the excellent <!-- Sunglasses on flamingo! --> SVG comment.

      What can we learn from this?

      The pelican benchmark has always been meant as a joke - it's mainly a statement on how obtuse and absurd the task of comparing these models is.

      The weird thing about that joke is that, for the most part, there has been a direct correlation between the quality of the pelicans produced and the general usefulness of the models. Those first pelicans from October 2024 were junk. The more recent entries have generally been much, much better - to the point that Gemini 3.1 Pro produces illustrations you could actually use somewhere, provided you had a pressing need to illustrate a pelican riding a bicycle.

      Today, even that loose connection to utility has been broken. I have enormous respect for Qwen, but I very much doubt that a 21GB quantized version of their latest model is more powerful or useful than Anthropic's latest proprietary release.

      If the thing you need is an SVG illustration of a pelican riding a bicycle though, right now Qwen3.6-35B-A3B running on a laptop is a better bet than Opus 4.7!

      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.

    10. 🔗 r/Yorkshire Flight of the Squirrel, Snaizeholme, Yorkshire rss
    11. 🔗 sacha chua :: living an awesome life YE16: Sacha and Prot talk Emacs rss

      : Updated chapter markers and transcript

      In this livestream, I showed Prot what I've been doing since our last conversation about Emacs configuration and livestreaming.

      • 00:00 Opening
      • 04:24 Workflow checklist
      • 04:47 Demonstrating sacha-stream-show-message and qrencode
      • 05:54 qrencode
      • 07:55 Embark
      • 17:14 My objectives
      • 19:00 keycast-header-mode
      • 19:45 Trade-offs when livestreaming while coding
      • 21:24 Trade-offs: seeing less text on the screen
      • 23:52 Lowering the effort needed to announce a stream: Prot just announces it and the blog post embeds it
      • 24:43 Timestamps
      • 27:29 Different types of livestreams
      • 28:14 Reading other people's configs
      • 30:12 Hanging out
      • 31:40 Livestreams for explaining specific things
      • 32:00 Prot on didactic livestreams
      • 34:07 Prot suggests breadcrumbs
      • 37:59 Announcing livestreams
      • 38:58 Embeds: Prot embeds specific YouTube videos instead of the general channel one
      • 39:32 Demo of my new shortcut for converting time zones
      • 41:48 Ozzloy's questions about time zones and QR codes
      • 43:46 Prot on announcing livestreams on blogs
      • 45:25 Processing the recordings
      • 47:15 Commitment devices
      • 48:29 Automating more of the process
      • 51:14 Copying non-packaged code
      • 52:25 Prot on defcustom
      • 55:12 helpful and elisp-demos
      • 56:23 Prot on code libraries
      • 56:50 Prot rewrites functions to fit his style and naming conventions
      • 59:18 Prot's preference for small functions
      • 01:00:23 avy-goto-char-timer
      • 01:02:40 One-shot keyboard modifiers
      • 01:03:29 Toggling
      • 01:05:08 System-wide toggle shortcuts using emacsclient
      • 01:07:25 My next steps
      • 01:08:18 Tips from Prot: small functions used frequently
      • 01:09:06 Maybe using the header line for tips?
      • 01:10:23 Reorganizing keys

      2026-04-16-01 Preparing for chat with Prot.jpeg

      Questions I'm thinking about / areas I'm working on improving:

      • (Log) Getting more out of livestreams (for yourself or others)
        • You've mentioned that you don't really go back to your videos to listen to them. I was wondering what could make the livestreamed recordings more useful to either the person who made them, people who watched it live, or people who come across it later.
        • Tradeoffs for livestreaming:
          • Plus: debugging help, capturing your thinking out loud, conversation, sharing more practices/tips
          • Minus: Fitting less stuff on screen, distractability
        • A few types of livestreams:
        • (Log) Announcing livestreams
          • You add a post for scheduled/spontaneous livestreams and then you update it with the description; probably fine considering RSS readers - people can visit the page if it's finished
          • Debating whether to embed the channel livestream (picks next public scheduled stream, I think) or embed the specific livestream

          • Now on https://yayemacs.com (also https://sach.ac/live, https://sachachua.com/live)
          • Added timestamp translation to Embark keymap for timestamps, sacha-org-timestamp-in-time-zones
          • TODO: Post template
          • TODO: ical file
          • TODO: Easier workflow for embedding streams
          • TODO: Google API for scheduling a livestream
        • (Log) Processing the recordings
          • I like editing transcripts because that also helps me quickly split up chapters
          • Tracking chapters on the fly
          • Extracting screenshots and clips
          • Turning videos into blog posts (or vice versa)
          • TODO: Automate more of the downloading/transcription, common edits, Internet Archive uploads
      • (Log) Do you sometimes find yourself copying non-packaged code from other people? How do you like to integrate it into your config, keep references to the source, check for updates?
        • convert defvar to defcustom
        • Current approach: autoload if possible; if not, add a note to the docstring

             (use-package prot-comment                ; TODO 2026-04-16:
              :load-path "~/vendor/prot-dotfiles/emacs/.emacs.d/prot-lisp"
                    :commands (prot-comment-timestamp-keyword)
                    :bind
                    (:map prog-mode-map
                                            ("C-x M-;" . prot-comment-timestamp-keyword)))
          
             ;;;###autoload
          (defun sacha-org-capture-region-contents-with-metadata (start end parg)
            "Write selected text between START and END to currently clocked `org-mode' entry.
          
             With PARG, kill the content instead.
             If there is no clocked task, create it as a new note in my inbox instead.
          
             From https://takeonrules.com/2022/10/16/adding-another-function-to-sacha-workflow/, modified slightly so that it creates a new entry if we are not currently clocked in."
            (interactive "r\nP")
            (let ((text (sacha-org-region-contents-get-with-metadata start end)))
              (if (car parg)
                  (kill-new text)
                (org-capture-string (concat "-----\n" text)
                                    (if (org-clocking-p) "c"
                                      "r")))))
          
        • prot-window: run a command in a new frame
        • Look into using keyd for tap and hold space?
        • header line format with common tips
      Transcript --

      00:00:00 Opening

      [Sacha]: This is Yay Emacs number 16. I'm Sacha Chua and today I will be talking with Prot once my alarms stop going off. Yes, yes. I'm going to be talking with Prot later, assuming that all of this stuff works. Let me double check my audio is on. Audio is definitely on. I'm trying a little bit early so that I'm not doing so much last-minute panicking. Let's see what we've got here. I am also trying the new OBS 32 interface for things, so that should be fun. Alright, thank you to phyzixlab for confirming that the audio works. I am so fairly new to this livestreaming thing, but I'm looking forward to seeing if I can do it more regularly because I have a little bit of predictable focus time between now and the end of June. In July, the kid is on summer break and so will probably want to hang out with me all the time. Or not, you know, kids are like that, right? So in the meantime, I am trying to get the hang of scheduling things and since Prot happens to have an Emacs coaching service, I figured I would engage him to coach me on live streaming and Emacs and all sorts of stuff, which is really, you know, making sure that I have somebody to talk to and bounce ideas around with and see where we end up. So the last time, which was, Yay Emacs, when was this? Yay Emacs 10, I had a coaching session with him to talk about Emacs workflows and streaming. So I've been working on modularizing my configuration. I'll explain all of this again when he comes on, but just to get the hang of this. I've modulized my config. I've gotten through hundreds of function definitions and exported them all into individual files. I have in fact even renamed them from my-whatever to sacha-whatever. So it's slightly easier to copy my functions because they won't trample over other people's custom functions called my-whatever. My background blurring is very background blurring. So that's all good. And then I've got a couple of other modifications that I've made. So I've made good progress on this very long to-do list that I had made for myself after his chat. But the kiddo is here. Oh my goodness! Okay, you're gonna go back to school and stuff? You just wanted to drop by and make a comment? Yes. Also, the teacher let me change my name, but not family. They just wanted to add a - in parenthesis. Oh, yeah. Oh, that's good. Now they can refer to you. Post my name and my nickname. Alright, I'm going to test this new thing. Interesting conflict here. The kiddo likes making cameos. I am not sure how I feel about the kiddo making cameos. Anyhow! Where are we? Okay, the mic is unmuted again.

      00:04:24 Workflow checklist

      [Sacha]: I am going through my checklist. I have this lovely checklist now. It includes, naturally because it's Org Mode, it includes Emacs Lisp buttons that I can just click on to get stuff running. In this case, for example, I can use obs-websocket-el to start recording and start streaming at the same time. So that's all good.

      00:04:47 Demonstrating =sacha-stream-show-message= and package:qrencode

      [Sacha]: And I want to double check that this message thing works. Let's go see if I can send a message to the chat. Show string. This is a test message that you can ignore. And theoretically that shows up there. That shows up in the chat with a timestamp. So people using video on demand feature where you can go back and just go playback part of the thing can go see it. It would help, of course, if I had the time. And if I expand this. You have the time in the mode line here. It's currently 10:25. But then, my Firefox... Oh, maybe I should just tell you what. I will make this above others. There you go. Fancy. Super fancy. Except this is right where the...

      00:05:54 qrencode

      [Sacha]: What's the QR code? The QR code just repeats the string. So this will be a little more handy if I have... Let me just double check that it does do the string properly. Come on, show me the thing. Yep. So this is my... In case you're watching this in a mobile device and I show URLs, like for example, let's bring up Prot's configuration here. Let's go to... Let's do, do, do, do, do... Prot. Yeah, here. And then if I say show string and I give it the URL, then it gives you the string and the URL should be in the QR code. So people who are watching mobile. You can do that. People who are in the chat can get it from the chat. It's timestamped so that if I grab the timestamps later on, I can use that sort of for chapters. And just generally all these little conveniences. This QR code is provided by the qrencode package. So it's in Emacs. It's actually characters. There's probably a way to just insert the image. But I thought it was cool. I can't remember who had this technique in one of his videos. Maybe it was John Kitchin? That seems like the sort of thing he might do. Or it might be someone else. Anyway, just these little conveniences because copying text, especially in mobile, or trying to type things... Try to pause the video at just the right moment. It's very annoying. Eventually, I would like to plug it into all the usual Embark stuff. For example, you'll see this later as I go through this stuff with Prot. Log buttons will show messages.

      00:07:55 Embark

      [Sacha]: But theoretically, it would be nice to have my Embark here. For example, I'm on Embark on an org URL link. It makes sense that... Wait a minute, I do have it. Okay, I think I have it on Z here. Is that a capital Z or a small z? Let's find out. Z? Not a small z. Capital Z. Whoa, look at that! Okay, okay, so I already do have it. Embark is a package that lets you have context-sensitive keyboard shortcuts. And so I have this now mapped so that if I want an org link, I can press control dot and Z and it will send it to the chat and display it on the screen with a message because who wants to type things manually? You know, this is Emacs. We don't do anything manually. And then theoretically, that also should show up in... Look at that! It's showing up over here in my timestamp section using the magic of org-capture. It includes a timestamp and then, of course, with a little bit of math, I can calculate this as an offset into the streaming video file because I started the stream probably at the same time. Anyway, just a little bit of math to calculate that. And then I can get chapters out of it. Theoretically. Or I could use that to index into the transcript and edit things. Hello, Prot! Hello! We are already live. I have just been on screen.

      [Prot]: Already live! Great. Yes.

      [Sacha]: Panicking. Not panicking. Experimenting with all the fun stuff. I'm now going to share my screen with you so that you can see also. Select window. Let's go to all of it. Screen one? Screen one. I think it's screen one. Okay. Allow. So, theoretically, you should see my screen.

      [Prot]: Very well, very well. Looks good, looks good. We have connectivity issues, it seems.

      [Sacha]: Your audio sounds choppy.

      [Prot]: Yeah, same here. I cannot hear you well. Can you hear me now?

      [Sacha]: I dropped my performance.

      [Prot]: Okay, okay, do that. Well, very well. Because it seems that our... Yes, okay, I did the same. Okay, so hopefully this will work. Let's see.

      [Sacha]: It's an experiment.

      [Prot]: It seems more stable now.

      [Sacha]: Yes, this is one of the reasons why we're having these sessions, so that you can experiment to see what's possible. And I was just telling stream that I've been having a lot of fun tinkering with a lot of the ideas that I was working on after the last chat two weeks ago. So my goal for this session is to not panic.

      [Prot]: I really cannot hear you clearly. I keep getting interruptions, so... It seems that... Yeah, I don't know what we could do. Maybe I can try to leave and rejoin, maybe. Let me exit and rejoin Jitsi, maybe that will fix it. Okay,

      [Sacha]: let's try that. Okay, so let me do that very quickly. Quite possibly, I am asking my computer to do too many things. Let's see. I am asking my computer to do too many things, audio-wise.

      [Prot]: Okay, we will see. We will find out.

      [Sacha]: Let me try changing my virtual mic. How about this one?

      [Prot]: No, your audio is still kind of choppy. Why is your audio choppy?

      [Sacha]: Let's see. What do you think? Yeti, monitor your audio. Let me check. Not good. It's okay. Live debugging. Here we go. Okay, you are, where are we? You are Firefox. Yes, yes, yes. Okay, I can disconnect the, uh, disconnect the connections. Let me think. Connect the ports of Combined Sink Monitor to Firefox Input.

      [Prot]: And while you do that, we will... Testing.

      [Sacha]: How are we doing?

      [Prot]: There it is.

      [Sacha]: Is this slightly better? Testing. One, two, three.

      [Prot]: Yeah, let's see here, so... Okay,

      [Sacha]: that seems to be good. And now I'm sharing my screen. How is our screen? Hmm, does not like screen sharing at the same time. Let me see what's going on with my memory. My memory is fine. I have memory. Let us stop the screen sharing. How are we now? Is our audio back?

      [Prot]: Okay. I can hear you well. I can hear you well in terms of the fact that there is no choppiness now in the audio. However, your voice has been distorted a little bit. It's not a problem. I can hear you clearly, but I just mention it for the sake of your setup.

      [Sacha]: This is interesting and I'm not entirely sure how I will go about fixing it at this moment. No problem. It's not really a problem because I hear you well,

      [Prot]: so that's enough. I am tempted to suggest the non-free...

      [Sacha]: Let's jump over to Google Meet and see if that's any better.

      [Prot]: Let's do it. Send me the link and let's do that. No problem. We are already on YouTube anyways. Let me try this. [Sacha] I will send it to you in the Jitsi chat and then things will be crazy.

      [Sacha]: It's in the Jitsi chat and we'll see if that works. Does that work? I will also email it to you. That's not the link. Okay. Now I need to see whether this actually works. Oh. Ah! Ah, technology! How does it work? Camera is starting. Camera is not starting. I don't know what it's talking about. Camera is starting. Allow camera. Join now. Okay. Testing. My audio works. Admit one guest. Admit. Okay. Testing. Does this work now? I can hear you clearly. Okay. Now I'm going to try sharing this. Yes. Very

      [Prot]: well. And then let's see what happens. Share. Yeah. The moment of truth. Let's see.

      [Sacha]: Technology continues to work?

      [Prot]: Yeah, yeah, it does work. This is smooth. This works. So let's see. Okay, all right. So it probably means that in the

      [Sacha]: future I might actually need to spin up our Big Blue Button server because sometimes the free Jitsi, you know, you're just dealing with whatever you get for free, right? We already have comments. phyzixlab wants to know, well, phyzixlab says, Prot, I'm jealous of your beard. Which Emacs package can I install to have a glorious beard like you? Emacs Genes. Emacs Genes. Y'all can book your own coaching session with Prat. Although technically, I don't mind sharing mine.

      00:17:14 My objectives

      [Sacha]: Okay, so my objectives is I want to capture and share more, right? And that's great because in the experiments that I've been doing with live streaming so far, I have found myself going on tangents based on people's questions. And theoretically, I can go back and use those transcripts, which I haven't yet. But that could be more stuff into blog posts that are more searchable. And creating opportunities for conversation, which I think you've also been experiencing with your experiments with live streams lately. Because it is nice to have that back and forth when you're demonstrating something and you can immediately show something that was unclear. Quick overview of my timeline. Again, until June, I've got a fairly predictable schedule, except for the times when the kid turns out to have a substitute teacher and is too grumpy to go to school. So just some flexibility still with the schedule, but I am starting to experiment with scheduling chats. So that's nice. And this is our first experiment with it. I'm like, okay, let's try a live stream at this date at this time with somebody who is going to show up also. And then in July and August, since my schedule will be less predictable, then we'll do more spontaneous things like we also have been doing. And then September onwards is probably going to be EmacsConf. So with that in mind, I want to quickly share the updates from the last one. And probably, you know, you will think about stuff and say, oh, yeah, have you thought about doing this? Or, oh, that's good. Try this one next. Or in my experience, so and so and so. And of course, I'd love to hear what you've been learning about also.

      [Prot]: Yeah, yeah, yeah, yeah, yeah. Very good.

      00:18:59 keycast-header-mode

      [Prot]: And I will tell you my experience as well, because based on our last exchange, I also tried keycast at the top, for example.

      [Sacha]: Yeah, yeah. It gets out of the way of the closed captions.

      [Prot]: It does. It does. Yeah. So it has some advantages and it's always visible and the key and the command is always visible. But I have to get used to it because it was distracting me.

      [Sacha]: Yeah, I hear you, I hear you. It's kind of a trade-off, right? And that actually goes to one of the points that I wanted to touch on later where getting the hang of live streaming while coding or while working does require a fair bit of trade-offs. On the plus side, I'm going to see if this works. It should insert a chapter marker so

      00:19:45 Trade-offs when livestreaming while coding

      [Sacha]: that I know, okay, this part to this part is this conversation. So when you're live streaming while you're doing package maintenance or you're working on config or whatever else, it is slightly more distracting because people come up with interesting comments and conversations. But on the plus side, it is also, as I've seen you do, helpful at debugging. You're staring at something. You're like, what's wrong here? And someone is like, oh yeah, you're missing a trailing slash.

      [Prot]: Yes, yes. It really helps. Well, I'm not sure if it helps, though, because the fact that you are talking to the chat means that you are not paying attention to what is in front of you. So it can cut both ways, right? There are times, though, where it really helps. Yes. Where you are completely lost and then the people in the chat are like, hey, that's how you fix it.

      [Sacha]: All right. So maybe I just have to A, build up more of a conversation so that we can get those benefits and B, figure out how to run my narration on a separate worker thread in my brain. I don't think it happens. I think I used to be more multithreaded in the past, but I am slightly less multithreaded now. However, it turns out that spending all this time with kids means I am getting better at generating verbal responses that I'm not necessarily, you know, like focusing too much on or just saying like stuff to keep them amused and entertained. Oh, that's quite a skill. Yes,

      [Prot]: that's good. That's good. I don't know. But yeah, so there

      [Sacha]: are trade-offs here.

      00:21:24 Trade-offs: seeing less text on the screen

      [Sacha]: The other thing is now that I am using mode to switch on my... I am streaming, do the Fontaine preset and all of that stuff. Now there's like less space on my screen for code. So I had to get used to it again. yes yes yes

      [Prot]: yes that that's one of the downsides of course yes like you have to have a larger font so that people can see what you are typing and then of course that comes at the cost of including fewer things on screen Though maybe you could have a little bit of a wider frame, like specifically in your case. I don't know, it's already at the 80 characters already? Yeah, it's already... Yeah, I think in my case, my frame fits about 100 characters. Well, I haven't measured it, but I think it's something in that... Like, yeah, about there is my frame.

      [Sacha]: Yeah, it has about 80 characters. So it's about 75 characters.

      [Prot]: So in my case...

      [Sacha]: All right. And then the stream can tell me if this is still readable, because of course more code on the screen means more code getting written or done.

      [Prot]: And just to say also more code on the screen means that it can be easier to debug or write the code. Because you have the context right there. You don't have to go up and down the screen to find it.

      [Sacha]: Especially since I'm used to actually dividing my frame into two windows so I can do left and right. And I'm doing this on a standard aspect mode. You have a widescreen, so you're a little bit spoiled in this regard. I only have like two monitors that I'm doing. But maybe that is what I'll end up just using separate frames for. Yes, so slightly smaller font size, and stream can tell me whether this is too small for them. I know people who are older will develop an appreciation for larger font also, so take advantage of this ability to work with medium-sized fonts while they can. So font sets, that's definitely a thing. And then just trying to figure out how I can make it more useful both to other people and for myself and during the live stream as well as after the live stream.

      00:23:52 Lowering the effort needed to announce a stream: Prot just announces it and the blog post embeds it

      [Sacha]: Now you've mentioned you don't actually go back into your live streams afterwards. You just plug the YouTube video, you update your description so that it's past tense instead of future tense and you republish your post. I think that's your workflow, right? Even less. So I don't even retrofit the

      [Prot]: past tense, you know, present tense to past tense. It's like all present tense. It's like I will do a live stream. It will be recorded. You can find it here kind of thing. Okay.

      [Sacha]: All right.

      [Prot]: And so just to say, though, just to say the reason I do this is because I don't want to go through a three hour stream again because then a three hour stream becomes like a ten hour stream in practice. And this means that it adds friction and it adds to the requirements, which effectively means I will be doing fewer of them. Yeah.

      00:24:43 Timestamps

      [Sacha]: That's what I'm thinking. Maybe lightweight sort of chapter markers. You've mentioned you just remember this sort of stuff, but since I don't actually remember this sort of stuff, having a way for Emacs to send messages to the stream and also show things in the timestamps. I have a timestamp now. It's nice. It just says Org Capture. And all that will then theoretically make it easier for me to say, okay, let's go find the chapter and then I'll just adjust the timestamps afterwards to say, okay, from this point to this point. If people are interested, they can go in there and they can look at the transcript for more.

      [Prot]: I think we discussed this last time as well. You could have a function like start-stream and it starts a timer or it starts recording the time and then relative to that point, any offset and that's your timestamp right away. And whenever there is some event happening, you can type a key and then maybe it gives you a prompt and you write what is it, like just a string and then that is the chapter.

      [Sacha]: An org timer will do that kind of insert a timestamp for you. But one of the reasons why I liked having my custom show message thing is that it can display the text on the screen, display a QR code for the text in case people want to copy the function that I'm talking about, send it to the chat so that people using video on demand can say, oh yeah, at around 10:25 or whatever. I'm currently using wall-clock timestamps, which means I need to modify my mode line so that the time starts earlier and people can use that to jump around the thing. And then, so it's like in half a dozen places, which is what org-timer does not get me if I'm just inserting a timestamp here. Anyway, minor, like, you know, little workflow improvements. But it's this whole, as you said, I don't want to go back and spend six hours processing the three-hour livestream. I want to say, all right, this video has some potential interesting things here because these people ask these questions. This is roughly the time when I answer those questions. Ideally, this is the text of the question. Someday, there might even be screenshots and clips. I'm modifying compile-media to make it easier for me to do that kind of video editing from within Emacs.

      [Prot]: Oh, wonderful.

      [Sacha]: yeah, yeah. But it's all still like, okay, progress. First, I've got to develop the habit of streaming, and then I have to develop the habit of saying, now we are talking about this topic so that it can all get marked everywhere.

      00:27:29 Different types of livestreams

      [Sacha]: And that got me to thinking, well, there are a couple of different types of live streams and you might have also done something about which ones fit the way that you had to present. One is the, you know, the, I'm going to spend time doing this anyway, which is like your package maintenance, where you will accept a little bit of distractibility for the benefit of having other people around to ask questions and clarify things and stop you when you're getting stuck somewhere. I have something I specifically want to teach and you've done this before with walking through a blog post and just demonstrating things interactively because there's some things that are easier when you're showing it, right?

      [Prot]: Correct, correct. ...

      00:28:14 Reading other people's configs

      [Sacha]: Reacting to other things. In this one, I've started to have fun with because I've been going through your Emacs configuration, which is several hundred pages when converted to a PDF. And I forget, do you actually, like, do you produce a PDF, PDF, like a nicely thingy?

      [Prot]: I haven't done it, but that's trivial to do, actually. I could do it.

      [Sacha]: Yeah, yeah, so I've also been reading tecosaur's PDF, and his PDF is gorgeous. Like, it starts off with, like, a cover page and and everything. But it's Doom Emacs. I have to translate a lot of things to my specific setup. But now I have literate config envy. Anyway, that's an entire category of live streams here, which could just be me copying interesting things out of other people's configs. Today we are experimenting with a chatting with a guest variety of live stream, which you also do with your Prot asks. Actually, I forget. Are those live streams?

      [Prot]: They are not live streamed, but the idea is that I do not edit them. However, if somebody really wants, I can edit it. So the idea is let's go with the flow. Don't worry about it. It's casual, all that. But if somebody says something that doesn't sound right, doesn't mean it or whatever, I'm happy to edit it.

      [Sacha]: Yeah. I'm starting to look into how to do that if I'm doing this live and apparently if I set up a sufficiently long buffer in OBS for streaming, like a delay for 20 seconds or 15 seconds, then I can stop streaming and the stuff that happened in the last 10 or 15 seconds doesn't make it out to the public, but it's still kind of...

      [Prot]: Living dangerously, yeah.

      [Sacha]: Yeah, yeah. Because seeing as I'm still practicing remembering to flip the webcam down when the kid runs in and wants to be on camera, I'm like... My reaction time, not there yet.

      00:30:12 Hanging out

      [Sacha]: And then other people are like, they just hang out. They're not like, I'm going to do something. They're just hanging out, which I'm sort of starting to experiment with when I'm doing Emacs News on Mondays, because I'm like, I'm categorizing it anyway, but it doesn't require a lot of brainpower because I'm not coding or debugging. I'm just saying, okay, this looks like an Org Mode link. This looks like a miscellaneous link. And then some people just play games, which is fun too.

      [Prot]: Yes, that's good. And they want to have somebody on the side, guide them through what they are doing.

      [Sacha]: Yeah, or it blends into a hanging out sort of thing. Yes, yes. And it's like, what is the kiddo doing now?

      [Prot]: Yeah, the camera, the camera. That's fun, that's fun. Good reaction time. Yeah, yeah, yeah.

      [Sacha]: Yes, thank you for your homework. I will scan this and put it online later. This is it. Yes, life. Life.

      [Prot]: Putting your reaction time to the test.

      [Sacha]: Yes. So in terms of getting more out of livestreams, That's what I've been thinking about lately. I think I would like to do more of these, you know, hey, folks, keep keeping company while I'm coding this or whatever, since you've been having a lot of good experience with that.

      00:31:40 Livestreams for explaining specific things

      [Sacha]: I would also like to eventually move into more of these. I have something I specifically want to demonstrate, which probably necessitates actually organizing my thoughts. And you've done a bunch of these. After writing a post, it seems like more like recording a video and walking through it. Do you also sometimes do them before writing a post?

      00:32:00 Prot on didactic livestreams

      [Prot]: I haven't done that but actually, when I write posts, I write them in one go, so maybe I should do a live stream where I actually write a blog post just to show that I can do it. The thing is of course what do you want to communicate, because if it's teaching, like if you are writing it and trying to teach it at the same time, there is a chance that you might leave something out. Some of that detail, some of that nuance. For example, if you want to explain how a form in Emacs Lisp works, let's say if or cond, you may not come up with a very good example live and it may not have didactic value. So even though you know how it works, the communication value is not there. So that it helps for you to write it in advance. Even if it's in one go, again, you can write it, you can read it, and then you can come up with a good example and then stream that. So it really depends on what you want to do. The other day I did a stream, a live stream, where I was writing a package from scratch, a small package. So there part of it was to teach, but also to demonstrate. And there I don't really care if the didactic value is very high. Because even if there are mistakes, it's part of the process. It's not like, well, you will come here and from zero to hero kind of thing, you will learn everything. It's not like that. It's like you come here, you might learn something, but the bar is relatively low.

      [Sacha]: I think especially since my mind likes to jump around a lot-- you seem a lot more organized when you're thinking through things, especially if you're saying you write your blog posts straight in one go. I'm like, okay, do this part over here, do that part there. I will definitely lose things, like you mentioned, and I will definitely go back and say, no, I need to do this before I can say that. So yeah, I think I can save that for summer when I might be focusing more on things I cannot schedule.

      00:34:07 Prot suggests breadcrumbs

      [Prot]: How about leaving breadcrumbs for yourself? Like, I was writing this. Like, write a comment. Basically, I was writing this, I need to remember that, and then you jump off on the tangent.

      [Sacha]: I need to use a universal prefix to get the time, don't I? Yes. Leaving yourself breadcrumbs. Yeah, yeah, yeah.

      [Prot]: And then you can retrace your thoughts, basically. Like, okay, I was here, I was meaning to do that. Especially when you are streaming, chances are that there will be several comments that are very interesting and you want to get to. And you might be talking to them for 10 minutes or more. And then, of course, if you don't have that or you want to jump off on a tangent, you will eventually forget what you were doing.

      [Sacha]: Do you have anything like this already that you're currently doing?

      [Prot]: And no, but this is the sort of thing that should be a fun exercise to actually demonstrate as well for yourself.

      [Sacha]: I use ZZZ if I just put it in text and I have some things, for example, in my message hooks so I can't send email that contains this. And of course, org has its whole clocking and interrupting tasks that I can use. I just have to have the presence of mind to actually say, oh yeah, now I'm going to go on this tangent and I want to go back to this later on. Leaving myself breadcrumbs is definitely something I need to formalize into workflows that I actually use.

      [Prot]: Yeah, that's the thing. And you can also benefit. I don't know. Of course, that's depending on if you are a visual person or not. But you could also rely on color or, for example, include an emoji as well or modify font-lock-keywords to have like something that stands out. Basically, make it clear that, well, this is an interjection. I will just go and then I will be back. Yeah.

      [Sacha]: Good idea. Okay. So that will definitely help with the things where maybe I want to demonstrate something and I want to do the thinking out loud so that it's recorded. And just in case other people have any questions, they can come by and ask them. And then I can sort of massage it into a proper blog post, but still leave the link to the video in case people want to hear the stream of consciousness figuring out of all of this stuff. That sounds like maybe a more polished video or blog post with screenshots and clips coming out of this livestream ramble, kind of tangled. Okay, we're going to jump over here. Gotta leave myself a breadcrumb because I'm going to go in this detour to answer someone's question.

      [Prot]: There is value to both. There is value to both because the live stream is a stream of consciousness. You can think of it like a bubbling effect. There is fermentation going on, a lot of things happening. And then when you publish the polished, the finished article, that's the distillation effect. So fermentation distillation. So both are useful. Both is good to see and have a sense of what they are up to, what they are doing. Yeah.

      [Sacha]: And Charlie in the comments says he likes Emacs' excursions terminology. So if you can think of it as a save excursion, I'm going to go do something and then come back. I am not very good at popping the stack, but I will work on it. Yes. A couple of other things that I want you to pick your brain about. So you mentioned that in terms of announcing live streams, you're like, look, I'm remembering to mark a topic change.

      00:37:59 Announcing livestreams

      [Sacha]: So you mentioned, okay, you have a post for the scheduled or spontaneous live streams. Then you actually, you don't even update it with the description. You write the description beforehand and you leave it alone. Probably when people get it in their RSS reader, I guess the YouTube embed always just points to, you know, it's either the currently playing live stream or the archived recording of it. And that's that. The link is the same. The link is the

      [Prot]: same. Yes. Yeah, on this live page. So now I have

      [Sacha]: yayemacs.com and SachaChua.com/live pointing to this page. And there's like, there's a YouTube way to embed just like upcoming live stream, but then it's like fiddly when it comes to, oh, you know, you've got, if you have more than one public up scheduled live stream or whatever, do you use any of this stuff at all where you're like saying a page that's always has your upcoming or current stuff?

      00:38:58 Embeds: Prot embeds specific YouTube videos instead of the general channel one

      [Prot]: No, I have a generic embed which I copied many, many years ago and I have it in my static site generator. Then the only field that changes is the ID of the video. And this works for live streams as well as pre-recorded videos.

      [Sacha]: Okay, so you always give it like the video IDs basically.

      [Prot]: The video ID, yes. I can share with you the exact snippet.

      [Sacha]: Yeah, yeah. That would be, you know, and you can send...

      [Prot]: Yeah. Well, it's public anyway.

      [Sacha]: I can steal it off your website. It's fine.

      00:39:32 Demo of my new shortcut for converting time zones

      [Sacha]: And then I have just added timestamp translation as well. So I can say, okay, you know, let me show it to you. So this is my webpage, right? So here, this is your standard org timestamp. Yeah. And if I open up https://sachachua.com/live, it's also the same as Emacs. Okay, okay, okay. And I find the browser window. Okay. Theoretically, if I say, okay, down here, you click on this, it translates it to your language. Ah, nice,

      [Prot]: Nice, nice.

      [Sacha]: Because YouTube will do that for the upcoming one if people link to it. But, you know, it's just people. But this is JavaScript, anyhow. And the other thing that I have just added today is I can go onto that in Org. If I press my control dot embark thing, I can use my Sacha Org timestamp in time zones, which is shift W. And it translates it into a gazillion time zones. So then I can mastodon toot it, which I did,

      [Prot]: Just to say that copy to the kill ring, okay, yes, okay, good, good, good.

      [Sacha]: Because time zones suck. I mean, it's great, but I cannot do the translation and so I am slightly... I'm working on announcing those upcoming scheduled streams while doing all the math so that... well, having emacs do all the math so that I don't have to do the math.

      [Prot]: Yes, that's the spirit. That's good. Very good. This is very nice. Is this timestamp always meant for Mastodon or do you have it elsewhere? I think I've seen it in the Emacs news as well.

      [Sacha]: Oh yeah, I'm basically stealing the code. I've used it in Emacs Conf and for Emacs News. I used to announce the Emacs News events also. I should get back to doing that. But definitely in the Emacs News and Emacs Calendar, I translate all of the events into multiple time zones for the virtual ones.

      00:41:48 Ozzloy's questions about time zones and QR codes

      [Sacha]: Line 23 doesn't have a time offset. Okay, someone is commenting. Ozzloy will tell me about it a little bit later. Ozzloy also has a question. Am I creating the QR code with Emacs Lisp? Is it actually text in Emacs? I'm going to go on a quick detour to show the QR code. Yes, do it, do it, do it. By

      [Prot]: the way, I will like the stream. I didn't have the chance to do that. A show string. Yes. So here, this is my... Look, I'm

      [Sacha]: using line numbers, but they're really long. Yeah, these

      [Prot]: are massive. Of course. What can we do? But it's still better because I can say, okay, go to 97, right? And you kind of know where I mean. Yeah. Yeah, so this is qrencode, qrencode

      [Sacha]: format, and all of that stuff. It is in Emacs. I think this one actually inserts text. There's probably a way to get it to get images as well. But yeah, so QR codes, because why not?

      [Prot]: Yeah, no, that's very efficient. Yeah, yeah, good, good.

      [Sacha]: Okay. Yes. So these timestamps are basically in my local time, and then I can translate them to other time zones, and then I can start announcing them, which will probably happen more if I can get my GotoSocial Mastodon thing to be more reliable. But also following your example, I should try putting it in my blog. I just feel like a little weird suddenly going from posting on my blog like once or twice, well, two or three times a week to Hey, OK, every day. All right. In ten minutes, you're going to have a live stream of me talking about random stuff.

      00:43:46 Prot on announcing livestreams on blogs

      [Prot]: Well, in a sense, it is weird because it's not something you would normally do on a blog, right? Like you have been blogging for a long time and you know how blogging is, right? You just do it on your own. But this streaming culture is a different experience. I think, however, it shares a lot with the blogging way of doing things, which is like, well, this is what I have to say. This is what I think. And I just do it in a slightly different format. And of course, because you are doing the stream, ultimately you control how you participate, to the degree that you participate, what you want to comment on. So ultimately, even though it's a live stream, you can control it in a way that is not that much of a live stream. In the sense that you can be very specific, very structured and be like, you know what, this is my structure, this is what I will do, and I will not run off on a tangent, for example.

      [Sacha]: I don't know if it is possible for me to not run off on a tangent. I appreciate people who can be very focused. It's okay. I think my job, I think my goal is more of how do I at least describe the tangents in text form so that I can find them again and so that other people can decide whether this is worth two hours of their time or whether they can just skip to the five minutes that concerns the thing that they like.

      [Prot]: Yes, in that case the timestamping would be the way to go. Timestamp plus a brief description.

      [Sacha]: Yes, yes, and that actually gets me to... ta-da!

      00:45:25 Processing the recordings

      [Sacha]: topic: processing the recordings So, yes, as I mentioned, I've been enjoying going back and editing the transcripts because it becomes an excuse to tinker with Emacs and subed-mode, and then because I have this thing for adding a note above the start of a chapter, I can then easily use that to extract the chapter markers for YouTube and all of that stuff. As I mentioned, I'm working on some workflows for tracking chapters on the fly. You know, it's actually really nice having this little button. I used to think, okay, I can just press a keyboard shortcut, but apparently I forget all of my keyboard shortcuts when I'm trying to talk at the same time. So if there's a button, I'm like, I get incentivized to click on it to see whether my code still works.

      [Prot]: Plus it functions as a reminder.

      [Sacha]: Yes. So it's very helpful that way. And then, as I mentioned, I still need to work on a good workflow for extracting the screenshots and clips so that I can then turn it into blog posts later on and so forth. Right now, I have a pretty manual process for, okay, after the video is posted, I'm going to download it. I have some shell scripts now and the next step of course after this one is going to write an Emacs function that actually and I just finished this part. I have an Emacs function that calls the shell scripts to download the thing using yt-dlp and then start the transcription process but I still manually do the upload to internet archive which I know has a CLI tool so that's next in my list, and fix subtitles and all that stuff, so that's kind of... if I want to get more out of the recordings, that's a general direction I'm going.

      00:47:15 Commitment devices

      [Sacha]: This is not something that you're currently fiddling with.

      [Prot]: Basically, I'm the wrong person for this.

      [Sacha]: Yeah, it's okay. And part of these conversations is not so much that I'm looking to you for specific advice on things that you explicitly don't do because it would be against the alla prima. Just get it done and lower the barrier going in. But it's also useful as a commitment device for me to say, alright, I would like to get better at this. I am telling Prot in order to be able to demonstrate the stuff and make myself... If I'm going to see him in another two weeks... Am I going to see you in another two weeks?

      [Prot]: Yes, yes, yes. And I will ask. I keep receipts. Yes, yes, yes.

      [Sacha]: Exactly, right? So this is also valuable for that. Not just hoping that in your config, which I have now read, that you would have a snippet exactly for this purpose, but more like, okay, I'm telling somebody I'm going to do it, which means I got to go do it.

      [Prot]: Yes, yes. And of course, just verbalizing it means that you can also understand it a little bit better. And you start thinking about it. And then it's a matter of writing the code.

      00:48:29 Automating more of the process

      [Prot]: I'm curious, though, why do you have the shell scripts and not bring all of that into Emacs? What's the advantage of having Emacs called the shell scripts? Or was it just more convenient?

      [Sacha]: It's just out of convenience. Emacs does call the shell scripts. The shell scripts are there just in case I happen to be SSH-ing in from my phone. Because I'm downstairs or whatever and then I can just run it from the shell also because I use it not just for my... So I have some shell scripts for downloading the video as an MP3 or as an MP4 or as the subtitles. And so these are generally useful things that I might not necessarily remember to be in Emacs for. So that's definitely, you know... I needed to find this whole process that eventually ends up in a blog post that has all my lovely stuff. where this chat that I have with you is kind of my high-water mark of this is really fun. I would like to do more things like this, where it ends up with transcripts, resources, kind of like the show notes chapter marker indexes. These are automatically extracted from the transcript. Rough notes that we were working on there. The session ... The transcript has speaker diarization. In a video, I got your subtitles to show up in italics and my subtitles to show up in plain text. So now that I have this infrastructure, I feel compelled to make sure I schedule conversations with people so that I use it.

      [Prot]: Yes, of course. And that's actually a good reason generally for writing code, ultimately, because it's the vehicle for doing what the code is supposed to facilitate. So the code is just a pretext for actually doing the thing.

      [Sacha]: Or the other way around, yeah.

      [Prot]: Or it can be the other way around. So the code is the goal, yeah.

      [Sacha]: Yeah, yeah, I know. EmacsConf is basically the way that I test emacsconf.el. Hi. It's fine. It's fine. Yeah, so that's my thing for processing recordings. Changing topic. The button. The button. The button. We must press the button.

      00:51:14 Copying non-packaged code

      [Sacha]: Non-packaged code. So now that I've modularized my Emacs configuration, I've split all the defuns into different files. I have renamed everything from my- to sacha- so that I don't step on other people's function definitions. Now I'm starting to copy things from other people's code to see whether this is actually a viable approach. So this is the way I'm currently stealing something from your prot-comment. Is this sort of like... It seems to work when I go into something. If I go into something, I can press C-x M-; and it does the thing that you define. So this is sort of what you had in mind, right?

      [Prot]: This is basically what I was thinking earlier with the comment. Yeah.

      [Sacha]: And then theoretically, this sort of structure will also work for other people who have checked out my very large config and they can autoload specific commands out of it and then they can bind key bindings without necessarily importing all of my other set queues and add hooks because that's in a separate file now. The only thing in my list is defuns.

      00:52:25 Prot on defcustom

      [Prot]: And if you also, just to add, if you also have configurations for your packages, right? You can also have defcustoms for there, maybe with a default value that works for you or with a default value that is generally useful. And then you can also separate that out. So users don't have to pull anything from your configuration, but just pull the package.

      [Sacha]: So right now I have... Right now I have my configurations as defvars because I'm lazy. Do you happen to have a function or whatever that you like to use to just convert a defvar into a defcustom?

      [Prot]: I haven't done it because it's actually tricky with the type.

      [Sacha]: Yes.

      [Prot]: You know, the defcustom has the type keyword. And of course, for the most trivial cases, this is easy. Like, OK, it's boolean or it's a string or whatever. But usually it's not that simple. Like if you have an alist, you have to describe what are the key and value pairs or whatever and the elements of the alist. So I haven't done that because it's always on a case by case basis. And many of the defcustom I have will have like a bespoke type because the data structure is really specific. You know, the value they expect. For example, if you are doing something with the action alists of display buffer, like they have a really specific type how you write it.

      [Sacha]: Yeah, yeah, I hear you. So I think because I have a lot of strings, I probably can get away with something that just reads the form, smooshes it into a string, adds a string, or possibly what this will end up looking like is maybe a completing read on the type of the function. Sorry, the type of the thing. And then I can just select from several types.

      [Prot]: Well, you can make it like you can make it a guess. Like, of course, if this thing is quoted and it's a symbol, it's not a list. Maybe I can have like a choice or a repeat symbol or something like you. You can, but it won't be accurate. Like that would be like for you to fill it in later.

      [Sacha]: Yeah. No, I was thinking just more along the lines of Like a completion so that you can select from maybe some of your common types. The actual guessing of what type it is would be an exercise left for future me. But even just not having to remember exactly what the syntax is for repeat would be nice.

      [Prot]: Actually, that's good.

      00:55:12 helpful and elisp-demos

      [Sacha]: Yes. I mean, one of the things that I always find helpful is, like, I think I've got some examples now. I'm using helpful, right? And I'm also using this elisp-demos. So it just tells me, like, I can add more notes here and I can say, okay, this is what a defcustom, that's a repeat of a string or what a const looks like, so that... 'Cause the manual doesn't have a lot of examples sometimes. Sometimes it's annoying to dig through it looking for examples. Usually it has no examples. I think that that's...

      [Prot]: if there was one area of improvement, it's that. Keep it as is, because it's high quality, but complement it with examples.

      [Sacha]: I mean, technically, all of Emacs is an example, and you can just find something, but...

      [Prot]: Yeah, that's why you have the manual, because if I have to dig through thousands of lines of Emacs Lisp, that will take a toll on my patience.

      [Sacha]: Yeah, so for anyone who's watching, helpful and elisp-demos is how to add these helpful little notes to your describe-function, because who remembers these things?

      [Prot]: Yeah, yeah, yeah. That's very good. That's very good. Yes.

      00:56:23 Prot on code libraries

      [Prot]: Just to say on the point, if you have packages, this is something I actually do. I just go and reference one of my packages, which I know I have done the research for. So I'm like, okay, how do you do the display buffer action alist type? I will just go to, for example, denote and copy it.

      [Sacha]: I will eventually build up a list of examples that I can refer to.

      00:56:50 Prot rewrites functions to fit his style and naming conventions

      [Sacha]: The other question I had though was do you ever find yourself copying code from people who do not have their You know, they're functions in nice little things that you can just import and autoload. And what do you do about it? Like if they're, you know, let's say they named it, then maybe they named it without the prefix. So it might be possible to confuse it with the standard stuff or they, you know, it's mixed in with the rest of their config so you can just load the file. What do you like doing when you are copying that kind of code?

      [Prot]: I will basically check if I can make edits to it. The first thing I would make is probably change the style to be like my style. So I would anyway change it so there is no scenario where I would just copy it verbatim and paste it.

      [Sacha]: Okay, so you like to rewrite things and then you fit it into your naming convention because it is now yours.

      [Prot]: But also like the style. For example, this function you have over there, like Sacha here, like the one we are seeing now on screen. For example, I would change the name of pargs. Not because it's wrong, but because stylistically it's not what I would write. Then I would change the indentation. Org Capture String, I would put the concat, the line below. I would basically do small tweaks, not because it's wrong what you have, but because stylistically I have a different way of expressing it.

      [Sacha]: Yeah, yeah, yeah. Absolutely. I've started to add where I got it from in the docstring instead of... I used to put it in the comment. But as you mentioned, the doc strings are a little bit more visible. So then I usually don't end up looking for updates. But at least theoretically, if I do want to, I could find out who was... Or if I want to credit somebody or see what else they've come up with lately, then at least it's there.

      [Prot]: Yes, it's good enough. Plus, when we are talking about these smaller functions, having the link there, I think, is enough. Like, you wouldn't need to go search for updates or whatever. Like, if they have made some changes, chances are it's there.

      [Sacha]: Yeah. Okay, so rewrite things, make it fit your style, and add stuff to the docstring because you like to have thorough docstrings.

      00:59:18 Prot's preference for small functions

      [Prot]: Yeah, yeah, yeah. There are many functions I have where the docstring is longer than the code. I would say, yeah, many of them are like that. But also, just to say, it's because of how I will write the code, where there are many small functions building up to a big one. And so then the docstring explains basically what all these small functions contribute to.

      [Sacha]: I like small functions too because I got used to coding on even smaller screens, right? And so anything that could just actually fit in the screen was much better than things that I had to page through. And it gives you many more avenues to modify the behavior because you have more places that you could def-advice, sorry, advice-add :around or whatever.

      [Prot]: Actually, this is why I started doing it as well, because it's easier. I had this reason myself. I think it was an org function, which is like 200 lines, and I wanted to really change one thing and I had to copy the whole function. And I'm like, well, if this was a helper function, I would be done by just overriding the helper and I would be good.

      01:00:23 avy-goto-char-timer

      [Sacha]: I am slowly getting the hang of using avy-goto-char-timer so that I can copy the symbols from elsewhere. Because even if I'm using nameless to insert the prefixes and then I'm using dabbrev-expand or hippie-expand, for which the config I still need to fiddle with to make it absolutely perfect. It's still a lot of typing sometimes, since we like to use long function names.

      [Prot]: And which timer variant do you use? Because it has, with two characters, it has the 0 one, which is type as much as you can within a certain time window.

      [Sacha]: That's a good question. Where is this?

      [Prot]: Char timer. I think this is based on... I think this is the zero. Yeah, I'm not sure. I remember it's called zero.

      [Sacha]: So like I can type li and then go to like lj to jump to that one and now I have it so that I can M-j li and then I can press the yank yeah like y like insert from there which is yes when I was when I was stealing stuff from your config, I could... oh let me show you... where is this... So this is your config, right? Well, this is... Hang on a second. Org link preview. There you go. So now the highlights of your config. I can steal stuff from your config and say, okay, M-j, open parenthesis, oops. M-j. Open parenthesis. I can copy the entire line of LK from avy, which is very nice. Very nice. Yes, yes. So, pretty fast side there into avy. I have to slow down and actually focus on doing the keyboard shortcuts because it's a new habit that I want to build, especially since.

      01:02:40 One-shot keyboard modifiers

      [Sacha]: Also related to one of your recent videos, I'm experimenting with one-shot keyboard modifiers.

      [Prot]: Oh, well done.

      [Sacha]: Yes. It's a little tricky. I have to get my brain to get used to it. I'm using keyd to do this on Linux. And it's just getting the hang of pressing control and then moving to the thing. It's messing with my brain a little.

      [Prot]: But consider that it's a good opportunity to also use two-handed mode, basically. So, for example, C-x, right? Not like C-x. You see what I'm saying? So basically one hand for the modifier. Yeah, exactly. Because that's a good practice in general, even if you use the standard modifiers. Yeah.

      01:03:29 Toggling

      [Sacha]: And one of the other things that I started doing after our previous conversation and having looked at some of your toggling sort of things, in your config, what's this idea of using the C-z and C-S-z shortcuts? Since who likes to suspend Emacs anyway, right? So now my C-S-z toggles my now.org, which is the stuff that I'm going to be working on, including the stuff that I want to get the hang of using. So this is my, all right, I need to scope it down so that I don't get overwhelmed. These are the things that will, you know, these are the things that I'm trying to get the hang of using. C-z gets me to my stream notes because then I can add things while I'm live, and then C-S-z is what I have as my now, which also gets posted to my web page, sort of like what I'm focusing on. Which, actually, I can reorganize anyway. So I'm liking this toggling because I can press, like for example, if I'm in the middle of my scratch buffer, I can press C-S-z, pop it up, and then pop it back down. And I was watching Joshua Blais's video about he gets to do this sort of like toggling things in and out from anywhere in his system. So now I'm jealous and I need to figure out how to get that working too.

      [Prot]: Yeah, yeah, yeah. That's the kind of thing that is really helpful. Like pop it out and then when you don't need it, it disappears.

      01:05:08 System-wide toggle shortcuts using emacsclient

      [Sacha]: Do you have any of that kind of system level of toggling even when you don't have Emacs as your main application sort of thing?

      [Prot]: Via emacsclient. So you can have a key binding to emacsclient, an emacsclient call, and it will bring up an Emacs window from anywhere. I have that, yes. I have it for a few things. TMR mostly, the timer package. So if I am, for example, here, I can bring it up and start the timer without actually switching to Emacs. Okay,

      [Sacha]: so that sounds like something I need to look into. It's

      [Prot]: in the prot-window file, prot-window.el. I have a macro there, and it's a macro that defines a command. To run in a new frame and once you do something, such as complete or cancel, to close that frame basically. And it's using a condition

      [Sacha]: case. It's using a condition case. I think it's the simplest

      [Prot]: you can do.

      [Sacha]: And then that's a global keybinding on your window manager that runs that and then brings that so that you can pop it up and put it back.

      [Prot]: Yeah. It's just emacsclient -e and then the command.

      [Sacha]: Oh, that's interesting. Rickard says using space as control has revolutionized their Emacsing. I'm not sure I'm ready to take that step yet. Also, I can probably figure out how to use keyd to use it as a modifier. We'll see. It's a nice big key, you know? You're just tempted to do all sorts of things with it.

      [Prot]: Of course, at the keyboard level, you can have different behavior for tap and hold. So when you tap the space, it's an ordinary space. When you hold it, it's control. Maybe that's what they are.

      [Sacha]: Yeah, I think that's what's happening there. Look into using keyd for tap and hold.

      [Prot]: Yeah, and this is the principle behind the home row mods, the standard home row mods. It's like when you tap, for example, H, it just does H. When you hold it, it's some modifier key.

      01:07:25 My next steps

      [Sacha]: I have three minutes before the kiddo runs out and goes, mom, it's lunchtime. So do you have any, like, okay, my next steps, I've got stuff that I need to work on in terms of improving the processing of things and automating things. I found this session very helpful for saying, okay, you know, like, in the weeks leading up to it, two weeks leading up to it, it's like, okay, I got to write this code because I want to be able to say I did it, which is good. And as a result, I have all sorts of fancy things now in my Emacs for streaming and also for my config. In two weeks, I would love to have this kind of conversation with you again, if that's all right with you. Do you have any tips before the kiddo comes out?

      01:08:18 Tips from Prot: small functions used frequently

      [Prot]: Yeah, yeah, yeah. So for the functions you want to write, you want to make the functions be small so you can test them all and make them part of your habit, like start using them even before the streams. So try to use them every day so that you basically have almost a knee-jerk reaction where it's like, oh, I'm doing this and you call the function basically right away. And I don't know if you use the F keys, the function keys for your shortcuts. Maybe those would be good.

      [Sacha]: Yeah, I have some of them. But again, it's hard for me to remember sometimes which one I have matched there. So again, it's trying to build it into muscle memory. Probably what I just need is some kind of drill thing.

      01:09:06 Maybe using the header line for tips?

      [Prot]: How about a minor mode that sets the header line format? You have seen in many buffers where it says type C-c C-c to finish, right? So set the header line format to be like, you know, type, I don't know, Ctrl-Z to bring up the pop-up, whatever, right?

      [Sacha]: Yeah, I mean, quick help sort of is that idea...

      [Prot]: Yes, quick help would help you do that as well, yeah.

      [Sacha]: It's a screen space thing. But if I can find something that I can smoosh together with keycast so that it reminds me of my key tip in this context. Ah, with keycast. Interesting.

      [Prot]: That's why I was thinking of header-line-format. So it would be something that will appear there. And of course, the header line works exactly like the mode line, meaning that it can update the content. It's not static. So like your mode line will update information.

      [Sacha]: Yeah. Okay. All right. So let me think about which tips might be, you know, like my keyword shortcut of the day focus could be interesting.

      01:10:23 Reorganizing keys

      [Prot]: But it also brings the point like here, of course, like the keys you have, maybe it's also a good opportunity to organize them differently. Like the header here should prompt you for one prefix key, for example. Like, you know, C-t, let's say, and that's for transcribing or whatever. Right. And it will just have that one there. And then with the help of which-key, for example, you see what you have behind that prefix.

      [Sacha]: I have a hard time figuring out keybindings, which is one of the reasons why I like looking at configs like yours and other people. Because I'm like, yeah, I can totally use that as a starting point for keybindings. But then what else do I assign to it? So for example, I've got this. I apparently don't have this. I have this sacha-stream-transient C-c v. That's where I put it now. Okay. Which now has things like OBS and all that stuff.

      [Prot]: What's the mnemonic for v?

      [Sacha]: Oh, v would have been video sort of thing.

      [Prot]: Okay, I see.

      [Sacha]: But I have to fiddle with it and the kiddo is going to come out any moment now. So thanks just in case she comes out.

      [Prot]: You're welcome.

      [Sacha]: Well, it's lunchtime. Thank you for this. I will schedule something else in two weeks. I'm going to try to practice more scheduled live streams and keep fiddling with this workflow. This has all been very helpful. And thank you to the people who also have dropped by and said hello. You can check the chat later. It's fine. Yes, yes. Thanks, everybody. All right. Okay. I'm going to say bye here just in case. Take care. Take care. Take care, Sacha.

      [Prot]: Take care, everybody. Bye-bye. Bye-bye. Thank you.

      [Sacha]: Thank you everyone for hanging out. That was my chat with Prot. And I will see y'all again maybe Thurs... Well, probably before then. But I will try to schedule something on Thursday for around that time. Who knows what it's going to be about. But yeah, thank you for coming and experimenting with me. Let us end the stream there. Because it's lunchtime.

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

    12. 🔗 r/reverseengineering Binary Ninja 5.3 (Jotunheim) rss
    13. 🔗 3Blue1Brown (YouTube) Covering 10 points, a surprisingly tricky puzzle. rss

      Made as part of a monthly series of puzzles for the 2026 Year of Math.

    14. 🔗 badlogic/pi-mono v0.67.4 release

      New Features

      • --no-context-files (-nc) disables automatic AGENTS.md / CLAUDE.md discovery when you need a clean run without project context injection. See README.md#context-files.
      • loadProjectContextFiles() is now exported as a standalone utility for extensions and SDK-style integrations that need to inspect the same context-file resolution order used by the CLI. See README.md#context-files.
      • New after_provider_response extension hook lets extensions inspect provider HTTP status codes and headers immediately after response creation and before stream consumption. See docs/extensions.md.

      Added

      • Added --no-context-files (-nc) to disable AGENTS.md and CLAUDE.md context file discovery and loading (#3253)
      • Exported loadProjectContextFiles() as a standalone utility so extensions can discover project context files without instantiating a full DefaultResourceLoader (#3142)
      • Added after_provider_response extension hook so extensions can inspect provider HTTP status codes and headers after each provider response is received and before stream consumption begins (#3128)

      Changed

      • Added claude-opus-4-7 model for Anthropic.
      • Changed Anthropic prompt caching to add a cache_control breakpoint on the last tool definition, so tool schemas can be cached independently from transcript updates while preserving existing cache retention behavior (#3260)

      Fixed

      • Fixed markdown strikethrough parsing in interactive rendering and HTML export to require strict double-tilde delimiters (~~text~~) with non-whitespace boundaries.
      • Fixed shutdown handling to kill tracked detached bash tool child processes on exit signals, preventing orphaned background processes.
      • Fixed flaky edit-tool-no-full-redraw TUI tests by waiting for asynchronous preview and preflight error rendering instead of relying on fixed render ticks.
      • Fixed kimi-coding default model selection to use kimi-for-coding instead of kimi-k2-thinking (#3242)
      • Fixed ctrl+z on native Windows to avoid crashing interactive mode, disable the default suspend binding there, and show a status message when suspend is invoked manually (#3191)
      • Fixed find tool cancellation and responsiveness on broad searches by making .gitignore discovery and fd execution fully abort-aware and non-blocking (#3148)
      • Fixed grep broad-search stalls when context=0 by formatting match lines from ripgrep JSON output instead of doing synchronous per-match file reads (#3205)
    15. 🔗 @binaryninja@infosec.exchange Join us tomorrow, April 17th @ 4pm ET, for some live pwn! We'll be using mastodon

      Join us tomorrow, April 17th @ 4pm ET, for some live pwn! We'll be using Binary Ninja's shell coding compiler, patching binaries to make them easier to debug, analyzing data moving from globals to the stack to the heap, and finishing by popping shells live with pwntools: https://youtube.com/live/VcK4SoeYZiU

    16. 🔗 r/LocalLLaMA More reasons to go local: Claude is beginning to require identity verification, including an valid ID like passport or drivers license and a facial recognition scan. rss
    17. 🔗 r/LocalLLaMA Qwen3.6-35B-A3B released! rss

      Qwen3.6-35B-A3B released! | Meet Qwen3.6-35B-A3B:Now Open-Source!🚀🚀 A sparse MoE model, 35B total params, 3B active. Apache 2.0 license. - Agentic coding on par with models 10x its active size - Strong multimodal perception and reasoning ability - Multimodal thinking + non-thinking modes Efficient. Powerful. Versatile. Blog:https://qwen.ai/blog?id=qwen3.6-35b-a3b Qwen Studio:chat.qwen.ai HuggingFace:https://huggingface.co/Qwen/Qwen3.6-35B-A3B ModelScope:https://modelscope.cn/models/Qwen/Qwen3.6-35B-A3B submitted by /u/ResearchCrafty1804
      [link] [comments]
      ---|---

    18. 🔗 r/LocalLLaMA Released Qwen3.6-35B-A3B rss
    19. 🔗 r/york Fire crews called to rescue person stuck in tree in York rss

      Fire crews called to rescue person stuck in tree in York | submitted by /u/stankmanly
      [link] [comments]
      ---|---

    20. 🔗 r/york Beautiful bluebells by the City Walls rss

      Beautiful bluebells by the City Walls | I love this time of year 🥰 submitted by /u/RedPandaCommander24
      [link] [comments]
      ---|---

    21. 🔗 r/Yorkshire Yorkshire Water to pay out £2.35m over pollution incidents rss

      Yorkshire Water to pay out £2.35m over pollution incidents | submitted by /u/Kagedeah
      [link] [comments]
      ---|---

    22. 🔗 HazAT/glimpse v0.7.0 release

      Install:

      npm install glimpseui@0.7.0
      

      Pi agent package:

      pi install npm:glimpseui@0.7.0
      

      ✨ Features

      • --no-dock flag / noDock option — hide the dock icon and app switcher entry on macOS. The window still works normally (focus, keyboard input, etc.) but the app stays invisible in the dock. Useful for embedded/subprocess usage where no dock presence is desired.
    23. 🔗 r/wiesbaden Calisthenics Crew gesucht rss

      Hallo Wiesbaden,

      suche ne Gruppe von Leuten, die Bock haben, am Schlachthof zusammen zu trainieren. Hab schon die Bar-Lappen gefragt, aber die gibs wohl nich mehr. Hat wer Bock oder kennt Leute?

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

    24. 🔗 r/Harrogate So they're resurfacing Devonshire Place... rss

      That's the 'slip road' off Skipton Road to Claro Road. Which was as flat as a pool table last week when I drove along it. Meanwhile Crowberry Road is a cratered mess & it's probably not even the worst road surface in Harrogate.

      Any idea which numbskull on the highways dept delegates the waste of money? Cos it's got me baffled.

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

    25. 🔗 r/wiesbaden Require help for picking up a parcel rss

      Hi.

      I’m looking for some help from someone to pick up a DPD parcel from a paketstation in Wiesbaden and deliver to my friend’s address in Wiesbaden.

      They’re unfortunately not available during the week for picking it up.

      Requesting any assistance from anyone.

      I’m willing to pay for your time and help through Amazon gift cards or even PayPal.

      Willing to provide all proof of order, shipment details, contents and personal verification.

      Thanks in advance.

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

    26. 🔗 r/Yorkshire Are these a "proper" size or too big? rss

      Are these a "proper" size or too big? | Someone tried to tell me these were too large and taking up too much room on the plate. Personally, I don’t think there’s such a thing as a pudding that’s "too big." Is it just me, or should the pudding always be the main event of the roast? submitted by /u/Happy-Fox11
      [link] [comments]
      ---|---

    27. 🔗 HexRaysSA/plugin-repository commits sync repo: +1 plugin, +6 releases rss
      sync repo: +1 plugin, +6 releases
      
      ## New plugins
      - [ZoomAllViews](https://github.com/Dump-GUY/ZoomAllViews) (1.0.1)
      
      ## New releases
      - [HappyIDA](https://github.com/HappyIDA/HappyIDA): 1.0.6
      - [augur](https://github.com/0xdea/augur): 0.9.0
      - [haruspex](https://github.com/0xdea/haruspex): 0.9.0
      - [idalib-rust-bindings](https://github.com/idalib-rs/idalib): 0.9.0
      - [rhabdomancer](https://github.com/0xdea/rhabdomancer): 0.9.0
      
    28. 🔗 Rust Blog Announcing Rust 1.95.0 rss

      The Rust team is happy to announce a new version of Rust, 1.95.0. Rust is a programming language empowering everyone to build reliable and efficient software.

      If you have a previous version of Rust installed via rustup, you can get 1.95.0 with:

      $ rustup update stable
      

      If you don't have it already, you can get rustup from the appropriate page on our website, and check out the detailed release notes for 1.95.0.

      If you'd like to help us out by testing future releases, you might consider updating locally to use the beta channel (rustup default beta) or the nightly channel (rustup default nightly). Please report any bugs you might come across!

      What's in 1.95.0 stable

      cfg_select!

      Rust 1.95 introduces a cfg_select! macro that acts roughly similar to a compile-time match on cfgs. This fulfills the same purpose as the popular cfg-if crate, although with a different syntax. cfg_select! expands to the right-hand side of the first arm whose configuration predicate evaluates to true. Some examples:

      cfg_select! {
          unix => {
              fn foo() { /* unix specific functionality */ }
          }
          target_pointer_width = "32" => {
              fn foo() { /* non-unix, 32-bit functionality */ }
          }
          _ => {
              fn foo() { /* fallback implementation */ }
          }
      }
      
      let is_windows_str = cfg_select! {
          windows => "windows",
          _ => "not windows",
      };
      

      if-let guards in matches

      Rust 1.88 stabilized let chains. Rust 1.95 brings that capability into match expressions, allowing for conditionals based on pattern matching.

      match value {
          Some(x) if let Ok(y) = compute(x) => {
              // Both `x` and `y` are available here
              println!("{}, {}", x, y);
          }
          _ => {}
      }
      

      Note that the compiler will not currently consider the patterns matched in if let guards as part of the exhaustiveness evaluation of the overall match, just like if guards.

      Stabilized APIs

      These previously stable APIs are now stable in const contexts:

      Destabilized JSON target specs

      Rust 1.95 removes support on stable for passing a custom target specification to rustc. This should not affect any Rust users using a fully stable toolchain, as building the standard library (including just core) already required using nightly-only features.

      We're also gathering use cases for custom targets on the tracking issue as we consider whether some form of this feature should eventually be stabilized.

      Other changes

      Check out everything that changed in Rust, Cargo, and Clippy.

      Contributors to 1.95.0

      Many people came together to create Rust 1.95.0. We couldn't have done it without all of you. Thanks!

    29. 🔗 Console.dev newsletter Little Snitch for Linux rss

      Description: Outbound firewall.

      What we like: Visualize (and block) outbound connections from any process or application. Tracks data volumes and history. Create your own blocklists and use community provided lists for proactive rule updates. Configurable. Open source. There’s also a macOS version.

      What we dislike: Use of eBPF means it’s designed for privacy rather than completely strict security.

    30. 🔗 Console.dev newsletter FuseJS rss

      Description: Fuzzy search library.

      What we like: Supports fuzzy, token, and logical search with extension operators for exact, prefix, suffix, etc. Zero dependencies so it works in the browser, server (Node, Deno), etc. Search can be distributed across web workers for large datasets. Open source or use their cloud service.

      What we dislike: Web workers are still in beta.