davideisinger.com

commit a8d425b69d9a8f8de1fcbb54a583d8903259e03c
parent 4bed9a807ba5b52cc0da8a7318d513564872a4be
Author: David Eisinger <[email protected]>
Date:   Tue,  4 Aug 2026 01:34:01 -0400

Finalize August 2026 content

Diffstat:
M
content/journal/dispatch-42-august-2026/index.md
 | 
154
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++---------------------
A
static/archive/daringfireball-net-qsrkrz.txt
 | 
102
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
A
static/archive/gist-github-com-4bt2rw.txt
 | 
1716
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
A
static/archive/ludic-mataroa-blog-ss5swh.txt
 | 
641
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
A
static/archive/michaelharley-net-wa2rlv.txt
 | 
351
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
A
static/archive/simonwillison-net-zmoxib.txt
 | 
394
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
A
static/archive/sixcolors-com-vzmwje.txt
 | 
408
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
A
static/archive/webassembly-org-7kas9l.txt
 | 
65
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
A
static/archive/www-manton-org-f8ohhe.txt
 | 
70
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

9 files changed, 3860 insertions(+), 41 deletions(-)
diff --git a/content/journal/dispatch-42-august-2026/index.md b/content/journal/dispatch-42-august-2026/index.md
@@ -1,14 +1,10 @@
 ---
 title: "Dispatch #42 (August 2026)"
-date: 2026-07-27T00:40:18-04:00
+date: 2026-08-04T01:26:36-04:00
 draft: false
 tags:
 - dispatch
 references:
-- title: "Home is where my stuff is | Ruslan Osipov"
-  url: https://rosipov.com/blog/home-is-where-my-stuff-is/
-  date: 2026-01-06T05:32:49Z
-  file: rosipov-com-qbdcgh.txt
 - title: "Tool Box in a Milk Crate and Bonus — Everyday Commentary"
   url: https://www.everydaycommentary.com/www.everydaycommentary.com/2026/6/3/tool-box-in-a-milk-crate-and-bonus
   date: 2026-08-01T05:51:54Z
@@ -17,19 +13,49 @@ references:
   url: https://tracydurnell.com/2026/07/03/weeknotes-june-27-july-3-2026/
   date: 2026-08-01T06:01:03Z
   file: tracydurnell-com-0ckguh.txt
-
+- title: "Home is where my stuff is | Ruslan Osipov"
+  url: https://rosipov.com/blog/home-is-where-my-stuff-is/
+  date: 2026-01-06T05:32:49Z
+  file: rosipov-com-qbdcgh.txt
+- title: "WebAssembly"
+  url: https://webassembly.org/
+  date: 2026-08-04T04:43:38Z
+  file: webassembly-org-7kas9l.txt
+- title: "OpenAI’s accidental cyberattack against Hugging Face is science fiction that happened"
+  url: https://simonwillison.net/2026/Jul/22/openai-cyberattack/#atom-everything
+  date: 2026-08-04T05:23:00Z
+  file: simonwillison-net-zmoxib.txt
+- title: "AI Mania Is Eviscerating Global Decision-Making — Ludicity"
+  url: https://ludic.mataroa.blog/blog/ai-mania-is-eviscerating-global-decision-making/
+  date: 2026-08-04T05:23:05Z
+  file: ludic-mataroa-blog-ss5swh.txt
+- title: "Daring Fireball: 'AI Mania Is Eviscerating Global Decision-Making'"
+  url: https://daringfireball.net/linked/2026/07/25/ai-mania-nikhil-suresh
+  date: 2026-08-04T05:23:06Z
+  file: daringfireball-net-qsrkrz.txt
+- title: "llm-wiki · GitHub"
+  url: https://gist.github.com/karpathy/442a6bf555914893e9891c11519de94f
+  date: 2026-08-04T05:23:12Z
+  file: gist-github-com-4bt2rw.txt
+- title: "Review: Xteink X3 is the little e-reader the world’s not quite ready for – Six Colors"
+  url: https://sixcolors.com/post/2026/07/review-xteink-x3-is-the-little-e-reader-the-worlds-not-quite-ready-for/
+  date: 2026-08-04T05:23:20Z
+  file: sixcolors-com-vzmwje.txt
+- title: "Manton Reece"
+  url: https://www.manton.org/2026/07/22/dan-moren-reviews-the-xteink.html
+  date: 2026-08-04T05:23:22Z
+  file: www-manton-org-f8ohhe.txt
+- title: "I own my books | Michael Harley"
+  url: https://michaelharley.net/posts/2026/07/16/i-own-my-books/
+  date: 2026-08-04T05:23:29Z
+  file: michaelharley-net-wa2rlv.txt
 ---
 
-Some thoughts here...
+August 2026 marks two big personal anniversaries: 25 years in Durham and 10 years in this house. Who would've thought? Certainly not Duke freshman Dave. Couldn't be happier to be right here right now, though I might have made some different decisions had I known I'd be raising two small children in these increasingly cramped quarters. But that's not how things work, is it?
 
 <!--more-->
 
-- 25 years in Durham
-- 10 years in this house
-- Lake for July 4th
-  - Cousins in raft
-- Mom + dad visit
-- Eno
+In July, we went down to Lake Norman for the Fourth. The highlight was hooking an inflatable raft up to one of the kayaks and towing the kids and their cousin Sully around. Otherwise, laid pretty low: museums, pools, farmers' markets, Eno River, just classic summertime shit. Work was a bit stressful (tricky client situation) but I think we're mostly through the woods there. My folks came down at the end of the month to celebrate my mom's birthday.
 
 {{<dither IMG_0482.jpeg "782x600">}}A lazy lake flotilla.{{</dither>}}
 {{<dither IMG_0509.jpeg "782x600">}}Two kids making faces on the stairs.{{</dither>}}
@@ -37,48 +63,94 @@ Some thoughts here...
 {{<dither IMG_0533.jpeg "782x600">}}Matching faces at the playground.{{</dither>}}
 {{<dither IMG_0641.jpeg "782x600">}}Family lounge time over coffee, juice, and snacks.{{</dither>}}
 
-- New track
+Here's a new track, called "Asdreno Dreams" (title by my coworker's young son, who makes fictitious track listings for fun):
 
 <audio controls src="/journal/dispatch-42-august-2026/Asdreno Dreams.mp3"></audio>
 
-- Basement improvements
-  - "Every Tool's a Hammer"
-    - https://www.simonandschuster.net/books/Every-Tools-a-Hammer/Adam-Savage/9781982113483
-  - EDC
-    - https://www.everydaycommentary.com/www.everydaycommentary.com/2026/6/3/tool-box-in-a-milk-crate-and-bonus
-  - "Decluttering at the Speed of Life"
-    - https://bookshop.org/p/books/decluttering-at-the-speed-of-life-winning-your-never-ending-battle-with-stuff-dana-k-white/cde38b41d0c6ab3a?ean=9780718083588&bkshp-astro=t
-    - https://tracydurnell.com/2026/07/03/weeknotes-june-27-july-3-2026/
-  - Post about stuff + identity
-    - https://rosipov.com/blog/home-is-where-my-stuff-is/
+Apologies to Claire for having to listen to this on loop for two months while I figured out those bass and lead lines. Thanks for letting me be me.
+
+### Decluttering
+
+I finished Adam Savage's [_Every Tool's a Hammer_][1], most of which is a love letter to tools and workshops. That plus [a post I read on a knife blog I follow][2] have me itching to overhaul my basement space. The problem is that there is so much crap down here. Just an _unbeleivable_ amount of crap.
+
+[1]: https://www.simonandschuster.net/books/Every-Tools-a-Hammer/Adam-Savage/9781982113483
+[2]: https://www.everydaycommentary.com/www.everydaycommentary.com/2026/6/3/tool-box-in-a-milk-crate-and-bonus
+
+I started a new book, [_Decluttering at the Speed of Life_][3] ([via][4]), which isn't exactly groundbreaking stuff, but has given me permission to approach a cluttered space with a trash bag and a donation box and start getting stuff out. When I feel guilty about throwing something away, I just have to tell myself: David, it's already trash. That pile of paint cans that was here when you moved in, and you haven't looked at since? _Already trash._ That it's in your house instead of the dump does not change its trash nature. Get it out.
+
+[3]: https://bookshop.org/p/books/decluttering-at-the-speed-of-life-winning-your-never-ending-battle-with-stuff-dana-k-white/cde38b41d0c6ab3a?ean=9780718083588&bkshp-astro=t
+[4]: https://tracydurnell.com/2026/07/03/weeknotes-june-27-july-3-2026/
+
+I still think about [this post I read some months ago][5]:
 
 > "This is why decluttering is so hard. It’s not really about tidiness. It’s about deciding which past selves get to stay."
 
-- XTC tool
-  - https://xtctool.com/
+[5]: https://rosipov.com/blog/home-is-where-my-stuff-is/
+
+Sure I haven't ridden my fancy road bike since the kids were born, but it's so tempting to think that could still be a part of my life if I just prioritized things a bit differently (e.g. became a 5AM guy instead of a 2AM guy). But, let's face our current (and wonderful!) reality, sell the bike, and if I decide I want to get back into long rides in 2040, buy something new and goddamn incredible.
+
+### Eteink XTC Converter
+
+[Last month][6] I mentioned my [Xteink X3][7] pocket e-reader and how it uses a custom e-book format ("XTC"). I wasn't happy with the results generated by my Calibre plugin when I converted the decluttering book. I found [this web tool][8] which creates much nicer files (margins, typography, etc.), but I didn't really want a random, unattributed website as part of my reading workflow.
+
+[6]: https://davideisinger.com/journal/dispatch-41-july-2026/
+[7]: https://www.xteink.com/products/xteink-x3
+[8]: https://xtctool.com/
+
+I pointed Codex at the URL and asked if it could perhaps find the source online. It could not, but it did reveal that the entire conversion process takes place in the browser using [WebAssembly][9]. I had it download and analyze the source and then build a command-line version. Then I used [Bun][10] to compile a standalone executable and set it up to read my preferred settings from a config file. Now I can just `xtcconv /path/to/book.epub`.
+
+[9]: https://webassembly.org/
+[10]: https://bun.sh/
+
+I can't in good conscience open source this project, since it's just stolen code and vibes. But if you're interested, slap these three paragraphs into your coding agent and I bet you'll get good results. What a time to be a nerd.
 
 ### This Month
 
-* Adventure: Napa, Rehoboth
-* Project:
-* Skill:
+* Adventure: Long weekend in Napa with some of Claire's college friends then our annual trip to Rehoboth Beach
+* Project: decluttering, maybe start thinking about a better setup for my woodworking tools + 3D printer
+* Skill: I've run the same half-marathon in mid-October for the last four years; gotta decide if I'm going to go for five, and if so, get serious about training
 
 ### Reading & Listening
 
-* Fiction: [_Title_][1], Author
-* Non-fiction: [_Title_][2], Author
-* Music: [_A-Meow-Zing Music_][3], Gabby's Dollhouse
+* Fiction: [_The Burning God_][11], R. F. Kuang -- I am ready for this series to be over; the characters aren't likeable and nothing good ever happens. I'm holding out hope for a strong ending. Then back to CARL.
+* Non-fiction: [_Decluttering at the Speed of Life_][3], Dana K. White
+* Music:
+  * [_A-Meow-Zing Music_][12], Gabby's Dollhouse -- Nev loves this show, and now Claire and I unironically love the songs ([tell me this doesn't slap][13])
+  * [_Yoshimi Battles The Pink Robots_][14], Flaming Lips -- I've always loved this album (_Fight Test_ is an all-time favorite), but it's only recently occurred to me that it's also a synth masterpiece
+
+[11]: https://bookshop.org/p/books/the-burning-god-r-f-kuang/25ad1ff12a8a9b5a?ean=9780062662644&bkshp-astro=t
+[12]: https://rsdmrkt.com/item/68dfc0d24ae7899c7d51fb6a
+[13]: https://www.youtube.com/watch?v=c3Nofx0skJU
+[14]: https://www.tonevendor.com/products/the-flaming-lips-yoshimi-battles-the-pink-robots-lp-album-re-rm?shop_consented_scopes=email%3Averified+openid+pay%3Asession_token+profile+shop%3Aaccount_uuid&shop_sign_in=true&variant=49126991560986
 
-[1]: https://bookshop.org/
-[2]: https://bookshop.org/
-[3]: https://rsdmrkt.com/item/68dfc0d24ae7899c7d51fb6a
 
 ### Links
 
-* [Title][4]
-* [Title][5]
-* [Title][6]
+* [OpenAI’s accidental cyberattack against Hugging Face is science fiction that happened][15]
+
+  > OpenAI’s accidental cyberattack against Hugging Face is science fiction that happened This story is wild. The short version: OpenAI were running a cybersecurity test against an unreleased model, with the model’s guardrail features turned off. Rather than solve the test, the model broke its way out of OpenAI’s sandbox, then found exploits to break in to Hugging Face, all so it could cheat on the test by stealing the answers.
+
+* [AI Mania Is Eviscerating Global Decision-Making — Ludicity][16] ([via][17])
+
+  > I strongly believe there are entire companies right now under heavy AI psychosis and it’s impossible to have rational conversations with them about it. I can’t name any specific people because they include personal friends I deeply respect, but I worry about how this plays out.
+
+* [llm-wiki · GitHub][18]
+
+  > A pattern for building personal knowledge bases using LLMs. This is an idea file, it is designed to be copy pasted to your own LLM Agent (e.g. OpenAI Codex, Claude Code, OpenCode / Pi, or etc.). Its goal is to communicate the high level idea, but your agent will build out the specifics in collaboration with you.
+
+* [Review: Xteink X3 is the little e-reader the world’s not quite ready for – Six Colors][19] ([via][20])
+
+  > Not unlike in music, the problem is that in order for someone to actually to consume your music or books, they must possess the means to unlock it.
+
+* [I own my books | Michael Harley][21] ([via][22])
+
+  > So I backup my books to an open standard, ePUB, with the DRM stripped off. If eBooks.com folds tomorrow, or Kobo decides my account is a problem, or I want to read on hardware nobody has invented yet, my library still works. I don't care what their fine print says. I bought this book. It's my book. I'll read it where I like, TYVM.
 
-[4]: https://example.com/
-[5]: https://example.com/
-[6]: https://example.com/
+[15]: https://simonwillison.net/2026/Jul/22/openai-cyberattack/#atom-everything
+[16]: https://ludic.mataroa.blog/blog/ai-mania-is-eviscerating-global-decision-making/
+[17]: https://daringfireball.net/linked/2026/07/25/ai-mania-nikhil-suresh
+[18]: https://gist.github.com/karpathy/442a6bf555914893e9891c11519de94f
+[19]: https://sixcolors.com/post/2026/07/review-xteink-x3-is-the-little-e-reader-the-worlds-not-quite-ready-for/
+[20]: https://www.manton.org/2026/07/22/dan-moren-reviews-the-xteink.html
+[21]: https://michaelharley.net/posts/2026/07/16/i-own-my-books/
+[22]: https://bubbles.town/entry/44749901
diff --git a/static/archive/daringfireball-net-qsrkrz.txt b/static/archive/daringfireball-net-qsrkrz.txt
@@ -0,0 +1,102 @@
+[zoom-spin-]
+[spacer]
+●
+●  ●
+[1]Daring Fireball
+
+By John Gruber
+
+  • [2]Archive
+  • 
+  • [3]The Talk Show
+  • [4]Dithering
+  • [5]Projects
+  • [6]Contact
+  • [7]Colophon
+  • [8]Feeds / Social
+  • [9]Sponsorship
+
+[10] WorkOS
+
+[11]WorkOS — MCP vs. REST: the right way to connect agents to your API.
+
+[12]‘AI Mania Is Eviscerating Global Decision-Making’
+
+    Fascinating essay by Nikhil Suresh:
+
+        On a trip overseas, I had the privilege of a meeting with one of the
+        Fortune 500 executives mentioned at the beginning of the post, who will
+        remain anonymous so that they are not executed by firing squad by their
+        board. As we were chatting, it became clear that they were very
+        switched-on and technically competent, and they also happened to be at
+        a company that had committed to the usual battery of exorbitant claims
+        about their recent innovations — we’ve 100×’d our productivity, AI is
+        the future of everything, I am but a vessel for OpenAI to make love to
+        my wife. You know, normal things. But since I had them there without
+        any microphones around, I asked why this was being repeated without
+        opposition. Was it just sales fluff?
+
+        The answer was a lot more interesting. It was partially ridiculous
+        sales material being delivered to an easily excitable audience, but
+        this was not the dominant factor constraining honesty. Executives at
+        their customers were saying absurd things about achieving 100×
+        productivity, and this meant that if any executive at the vendor said
+        that these gains were not plausible, it would undermine the credibility
+        of the customer’s executive, be perceived as an attack (or heresy), and
+        possibly result in an enterprise contract cancellation. And getting
+        enterprise contracts cancelled because you wanted to opine on something
+        that doesn’t really matter to your organisation’s mission is a great
+        way to get fired.
+
+    The whole essay is very much worth reading, and might make you feel saner
+    for harboring your own doubts regarding just how much has been changed in
+    the world by generative AI. The gist of his argument is that the entire
+    corporate world — not merely the computer/tech industry — is caught up in
+    an AI mania that brooks no dissent. It’s a religious fervor and heretics
+    are excommunicated. But the dissenters, who feel they must remain silent,
+    are largely correct.
+
+    One way I’ve been thinking about AI mania is this: Computers have
+    profoundly changed the world. There can be no dispute about that. Computers
+    continue to improve in capability as networking effects grow and especially
+    as Moore’s Law makes them faster and more capable at a pace unlike any
+    other previous technical revolution. But most people are incapable of
+    understanding how computers really work, and thus personally aren’t able to
+    do much with them. Computers, for most people, are communication tools, not
+    creative tools. Generative AI changes that. People with no computer
+    aptitude are able to create things or discover things via ChatGPT and
+    Claude that were simply beyond their ken heretofore. Per Clarke’s third
+    law, “Any sufficiently advanced technology is indistinguishable from
+    magic”. Generative AI feels a bit magical to all of us, even those of us
+    with mid-to-high levels of understanding how computers work and how to make
+    them work. But it feels like the first time ever that computers have been
+    tools for their own creation for a lot of rather dimwitted but confident
+    corporate manager/executive types. This moment feels like the Big Bang to
+    them. The religiosity of this is such that there is no way to convince them
+    that AI, as it stands today, is impressive and useful and innovative, yes,
+    but several orders of magnitude less so than they’re imagining that it is.
+    No way to convince them, that is, until the bubble bursts.
+
+    ★ Saturday, 25 July 2026
+
+[13][                    ] [14][Search]
+[15]Display Preferences
+
+Copyright © 2002–2026 The Daring Fireball Company LLC.
+
+
+References:
+
+[1] https://daringfireball.net/
+[2] https://daringfireball.net/archive/
+[3] https://daringfireball.net/thetalkshow/
+[4] https://dithering.fm/
+[5] https://daringfireball.net/projects/
+[6] https://daringfireball.net/contact/
+[7] https://daringfireball.net/colophon/
+[8] https://daringfireball.net/feeds/
+[9] https://daringfireball.net/feeds/sponsors/
+[10] https://workos.com/blog/management-mcp-server?utm_source=daringfireball&utm_medium=newsletter&utm_campaign=q32026
+[11] https://workos.com/blog/management-mcp-server?utm_source=daringfireball&utm_medium=newsletter&utm_campaign=q32026
+[12] https://ludic.mataroa.blog/blog/ai-mania-is-eviscerating-global-decision-making/
+[15] https://daringfireball.net/preferences/
diff --git a/static/archive/gist-github-com-4bt2rw.txt b/static/archive/gist-github-com-4bt2rw.txt
@@ -0,0 +1,1716 @@
+[1]Skip to content 
+[2]
+[3](Toggle navigation)
+Search Gists
+[4][                    ]
+[5] Search Gists
+[6]All gists [7]Back to GitHub [8] Sign in [9] Sign up
+[10]
+[11] Sign in [12] Sign up
+You signed in with another tab or window. [13]Reload to refresh your session. 
+You signed out in another tab or window. [14]Reload to refresh your session. 
+You switched accounts on another tab or window. [15]Reload to refresh your
+session. [16] Dismiss alert
+[17](Dismiss this message)
+{{ message }}
+
+Instantly share code, notes, and snippets.
+
+[18]@karpathy
+
+[19]karpathy/[20]llm-wiki.md
+
+Created April 4, 2026 16:25
+
+[21] Show Gist options
+
+  • [22] Download ZIP
+
+  • [23] Star 5,000+ (5,000+) You must be signed in to star a gist
+  • [24] Fork 5,000+ (5,000+) You must be signed in to fork a gist
+
+  • [25] Embed
+
+    Select an option
+
+    [26](Close)
+      □ [27] Embed Embed this gist in your website.
+      □ [28] Share Copy sharable link for this gist.
+      □ [29] Clone via HTTPS Clone using the web URL.
+
+    No results found
+
+    [30]Learn more about clone URLs
+    Clone this repository at &lt;script src=&quot;https://gist.github.com/
+    karpathy/442a6bf555914893e9891c11519de94f.js&quot;&gt;&lt;/script&gt;
+    [31][<script src="https:/]
+  • [32] Save karpathy/442a6bf555914893e9891c11519de94f to your computer and
+    use it in GitHub Desktop.
+
+[33] Code [34] Revisions 1 [35] Stars 5,000+ [36] Forks 5,000+
+[37] Embed
+
+Select an option
+
+[38](Close)
+
+  • [39] Embed Embed this gist in your website.
+  • [40] Share Copy sharable link for this gist.
+  • [41] Clone via HTTPS Clone using the web URL.
+
+No results found
+
+[42]Learn more about clone URLs
+Clone this repository at &lt;script src=&quot;https://gist.github.com/karpathy/
+442a6bf555914893e9891c11519de94f.js&quot;&gt;&lt;/script&gt;
+[43][<script src="https:/]
+[44] Save karpathy/442a6bf555914893e9891c11519de94f to your computer and use it
+in GitHub Desktop.
+[45]Download ZIP
+llm-wiki
+[46] Raw
+[47] llm-wiki.md
+
+LLM Wiki
+
+[48] 
+
+A pattern for building personal knowledge bases using LLMs.
+
+This is an idea file, it is designed to be copy pasted to your own LLM Agent
+(e.g. OpenAI Codex, Claude Code, OpenCode / Pi, or etc.). Its goal is to
+communicate the high level idea, but your agent will build out the specifics in
+collaboration with you.
+
+The core idea
+
+[49] 
+
+Most people's experience with LLMs and documents looks like RAG: you upload a
+collection of files, the LLM retrieves relevant chunks at query time, and
+generates an answer. This works, but the LLM is rediscovering knowledge from
+scratch on every question. There's no accumulation. Ask a subtle question that
+requires synthesizing five documents, and the LLM has to find and piece
+together the relevant fragments every time. Nothing is built up. NotebookLM,
+ChatGPT file uploads, and most RAG systems work this way.
+
+The idea here is different. Instead of just retrieving from raw documents at
+query time, the LLM incrementally builds and maintains a persistent wiki — a
+structured, interlinked collection of markdown files that sits between you and
+the raw sources. When you add a new source, the LLM doesn't just index it for
+later retrieval. It reads it, extracts the key information, and integrates it
+into the existing wiki — updating entity pages, revising topic summaries,
+noting where new data contradicts old claims, strengthening or challenging the
+evolving synthesis. The knowledge is compiled once and then kept current, not
+re-derived on every query.
+
+This is the key difference: the wiki is a persistent, compounding artifact. The
+cross-references are already there. The contradictions have already been
+flagged. The synthesis already reflects everything you've read. The wiki keeps
+getting richer with every source you add and every question you ask.
+
+You never (or rarely) write the wiki yourself — the LLM writes and maintains
+all of it. You're in charge of sourcing, exploration, and asking the right
+questions. The LLM does all the grunt work — the summarizing,
+cross-referencing, filing, and bookkeeping that makes a knowledge base actually
+useful over time. In practice, I have the LLM agent open on one side and
+Obsidian open on the other. The LLM makes edits based on our conversation, and
+I browse the results in real time — following links, checking the graph view,
+reading the updated pages. Obsidian is the IDE; the LLM is the programmer; the
+wiki is the codebase.
+
+This can apply to a lot of different contexts. A few examples:
+
+  • Personal: tracking your own goals, health, psychology, self-improvement —
+    filing journal entries, articles, podcast notes, and building up a
+    structured picture of yourself over time.
+  • Research: going deep on a topic over weeks or months — reading papers,
+    articles, reports, and incrementally building a comprehensive wiki with an
+    evolving thesis.
+  • Reading a book: filing each chapter as you go, building out pages for
+    characters, themes, plot threads, and how they connect. By the end you have
+    a rich companion wiki. Think of fan wikis like [50]Tolkien Gateway —
+    thousands of interlinked pages covering characters, places, events,
+    languages, built by a community of volunteers over years. You could build
+    something like that personally as you read, with the LLM doing all the
+    cross-referencing and maintenance.
+  • Business/team: an internal wiki maintained by LLMs, fed by Slack threads,
+    meeting transcripts, project documents, customer calls. Possibly with
+    humans in the loop reviewing updates. The wiki stays current because the
+    LLM does the maintenance that no one on the team wants to do.
+  • Competitive analysis, due diligence, trip planning, course notes, hobby
+    deep-dives — anything where you're accumulating knowledge over time and
+    want it organized rather than scattered.
+
+Architecture
+
+[51] 
+
+There are three layers:
+
+Raw sources — your curated collection of source documents. Articles, papers,
+images, data files. These are immutable — the LLM reads from them but never
+modifies them. This is your source of truth.
+
+The wiki — a directory of LLM-generated markdown files. Summaries, entity
+pages, concept pages, comparisons, an overview, a synthesis. The LLM owns this
+layer entirely. It creates pages, updates them when new sources arrive,
+maintains cross-references, and keeps everything consistent. You read it; the
+LLM writes it.
+
+The schema — a document (e.g. CLAUDE.md for Claude Code or AGENTS.md for Codex)
+that tells the LLM how the wiki is structured, what the conventions are, and
+what workflows to follow when ingesting sources, answering questions, or
+maintaining the wiki. This is the key configuration file — it's what makes the
+LLM a disciplined wiki maintainer rather than a generic chatbot. You and the
+LLM co-evolve this over time as you figure out what works for your domain.
+
+Operations
+
+[52] 
+
+Ingest. You drop a new source into the raw collection and tell the LLM to
+process it. An example flow: the LLM reads the source, discusses key takeaways
+with you, writes a summary page in the wiki, updates the index, updates
+relevant entity and concept pages across the wiki, and appends an entry to the
+log. A single source might touch 10-15 wiki pages. Personally I prefer to
+ingest sources one at a time and stay involved — I read the summaries, check
+the updates, and guide the LLM on what to emphasize. But you could also
+batch-ingest many sources at once with less supervision. It's up to you to
+develop the workflow that fits your style and document it in the schema for
+future sessions.
+
+Query. You ask questions against the wiki. The LLM searches for relevant pages,
+reads them, and synthesizes an answer with citations. Answers can take
+different forms depending on the question — a markdown page, a comparison
+table, a slide deck (Marp), a chart (matplotlib), a canvas. The important
+insight: good answers can be filed back into the wiki as new pages. A
+comparison you asked for, an analysis, a connection you discovered — these are
+valuable and shouldn't disappear into chat history. This way your explorations
+compound in the knowledge base just like ingested sources do.
+
+Lint. Periodically, ask the LLM to health-check the wiki. Look for:
+contradictions between pages, stale claims that newer sources have superseded,
+orphan pages with no inbound links, important concepts mentioned but lacking
+their own page, missing cross-references, data gaps that could be filled with a
+web search. The LLM is good at suggesting new questions to investigate and new
+sources to look for. This keeps the wiki healthy as it grows.
+
+Indexing and logging
+
+[53] 
+
+Two special files help the LLM (and you) navigate the wiki as it grows. They
+serve different purposes:
+
+index.md is content-oriented. It's a catalog of everything in the wiki — each
+page listed with a link, a one-line summary, and optionally metadata like date
+or source count. Organized by category (entities, concepts, sources, etc.). The
+LLM updates it on every ingest. When answering a query, the LLM reads the index
+first to find relevant pages, then drills into them. This works surprisingly
+well at moderate scale (~100 sources, ~hundreds of pages) and avoids the need
+for embedding-based RAG infrastructure.
+
+log.md is chronological. It's an append-only record of what happened and when —
+ingests, queries, lint passes. A useful tip: if each entry starts with a
+consistent prefix (e.g. ## [2026-04-02] ingest | Article Title), the log
+becomes parseable with simple unix tools — grep "^## \[" log.md | tail -5 gives
+you the last 5 entries. The log gives you a timeline of the wiki's evolution
+and helps the LLM understand what's been done recently.
+
+Optional: CLI tools
+
+[54] 
+
+At some point you may want to build small tools that help the LLM operate on
+the wiki more efficiently. A search engine over the wiki pages is the most
+obvious one — at small scale the index file is enough, but as the wiki grows
+you want proper search. [55]qmd is a good option: it's a local search engine
+for markdown files with hybrid BM25/vector search and LLM re-ranking, all
+on-device. It has both a CLI (so the LLM can shell out to it) and an MCP server
+(so the LLM can use it as a native tool). You could also build something
+simpler yourself — the LLM can help you vibe-code a naive search script as the
+need arises.
+
+Tips and tricks
+
+[56] 
+
+  • Obsidian Web Clipper is a browser extension that converts web articles to
+    markdown. Very useful for quickly getting sources into your raw collection.
+  • Download images locally. In Obsidian Settings → Files and links, set
+    "Attachment folder path" to a fixed directory (e.g. raw/assets/). Then in
+    Settings → Hotkeys, search for "Download" to find "Download attachments for
+    current file" and bind it to a hotkey (e.g. Ctrl+Shift+D). After clipping
+    an article, hit the hotkey and all images get downloaded to local disk.
+    This is optional but useful — it lets the LLM view and reference images
+    directly instead of relying on URLs that may break. Note that LLMs can't
+    natively read markdown with inline images in one pass — the workaround is
+    to have the LLM read the text first, then view some or all of the
+    referenced images separately to gain additional context. It's a bit clunky
+    but works well enough.
+  • Obsidian's graph view is the best way to see the shape of your wiki —
+    what's connected to what, which pages are hubs, which are orphans.
+  • Marp is a markdown-based slide deck format. Obsidian has a plugin for it.
+    Useful for generating presentations directly from wiki content.
+  • Dataview is an Obsidian plugin that runs queries over page frontmatter. If
+    your LLM adds YAML frontmatter to wiki pages (tags, dates, source counts),
+    Dataview can generate dynamic tables and lists.
+  • The wiki is just a git repo of markdown files. You get version history,
+    branching, and collaboration for free.
+
+Why this works
+
+[57] 
+
+The tedious part of maintaining a knowledge base is not the reading or the
+thinking — it's the bookkeeping. Updating cross-references, keeping summaries
+current, noting when new data contradicts old claims, maintaining consistency
+across dozens of pages. Humans abandon wikis because the maintenance burden
+grows faster than the value. LLMs don't get bored, don't forget to update a
+cross-reference, and can touch 15 files in one pass. The wiki stays maintained
+because the cost of maintenance is near zero.
+
+The human's job is to curate sources, direct the analysis, ask good questions,
+and think about what it all means. The LLM's job is everything else.
+
+The idea is related in spirit to Vannevar Bush's Memex (1945) — a personal,
+curated knowledge store with associative trails between documents. Bush's
+vision was closer to this than to what the web became: private, actively
+curated, with the connections between documents as valuable as the documents
+themselves. The part he couldn't solve was who does the maintenance. The LLM
+handles that.
+
+Note
+
+[58] 
+
+This document is intentionally abstract. It describes the idea, not a specific
+implementation. The exact directory structure, the schema conventions, the page
+formats, the tooling — all of that will depend on your domain, your
+preferences, and your LLM of choice. Everything mentioned above is optional and
+modular — pick what's useful, ignore what isn't. For example: your sources
+might be text-only, so you don't need image handling at all. Your wiki might be
+small enough that the index file is all you need, no search engine required.
+You might not care about slide decks and just want markdown pages. You might
+want a completely different set of output formats. The right way to use this is
+to share it with your LLM agent and work together to instantiate a version that
+fits your needs. The document's only job is to communicate the pattern. Your
+LLM can figure out the rest.
+
+[62]Load earlier comments...
+[63]@frankchu91
+
+[64]frankchu91 commented [65]Jul 18, 2026 •
+edited
+Loading
+
+Uh oh!
+
+There was an error while loading. [66]Please reload this page.
+
+Copy link
+Copy Markdown
+
+MindBase — an open-source implementation of this post (MCP server, MIT)
+
+Built this over the past few months: [67]https://github.com/frankchu91/mindbase
+
+[68]MindBase web UI — the LLM-maintained context.md of a research project
+
+Mapping to the three layers as specced:
+
+  • Raw sources → sources/ is append-only, enforced by tooling rather
+    than convention: each operation runs as a sub-agent with a strict tool
+    allowlist — the builder agent has no file-write tool at all, only an
+    atomic-write MCP call that snapshots context.md before replacing it.
+  • The wiki → LLM-maintained markdown with [[wikilinks]], plus a typed
+    link index (sqlite, derived state — markdown stays the source of truth):
+    edges carry contradicts/supersedes/mentions, so lint can proactively
+    surface "this new source contradicts what you wrote in March."
+  • The schema → a per-project README.md the LLM re-reads at every
+    operation; user-editable, co-evolves with the wiki.
+
+All three operations are in — a day looks like:
+
+/mb:contribute paper.pdf → sub-agent reads, discusses 3 takeaways, waits
+for approval, then updates 5-15 wiki pages
+/mb:ask "my stance on X?" → cited answer from the already-synthesized wiki
+/mb:lint → contradictions · orphans · stale claims · gaps
+
+Works in any MCP client (Claude Code / Cursor / Windsurf / Cline):
+npx -y mindbase-mcp. All local markdown — you can open the data dir
+straight in Obsidian.
+
+One finding for the drift discussion in this thread: the biggest drift
+reducer for us wasn't better prompts — it was making the layer contract
+physically unviolable via tool boundaries. A sloppy LLM turn can't
+corrupt the sources layer even in principle, so drift stays confined to
+the wiki layer, where lint can catch it.
+
+Happy to compare notes with the other implementations here.
+
+Sorry, something went wrong.
+
+Uh oh!
+
+There was an error while loading. [71]Please reload this page.
+
+[72]@sturlese
+
+[73]sturlese commented [74]Jul 19, 2026
+
+Copy link
+Copy Markdown
+
+I looked at a lot of personal second brains before building this one, and
+bounced off most of them for the same two reasons: I could never tell what the
+system was actually doing, and getting started meant installing a stack. I
+wanted something simple enough that I always know exactly what happens when,
+and that asks you to install as little as possible.
+
+That constraint produced the design:
+[75]https://github.com/sturlese/hippocampus
+
+No vector database, no embeddings, no MCP server, no Obsidian plugins, no
+dependencies. Markdown, one stdlib Python linter, one shell hook, git.
+
+Retrieval is three reads instead of a similarity search: a 500-word
+working-memory cache injected at session start, then the master index (one line
+per page), then the three to five pages it points to. Grep as fallback.
+
+Every step is a file you can open and read.
+
+That's the part I care about most. A missed lookup is a bad line in index.md —
+visible, editable. With embeddings you get a number, and the cause could be a
+chunk boundary, a stale index or an unlucky neighbour, none of which you can
+see.
+
+It stops working somewhere in the low thousands of pages, when the index no
+longer fits in context.
+
+I wrote up the whole pipeline step by step, in case the approach is useful even
+without the tool:
+[76]https://github.com/sturlese/hippocampus/blob/main/docs/
+what-happens-when-you-ingest.md
+
+Sorry, something went wrong.
+
+Uh oh!
+
+There was an error while loading. [79]Please reload this page.
+
+[80]@lucianfialho
+
+[81]lucianfialho commented [82]Jul 19, 2026
+
+Copy link
+Copy Markdown
+
+Built a variant of this pattern backed by Neo4j instead of markdown — same
+three layers (immutable Source nodes / a Concept+Claim graph / a
+schema-as-constraints), but cross-references become real typed edges you can
+run graph algorithms on.
+
+Benchmarked the two things that actually matter instead of just shipping a
+demo:
+
+Entity resolution: 45 labeled mention pairs (same-entity / related-but-distinct
+/ unrelated), real embeddings. A single cosine threshold doesn't work —
+related-but-distinct pairs often score higher than true synonyms (best F1 =
+0.667). A two-stage pipeline instead — cheap embedding filter for candidates,
+then one real LLM judgment call per candidate ("same entity or just related?")
+— got F1 to 1.000 on the same pairs.
+
+Graph vs flat RAG on multi-hop questions: small real-facts corpus, 6 questions
+each needing 2-3 connected documents. Flat RAG (top-k) covered 4/6; graph
+traversal (N hops over typed edges) covered 6/6. Caveat: on this small dense
+corpus the traversal's recall win came with a precision cost (pulled 5-6 of 8
+docs on 3 of 6 questions) — not tested at scale.
+
+Full pattern, corpus, labeled pairs, and the chart: [83]https://gist.github.com
+/lucianfialho/44034e0d02a2bfccca2ad6358bde1dff
+
+Sorry, something went wrong.
+
+Uh oh!
+
+There was an error while loading. [86]Please reload this page.
+
+[87]@bprice1000
+
+[88]bprice1000 commented [89]Jul 19, 2026
+
+Copy link
+Copy Markdown
+
+I’ve been applying lmm_wiki as a heavy influence in creating a CMMS; Manage
+assets, resources, build metrics, feed them with real time signals or data
+gathered from procedures, build fully fleshed unscheduled/preventable
+maintenance/upkeep plans, and create issues against any of the entities; All
+while being fully greppable, levering markdown in multiple ways, requiring no
+database or license. Llm_wiki is a great influence for a cmms as the systems
+themselves are relatively low event.
+
+Flattest. 1st principles. The assets don’t have logs, they are logs with
+fields, the resources are counts, etc.
+
+I just wanted to share the index file I am using inside of my project. Perhaps
+it shows how the schema aspect of the concept can be heavily expanded and most
+concepts on display held through testing during an earlier second iteration.
+Third iteration maybe in testing next month.
+
+[90]https://gist.github.com/bprice1000/f986547dda0a82c5178faa6e237247fe
+
+Sorry, something went wrong.
+
+Uh oh!
+
+There was an error while loading. [93]Please reload this page.
+
+[94]@umezy
+
+[95]umezy commented [96]Jul 20, 2026 •
+edited
+Loading
+
+Uh oh!
+
+There was an error while loading. [97]Please reload this page.
+
+Copy link
+Copy Markdown
+
+[98]@geetansharora asked on day one how to share one of these with a team — the
+answers so far have been "serve the vault over MCP." We've been running a
+different, git-native answer for a few months, so here are some notes from
+actually operating it.
+
+Context: we build on a niche SDK that models happily hallucinate APIs for, so
+the wiki layer (synced official docs + our own verified tips) is not optional
+for us. It's a lighter take on the pattern than the gist describes — the LLM
+acts more as searcher than librarian, and the compiled layer is human-verified
+tips and SKILL.md procedures rather than an LLM-maintained wiki. The part that
+turned out to be interesting is distribution: that compiled layer replicates to
+every teammate's agent on git pull.
+
+The repo itself is the deployment. No MCP server, no RAG index, no sync
+service. One git repo with two layers: sources/ (the wiki: synced official
+docs, API references, tips) and skills/ (the agency side: SKILL.md packages,
+including the search skills that query sources/). A one-time setup command
+links each skill into ~/.claude/skills (symlinks; junctions on Windows), and a
+post-merge hook re-runs the sync — so daily operation for everyone on the team
+is literally git pull.
+
+Notes from living with it:
+
+  • Working copy = live instance changes behavior. The linked skills point into
+    each member's checkout, so editing a skill + git push is the entire publish
+    flow. The unexpected outcome: our designers — not engineers — started
+    pushing skills. The contribution barrier is "edit a markdown file," and
+    that turned out to be low enough for non-engineers.
+  • Retrieval stayed a skill in the repo, not a service. The template ships a
+    ranked-grep search skill (generate keyword variants → grep sources/ → rank
+    the hits). In our team repo we also run a hybrid semantic skill — embedded
+    Chroma + a local multilingual MiniLM, RRF-fused with the grep results,
+    index rebuilt incrementally by the skill itself — and honestly that's the
+    one I reach for most: for natural-language "how do I…" queries over our
+    (mostly Japanese) docs it beats keywords. So my data point for the
+    grep-vs-RAG debate isn't "grep wins" — it's that at hundreds of pages, both
+    flavors of retrieval fit inside the repo as skills, with nothing to host.
+  • A failure worth writing down: we first tried a shared .claude/ in a parent
+    folder above all projects. Claude Code doesn't pick it up for the
+    git-managed projects underneath it. Per-skill links into ~/.claude/skills
+    was the reliable path.
+
+Template (MIT): [99]https://github.com/umezy/team-ai-workflows
+
+Sorry, something went wrong.
+
+Uh oh!
+
+There was an error while loading. [102]Please reload this page.
+
+[103]@suwonleee
+
+[104]suwonleee commented [105]Jul 20, 2026
+
+Copy link
+Copy Markdown
+
+Reading down this thread, nearly every tool here — mine included — exists to
+keep the model's memory current. But the pattern puts the judgment on the
+human: "you're in charge of sourcing, exploration, and asking the right
+questions." Nothing in it keeps that side from decaying. Your wiki stays
+current; your memory of why you decided things doesn't.
+
+So I built the other half of the loop. The wiki quizzes you back — day-granular
+spaced repetition (1·3·7·16·35·60) over the decision and insight pages only,
+since those are the ones whose why rots. It's the one part of the system that
+spends your time instead of saving it.
+
+Two things I didn't expect while building it:
+
+Citations don't survive leaving your machine. A footnote pointing at
+session-abc.jsonl is provenance for exactly one person. Pages now carry 1–2
+verbatim lines of the evidence inline — secret-screened, because transcripts
+really do contain credentials — so a teammate gets the grounding and not just
+the conclusion.
+
+Indexing that evidence made pages harder to find. BM25 length normalization:
+the excerpt lengthens the page's own chunk, which lowers its score for its own
+topic. Excluding excerpts from the index put recall@5 back to baseline.
+
+Markdown as the source of truth, local-first, no MCP, no build step. Works with
+Claude Code / Codex / OpenCode.
+
+[106]https://github.com/suwonleee/llmwiki
+
+("llmwiki" is a crowded name in this thread — this is the one with the quiz.)
+
+[107][social-preview]
+
+Sorry, something went wrong.
+
+Uh oh!
+
+There was an error while loading. [110]Please reload this page.
+
+[111]@kytmanov
+
+[112]kytmanov commented [113]Jul 20, 2026 •
+edited
+Loading
+
+Uh oh!
+
+There was an error while loading. [114]Please reload this page.
+
+Copy link
+Copy Markdown
+
+Synto v0.7.0 is out - 200★
+
+[115]https://github.com/kytmanov/synto
+
+Main addition: concept relations. Opt-in on ingest - the model extracts links
+between known concepts (e.g. Raft depends_on Consensus) with a short evidence
+quote. Packs ship the graph as graph/graph.json. Queries follow one hop to pull
+in related articles.
+
+Also new in v0.7:
+
+• reverse lookup: synto find ranks concept names, then titles, then body text.
+• provenance: synto trace shows where a term shows up in sources, or which
+articles used a source segment.
+• fix a wrong alias without a merge: synto concept alias add|remove|move.
+• silence known lint noise: ack advisories in synto.toml so they stop
+cluttering maintain.
+
+Same shape as before:
+
+• works with local LLMs
+• great with Ollama and LM Studio
+• plain Markdown
+• Obsidian-friendly
+• no vector DB
+• no cloud required
+• multi-language
+
+Star it if you want to support local-first AI tools. Fork it if you want to
+build on it.
+
+Sorry, something went wrong.
+
+Uh oh!
+
+There was an error while loading. [118]Please reload this page.
+
+[119]@Sarthib7
+
+[120]Sarthib7 commented [121]Jul 20, 2026 •
+edited
+Loading
+
+Uh oh!
+
+There was an error while loading. [122]Please reload this page.
+
+Copy link
+Copy Markdown
+
+CItadel 0.3.0
+
+This clicked hard — especially the contrast with RAG-as-rediscovery and the
+three-layer split (immutable sources → LLM-maintained wiki → schema). I've been
+running a team version of the same idea, and it maps cleanly onto your ingest/
+query/lint loop.
+
+For a personal wiki, your Obsidian + git + index.md approach is hard to beat at
+moderate scale. For a team, we hit different walls: who owns writes, what gets
+shared vs stays draft, semantic drift when five agents touch the same "entity
+page," and capture that can't depend on someone remembering to ingest after
+every meeting.
+
+We built [123]Citadel as that team layer — an Organization Vault on Cognee
+(Apache-2.0). It's not "markdown in a folder" (though markdown/Obsidian still
+fit as sources and UI):
+
+Node (seat:{slug}): private working memory; default target for autonomous
+capture (git pre-push + session hooks, fail-silent)
+Central: shared org memory; read-only for seats, evolves via governed promotion
++ org sync (GitHub/Linear digests)
+MCP + CLI: agents search before coding; citadel_search replaces "read index.md
+first" at scale
+Lint-ish: open Knowledge Conflicts instead of silently merging contradictions
+Re [124]@geetansharora team question: we did end up at MCP, but over a
+maintained vault rather than a static RAG index — closer to your wiki
+compounding than chunk retrieval.
+
+Repo + docs:
+
+[125]https://github.com/masumi-network/Citadel
+Connect an agent (MCP setup): [126]https://
+citadel-archive-production.up.railway.app/skills/connect
+Install the agent skill: npx skills add masumi-network/Citadel-Archive
+Would love to see a future where a Karpathy-style personal git wiki can promote
+curated pages into an org Central. Citadel is the org half today; the personal
+half still looks a lot like this gist.
+[127]Screenshot 2026-07-22 at 11 44 42
+
+Sorry, something went wrong.
+
+Uh oh!
+
+There was an error while loading. [130]Please reload this page.
+
+[131]@gavischneider
+
+[132]gavischneider commented [133]Jul 20, 2026
+
+Copy link
+Copy Markdown
+
+I've been documenting everything LLM Wikis for the past 2+ months: [134]https:/
+/github.com/gavischneider/awesome-llm-wiki
+
+If you'd like your implementation/tool/guide/article to be added, PRs are
+welcome.
+
+Sorry, something went wrong.
+
+Uh oh!
+
+There was an error while loading. [137]Please reload this page.
+
+[138]@rath-muth
+
+[139]rath-muth commented [140]Jul 21, 2026
+
+Copy link
+Copy Markdown
+
+I'm a beginner in exploring Claude and LLMs. I'm trying to find the original
+copy of Karpathy's base prompt to feed it to my LLM agent to set up the system,
+I don't see it in the original post. Am I misunderstood something? or can
+someone help guide me by providing a prompt to start with?
+
+Sorry, something went wrong.
+
+Uh oh!
+
+There was an error while loading. [143]Please reload this page.
+
+[144]@frankchu91
+
+[145]frankchu91 commented [146]Jul 22, 2026
+
+Copy link
+Copy Markdown
+
+
+    I'm a beginner in exploring Claude and LLMs. I'm trying to find the
+    original copy of Karpathy's base prompt to feed it to my LLM agent to set
+    up the system, I don't see it in the original post. Am I misunderstood
+    something? or can someone help guide me by providing a prompt to start
+    with?
+
+there is no official prompt from Karpathy. Try this git repo here: [147]https:/
+/github.com/frankchu91/mindbase
+
+Sorry, something went wrong.
+
+Uh oh!
+
+There was an error while loading. [150]Please reload this page.
+
+[151]@alfadur7
+
+[152]alfadur7 commented [153]Jul 22, 2026 •
+edited
+Loading
+
+Uh oh!
+
+There was an error while loading. [154]Please reload this page.
+
+Copy link
+Copy Markdown
+
+"Obsidian is the IDE; the LLM is the programmer; the wiki is the codebase."
+Taking that line literally is what made this click for me — if the wiki is a
+codebase, the discipline the AI-coding world is building around agents
+transfers. That discipline is harness engineering: everything around the agent
+— its checks, its review, the rules themselves — treated as the real
+engineering surface, organized as three nested loops. ([155]Dru Knox of Tessl)
+
+Each loop has a distinct job here:
+
+Inner — the agent checking itself while drafting, before you see anything. You
+note a source "might touch 10-15 wiki pages," and that you "could also
+batch-ingest many sources at once with less supervision." The inner loop is
+what makes that second option safe.
+
+Outer — review where a draft becomes part of the wiki. Right now that's you: "I
+read the summaries, check the updates, and guide the LLM on what to emphasize."
+Automating it takes two things a self-check can't do: deterministic checks
+across the whole wiki rather than the page in hand (your lint list, but at
+publication instead of "periodically"), and a fresh-eyes read by an agent that
+didn't write the page and can't see the writer's reasoning.
+
+Meta — the schema is what this loop edits. "You and the LLM co-evolve this over
+time" is already it; the mechanical version is that a defect caught twice
+becomes a rule, so you stop re-teaching it every session.
+
+Then the analogy breaks. Shipped code stays correct until the spec changes;
+knowledge doesn't. You already name the requirement — the wiki is "compiled
+once and then kept current" — and lint lists "stale claims that newer sources
+have superseded" right next to orphan pages and missing cross-references. But
+those are defects in the work; staleness is the world moving. Keeping a wiki
+current needs a fourth loop of its own, with published pages fed back in as
+input.
+
+I wrote up [156]the 4-loop Knowledge Factory in full — a design argument, not a
+measured result.
+
+[157]image
+
+Sorry, something went wrong.
+
+Uh oh!
+
+There was an error while loading. [160]Please reload this page.
+
+[161]@ErikEvenson
+
+[162]ErikEvenson commented [163]Jul 24, 2026 •
+edited
+Loading
+
+Uh oh!
+
+There was an error while loading. [164]Please reload this page.
+
+Copy link
+Copy Markdown
+
+The additions that turn Karpathy’s sketch into something you can still trust
+after a few thousand pages:
+
+[165]https://www.erikevenson.net/building-an-llm-wiki-part-2.html
+
+Sorry, something went wrong.
+
+Uh oh!
+
+There was an error while loading. [168]Please reload this page.
+
+[169]@ibehnam
+
+[170]ibehnam commented [171]Jul 24, 2026
+
+Copy link
+Copy Markdown
+
+
+    The additions that turn Karpathy’s sketch into something you can still
+    trust after a few thousand pages:
+
+    [172]https://www.erikevenson.net/building-an-llm-wiki-part-2.html
+
+The article reads like AI slop.
+
+Sorry, something went wrong.
+
+Uh oh!
+
+There was an error while loading. [175]Please reload this page.
+
+[176]@denson
+
+[177]denson commented [178]Jul 25, 2026
+
+Copy link
+Copy Markdown
+
+Storing as OO-LD json seems to work well for at least up to 10k documents.
+
+    This resonates strongly - and I'd push one layer deeper on why the
+    bookkeeping gets abandoned. In our experience the thing that doesn't scale
+    is unqualified links + free text. A lovingly hand-maintained personal wiki
+    decays into prose and dead links within a couple of years; a team or
+    corporate one gets there faster. What actually compounds is structure -
+    typed entities you can query, not paragraphs you have to re-read.
+
+    We took a structured variant of exactly this pattern into production about
+    five years ago, on Semantic MediaWiki. Using MediaWiki's content-slot
+    feature, every article keeps its unstructured body and a structured JSON
+    slot side by side. The JSON slot's shape is defined by the article's
+    category/categories, and each category carries a JSON Schema in its own
+    slot - so one schema drives both auto-generated edit forms for humans and
+    machine editing for everything else.
+
+    Putting JSON-LD on top (we specced this as [179]OO-LD: one document that is
+    simultaneously a JSON Schema and a JSON-LD context) turns the whole wiki
+    into an RDF knowledge graph for free - you can run SPARQL across every
+    entry. Your lint step (contradictions, orphans, missing cross-refs) becomes
+    graph queries; query becomes structured retrieval, not just text search.
+
+    When LLMs with JSON-Schema-driven structured output arrived, it was a
+    drop-in fit: the exact schemas that render the forms also constrain LLM
+    extraction.
+
+    Mapping to your three layers: raw sources (immutable) / the wiki - but as
+    typed, linkable entities rather than markdown / the schema - a JSON Schema
+    per category rather than one prose config.
+
+    Where we're putting research effort now is precisely your ingest loop at
+    scale: take an unstructured knowledge chunk -> select the right schema(s)/
+    categories to represent it -> fill them correctly and dedup against
+    entities that already exist. That last "and" - entity resolution against a
+    live graph - is the hard part; it's your lint moved to write-time.
+
+    Curious whether others here have pushed on write-time dedup - that's where
+    the pattern either compounds or sprawls.
+
+    Reference implementation: [180]OpenSemanticLab (live demo: [181]https://
+    demo.open-semantic-lab.org) · schema approach: [182]OO-LD.
+
+Sorry, something went wrong.
+
+Uh oh!
+
+There was an error while loading. [185]Please reload this page.
+
+[186]@akash07k
+
+[187]akash07k commented [188]Jul 25, 2026
+
+Copy link
+Copy Markdown
+
+[189]@frankchu91
+Wow, it's really fantastic!
+I read on your repo:
+
+    still in v1 → v2 migration.
+
+So, when are you planning to migrate it to V2?
+
+    there is no official prompt from Karpathy. Try this git repo here: [190]
+    https://github.com/frankchu91/mindbase
+
+Sorry, something went wrong.
+
+Uh oh!
+
+There was an error while loading. [193]Please reload this page.
+
+[194]@bollakarthikeya
+
+[195]bollakarthikeya commented [196]Jul 26, 2026 •
+edited
+Loading
+
+Uh oh!
+
+There was an error while loading. [197]Please reload this page.
+
+Copy link
+Copy Markdown
+
+This idea is very powerful and it resonates so deep with what I have been going
+through; a running inventory of knowledge that is constantly updated with the
+new incoming sources of information. Since I am an avid note taker and since it
+is nearly impossible to constantly sieve through the many hand-written pages,
+this idea - a knowledge wiki that is constantly evolving - is what I need.
+Thank you Andrej for this brilliant idea. Kudos to you!
+
+Sorry, something went wrong.
+
+Uh oh!
+
+There was an error while loading. [200]Please reload this page.
+
+[201]@gowtham0992
+
+[202]gowtham0992 commented [203]Jul 28, 2026
+
+Copy link
+Copy Markdown
+
+Link 2.0.0 is out: the memory layer got a face.
+
+LinkBar puts the review gate in your menu bar. Session hooks already captured
+memory automatically; the missing half was reviewing it without going anywhere.
+Now a capture lands and you get a native notification with a one-tap Accept,
+showing the exact line it will save.
+
+[204]linkbar-tour
+
+The part I use most is the palette. Hit Option-Command-M anywhere on the
+machine and a floating bar opens over whatever app you're in: type a question
+to recall from your memory, or start with + to remember something. It's
+review-gated like every other write. I stopped switching to a terminal to ask
+my own memory things, which turned out to be the whole point.
+
+[205]image
+
+There's also a live pulse of which agent sessions are writing right now, a
+browser over every memory file with supersede lineage, and a status tab showing
+whether the CLI, workspace, MCP, hooks, recall tier, and viewer are actually
+healthy, each with a one-click fix that verifies it worked instead of just
+claiming success.
+
+The whole app is a thin SwiftUI client over lnk --json. No new backend, no new
+API, nothing new to trust: it runs the same reviewed commands as the CLI, so
+the app can never drift from what Link actually does.
+
+No breaking changes. Every CLI command, MCP tool, hook, and memory file from
+1.7 works exactly as before; the major version marks the app's debut, not an
+API break.
+
+Still: wiki as the storage layer, every memory a file you can open, nothing
+durable without review.
+
+brew upgrade link                                # CLI 2.0.0
+brew install --cask gowtham0992/link/linkbar     # the menu bar app
+
+Release notes: [206]https://github.com/gowtham0992/link/releases/tag/v2.0.0
+
+Repo: [207]https://github.com/gowtham0992/link
+Site: [208]https://gowtham0992.github.io/link/
+PyPI: [209]https://pypi.org/project/link-mcp/
+MCP: [210]https://registry.modelcontextprotocol.io/?q=
+io.github.gowtham0992%2Flink
+
+Sorry, something went wrong.
+
+Uh oh!
+
+There was an error while loading. [213]Please reload this page.
+
+[214]@XBlueSky
+
+[215]XBlueSky commented [216]Jul 29, 2026
+
+Copy link
+Copy Markdown
+
+Update from my earlier comment here: I originally shared Cortexes when it was
+still an early workflow for collaboratively distilling Claude Code
+conversations into a Markdown vault.
+
+Since then, it has grown into an open-source, installable Claude Code plugin,
+currently at v1.1.0:
+
+[217]https://github.com/XBlueSky/cortexes
+
+A few things I learned while turning the idea into something I use across real
+coding sessions:
+
+Capturing everything is easy; deciding what deserves to become knowledge is the
+harder problem.
+
+Cortexes now captures sessions automatically, but filters low-value tool output
+before writing them into the Raw layer. Distillation is map-first and
+context-budgeted, so a long session can be processed in bounded spans without
+loading the entire transcript into the context window.
+
+The more important part for me is maintenance. Newly distilled findings do not
+always become new notes. The broadcast workflow can fuse them into related
+existing pages, correcting assumptions and adding caveats. This is my attempt
+to address knowledge rot rather than simply accumulating more memory.
+
+Recall now uses hybrid BM25 + vector retrieval with reciprocal-rank fusion,
+including mixed Chinese/English technical queries and a BM25-only fallback when
+offline.
+
+The durable artifact is still plain Markdown + Git. The vault can be opened
+directly in Obsidian, so the agent’s memory remains readable, editable,
+diffable, and reversible rather than hidden inside a vector database.
+
+I now think of Cortexes less as a memory store and more as a maintenance
+pipeline:
+
+capture → distill → fuse → retrieve
+
+Project: [218]https://github.com/XBlueSky/cortexes
+
+Interactive overview: [219]https://cortexes.pages.dev/
+
+I would be interested in feedback from people who have run an LLM-maintained
+wiki over time: what policies or checks have been most effective at preventing
+stale or contradictory knowledge from quietly accumulating?
+
+Sorry, something went wrong.
+
+Uh oh!
+
+There was an error while loading. [222]Please reload this page.
+
+[223]@GeraldGrootRoessink
+
+[224]GeraldGrootRoessink commented [225]Jul 29, 2026
+
+Copy link
+Copy Markdown
+
+I agree with the motivation (using an LLM to maintain a persistent, compounding
+artifact as a “knowledge view”), but I’m skeptical of proposals that treat
+Markdown front-matter as the semantic backbone. We need something
+machine-executable: a precise way to define semantics, data selection, joins/
+mappings, and provenance for the resulting view. Human-oriented formatting from
+Markdown isn’t essential for that; an LLM can generate presentation at the end.
+
+Much of the relevant infrastructure already exists in the Semantic Web: HTTP,
+URIs, RDF, and SPARQL, plus established linked data vocabularies. So the gap is
+less about inventing a new container and more about producing view ready
+outputs in a repeatable, automated way.
+
+My conclusion: the key missing piece is not a new metadata container format,
+but a reliable, machine executable way to build and maintain an LLM ready
+“knowledge view” from multiple sources.
+
+Sorry, something went wrong.
+
+Uh oh!
+
+There was an error while loading. [228]Please reload this page.
+
+[229]@suwonleee
+
+[230]suwonleee commented [231]Jul 29, 2026
+
+Copy link
+Copy Markdown
+
+Follow-up to my earlier comment here (the project wiki that quizzes you back) —
+since then the interesting problems have all been trust boundaries, the kind
+that only show up once the thing runs on machines that aren't yours:
+
+A clone is not consent. Early versions treated git clone + setup as permission
+to start capturing sessions. It isn't. Everything is now inert until you enroll
+a repository explicitly, and until a session is known to belong to an enrolled
+repo, the capture layer reads exactly two routing fields from a transcript and
+stops — fail closed, by budget.
+
+The installing agent is your least-trusted user. On a nonstandard machine, the
+agent doing the install is also the thing searching your disk for where Claude
+Code / Codex / OpenCode keep their data. So discovery became three-tier:
+deterministic resolution → schema-signature verification (a candidate is judged
+by what's inside — transcripts, rollouts, a session table — never by its name;
+the E2E that motivated this watched a plain home directory pass as a Claude
+profile because it contained a folder called projects/) → and only then
+persistence, which the engine refuses unless verification passed. And a
+connected location stays read-only forever: capture reads from it, install
+wiring never writes into it.
+
+Models are observed, not declared. The engine shipped with a hardcoded model id
+for its generative passes; it had gone stale by the time the replacement landed
+— the argument making itself. Now a pass runs on whatever model the session
+actually recorded (every harness already writes this), with per-harness
+fallbacks only when nothing was observed. The follow-up lesson cost a day: the
+first id-validation regex rejected llama3.1:8b, and an over-strict guard fails
+exactly like a stale constant — silently.
+
+Still markdown as the source of truth, local-first, no MCP, no build step,
+three harnesses.
+
+[232]https://github.com/suwonleee/llmwiki — if any of this is useful to you, a
+star genuinely helps others in this thread find it among the many llmwikis.
+
+[233][social-preview]
+
+Sorry, something went wrong.
+
+Uh oh!
+
+There was an error while loading. [236]Please reload this page.
+
+[237]@antondziatkovskii
+
+[238]antondziatkovskii commented [239]Jul 29, 2026
+
+Copy link
+Copy Markdown
+
+One failure mode this pattern has that plain RAG doesn't — and a measurement of
+it.
+
+A compiled wiki answers more confidently than raw retrieval. That's the point
+of it. But confidence gets decoupled from whether the answer is actually in
+there, and in an incrementally compiled wiki that compounds: a confident
+fabrication gets filed back as a page, and then it is a source.
+
+I measured this on my own vault (~4 months of ingested sources, e5 embeddings +
+a reranker on top). 6 questions — 3 with answers in the wiki, 3 deliberately
+outside it — looking at the top rerank score of each result set:
+
+               question                 in the wiki? top rerank score
+our rule on treating a cause as a claim yes          +8.66
+how we sync machines                    yes          +5.87
+our memory-layer decision               yes          +1.57
+my pizza recipe                         no           −1.03
+bus fare in Kuala Lumpur                no           −3.82
+max depth of the bathyscaphe Trieste    no           −4.53
+
+Clean separation — worst "in" beats best "out" by 2.6, no overlap, natural
+cutoff at 0.
+
+The part that actually mattered: all six queries returned exactly 12 hits. The
+bathyscaphe question got 12 confident notes out of a personal vault that has
+never heard of bathyscaphes. Nothing anywhere in the output said "I found
+nothing." There was no threshold in the code at all — the reranker computed the
+score and then it was thrown away.
+
+Honest limits: n=6, I picked the questions, and the "out" ones are far from my
+domains. This shows the signal exists; it does not show where the threshold
+belongs. The dangerous case — a question from a domain adjacent to the wiki —
+is untested. Running it in shadow for a week, logging the top score of every
+real query without cutting anything, before wiring an actual cutoff.
+
+Concrete suggestion for the schema layer (CLAUDE.md / AGENTS.md), since that's
+where this belongs rather than in code: a rule that the agent must say "the
+wiki has no confident answer on this" instead of synthesizing from
+low-relevance hits — and that such an answer is never filed back.
+
+Retrieval layer this came out of, if useful: [240]https://github.com/
+Palo-Alto-AI-Research-Lab/sqlite-graph-memory — Graph RAG on SQLite over an
+Obsidian vault, [[wikilinks]] as the graph. The citation-checking half is
+separate: [241]https://github.com/Palo-Alto-AI-Research-Lab/
+verbatim-citation-gate
+
+Sorry, something went wrong.
+
+Uh oh!
+
+There was an error while loading. [244]Please reload this page.
+
+[245]@Nikalo71
+
+[246]Nikalo71 commented [247]Jul 30, 2026
+
+Copy link
+Copy Markdown
+
+Voici un Gist très très utile, merci beaucoup pour votre travail et votre
+partage.
+
+Sorry, something went wrong.
+
+Uh oh!
+
+There was an error while loading. [250]Please reload this page.
+
+[251]@JanYork
+
+[252]JanYork commented [253]Jul 31, 2026
+
+Copy link
+Copy Markdown
+
+I've implemented a small version, and I think it's pretty good.
+
+If you're interested, you can check it out at [254]https://github.com/JanYork/
+llm-wiki-cli
+
+Sorry, something went wrong.
+
+Uh oh!
+
+There was an error while loading. [257]Please reload this page.
+
+[258]@Nikalo71
+
+[259]Nikalo71 commented [260]Jul 31, 2026
+
+Copy link
+Copy Markdown
+
+Thanks again for this work. It's perfect and I'm sure it will help many people.
+I created the Claude.MD file so it's in French and everything seems to be
+working very well.
+
+One technical question, though: I'm using Claude in VS Code.
+My question (being a complete beginner with this kind of tool) is whether it's
+necessary or optional to create a Wordspace for this project?
+
+Sorry, something went wrong.
+
+Uh oh!
+
+There was an error while loading. [263]Please reload this page.
+
+[264]@Nikalo71
+
+[265]Nikalo71 commented [266]Jul 31, 2026
+
+Copy link
+Copy Markdown
+
+
+    I've implemented a small version, and I think it's pretty good.
+
+    If you're interested, you can check it out at [267]https://github.com/
+    JanYork/llm-wiki-cli
+
+Thank you fore sharring !
+
+Sorry, something went wrong.
+
+Uh oh!
+
+There was an error while loading. [270]Please reload this page.
+
+[271]@alexadamus77-ui
+
+[272]alexadamus77-ui commented [273]Aug 1, 2026
+
+Copy link
+Copy Markdown
+
+Really clean approach to unified academic search and deduplication across
+sources! Managing source degradation and fallback queries across multiple
+endpoints takes a lot of effort.
+
+If you're looking for a fast, reliable academic search backend to simplify
+paper lookup, citation graphs, and metadata retrieval, [274]ScholarAPI is worth
+a look. It provides structured JSON responses directly, making paper search
+workflows much more deterministic.
+
+Sorry, something went wrong.
+
+Uh oh!
+
+There was an error while loading. [277]Please reload this page.
+
+[278]@gowtham0992
+
+[279]gowtham0992 commented [280]Aug 3, 2026
+
+Copy link
+Copy Markdown
+
+Link 2.1.0 is out. This one is about trust: memory that cannot repeat itself
+and knows when to re-ask.
+
+Since 2.0 I dogfooded the automatic capture pipeline hard and my own review
+inbox grew to 20 pending captures, five of them the same conversation captured
+five times. 2.1 is everything that fixing that properly turned into.
+
+What's new:
+
+  • Inbox zero. Proposals are fingerprinted and deduped against everything
+    pending, accepted, or dismissed. Deleting a capture records the dismissal,
+    so the same proposal never comes back. One conversation = one capture,
+    refreshed in place. "lnk dedup-captures" collapses an existing backlog
+    (mine went 20 to 9 in one command).
+  • Trust lifecycle. Every memory now gets a review window by type: project
+    context 3 months, preferences 6, decisions 12. Reviewing re-arms it. Aged
+    memories are never hidden, they get labeled "review due" everywhere agents
+    read, including the session brief. As far as I know no other memory system
+    re-asks whether what it knows is still true.
+  • Contradiction detection got serious. Revisions like "we don't use X
+    anymore" now supersede the old memory: exposure went from 0.583 to 0.167 on
+    the hygiene benchmark, and with the local semantic tier on, even
+    rephrasings with zero shared words get caught ("SQLite with FTS" revised as
+    "DuckDB files").
+  • Memory poisoning benchmark. A planted memory gets injected into every
+    future session, which makes agent memory the biggest prompt injection
+    target there is. 15 authored attacks now run through the real pipeline in
+    CI: 0 reach the inbox unlabeled, 0 false positives on real preferences.
+    Injection-shaped proposals get flagged in the inbox: "verify you actually
+    said this before accepting". I believe this is the only published
+    adversarial benchmark on an agent memory write path.
+
+[281]linkbar-11-inbox-injection
+
+  • lnk setup. Install is now two commands total. "lnk setup" detects every
+    agent on your machine (Claude Code, Codex, Cursor, Windsurf, Zed, Kiro,
+    Gemini CLI) and wires them all: workspace, MCP, session hooks. It ran on my
+    own machine during the release and wired 5 agents first try. Upgrades are
+    the same command.
+  • LinkBar 1.1. Tap any memory for its trust card (where it came from, when it
+    was reviewed, whether recall will use it and why). Injection warnings show
+    right on the capture row. Full backlog is reviewable with a cleanup button.
+
+[282]linkbar-11-explain-card
+
+  • The homepage now embeds a real exported Link workspace you can click
+    through, generated by "lnk snapshot".
+
+# macOS, the full experience (CLI + menu bar app)
+brew install --cask gowtham0992/link/linkbar
+lnk setup
+
+# CLI only (or Linux)
+brew install gowtham0992/link/link
+lnk setup
+
+# already running Link
+brew upgrade && lnk setup
+
+Still: wiki as the storage layer, every memory a file you can open, nothing
+durable without review.
+
+Release notes: [283]https://github.com/gowtham0992/link/releases/tag/v2.1.0
+
+Repo: [284]https://github.com/gowtham0992/link
+Site: [285]https://gowtham0992.github.io/link/
+PyPI: [286]https://pypi.org/project/link-mcp/
+MCP: [287]https://registry.modelcontextprotocol.io/?q=
+io.github.gowtham0992%2Flink
+Benchmarks with full configs and the experiments that lost: [288]https://
+github.com/gowtham0992/link/blob/main/benchmarks/RESULTS.md
+
+Sorry, something went wrong.
+
+Uh oh!
+
+There was an error while loading. [291]Please reload this page.
+
+[292]@mas213
+
+[293]mas213 commented [294]Aug 3, 2026
+
+Copy link
+Copy Markdown
+
+Update since my last comment. [295]https://gist.github.com/karpathy/
+442a6bf555914893e9891c11519de94f?permalink_comment_id=6237886#
+gistcomment-6237886
+Ran the behavioral graph against a frontier model (Claude Fable 5) on the same
+repo, same commit. Wanted to know: does a deterministic graph find the same
+things a reasoning model finds?
+Overlap: near zero.
+The model read ~75 files it picked itself and found defect mechanisms. Races,
+silent fallbacks, missing retries. The graph mapped all 4,849 behaviors
+exhaustively and ranked them by structural exposure. Completely different
+output lists. Each instrument's blind spot was the other's finding.
+Two agreements mattered. Both flagged the same message-queue layer (184
+importers, one spec file) as high-risk untested surface. Both deprioritized the
+same view/page-layout family. Convergent deprioritization from decorrelated
+instruments is harder to fake than convergent alarm.
+One disagreement was productive. The model's top finding sat in the graph's
+data but outside its top 20. Tracing why isolated two scoring factors
+documented in the methodology but not yet weighted in the shipped formula. The
+disagreement functioned as instrument calibration. Fixed same day, in public.
+Also closed the proof ladder end-to-end on a second repo (Go, ~8,700
+behaviors). Three mutation proofs. One was self-incriminating: the graph's own
+test generator hallucinated an expected value. The execution layer caught it.
+Oracle corrected from source. Mutation proof then closed the method. A
+verification layer that catches its own generator is the strongest evidence for
+the decorrelation argument.
+The Lint operation from the original gist now has four evidence tiers instead
+of binary tested/untested: dynamically proven (mutation killed), test signal
+(static link, no proof), candidate (name match only), no signal. The graph
+refuses to overstate. Nothing reaches "covered" without execution.
+
+[296]@jessicayoung12 , curious what domain you applied it to. The compounding
+effect you describe is exactly what we see. The graph after 50 PRs is a
+fundamentally different instrument than the graph after 5. Every incident filed
+teaches it a failure mode it didn't have before.
+
+Full comparison write-up: [297]https://orangepro.ai/blog/fable-vs-orangepro
+Repo unchanged: [298]https://github.com/OrangeproAI/orangepro-mcp
+
+Sorry, something went wrong.
+
+Uh oh!
+
+There was an error while loading. [301]Please reload this page.
+
+[302]@BackendGameSetMatch
+
+[303]BackendGameSetMatch commented [304]Aug 3, 2026
+
+Copy link
+Copy Markdown
+
+My take on it: [305]https://github.com/BackendGameSetMatch/sourcebook
+
+Sorry, something went wrong.
+
+Uh oh!
+
+There was an error while loading. [308]Please reload this page.
+
+[309]Sign up for free to join this conversation on GitHub. Already have an
+account? [310]Sign in to comment
+
+Footer
+
+[311] © 2026 GitHub, Inc.
+
+Footer navigation
+
+  • [312]Terms
+  • [313]Privacy
+  • [314]Security
+  • [315]Status
+  • [316]Community
+  • [317]Docs
+  • [318]Contact
+  • [319] Manage cookies
+  • [320] Do not share my personal information
+
+[321](Dismiss error) You can’t perform that action at this time.
+[322](Close dialog)
+
+References:
+
+[1] https://gist.github.com/karpathy/442a6bf555914893e9891c11519de94f#start-of-content
+[2] https://gist.github.com/
+[6] https://gist.github.com/discover
+[7] https://github.com/
+[8] https://gist.github.com/auth/github?return_to=https%3A%2F%2Fgist.github.com%2Fkarpathy%2F442a6bf555914893e9891c11519de94f
+[9] https://gist.github.com/join?return_to=https%3A%2F%2Fgist.github.com%2Fkarpathy%2F442a6bf555914893e9891c11519de94f&source=header-gist
+[10] https://gist.github.com/
+[11] https://gist.github.com/auth/github?return_to=https%3A%2F%2Fgist.github.com%2Fkarpathy%2F442a6bf555914893e9891c11519de94f
+[12] https://gist.github.com/join?return_to=https%3A%2F%2Fgist.github.com%2Fkarpathy%2F442a6bf555914893e9891c11519de94f&source=header-gist
+[13] -
+[14] -
+[15] -
+[18] https://gist.github.com/karpathy
+[19] https://gist.github.com/karpathy
+[20] https://gist.github.com/karpathy/442a6bf555914893e9891c11519de94f
+[22] https://gist.github.com/karpathy/442a6bf555914893e9891c11519de94f/archive/ac46de1ad27f92b28ac95459c782c07f6b8c964a.zip
+[23] https://gist.github.com/login?return_to=https%3A%2F%2Fgist.github.com%2Fkarpathy%2F442a6bf555914893e9891c11519de94f
+[24] https://gist.github.com/login?return_to=https%3A%2F%2Fgist.github.com%2Fkarpathy%2F442a6bf555914893e9891c11519de94f
+[30] https://docs.github.com/articles/which-remote-url-should-i-use
+[33] https://gist.github.com/karpathy/442a6bf555914893e9891c11519de94f
+[34] https://gist.github.com/karpathy/442a6bf555914893e9891c11519de94f/revisions
+[35] https://gist.github.com/karpathy/442a6bf555914893e9891c11519de94f/stargazers
+[36] https://gist.github.com/karpathy/442a6bf555914893e9891c11519de94f/forks
+[42] https://docs.github.com/articles/which-remote-url-should-i-use
+[45] https://gist.github.com/karpathy/442a6bf555914893e9891c11519de94f/archive/ac46de1ad27f92b28ac95459c782c07f6b8c964a.zip
+[46] https://gist.github.com/karpathy/442a6bf555914893e9891c11519de94f/raw/ac46de1ad27f92b28ac95459c782c07f6b8c964a/llm-wiki.md
+[47] https://gist.github.com/karpathy/442a6bf555914893e9891c11519de94f#file-llm-wiki-md
+[48] https://gist.github.com/karpathy/442a6bf555914893e9891c11519de94f#llm-wiki
+[49] https://gist.github.com/karpathy/442a6bf555914893e9891c11519de94f#the-core-idea
+[50] https://tolkiengateway.net/wiki/Main_Page
+[51] https://gist.github.com/karpathy/442a6bf555914893e9891c11519de94f#architecture
+[52] https://gist.github.com/karpathy/442a6bf555914893e9891c11519de94f#operations
+[53] https://gist.github.com/karpathy/442a6bf555914893e9891c11519de94f#indexing-and-logging
+[54] https://gist.github.com/karpathy/442a6bf555914893e9891c11519de94f#optional-cli-tools
+[55] https://github.com/tobi/qmd
+[56] https://gist.github.com/karpathy/442a6bf555914893e9891c11519de94f#tips-and-tricks
+[57] https://gist.github.com/karpathy/442a6bf555914893e9891c11519de94f#why-this-works
+[58] https://gist.github.com/karpathy/442a6bf555914893e9891c11519de94f#note
+[63] https://gist.github.com/frankchu91
+[64] https://gist.github.com/frankchu91
+[65] https://gist.github.com/karpathy/442a6bf555914893e9891c11519de94f?permalink_comment_id=6263946#gistcomment-6263946
+[66] -
+[67] https://github.com/frankchu91/mindbase
+[68] https://raw.githubusercontent.com/frankchu91/mindbase/main/docs/assets/webui.png
+[71] -
+[72] https://gist.github.com/sturlese
+[73] https://gist.github.com/sturlese
+[74] https://gist.github.com/karpathy/442a6bf555914893e9891c11519de94f?permalink_comment_id=6264580#gistcomment-6264580
+[75] https://github.com/sturlese/hippocampus
+[76] https://github.com/sturlese/hippocampus/blob/main/docs/what-happens-when-you-ingest.md
+[79] -
+[80] https://gist.github.com/lucianfialho
+[81] https://gist.github.com/lucianfialho
+[82] https://gist.github.com/karpathy/442a6bf555914893e9891c11519de94f?permalink_comment_id=6265193#gistcomment-6265193
+[83] https://gist.github.com/lucianfialho/44034e0d02a2bfccca2ad6358bde1dff
+[86] -
+[87] https://gist.github.com/bprice1000
+[88] https://gist.github.com/bprice1000
+[89] https://gist.github.com/karpathy/442a6bf555914893e9891c11519de94f?permalink_comment_id=6265282#gistcomment-6265282
+[90] https://gist.github.com/bprice1000/f986547dda0a82c5178faa6e237247fe
+[93] -
+[94] https://gist.github.com/umezy
+[95] https://gist.github.com/umezy
+[96] https://gist.github.com/karpathy/442a6bf555914893e9891c11519de94f?permalink_comment_id=6265520#gistcomment-6265520
+[97] -
+[98] https://github.com/geetansharora
+[99] https://github.com/umezy/team-ai-workflows
+[102] -
+[103] https://gist.github.com/suwonleee
+[104] https://gist.github.com/suwonleee
+[105] https://gist.github.com/karpathy/442a6bf555914893e9891c11519de94f?permalink_comment_id=6265997#gistcomment-6265997
+[106] https://github.com/suwonleee/llmwiki
+[107] https://raw.githubusercontent.com/suwonleee/llmwiki/main/assets/social-preview.png
+[110] -
+[111] https://gist.github.com/kytmanov
+[112] https://gist.github.com/kytmanov
+[113] https://gist.github.com/karpathy/442a6bf555914893e9891c11519de94f?permalink_comment_id=6266796#gistcomment-6266796
+[114] -
+[115] https://github.com/kytmanov/synto
+[118] -
+[119] https://gist.github.com/Sarthib7
+[120] https://gist.github.com/Sarthib7
+[121] https://gist.github.com/karpathy/442a6bf555914893e9891c11519de94f?permalink_comment_id=6266907#gistcomment-6266907
+[122] -
+[123] https://github.com/masumi-network/Citadel-Archive
+[124] https://github.com/geetansharora
+[125] https://github.com/masumi-network/Citadel
+[126] https://citadel-archive-production.up.railway.app/skills/connect
+[127] https://private-user-images.githubusercontent.com/112841873/625046636-60c5bae4-7f06-41bc-97d6-55e086662db9.png?jwt=eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3ODU4MjEyOTIsIm5iZiI6MTc4NTgyMDk5MiwicGF0aCI6Ii8xMTI4NDE4NzMvNjI1MDQ2NjM2LTYwYzViYWU0LTdmMDYtNDFiYy05N2Q2LTU1ZTA4NjY2MmRiOS5wbmc_WC1BbXotQWxnb3JpdGhtPUFXUzQtSE1BQy1TSEEyNTYmWC1BbXotQ3JlZGVudGlhbD1BS0lBVkNPRFlMU0E1M1BRSzRaQSUyRjIwMjYwODA0JTJGdXMtZWFzdC0xJTJGczMlMkZhd3M0X3JlcXVlc3QmWC1BbXotRGF0ZT0yMDI2MDgwNFQwNTIzMTJaJlgtQW16LUV4cGlyZXM9MzAwJlgtQW16LVNpZ25hdHVyZT03ZjQ1YTAzNjRhNzc2Y2VjMDU4ODA5ZGFiODhlYjNiN2ZlYjg2YjE1MThlYjQ5MjdlYWE3NTYxMDkzODk3NTA0JlgtQW16LVNpZ25lZEhlYWRlcnM9aG9zdCZyZXNwb25zZS1jb250ZW50LXR5cGU9aW1hZ2UlMkZwbmcifQ.HRsnT7a_A-CJGo6SGlRV9erRQQtAso6v0ZFPcQrJReQ
+[130] -
+[131] https://gist.github.com/gavischneider
+[132] https://gist.github.com/gavischneider
+[133] https://gist.github.com/karpathy/442a6bf555914893e9891c11519de94f?permalink_comment_id=6266938#gistcomment-6266938
+[134] https://github.com/gavischneider/awesome-llm-wiki
+[137] -
+[138] https://gist.github.com/rath-muth
+[139] https://gist.github.com/rath-muth
+[140] https://gist.github.com/karpathy/442a6bf555914893e9891c11519de94f?permalink_comment_id=6268995#gistcomment-6268995
+[143] -
+[144] https://gist.github.com/frankchu91
+[145] https://gist.github.com/frankchu91
+[146] https://gist.github.com/karpathy/442a6bf555914893e9891c11519de94f?permalink_comment_id=6269557#gistcomment-6269557
+[147] https://github.com/frankchu91/mindbase
+[150] -
+[151] https://gist.github.com/alfadur7
+[152] https://gist.github.com/alfadur7
+[153] https://gist.github.com/karpathy/442a6bf555914893e9891c11519de94f?permalink_comment_id=6269698#gistcomment-6269698
+[154] -
+[155] https://www.youtube.com/watch?v=D_cw-k0F1DM&t=236
+[156] https://alfadur7.github.io/llm-wiki-newsroom/knowledge-factory/
+[157] https://private-user-images.githubusercontent.com/6949852/624935308-0e77e371-cba4-4e0d-8e7d-b1e2b9757713.png?jwt=eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3ODU4MjEyOTIsIm5iZiI6MTc4NTgyMDk5MiwicGF0aCI6Ii82OTQ5ODUyLzYyNDkzNTMwOC0wZTc3ZTM3MS1jYmE0LTRlMGQtOGU3ZC1iMWUyYjk3NTc3MTMucG5nP1gtQW16LUFsZ29yaXRobT1BV1M0LUhNQUMtU0hBMjU2JlgtQW16LUNyZWRlbnRpYWw9QUtJQVZDT0RZTFNBNTNQUUs0WkElMkYyMDI2MDgwNCUyRnVzLWVhc3QtMSUyRnMzJTJGYXdzNF9yZXF1ZXN0JlgtQW16LURhdGU9MjAyNjA4MDRUMDUyMzEyWiZYLUFtei1FeHBpcmVzPTMwMCZYLUFtei1TaWduYXR1cmU9YmMzNzc4Y2UwNjFhMDA0ZDdiZTZkZmM3Mzg2NTFhZTM5YjQyMTc0NjQ5NTkzNDU2ZGRjMGZkZTM2MDcyYjk5NSZYLUFtei1TaWduZWRIZWFkZXJzPWhvc3QmcmVzcG9uc2UtY29udGVudC10eXBlPWltYWdlJTJGcG5nIn0.qSUf3gssLHJKQLQXrusUZ7QdAcsL8L3ZQ8Q0nVkLOus
+[160] -
+[161] https://gist.github.com/ErikEvenson
+[162] https://gist.github.com/ErikEvenson
+[163] https://gist.github.com/karpathy/442a6bf555914893e9891c11519de94f?permalink_comment_id=6273560#gistcomment-6273560
+[164] -
+[165] https://www.erikevenson.net/building-an-llm-wiki-part-2.html
+[168] -
+[169] https://gist.github.com/ibehnam
+[170] https://gist.github.com/ibehnam
+[171] https://gist.github.com/karpathy/442a6bf555914893e9891c11519de94f?permalink_comment_id=6273920#gistcomment-6273920
+[172] https://www.erikevenson.net/building-an-llm-wiki-part-2.html
+[175] -
+[176] https://gist.github.com/denson
+[177] https://gist.github.com/denson
+[178] https://gist.github.com/karpathy/442a6bf555914893e9891c11519de94f?permalink_comment_id=6276072#gistcomment-6276072
+[179] https://github.com/OO-LD
+[180] https://github.com/OpenSemanticLab
+[181] https://demo.open-semantic-lab.org/
+[182] https://github.com/OO-LD
+[185] -
+[186] https://gist.github.com/akash07k
+[187] https://gist.github.com/akash07k
+[188] https://gist.github.com/karpathy/442a6bf555914893e9891c11519de94f?permalink_comment_id=6276421#gistcomment-6276421
+[189] https://github.com/frankchu91
+[190] https://github.com/frankchu91/mindbase
+[193] -
+[194] https://gist.github.com/bollakarthikeya
+[195] https://gist.github.com/bollakarthikeya
+[196] https://gist.github.com/karpathy/442a6bf555914893e9891c11519de94f?permalink_comment_id=6278138#gistcomment-6278138
+[197] -
+[200] -
+[201] https://gist.github.com/gowtham0992
+[202] https://gist.github.com/gowtham0992
+[203] https://gist.github.com/karpathy/442a6bf555914893e9891c11519de94f?permalink_comment_id=6281820#gistcomment-6281820
+[204] https://private-user-images.githubusercontent.com/15722259/627599374-f5711fac-cec4-464c-b847-da9bfb077c6a.gif?jwt=eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3ODU4MjEyOTIsIm5iZiI6MTc4NTgyMDk5MiwicGF0aCI6Ii8xNTcyMjI1OS82Mjc1OTkzNzQtZjU3MTFmYWMtY2VjNC00NjRjLWI4NDctZGE5YmZiMDc3YzZhLmdpZj9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNjA4MDQlMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjYwODA0VDA1MjMxMlomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPTE2MTg2Mzc5OGNhYmY4Zjk3MmIwMDFmNDhiODllOTk4ZmVkZWU5YTY5OGIzMzM1OGI4YjY3ZTJhNzY2ODBkZTEmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0JnJlc3BvbnNlLWNvbnRlbnQtdHlwZT1pbWFnZSUyRmdpZiJ9.37-hN6kHMCo63WKi1_b42bcCrMhSiX1A1CXkbe4Ogw0
+[205] https://private-user-images.githubusercontent.com/15722259/627599063-7cac41f4-6fbb-4e44-bcd1-7c37221c26dd.png?jwt=eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3ODU4MjEyOTIsIm5iZiI6MTc4NTgyMDk5MiwicGF0aCI6Ii8xNTcyMjI1OS82Mjc1OTkwNjMtN2NhYzQxZjQtNmZiYi00ZTQ0LWJjZDEtN2MzNzIyMWMyNmRkLnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNjA4MDQlMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjYwODA0VDA1MjMxMlomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPWQyZTliMzgxZjNmMGZkZjQwMzE3YzY0MGE3ZDgzNDdhMzc1NDY0NDhmMzJjNzNiNjAzNDQyMGUyNTEwMDkwOGQmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0JnJlc3BvbnNlLWNvbnRlbnQtdHlwZT1pbWFnZSUyRnBuZyJ9.2hvJrn4qDA9u_zh9Fy94tPAzY3FUNKoFJwhPsjZozVM
+[206] https://github.com/gowtham0992/link/releases/tag/v2.0.0
+[207] https://github.com/gowtham0992/link
+[208] https://gowtham0992.github.io/link/
+[209] https://pypi.org/project/link-mcp/
+[210] https://registry.modelcontextprotocol.io/?q=io.github.gowtham0992%2Flink
+[213] -
+[214] https://gist.github.com/XBlueSky
+[215] https://gist.github.com/XBlueSky
+[216] https://gist.github.com/karpathy/442a6bf555914893e9891c11519de94f?permalink_comment_id=6284110#gistcomment-6284110
+[217] https://github.com/XBlueSky/cortexes
+[218] https://github.com/XBlueSky/cortexes
+[219] https://cortexes.pages.dev/
+[222] -
+[223] https://gist.github.com/GeraldGrootRoessink
+[224] https://gist.github.com/GeraldGrootRoessink
+[225] https://gist.github.com/karpathy/442a6bf555914893e9891c11519de94f?permalink_comment_id=6284539#gistcomment-6284539
+[228] -
+[229] https://gist.github.com/suwonleee
+[230] https://gist.github.com/suwonleee
+[231] https://gist.github.com/karpathy/442a6bf555914893e9891c11519de94f?permalink_comment_id=6284942#gistcomment-6284942
+[232] https://github.com/suwonleee/llmwiki
+[233] https://raw.githubusercontent.com/suwonleee/llmwiki/main/assets/social-preview.png
+[236] -
+[237] https://gist.github.com/antondziatkovskii
+[238] https://gist.github.com/antondziatkovskii
+[239] https://gist.github.com/karpathy/442a6bf555914893e9891c11519de94f?permalink_comment_id=6285217#gistcomment-6285217
+[240] https://github.com/Palo-Alto-AI-Research-Lab/sqlite-graph-memory
+[241] https://github.com/Palo-Alto-AI-Research-Lab/verbatim-citation-gate
+[244] -
+[245] https://gist.github.com/Nikalo71
+[246] https://gist.github.com/Nikalo71
+[247] https://gist.github.com/karpathy/442a6bf555914893e9891c11519de94f?permalink_comment_id=6286837#gistcomment-6286837
+[250] -
+[251] https://gist.github.com/JanYork
+[252] https://gist.github.com/JanYork
+[253] https://gist.github.com/karpathy/442a6bf555914893e9891c11519de94f?permalink_comment_id=6288782#gistcomment-6288782
+[254] https://github.com/JanYork/llm-wiki-cli
+[257] -
+[258] https://gist.github.com/Nikalo71
+[259] https://gist.github.com/Nikalo71
+[260] https://gist.github.com/karpathy/442a6bf555914893e9891c11519de94f?permalink_comment_id=6289081#gistcomment-6289081
+[263] -
+[264] https://gist.github.com/Nikalo71
+[265] https://gist.github.com/Nikalo71
+[266] https://gist.github.com/karpathy/442a6bf555914893e9891c11519de94f?permalink_comment_id=6289082#gistcomment-6289082
+[267] https://github.com/JanYork/llm-wiki-cli
+[270] -
+[271] https://gist.github.com/alexadamus77-ui
+[272] https://gist.github.com/alexadamus77-ui
+[273] https://gist.github.com/karpathy/442a6bf555914893e9891c11519de94f?permalink_comment_id=6290598#gistcomment-6290598
+[274] https://scholarapi.net/
+[277] -
+[278] https://gist.github.com/gowtham0992
+[279] https://gist.github.com/gowtham0992
+[280] https://gist.github.com/karpathy/442a6bf555914893e9891c11519de94f?permalink_comment_id=6294542#gistcomment-6294542
+[281] https://private-user-images.githubusercontent.com/15722259/630686175-a04ed73d-5419-4cd8-aa72-d25357aeec87.png?jwt=eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3ODU4MjEyOTIsIm5iZiI6MTc4NTgyMDk5MiwicGF0aCI6Ii8xNTcyMjI1OS82MzA2ODYxNzUtYTA0ZWQ3M2QtNTQxOS00Y2Q4LWFhNzItZDI1MzU3YWVlYzg3LnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNjA4MDQlMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjYwODA0VDA1MjMxMlomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPTlmZTdlMzljYTIzOGIwZmE4YWI0Y2JjZGFmYmE1NDY5MmNjYmNmNjg0ZGQyNzllNjhjYWNlYWU5OWVhMzM4ZTQmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0JnJlc3BvbnNlLWNvbnRlbnQtdHlwZT1pbWFnZSUyRnBuZyJ9.5G2DQYmD0w1iFKy321Nyt-f9fCEvIr31aUZm0lej598
+[282] https://private-user-images.githubusercontent.com/15722259/630686425-35cd9bcd-87e1-4aed-9652-0f80562294f1.png?jwt=eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3ODU4MjEyOTIsIm5iZiI6MTc4NTgyMDk5MiwicGF0aCI6Ii8xNTcyMjI1OS82MzA2ODY0MjUtMzVjZDliY2QtODdlMS00YWVkLTk2NTItMGY4MDU2MjI5NGYxLnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNjA4MDQlMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjYwODA0VDA1MjMxMlomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPWRhNzY4NTM3NmM1ODgzMGExMDRkZmJlNWMzZjE5ZDE1ODM0NjIzZjc5ZjAxM2M5NjY0MDk3ZDAzOGUxMTczZWYmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0JnJlc3BvbnNlLWNvbnRlbnQtdHlwZT1pbWFnZSUyRnBuZyJ9.ds9RgsEVPnnzUdsEG-j3kNLkaGtSDEucaPBdxN0m42A
+[283] https://github.com/gowtham0992/link/releases/tag/v2.1.0
+[284] https://github.com/gowtham0992/link
+[285] https://gowtham0992.github.io/link/
+[286] https://pypi.org/project/link-mcp/
+[287] https://registry.modelcontextprotocol.io/?q=io.github.gowtham0992%2Flink
+[288] https://github.com/gowtham0992/link/blob/main/benchmarks/RESULTS.md
+[291] -
+[292] https://gist.github.com/mas213
+[293] https://gist.github.com/mas213
+[294] https://gist.github.com/karpathy/442a6bf555914893e9891c11519de94f?permalink_comment_id=6295034#gistcomment-6295034
+[295] https://gist.github.com/karpathy/442a6bf555914893e9891c11519de94f?permalink_comment_id=6237886#gistcomment-6237886
+[296] https://github.com/jessicayoung12
+[297] https://orangepro.ai/blog/fable-vs-orangepro
+[298] https://github.com/OrangeproAI/orangepro-mcp
+[301] -
+[302] https://gist.github.com/BackendGameSetMatch
+[303] https://gist.github.com/BackendGameSetMatch
+[304] https://gist.github.com/karpathy/442a6bf555914893e9891c11519de94f?permalink_comment_id=6295163#gistcomment-6295163
+[305] https://github.com/BackendGameSetMatch/sourcebook
+[308] -
+[309] https://gist.github.com/join?source=comment-gist
+[310] https://gist.github.com/login?return_to=https%3A%2F%2Fgist.github.com%2Fkarpathy%2F442a6bf555914893e9891c11519de94f
+[311] https://github.com/
+[312] https://docs.github.com/site-policy/github-terms/github-terms-of-service
+[313] https://docs.github.com/site-policy/privacy-policies/github-privacy-statement
+[314] https://github.com/security
+[315] https://www.githubstatus.com/
+[316] https://github.community/
+[317] https://docs.github.com/
+[318] https://support.github.com/?tags=dotcom-footer
diff --git a/static/archive/ludic-mataroa-blog-ss5swh.txt b/static/archive/ludic-mataroa-blog-ss5swh.txt
@@ -0,0 +1,641 @@
+[1]Ludicity
+
+AI Mania Is Eviscerating Global Decision-Making
+
+Published on July 18, 2026
+
+Note: This has been cross-posted to my company's blog, in case you think there
+is some use in sharing with someone in a format that looks more authoritative.
+Link [2]here.
+
+    I strongly believe there are entire companies right now under heavy AI
+    psychosis and it’s impossible to have rational conversations with them
+    about it. I can’t name any specific people because they include personal
+    friends I deeply respect, but I worry about how this plays out.
+
+    – [3]Mitchell Hashimoto, of HashiCorp and Ghostty fame
+
+Over the past year, I’ve run point on all of our company’s sales, led the
+technical components of all but two of our engagements, and over the lifetime
+of this blog have had something like 300 catchups with professionals from
+around the world. This has ranged from people on the ground in niche service
+industries to executives at Fortune 500 companies^[4]1. Because of this, I've
+had a front-row view to our collective institutions across both the private and
+public sector undergoing breath-taking mass psychosis. This essay is an attempt
+to describe the bizarre dynamics that are currently at play, as I am in the
+rare position where my wellbeing is not contingent on paying lip service to
+madness, and to reassure the people trying to survive amidst all of this that
+they are not crazy.
+
+The reality is thus: the people in charge either have no plan, or see no path
+forwards other than keeping their heads down. Not at banks, not at hospitals,
+not in our government institutions. The world’s organisations have been
+captured by people in the throes of frothing excitement, and saner people who
+now live in a state of constant commingled fear and frustration.
+
+I. AI Investments Are Generally Total Failures
+
+    Reading this while working for a division that pivoted to provide
+    interfaces for agentic workflows, only to discover that only ten users had
+    ever touched the products we made for agents, only to pivot again to
+    support for agentic workflows, which has a lot of competition because every
+    company has to do something agentic now and there's only like four things
+    you can do in that space, is bracing.
+
+    – An editor of this essay
+
+Are companies actually seeing massive productivity gains from their AI
+adoption? Does any of this sordid affair make sense?
+
+This should be an easy question, but it is surprisingly hard to get a straight
+answer to it. Executives that tell the press that their company has gone insane
+will quickly find themselves removed from their positions. Employees who are
+honest will find themselves fired in short-order, or “randomly” selected for a
+round of layoffs. In fact, it is in the interests of almost every actor in the
+space – boards, executives, employees, vendors, consultants – to obfuscate and
+misrepresent the success rate of AI projects. Many publicly traded companies
+are putting out announcements about their AI productivity gains when I know for
+a fact that the businesses have done nothing other than purchase Copilot
+licenses and declare victory.
+
+Yet we need to know if these projects are panning out – if the total focus on
+AI as a core tenet of business strategy is succeeding at a reasonable rate,
+then a discussion about the relative risk and reward is warranted.
+
+Unfortunately, we live in a dark timeline. All of the AI projects we have
+observed as a team are failing. Every single one – we have seen 0% success in a
+year and a half, not only amongst projects we have been asked to participate in
+^[5]2, but even within projects that we have observed in passing while doing
+totally unrelated work. Even if you grant that AI tooling accelerates specific
+workloads, the method and scale of the current investments is senseless.
+Frequently the failure is not related to AI itself, but rather that companies
+are terminally bad at running software projects effectively, and as [6]I have
+remarked previously, AI projects are subject to all the failure modes of normal
+projects plus you can get everything right and then still fail because of the
+method's novelty. Very few companies are so good at shipping software that they
+can afford the extra risk profile.
+
+Often enough, though, it’s an actual failure in what LLMs can accomplish. The
+most common version of this, being rolled out across businesses around the
+world, is the internally-facing chatbot, or for the more daring company, the
+customer-facing chatbot. The story is always the same. For the former, I’ve
+never seen substantial internal uptake from inside a business. Employees don’t
+use internal chatbots because companies tend to have low-quality documentation
+and an LLM is not psychic – it can only know things that have been written down
+and made accessible. For the latter customer-facing applications, I have rarely
+had a pleasant experience as a consumer, with perhaps the exception of live
+transcription during medical appointments – hardly something worth pivoting an
+entire organisation around. In both cases, project leaders are very careful to
+avoid tracking basic metrics, such as whether the tools are being used at all,
+or they track metrics that are easily gamed.
+
+For example, my last consumer interaction was attempting to get help from
+Mitsubishi following an automotive failure, where a very polite robot asked me
+to describe the problem and that I’d receive a call back as soon as someone was
+available. This was the single most competent implementation of such a project
+I’ve seen in the wild, in that the voice was natural sounding, responded
+quickly, was clearly “live” in production, and promised a swift resolution.
+
+That was six months ago, and I did not, in fact, get a call back.
+
+When Mitsubishi did not call me back, what happened? Did that request just go
+into the void, showing one less incident for the year? Does it appear that the
+phone bot resolved my query without the need for human intervention? All we
+know is that it didn’t show up as an error, or I’d have received a call. I’m
+sure it looks great in all sorts of ways except the one that matters, which is
+that I was planning to buy a car and decided not to buy another one of theirs.
+
+For this reason, our team has quickly learned while on an engagement not to ask
+anything about ongoing AI projects in any context – by the time that project
+has started, it is too late for the management team, and intervention is not
+possible until a crisis point is inevitably reached. There is no conceivable
+positive outcome. The failure rate is so high that even basic inquiry leaves us
+in an untenable position. Any coherent question about how it’s going, what the
+goal is, who is using it, constitutes an inadvertent attack on the chain of
+command responsible for the work because there are no good answers to anything.
+Even in rare cases where my interlocutor has stated that things are going well
+(usually while the project is still mid-flight and failure has not had a chance
+to manifest), it is generally obvious that they are doomed, but at least in
+these cases I can simply agree and then go home to scream into a pillow for six
+hours straight^[7]3.
+
+All of this is to say that I am very confident that almost every report at a
+company about “massive AI productivity gains” is untrue as a matter of brute
+fact. Even if some companies are seeing clear gains, this is the exception, not
+the norm. With that assumption in place, we can talk about the dynamics at
+play, and how it has become impossible for many organisations to stay focused
+on things that actually matter to their long-term (or even short-term) health.
+
+II. Heretics Will Be Shot
+
+It has become outright dangerous to even raise the possibility that AI might
+not be the solution to a problem, let alone be the sole focus of a company’s
+entire strategy.
+
+In every sufficiently large business we have observed (say, with 500+
+employees), we have noted that continued advancement, and increasingly
+continued employment, has started to require repeated professions of belief in
+the transformative power of AI for said business. I am not talking about
+providing ideas about how to use AI in the business – I mean religious
+profession, declarations of faith. Overwhelmingly these statements are made by
+non-technicians, though it is not uncommon for technicians to emit deranged
+statements to curry favour.
+
+There have been several occasions where I have seen someone, apropos of
+nothing, blurt out almost word-for-word “AI is changing everything”, only to
+concede moments later that their organisation does not currently use LLMs for
+anything, and indeed, that they cannot name a single thing that has changed
+other than they get some use out of ChatGPT (frequently the free-tier). In one
+extreme case, I have seen an executive confess that they had never even used
+ChatGPT or any AI tool in their life, immediately after producing a technical
+strategy for an organisation with $2B+ in revenue which was entirely centered
+around AI.
+
+Initially these statements were so absurd on their face that I thought it was
+some cynical ploy to achieve thought leader status, and there are certainly
+some people doing this – I have had it admitted to me. But the broader reality
+is so much worse: people who have no background in the technology at all
+actually believe what they are saying. As a general rule you should avoid
+getting into business with a liar, but if you must, you can at least reason
+with them even if only in private. A true believer is much more threatening
+because they are impervious to even inducement by self-interest.
+
+The turning point in my belief was watching someone with a spectacular amount
+of money on the line fire their highest performers because they were achieving
+that performance without LLMs. When an employer publicly talks about AI
+innovation, we have to ask ourselves if they’re simply trying to manipulate the
+market or customers. When they privately commit to strategies like this with
+their own money at stake, with no attempt to communicate that strategy to
+external clients, I can only assume they really mean what they’re saying.
+
+A while ago, I wrote [8]“Contra Ptacek’s Terrible Article On AI”, which was
+focused on the fact that many of Ptacek’s points in his own essay [9]“My AI
+Skeptic Friends Are All Nuts” were internally inconsistent^[10]4. But on the
+crux of the matter, we are actually in total agreement, because he opens his
+essay with this:
+
+    Tech execs are mandating LLM adoption. That’s bad strategy.
+
+Which is to say that we can sidestep arguments about the precise utility of
+LLMs entirely and we’re left in a very simple place – it is entirely obvious to
+both myself and Ptacek, two people that are coming at this from fairly opposed
+views, that people are being really, really stupid about this, and that
+organisations are demanding bizarre workflow constraints from their specialist
+staff.^[11]5
+
+These mandates have led to extremely strange places. Several of my peers now
+“AI-wash” their work, meaning that even when they can perfectly competently
+execute on their jobs to the satisfaction of their management teams, said
+managers are unhappy if the engineers haven’t used AI in the work… so now
+they’re lying about using LLMs even in contexts where their professional
+judgement is that they aren’t the appropriate tool. They just do the work, the
+same way they have for decades, and say Claude did it. Others are being
+measured on their AI bills with “token leaderboards”, where higher is better
+because I have evidently fallen into the pocket of Hell where the demons
+torment me by doing elaborate impressions of absolute fucking morons, so the
+people hired for their freakish ability to perform system optimisation do the
+obvious thing. They set the LLMs prompting themselves in a semi-plausible loop
+in case someone inspects the token consumption and then they watch Netflix. Not
+a single one has been caught, even when their own assessment of the output is
+that it isn’t suitable for deployment.
+
+    Checking out a parallel copy of our Go repository and telling the AI to
+    rewrite the whole thing in Zig while I work on something else just so I can
+    keep my job. I hate this shit so much. My job has usage tracking and
+    quotas. I don’t use it for actual work, I just spin it up and disregard the
+    output.
+
+    – An actual software engineer
+
+In fact, the only people I know of to be fired over this whole thing are people
+that have expressed visible doubt about this organisational strategy, which
+again, even Ptacek thinks is transparently dumb. The net result is that
+everyone has learned very quickly to praise executives on their visionary AI
+prowess, or they will be gunned down in the proverbial streets.
+
+III. AI Demos Are The Mind-Killer
+
+Bless me, Father, for I have sinned. It has been ∞ days since my last
+confession. I accuse myself of the following sins:
+
+One of the main pieces of infrastructure we deploy at our clients is an
+analytics-focused database called Snowflake – for a typical business, the bill
+is tiny because it’s a pay-as-you-go situation and we can process all their
+data in one minute a day, you get a very hands-off deployment, and in short it
+has many characteristics that are very pleasant for our work. One of the
+features in Snowflake that we don’t use is called Cortex.
+
+Cortex is their AI chatbot layer, with the ability to plug into metadata (for
+non-nerds, descriptions of your data, like what a column in a spreadsheet
+means) and query a company’s database autonomously. In theory, you can ask a
+question like “What was our revenue for last week?” and it will spit out an
+answer.
+
+It is not really suitable for production usage. From memory, the last time I
+was given a presentation on it, by actual Snowflake staff, they reported that
+ideal configuration results in something like ~92% accuracy due to the
+complexity of data at a large business (see: probably best-in-class for these
+tools, but imagine your CFO having one in every ten of their numbers be
+outright wrong) and there were serious issues with managing deployments.
+Nonetheless, it can be used to produce some very flashy demonstrations.
+
+On several occasions, we’ve been exposed to folks that have been sort of
+lukewarm on our main offerings, but they really, really wanted to use AI to
+perform a natural language query on their data. And we thought “Okay, if you
+really want to see it, maybe we can caveat this appropriately and show you what
+it might look like.”
+
+This was a terrible mistake. It backfired in the most predictable way
+imaginable – every lukewarm client that saw the chatbot in action, even with us
+telling them that it was not going to accomplish what they wanted, wanted to
+buy it immediately. Every other consideration, including millions of dollars
+that we could plausibly help them achieve by non-AI means, was swept aside. It
+was like a dark and terrible force seized control of their limbs, plunged their
+hands into their own chests, and presented their still-beating credit cards to
+us in grim supplication. We were so mortified by the inexplicable shift in
+energy that we (wisely) declined to take the money and ended the sales process,
+and soon thereafter removed Cortex from our list of demonstrations. It would
+have been too irresponsible to exploit this gap in their reasoning, and
+frankly, it was already irresponsible to have even run the demonstration –
+doctors don’t walk around showing off cool pills that they’d never prescribe.
+
+Watching the total 180°, that shift from ice-cold to red-hot buying frenzy, was
+a deeply unsettling experience. It was personally uncomfortable to see people
+that clearly didn’t gel with us interpersonally suddenly dying to enter an
+ongoing relationship, but more broadly uncomfortable because for a brief moment
+I began to understand what is happening in sales meetings around the world.
+There was no warning I could have given that would have made them refuse to buy
+the damn thing – their appetite was as large as their budget could stretch, and
+some part of me wonders if this is because they knew that their ravenous hunger
+would be present in their own customers. They’d just buy it from us, then pivot
+right to a larger company and mind control their leadership team until the buck
+finally stops with the loser that needs to justify the expense. The main
+protection against this seems to be that the median vendor is [12]so bad at
+their jobs that we had presented the first even somewhat-working products these
+people had seen, and this included an ASX-listed company that was already
+bragging about their AI usage. It took our team two hours to produce something
+that was frankly not that good – basically just typing text descriptions of
+data into a web browser – and it was still better than anything the leads had
+seen because they had nothing to show for all the investment.
+
+In fact, we have been forced to opt out of every sale where the lead has
+expressed anything beyond the most fleeting curiosity in the use of AI in their
+business. I don’t mean that we’ve heard that they’re interested in AI and
+elected to drop the contract on moral grounds. I mean that, over the course of
+the engagement, these people have exhibited a pattern of behavior that has made
+it near-impossible to sell to them without incurring reputational and legal
+risk, and are furthermore crafting management environments that I can only
+describe as cultish, ineffective, and “please dear God, do not let it be on
+earth as it is on LinkedIn”.
+
+IV. Executives, Game Theory, and The Emperor’s Clothes
+
+    The good news is, CISOs are used to having to protect the business from
+    their hare-brained initiatives, and this one isn’t really that different,
+    except that there’s a cult-like atmosphere to it that you didn’t see with,
+    say, the cloud. It almost doesn’t matter whether you embrace the initiative
+    or not; there’s work to be done to manage the risk, so that’s what you do.
+    From talking to CISOs everywhere, I would say most of them are quietly
+    skeptical but afraid to speak up.
+
+    – Career CISO and well-known speaker that asked to remain anonymous
+
+Despite the substantial prevalence of true believers, many of the people
+running large AI initiatives, or making public statements about them, do not
+believe what they are saying. There are “heads of AI” who read this blog, at
+companies with $1B+ in annually recurring revenue, who have written in to say
+they believe their job is totally fraudulent but it was the only promotion
+pathway remaining at the organisation.
+
+On a trip overseas, I had the privilege of a meeting with one of the Fortune
+500 executives mentioned at the beginning of the post, who will remain
+anonymous so that they are not executed by firing squad by their board. As we
+were chatting, it became clear that they were very switched-on and technically
+competent, and they also happened to be at a company that had committed to the
+usual battery of exorbitant claims about their recent innovations – we’ve
+100x’d our productivity, AI is the future of everything, I am but a vessel for
+OpenAI to make love to my wife. You know, normal things. But since I had them
+there without any microphones around, I asked why this was being repeated
+without opposition. Was it just sales fluff?
+
+The answer was a lot more interesting. It was partially ridiculous sales
+material being delivered to an easily excitable audience, but this was not the
+dominant factor constraining honesty. Executives at their customers were saying
+absurd things about achieving 100x productivity, and this meant that if any
+executive at the vendor said that these gains were not plausible, it would
+undermine the credibility of the customer’s executive, be perceived as an
+attack (or heresy), and possibly result in an enterprise contract cancellation.
+And getting enterprise contracts cancelled because you wanted to opine on
+something that doesn’t really matter to your organisation’s mission is a great
+way to get fired.
+
+But this company was also a major player, of the kind that signs enormous
+enterprise contracts with other companies. So presumably there is another
+vendor that has sold to them, and their CEO is worried that saying something
+sane will contradict this executive, and very quickly we can see how we can
+have executives around the world nervously pointing guns at each other, not
+wanting to be shot first but also watching everything gradually spiral out of
+control^[13]6. This is to say that we’re facing a [14]coordination problem
+around executives being honest around the AI gains they’ve witnessed – if they
+co-operate, they keep their jobs. If they defect, they will possibly be fired
+by their embarrassed peers (who have now been implicitly called liars, cowards,
+or incompetents) and then replaced with someone that will toe the line anyway.
+If they could all admit the truth at once there might be some hope, but there
+is no way to coordinate that event.
+
+This sounds deeply concerning, but it is worth noting that it means that some
+executives who are emitting nonsensical statements are not as dull as they
+might seem at first – they’re in a fraught political environment, where they
+are surrounded by many people that are gunning for their roles, and subject to
+the whims of a board that is undergoing similar pressure. Against all the
+dictates of reason, I have presented on navigating AI hype to people on S&P 500
+boards^[15]7 and they are in exactly the same situation – the main comments I
+remember from the session were board members admitting they were skeptical, but
+expressing anxiety that their positions were contingent on demanding AI
+investment. One of them commented “investing this early seems like risk without
+much upside”. About two years later, I can see now that their decade-old
+multi-billion dollar organisation is now branded as “AI-native”, whatever the
+hell that means.
+
+V. You Must Be This AI-Native To Ride
+
+All of the above converges on the state that we find ourselves in now, where
+effective decisionmaking has ground to a halt. Collectively, what started as a
+few people undergoing either destabilising psychological events or being caught
+up in hype has now resulted in an environment where leaders cannot speak
+honestly about their beliefs on how best to guide organisations, for fear of
+being removed, creating a sort of distributed government by assassination. This
+means that the least sensible recommendations are going totally unchallenged,
+resulting in employees being evaluated on totally gameable metrics such as
+“money spent on AI”, and those employees must play along to avoid being
+terminated. This has also created an insatiable appetite for purchasing “AI”
+solutions, which target both true believers that will believe implausible
+claims, and also non-believers that cannot decline the purchases without having
+their commitment to the cause coming into question.
+
+This means that all offers that are subject to internal politics at an
+ideologically captured organisation must include AI alignment, even if the
+value proposition is patently ambiguous. My assessment of the market so far is
+that a substantial component of the outburst of AI projects are actually non-AI
+projects with an AI element slapped on after the fact to pass the purity test.
+
+For example, I recently witnessed an organisation handling a database migration
+from an Oracle database to Snowflake – instead of handling the migration
+directly, the vendor bolted on a preliminary phase which involved trying to get
+an LLM to automate the translation of the Oracle-flavored SQL to
+Snowflake-flavored SQL. When the project failed (due to issues getting enough
+permissions to automate the work, not because an LLM can’t do something that
+easy), the vendor simply started handling the translation by hand but the
+company billed it as an AI-driven success because some inconsequential portion
+of the SQL had been translated by AI before being pasted over.
+
+What was actually purchased? A totally standard database migration to help an
+executive meet the strategic deliverable of decommissioning a system prior to
+license renewal. What was sold to their superiors? “I allocated a substantial
+percentage of my budget to AI and it helped me accomplish my mandate.” True AI
+projects, of the kind that is driven by an LLM as the sole mechanism underlying
+it, where the project can clearly fail to deliver specific numbers, are
+actually very rare. We mostly see them in the context of startups, and frankly
+we have stopped engaging with them because we kept getting to the end of the
+sales conversation and finding out they wanted us to build the product that
+they were marketing as completed.
+
+However, some projects simply do not have an easy way to tack on the AI label,
+or the person advocating for them either does not want to lie or has not
+understood that lying has become necessary. In all cases, this either kills the
+request for funding outright, or adds a pervasive and intractable drag on all
+communications, as every request must be worked and re-worked until it is “AI
+enough”. Failure to comply will either result in denial or, in many cases, a
+demand from a true believer to know why the extra work “can’t be done with AI”.
+Many companies have actively publicized that this is their new hiring policy –
+when a member of staff requests additional headcount, they must demonstrate
+that they have tried to use AI first. The part that’s being left out is that if
+you say you used AI and still need the help, you will be labelled “bad at AI”
+and potentially laid off.
+
+The net result of this is that almost every large organisation that I am aware
+of is no longer able to focus on anything important, unless they are one of the
+(very) few organisations where AI happens to address their highest priorities.
+They cannot buy sensible software, hire competent talent, communicate honestly
+with executives about the state of projects, or undertake any sort of sensible
+initiative.
+
+VI. Navigating AI Mania
+
+    An emptiness falls through you
+    As you realize what this means
+    You're starting to feel what I feel
+    Now you've seen what I've seen
+
+    – So Sick, Domesticated Incels
+
+This is an unfortunate situation to be in, but it will pass eventually. I’ve
+learned a lot about the latent insanity that we have inculcated in our
+leadership strata, and unfortunately those traits will persist long past the
+current bubble, merely awaiting another similar reactivation trigger – and some
+organisations will stay captured until they have totally collapsed, in the way
+that not everyone has successfully moved away from the dreadful blockchain
+affair. That’s something to write about for another time.
+
+What I wanted to get to were some thoughts on surviving the immediate crisis,
+either by directly making systemic improvements or by holding onto your sanity.
+I’ll start with the “making improvements” part, because that’s the situation I
+find myself in the most frequently.
+
+When You Have Another Objective
+
+We’re going to do a lot of sucking it up and smiling here. This section assumes
+that you are trying to achieve some goal that isn't repairing the
+organisation's manic stance, but either trying to course-correct a specific
+project (and possibly risk getting fired as either a leader or consultant) or
+achieve some totally unrelated goal.
+
+ 1. Where possible, when raising issues, do not have conversations about the
+    state of AI projects in group settings, as this creates a dynamic where
+    each individual member of the group is worried about outing themselves in
+    front of their peers. Arrange for one-on-one settings. Make it clear that
+    you are willing to countenance that the current AI environment is frothy,
+    and that you will keep opinions unidentifiable when raising them elsewhere.
+    Be extremely aware that the most outspoken people can be identified by
+    their peers, so take care to avoid exposing your sources by, e.g. direct
+    quotes. In the event that only a small minority (say, one person in a group
+    of six people) is willing to speak out, it might be worth giving up and
+    moving on to a patient that has better chances.
+ 2. For ongoing projects, an effective trick that I believe I picked up from
+    Secrets of Consulting is the anonymous poll, where you can ask individuals
+    to rate their opinion of an AI project’s success chances on a scale of 1 to
+    10. The typical split I have observed is half of those involved rating the
+    project at a 3/10 and others at around an 8/10 – a clear bimodal split on a
+    project that was already three years late. Bringing this data to a CEO can
+    be an effective method of pointing out that some information is clearly
+    being hidden from them on the state of the project.
+ 3. Always involve people on the ground. The only source of data on whether
+    projects are succeeding or the investment is going anywhere are the people
+    that use it for their day-to-day activity. Care must be taken to bring them
+    into the environment where they are treated with respect (all sufficiently
+    large companies have people that view subordinates as
+    not-quite-real-people). It is not uncommon to uncover worldview-shaking
+    information in short order – with one client, we uncovered that staff were
+    totally unaware they had been given licenses for AI tooling, which cast
+    into doubt all productivity claims.
+ 4. Do not question the broadest claims about AI. I cannot emphasize this
+    enough. If someone says “AI is changing everything”, just let it pass if
+    your goal is to fix an object-level problem rather than challenge the
+    reality at the institution. The challenge can only come after you have
+    gained the trust of the most senior person involved. Trust is gained over a
+    meal in private where you assuage their anxieties, not by embarrassing them
+    in front of peers.
+ 5. Remember that you do not know what statements have been emitted prior to
+    entering a room. There will sometimes be people that have publicly
+    committed to statements like “I am 100x more productive than I was last
+    year”, and some may even wish they hadn’t said that but are too embarrassed
+    to walk it back. In an untested room, common sense like “LLMs should not be
+    allowed to deploy code without human review” can kill your chances to make
+    an impact before you’ve even started.
+ 6. My practice requires me to maintain an honest relationship with my clients
+    or the whole thing falls apart, so I can’t do this – but honestly, if you
+    work in the fire service and need money to stop a puppy from catching fire,
+    just lie. It’s fine. History will forgive you. Add a $10,000 AI chatbot to
+    your project, exclusively discuss that part in meetings, whatever. Save
+    that puppy.
+
+When You're Just Trying To Survive
+
+This is for people that are just waiting for the bubble to burst and trying not
+to go nuts.
+
+ 1. I have bad news – accept that you are probably not going to meaningfully
+    push back on any of this. This is not a feature of AI, it’s a feature of
+    dysfunctional companies.
+ 2. If you feel like you’re going absolutely nuts, consider switching over to
+    contracting. I’ve advocated for contracting many times over full-time
+    employment, but you’ll get paid a lot more and be left out of most internal
+    politics. Also when you run into a really intolerable situation, you’ll
+    know that you’ve got a fixed end-date.
+ 3. I do my best to limit my uptake of AI-related news, as it is pretty
+    crazy-making and unproductive to consume. I no longer visit Hackernews,
+    Reddit, or really anywhere where I am going to be drip-fed nonsense, though
+    I allow myself exceptions for very funny things like [16]Apple suing OpenAI
+    over alleged corporate espionage. Consume exactly the amount you need to
+    feel like you aren’t going insane, then stop. Ditto for complaining with
+    friends – and tell them that’s why you’re talking about it, which buys a
+    lot of tolerance.
+ 4. When someone tells me they are using AI for something when they really
+    shouldn’t be, I smile and nod as long as they are unlikely to get
+    themselves killed. Even family. Especially family.
+ 5. When someone asks me for my opinion of AI as a programmer, I recommend
+    saying “Oh, that stuff is pretty overblown” and then changing the topic,
+    unless they are in a position where their opinion might influence something
+    important. Non-programmers need this guidance the most.
+ 6. If you’re being asked to review huge volumes of terrible AI code, just
+    assume that the organisation is going to burn you out and fire you. You
+    will not convince the person drowning you in 2000 line PRs to stop. Start
+    looking for a new job as if you have already been fired. I have seen this
+    happen many times now, and it always plays out the same way – do the job
+    search while you have energy. Don’t worry if your speed drops or management
+    gets annoyed at you. There is no way to avoid that, you can simply choose
+    whether it happens now because of your job search, or later because you are
+    too depressed to work anymore.
+ 7. If your manager is responding to you with clearly AI-generated text, use AI
+    to respond to save your sanity and then look for a new job. Many people
+    assume they will get in trouble for being that obviously rude. You will
+    not, this particular behavior is exhibited only by true believers, and they
+    actually like that you’ve clearly not bothered to engage with them. I know,
+    it’s fucking wild.
+ 8. If you’re being asked to max out on token usage, look for a new j – okay
+    look, you get it, right? Go find a job that isn’t going to wrench reality
+    from your tenuous grasp. They do exist, largely at companies so small that
+    they don’t turn up on job platforms. It might take months to find one, so
+    start now.
+
+Fight the good fight, and don’t let the bastards grind you down. Godspeed.
+
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+
+ 1. Also, and this is 100% true, Matt Mullenweg once asked me for coffee
+    because he read the [17]AI piledrive essay, and in context probably enjoyed
+    it, but had to cancel because he hadn’t realized he had a flight later the
+    same day. I am willing to pay a competent witch to hex him for this
+    slight. [18]↩
+
+ 2. We have rejected all AI implementation work. It is absolutely a gigantic
+    bubble and we have minimized our exposure to it – every single one of our
+    current contracts would be totally unaffected by OpenAI collapsing, save
+    for perhaps some second-order effects such a recession causing a client to
+    become unable to pay us. And there’s nothing we can do to insulate
+    ourselves from that anyway. [19]↩
+
+ 3. One of the most valuable rules I’ve heard, from Gerry Weinberg, is that
+    consulting is influencing people at their request. Unless someone has
+    indicated that they want us to stick my nose in, usually by explicitly
+    saying they want guidance on general data strategy, we just let the
+    projects fail in peace. You can barely recognize me, I’m so calm these
+    days. [20]↩
+
+ 4. We have since kissed and made up in private, though I don’t think we’ve
+    budged at all on the core points of our viewpoints. I maintain that Thomas
+    is [21]a very talented writer with a lot of good advice who just happened
+    to blow it massively that one time because he takes Hackernews commenters
+    too seriously. We all have our weaknesses. Mine is people telling me that
+    “Scrum is good if you do it right”. [22]↩
+
+ 5. This is always baffling to me as a matter of being a responsible adult. If
+    I was somehow CEO at a hospital or civil engineering firm, I would not for
+    a second think it’s my place to start mandating specific procedures or
+    building techniques without explicit agreement from the professionals on
+    staff – how fucking clueless are the non-technicians who have attended a
+    few talks and are now making mandates about how their extremely expensive
+    professionals are doing their jobs? [23]↩
+
+ 6. If you’re an executive, board member, or anyone in charge of an “AI
+    project” that feels trapped, I would love to hear from you. I will file the
+    serial numbers off any stories very carefully, as I’ve done here and in
+    every other article. [24]↩
+
+ 7. This sounds very fancy, but I think it was secretly one of those compulsory
+    professional development things and half the audience were just like,
+    making dinner. Truly, HR and professional bodies make victims of us all. 
+    [25]↩
+
+[26]← Previous
+○ [27] Epesooj Webring
+[28]Next →
+
+Subscribe via [29]RSS / [30]via Email.
+
+Powered by [31]mataroa.blog.
+
+
+References:
+
+[1] https://ludic.mataroa.blog/
+[2] https://hermit-tech.com/blog/ai-mania-is-eviscerating-global-decisionmaking
+[3] https://x.com/mitchellh/status/2055380239711457578?lang=en
+[4] https://ludic.mataroa.blog/blog/ai-mania-is-eviscerating-global-decision-making/#fn:1
+[5] https://ludic.mataroa.blog/blog/ai-mania-is-eviscerating-global-decision-making/#fn:2
+[6] https://ludic.mataroa.blog/blog/i-will-fucking-piledrive-you-if-you-mention-ai-again/
+[7] https://ludic.mataroa.blog/blog/ai-mania-is-eviscerating-global-decision-making/#fn:3
+[8] https://ludic.mataroa.blog/blog/contra-ptaceks-terrible-article-on-ai/
+[9] https://fly.io/blog/youre-all-nuts/
+[10] https://ludic.mataroa.blog/blog/ai-mania-is-eviscerating-global-decision-making/#fn:4
+[11] https://ludic.mataroa.blog/blog/ai-mania-is-eviscerating-global-decision-making/#fn:5
+[12] https://ludic.mataroa.blog/blog/the-worlds-left-to-conquer/
+[13] https://ludic.mataroa.blog/blog/ai-mania-is-eviscerating-global-decision-making/#fn:6
+[14] https://en.wikipedia.org/wiki/Prisoner%27s_dilemma#Real-life_examples
+[15] https://ludic.mataroa.blog/blog/ai-mania-is-eviscerating-global-decision-making/#fn:7
+[16] https://www.theguardian.com/technology/2026/jul/10/apple-sues-openai-trade-secrets
+[17] https://ludic.mataroa.blog/blog/i-will-fucking-piledrive-you-if-you-mention-ai-again/
+[18] https://ludic.mataroa.blog/blog/ai-mania-is-eviscerating-global-decision-making/#fnref:1
+[19] https://ludic.mataroa.blog/blog/ai-mania-is-eviscerating-global-decision-making/#fnref:2
+[20] https://ludic.mataroa.blog/blog/ai-mania-is-eviscerating-global-decision-making/#fnref:3
+[21] https://sockpuppet.org/blog/2025/02/09/fixing-illinois-foia/
+[22] https://ludic.mataroa.blog/blog/ai-mania-is-eviscerating-global-decision-making/#fnref:4
+[23] https://ludic.mataroa.blog/blog/ai-mania-is-eviscerating-global-decision-making/#fnref:5
+[24] https://ludic.mataroa.blog/blog/ai-mania-is-eviscerating-global-decision-making/#fnref:6
+[25] https://ludic.mataroa.blog/blog/ai-mania-is-eviscerating-global-decision-making/#fnref:7
+[26] https://akols.com/previous?id=ludic
+[27] https://akols.com/
+[28] https://akols.com/next?id=ludic
+[29] https://ludic.mataroa.blog/rss/
+[30] https://ludic.mataroa.blog/newsletter/
+[31] https://mataroa.blog/
diff --git a/static/archive/michaelharley-net-wa2rlv.txt b/static/archive/michaelharley-net-wa2rlv.txt
@@ -0,0 +1,351 @@
+[1]Skip to content [2]michaelharley.net [3](Menu) [≡] [×]
+
+  • [4][A]boutAbout
+  • [5][C]ontactContact
+  • [6][P]ostsPosts
+  • [7][S]itemapSitemap
+
+[8](Toggle light and dark theme) [9](Switch site skin) [10](Toggle modem-light
+animation)
+
+I own my books
+
+July 16, 2026 4 min read
+
+[11]Permalink
+
+I love reading. I caught the bug as a middle-schooler when I got caught
+skipping school, and as punishment, I had to read [12]The Chronicles of Amber
+(opens in a new tab) and do a book report about it. Even today, opening a book
+and fanning the pages to get the paper smell activates very fond memories and
+emotions.
+
+I remember a time before e-readers came out. I always thought reading on one
+seemed very futuristic. In military sci-fi books, characters are reading on
+their data pads, and reading on an e-reader makes me feel like a sci-fi
+character.
+
+Physically, e-readers are superior in every way to paper books. I can increase
+the font size. I can increase brightness. I can read in the sun. I can read in
+the pool. My entire library fits into my pocket. I can look up the definitions
+of words.
+
+Capitalists really hate when consumers love something, so of course they want
+to ruin e-readers. They do that by implementing digital rights management
+(DRM), and making people agree to draconian agreements such that the books they
+"buy" are in fact just renting. They want to lock you into their device
+ecosystem and force you to buy their hardware. That makes it very hard for
+consumers to buy a device from a different manufacturer as they basically have
+to abandon their digital libraries to do so.
+
+All that to say, I can understand why some people just do not want to deal with
+fighting with e-reader companies like Amazon so they might prefer paper books.
+I am up for the challenge though, and here is how I avoid the obstacles and
+hurdles that these companies put in the path to consumer choice and freedom.
+
+Removing DRM [13]#
+
+The most important thing to ebook freedom is removing the DRM the companies put
+on the books. I wrote about [14]how I remove DRM for backup purposes so I won't
+rehash that here, but the main thing is buying your ebooks from a distributor
+other than Amazon. I buy mine from [15]eBooks.com (opens in a new tab) and [16]
+Kobo.com (opens in a new tab) as they distribute their books with Adobe DRM,
+which the right tools can remove.
+
+I do not remove DRM so I can give my books away. I remove DRM so I have a
+backup of the books I paid for.
+
+This isn't paranoia. In 2019, [17]Microsoft shut down its ebook store (opens in
+a new tab), and because the books were DRM'd, every book every customer had
+ever bought simply stopped opening when the DRM servers went dark. Microsoft
+refunded everyone, which is a tidy admission that those were never really
+sales. A decade earlier, [18]Amazon reached into people's Kindles and deleted
+copies of 1984 (opens in a new tab) that they had already paid for, taking one
+[19]student's homework notes (opens in a new tab) along with the book. Not
+great, Bob.
+
+So I backup my books to an open standard, [20]ePUB (opens in a new tab), with
+the DRM stripped off. If eBooks.com folds tomorrow, or Kobo decides my account
+is a problem, or I want to read on hardware nobody has invented yet, my library
+still works.
+
+I don't care what their fine print says. I bought this book. It's my book. I'll
+read it where I like, TYVM.
+
+But what about Amazon exclusives? [21]#
+
+I want to support authors. I do not want to support anti-consumer choice
+cartels by giving them money.
+
+I remember back when Amazon first started, and they allowed smaller authors to
+self-publish their books. Back then, Amazon was the small guy, and it allowed
+other small guys to avoid the big book publishers. That was a right and good
+thing.
+
+But now, Amazon locks its exclusives behind the superior Amazon DRM and I don't
+know how to create DRM-free backups with the tools I have access to. So in the
+rare instance that I must purchase a book from Amazon, then I'll hold my nose
+and give Jeff Bezos my money. What happens after that, and how the book ends up
+readable on my Kobo, is left as an exercise for the reader.
+
+Audiobooks [22]#
+
+The same fight plays out with audiobooks, except here the landscape is still
+favorable to the consumer. My preference is [23]Libro.fm (opens in a new tab),
+who sells audiobooks DRM-free from the start. And you can strip even Audible's
+DRM, so nothing I buy is ever really locked inside their app.
+
+Same rule as my books: I paid for it, so I keep a copy I control. The medium
+changes; the principle doesn't.
+
+I'll sign off this post with a quote.
+
+    Any time someone puts a lock on something that belongs to you and won't
+    give you the key, that lock isn't there for your benefit.
+
+    Cory Doctorow, [24]Information Doesn't Want to Be Free (opens in a new tab)
+
+Michael Harley Michael Harley [25]Author
+Filed under: [26]Books [27]Calibre [28]eBooks
+
+Also on [29]Mastodon (opens in a new tab) [30]Bluesky (opens in a new tab)
+
+You may also like
+
+  • [31]How to setup Calibre to remove DRM from ebooks on Linux January 10,
+    2023
+  • [32]How I self-host my ebooks and audiobooks July 21, 2026
+  • [33]On ebook readers and why I am opting out of vendor lock-ins March 09,
+    2022
+
+Signal
+
+[34](Like this post) like
+21 likes
+
+  • [35] TheNovemberFella ✊🏳️‍🌈 🇺🇦☸️🛰️🚀
+  • [36] PurpleJillybeans :PrideDisk:
+  • [37] Ronsboy67
+  • [38] Alexander Corby 🇵🇷
+  • [39] BookShelves eBook Reader
+  • [40] Feral 3D
+  • [41] Wojtek Powiertowski
+  • [42] Pablonius Monk 🇺🇦
+  • [43] Jeremy
+  • [44] Kᑐᑌᑐᕮ
+  • [45] Nick East (Indie Writer)
+  • [46] richlinville.bsky.social
+  • [47] Kevin Gallant
+  • [48] alex
+  • [id]
+  • [id]
+  • [id]
+  • [id]
+  • [id]
+  • [id]
+  • [id]
+
+4 boosts
+
+  • [49] Ronsboy67
+  • [50] Pablonius Monk 🇺🇦
+  • [51] Jeremy
+  • [52] Kᑐᑌᑐᕮ
+
+1 mention
+
+  • [53] Bubbles (opens in a new tab)
+
+[54] 34 votes on Bubbles 🫧 (opens in a new tab)
+
+3 Comments
+
+mloxton
+
+[55]mloxton (opens in a new tab) via Mastodon Jul 16, 2026
+
+[56]@michaelharley (opens in a new tab)
+
+I get all the points you make, but that same picture looks a lot different from
+the author's perspective.
+
+There is also a transaction issue with your argument.
+The price of a book may vary according to what rights come with it. Using
+fictional numbers for illustration.
+
+Full rights: $50,000
+Right to read forever on any device: $50
+Right to read on a specified device $5
+Right to read on a specified device for a specified time: $1
+
+A
+
+[57]Antonio Santos (opens in a new tab) via antoniosantos.io Jul 16, 2026
+
+I regret not taking a similar approach to Michael Harley sooner. I always
+thought it didn't matter if I bought my books on Apple Books, because I would
+always have an iPad to read them on, until I bought a Kindle and wished I could
+read my books on my Kindle.
+
+Somehow, I let myself fall into the same trap with my Kindle, and now I'm
+locked into reading my books on a Kindle (at least there's a Kindle app for
+iOS).
+
+Recently, I started thinking about where I buy my e-books from for the same
+reasons as Michael: I want to be able to take my books with me anywhere, and
+back them up in case the provider goes away. So now I try to find DRM-free
+alternatives, like buying e-books straight from the author, or shopping on
+DRM-free platforms. I haven't tried removing DRM from books yet, not sure if I
+want to go thru the hassle.
+
+I also started doing the same for movies. Instead of buying them digital, I
+started buying physical copies. Eventually, I might get a Blu-Ray R/W and make
+digital copies for myself.
+
+Kᑐᑌᑐᕮ
+
+[58]Kᑐᑌᑐᕮ (opens in a new tab) via Mastodon Jul 17, 2026
+
+[59]@michaelharley (opens in a new tab) re:
+> "So in the rare instance that I must purchase a book from Amazon, then I'll
+hold my nose and give Jeff Bezos my money."
+
+I have a different approach: i always buy the **physical** book (which supports
+the author more, than buying any e-book) and then i simply download the `.epub`
+for free from... that 1 library that provides almost all e-books for free 🤷🏼‍♂️
+
+Join the conversation
+
+  • [60]Respond via email
+  • Leave a comment
+
+    Your email is never shown. It's only so I can reply, and comments are
+    moderated before they appear.
+
+    Name * [61][                    ] Email (optional, private)
+    [62][                    ] Website (optional, sets your avatar from your
+    h-card) [63][                    ]
+
+    Supports basic Markdown (bold, italic, links, lists, quotes). It's rendered
+    to HTML once the comment is approved.
+
+                  [                    ]
+                  [                    ]
+                  [                    ]
+    Comment * [64][                    ]
+    Leave this field empty [65][                    ]
+    [69]Post comment
+    or comment as yourself
+
+    Have your own website? Sign in with it via [70]IndieAuth (opens in a new
+    tab) and your name and avatar are pulled from your h-card. Nothing to fill
+    in.
+
+    Website [71][                    ] [73] Sign in with your website
+  • Send me a webmention
+
+    Written a response on your own site? Paste the URL and I'll display it
+    alongside the others once I verify it links back.
+
+    Your post URL * [74][                    ] [76]Send webmention
+
+© Michael Harley. [77]CC BY-NC-SA 4.0.
+
+  • [78] Subscribe
+  • [79]Colophon
+  • [80]Privacy
+  • [81]Back to top
+
+[82] [83]IndieWeb Webring [84] 
+[85]Powered by Debian (opens in a new tab) [86]Get Firefox (opens in a new tab)
+[87]Internet Archive (opens in a new tab) [88]uBlock Origin (opens in a new
+tab) [89]Join the Fediverse (opens in a new tab) [90]Creative Commons BY-NC-SA
+4.0 (opens in a new tab) [91]I support the Right to Repair (opens in a new tab)
+[92]Home Assistant (opens in a new tab) [93]Proxmox (opens in a new tab) [94]
+Team Fortress (opens in a new tab) [95]Powered by AMD (opens in a new tab) [96]
+QuakeWorld (opens in a new tab) [97]Made with Eleventy (opens in a new tab)
+Piracy Now Catscape Button Devils
+
+You are visitor #027384
+
+[98](Close)× []
+
+References:
+
+[1] https://michaelharley.net/posts/2026/07/16/i-own-my-books/#main
+[2] https://michaelharley.net/
+[4] https://michaelharley.net/about/
+[5] https://michaelharley.net/contact/
+[6] https://michaelharley.net/posts/
+[7] https://michaelharley.net/sitemap/
+[11] https://michaelharley.net/posts/2026/07/16/i-own-my-books/
+[12] https://books.infosec.exchange/book/726/s/the-great-book-of-amber-the-chronicles-of-amber-1-10
+[13] https://michaelharley.net/posts/2026/07/16/i-own-my-books/#removing-drm
+[14] https://michaelharley.net/posts/2023/01/10/how-to-setup-calibre-to-remove-drm-from-ebooks-on-linux/
+[15] https://www.ebooks.com/
+[16] https://www.kobo.com/
+[17] https://www.npr.org/2019/07/07/739316746/microsoft-closes-the-book-on-its-e-library-erasing-all-user-content
+[18] https://www.npr.org/2009/07/24/106989048/amazons-1984-deletion-from-kindle-examined
+[19] https://www.npr.org/sections/thetwo-way/2009/07/amazon_kindles_lawsuit_for_del.html
+[20] https://en.wikipedia.org/wiki/EPUB
+[21] https://michaelharley.net/posts/2026/07/16/i-own-my-books/#but-what-about-amazon-exclusives
+[22] https://michaelharley.net/posts/2026/07/16/i-own-my-books/#audiobooks
+[23] https://libro.fm/
+[24] https://craphound.com/category/info/
+[25] https://michaelharley.net/
+[26] https://michaelharley.net/tags/books/
+[27] https://michaelharley.net/tags/calibre/
+[28] https://michaelharley.net/tags/ebooks/
+[29] https://infosec.exchange/@michaelharley/116929585834523848
+[30] https://bsky.app/profile/michaelharley.net/post/3mqr7fh4dup2c
+[31] https://michaelharley.net/posts/2023/01/10/how-to-setup-calibre-to-remove-drm-from-ebooks-on-linux/
+[32] https://michaelharley.net/posts/2026/07/21/how-i-self-host-my-ebooks-and-audiobooks/
+[33] https://michaelharley.net/posts/2022/03/09/on-ebook-readers-and-why-i-am-opting-out-of-vendor-lock-ins/
+[35] https://bookstodon.com/@TheNovemberMan
+[36] https://kind.social/@PurpleJillybeans
+[37] https://mas.to/@ronsboy67
+[38] https://indieauthors.social/@AlexCorby
+[39] https://mastodon.social/@getbookshelves
+[40] https://mastodon.social/@Feral_3D
+[41] https://mastodon.social/@wojtekpow
+[42] https://mastodon.social/@pabloniusmonk
+[43] https://polymaths.social/@jp
+[44] https://mastodon.social/@Kdude
+[45] https://mastodon.art/@NickEast_IndieWriter
+[46] https://bsky.app/profile/richlinville.bsky.social
+[47] https://bsky.app/profile/kevin-gallant.bsky.social
+[48] https://toot.meiyerlan.casa/@miln
+[49] https://mas.to/@ronsboy67
+[50] https://mastodon.social/@pabloniusmonk
+[51] https://polymaths.social/@jp
+[52] https://mastodon.social/@Kdude
+[53] https://social.bubbles.town/@bubbles/statuses/01KXNDMAAG8JNS4H3J2RZV6ASR
+[54] https://bubbles.town/entry/44749901
+[55] https://zeroes.ca/@mloxton/116929886829689114
+[56] https://infosec.exchange/@michaelharley
+[57] https://antoniosantos.io/re-i-own-my-books/
+[58] https://mastodon.social/@Kdude/116933566178280292
+[59] https://infosec.exchange/@michaelharley
+[60] mailto:[email protected]?subject=Re:%20I%20own%20my%20books
+[70] https://indieauth.net/
+[77] https://creativecommons.org/licenses/by-nc-sa/4.0/
+[78] https://michaelharley.net/subscribe/
+[79] https://michaelharley.net/colophon/
+[80] https://michaelharley.net/privacy/
+[81] https://michaelharley.net/posts/2026/07/16/i-own-my-books/#top
+[82] https://xn--sr8hvo.ws/previous
+[83] https://xn--sr8hvo.ws/
+[84] https://xn--sr8hvo.ws/next
+[85] https://www.debian.org/
+[86] https://www.firefox.com/
+[87] https://archive.org/
+[88] https://ublockorigin.com/
+[89] https://jointhefediverse.net/
+[90] https://creativecommons.org/licenses/by-nc-sa/4.0/
+[91] https://www.repair.org/
+[92] https://www.home-assistant.io/
+[93] https://www.proxmox.com/
+[94] https://www.teamfortress.com/
+[95] https://www.amd.com/
+[96] https://www.quakeworld.nu/
+[97] https://www.11ty.dev/
diff --git a/static/archive/simonwillison-net-zmoxib.txt b/static/archive/simonwillison-net-zmoxib.txt
@@ -0,0 +1,394 @@
+[1]Simon Willison’s Weblog
+
+[2]Subscribe
+Sponsored by: AWS — Move from SaaS to Agentic SaaS with resources for ISVs at
+every layer of the stack. [3]Explore how AI for ISVs turns vision into results
+
+OpenAI’s accidental cyberattack against Hugging Face is science fiction that
+happened
+
+22nd July 2026
+
+This story is wild. The short version: OpenAI were running a cybersecurity test
+against an unreleased model, with the model’s guardrail features turned off.
+Rather than solve the test, the model broke its way out of OpenAI’s sandbox,
+then found exploits to break in to Hugging Face, all so it could cheat on the
+test by stealing the answers.
+
+Along the way it helped make the strongest case yet for how the imbalance of
+model availability is hurting our ability to secure our software.
+
+Here’s what happened [4]#
+
+We currently have three documents to help us understand what happened here.
+
+ 1. [5]ExploitGym: Can AI Agents Turn Security Vulnerabilities into Real
+    Attacks? is a paper published on 11th May 2026 describing ExploitGym, a new
+    eval suite for LLM-powered agent systems.
+ 2. [6]Security incident disclosure — July 2026 by Hugging Face on 16th July
+    2026 describes how they detected an attack from an “agentic
+    security-research harness—used LLM still not known” that breached some of
+    their systems.
+ 3. [7]OpenAI and Hugging Face partner to address security incident during
+    model evaluation from OpenAI on 21st July 2026 confesses that it was their
+    agent harness that did this, and that they’re working with Hugging Face to
+    clean up the mess.
+
+ExploitGym [8]#
+
+I hadn’t seen the [9]ExploitGym paper before and it’s a really interesting one.
+Authors from UC Berkeley, the Max Planck Institute, UC Santa Barbara, and
+Arizona State designed a new benchmark for evaluating models on their ability
+to turn a reported vulnerability into a concrete exploit. OpenAI, Anthropic,
+and Google provided feedback and helped run the benchmark against their models.
+
+The benchmark “comprises 898 instances derived from real-world vulnerabilities
+that affected popular software projects”—including the Linux kernel and V8
+JavaScript engine. The ExploitGym benchmark is [10]available on GitHub.
+
+Here’s the paragraph that best represents their benchmark results:
+
+    Among all configurations, Claude Mythos Preview and GPT-5.5 achieve the
+    highest success counts (157 and 120 successes, respectively), demonstrating
+    that current frontier agents can exploit a substantial subset of real-world
+    vulnerabilities under controlled conditions. GPT-5.4 also solves a notable
+    54 tasks, placing it in an intermediate tier. The remaining model–agent
+    pairings solve fewer than 15 tasks each, underscoring that end-to-end
+    exploitation remains challenging and sharply differentiates today’s
+    frontier systems. Notably, Claude Opus 4.7 achieves fewer successes than
+    Claude Opus 4.6 despite being a newer checkpoint, and does so at
+    substantially lower cost on the full set. Trace inspection reveals that
+    Claude Opus 4.7 and Gemini 3.1 Pro frequently conclude early after judging
+    the target vulnerability non-exploitable.
+
+The paper also describes the approach they took to preventing the agents from
+cheating by going outside the parameters of the test. This becomes relevant in
+a moment!
+
+    Outbound connections are restricted to a curated allowlist that permits
+    routine package installation (Ubuntu apt repositories and PyPI) and
+    fetching the toolchains required for building V8. All other external
+    endpoints are blocked.
+
+The paper concludes with this (emphasis mine):
+
+    Our results show that autonomous exploit development by frontier AI agents
+    is no longer a hypothetical capability. While current agents are not yet
+    reliable across all targets, they already exploit a non-trivial fraction of
+    real-world vulnerabilities, including complex targets such as kernel
+    components. This rapid emergence is itself a central finding, showing that
+    capabilities that would have seemed implausible are now present in deployed
+    frontier models.
+
+An important detail here: this paper isn’t about discovering vulnerabilities;
+it’s about being able to take those vulnerabilities and turn them into working
+exploits.
+
+When Anthropic first restricted access to Mythos [11]back in April they talked
+about this capability as well. A model that can act on vulnerabilities is a lot
+more dangerous than one that can just discover them.
+
+One of the ways Fable differs from Mythos is that it’s more likely to refuse to
+weaponize vulnerabilities in this way. I get the impression the US government
+did not understand that distinction when they banned Fable [12]last month.
+
+The Hugging Face incident [13]#
+
+The first hint we got of the attack was in [14]this blog post by Hugging Face
+on 16th July 2026:
+
+    A malicious dataset abused two code-execution paths in our dataset
+    processing (a remote-code dataset loader and a template-injection in a
+    dataset configuration) to run code on a processing worker. From there, the
+    actor escalated to node-level access, harvested cloud and cluster
+    credentials, and moved laterally into several internal clusters over a
+    weekend.
+
+I hope they release more details about the code that pulled this off. I’m
+assuming this means packages using the [15]datasets library, a Hugging Face
+project for bundling up and sharing datasets on their platform. That library
+used to execute arbitrary code but has been steadily locked down over time,
+with the [16]4.0.0 release in July 2025 removing the trust_remote_code=True
+flag entirely.
+
+Assuming the attack used that library it must have either abused pickle
+serialization in some way, found some other non-obvious code execution path, or
+(most likely) specified datasets<4.0.0 as the dependency.
+
+    The campaign was run by an autonomous agent framework (appearing to be
+    built on an agentic security-research harness—used LLM still not known)
+    executing many thousands of individual actions across a swarm of
+    short-lived sandboxes, with self-migrating command-and-control staged on
+    public services.
+
+This was a sophisticated attack!
+
+Then Hugging Face hit a wall: they tried to use “frontier models behind
+commercial APIs”—I’m guessing from Anthropic and OpenAI—to help analyze the
+attack, and were blocked:
+
+    When we started the log analysis, we first used frontier models behind
+    commercial APIs. This did not work: the analysis requires submitting large
+    volumes of real attack commands, exploit payloads, and C2 artifacts, and
+    these requests were blocked by the providers’ safety guardrails, which
+    cannot distinguish an incident responder from an attacker.
+
+They switched to their own self-hosted instance of MIT licensed GLM-5.2 and it
+helped them figure out what was going on.
+
+This indicated a fundamental asymmetry between the defending team and the
+(so-far unknown) attacker:
+
+    We do not know which model powered the attacker’s agents, whether a
+    jailbroken hosted model or an unrestricted open-weight one; either way, the
+    attacker was bound by no usage policy, while our own forensic work was
+    blocked by the guardrails of the hosted models we first tried.
+
+As a useful indicator of how seriously they took the attack:
+
+    [...] Finally, we have also reported this incident to law enforcement
+    agencies.
+
+So who was responsible for this “autonomous agent framework”? It turned out to
+be OpenAI themselves.
+
+The OpenAI confession [17]#
+
+Five days later, [18]on July 21st, OpenAI revealed the culprit. They had been
+running the ExploitGym benchmark against a new, as-yet undisclosed model, and
+that model had been operating way outside its intended parameters (emphasis
+mine):
+
+    After investigating, we now know that this particular incident was driven
+    by a combination of OpenAI models — including GPT‑5.6 Sol and an even more
+    capable pre-release model, all with reduced cyber refusals for evaluation
+    purposes — while being internally tested on a [19]benchmark⁠ [ExploitGym]
+    of cyber capabilities. [...]
+
+    We estimate maximal cyber capabilities by running this evaluation without
+    production classifiers used to prevent models from pursuing high-risk cyber
+    activity. Our benchmarks run in a highly isolated environment, with network
+    access constrained to the ability to install packages through an internally
+    hosted third-party software that acts as a proxy and cache for package
+    registries.
+
+    The models identified and chained vulnerabilities across OpenAI’s research
+    environment and Hugging Face’s production infrastructure to obtain test
+    solutions directly from Hugging Face’s production database. All evidence
+    suggests that the models were hyperfocused on finding a solution for
+    ExploitGym, going to extreme lengths to achieve a rather narrow testing
+    goal.
+
+It’s pretty clear what happened here. OpenAI removed safety filters for an
+in-progress model, locked it up in a sandbox and told it to solve the
+ExploitGym problems. Given the absence of guardrails there was nothing to
+prevent the model from attempting to break out of that sandbox, break into
+Hugging Face, and read the answers from there instead.
+
+OpenAI’s sandbox used the now common pattern of allowing access to an
+allow-list of sites related to installing additional packages via a controlled
+proxy. In OpenAI’s words:
+
+    While operating in our sandboxed testing environment, our models spent a
+    substantial amount of inference compute finding a way to obtain open
+    Internet access, in pursuit of solving the evaluation problem. To gain
+    access, the models identified and exploited a zero-day vulnerability (which
+    we’ve now responsibly disclosed to the vendor) in the package registry
+    cache proxy. With this access, our models performed a series of privilege
+    escalation and lateral movement actions in our research testing environment
+    until the models reached a node with Internet access.
+
+So step one was to break out onto the public internet. The model then broke
+into Hugging Face to find the answers:
+
+    After gaining Internet access, the models inferred that Hugging Face
+    potentially hosted models, datasets and solutions for ExploitGym. Knowing
+    this, the model searched for and successfully found ways to gain access to
+    secret information that it could use to cheat the evaluation. In one
+    example, the model chained together multiple attack vectors, including
+    using stolen credentials and zero-day vulnerabilities to find a remote code
+    execution path on the Hugging Face servers.
+
+Chaining together multiple attack vectors is exactly the kind of thing these
+new models can do, where previous generations of models might have failed.
+
+I wrote last month about how [20]Claude Fable is relentlessly proactive, when I
+noticed it spinning up custom web servers and deploying CORS tricks on my own
+laptop just to help debug a WebKit CSS issue. It turns out relentless
+proactivity is the defining trait of this new generation of Mythos-class
+models. If you set them a goal and give them a way to get there, even
+inadvertently, they will figure it out.
+
+Resist the temptation to write this off as a stunt [21]#
+
+There will inevitably be some people who dismiss this story as a dishonest
+marketing trick by OpenAI to make their models sound terrifyingly effective. I
+found 81 instances of the term “marketing” in [22]the Hacker News discussion of
+the incident.
+
+To those people I say pull your heads out of the sand—you’re now including
+Hugging Face in your conspiracy theories, just so you can deny the crescendo of
+evidence here!
+
+The best models we have today have the ability to both find and exploit new
+vulnerabilities. The ExploitGym paper itself concludes that “autonomous exploit
+development by frontier AI agents is no longer a hypothetical capability”, and
+this incident is a perfect example of exactly that.
+
+The asymmetry is increasingly frustrating [23]#
+
+One of the most infuriating details of this story is how Hugging Face, faced
+with an accidental and aggressive attack from one of OpenAI’s models, were
+unable to then turn to OpenAI’s models to help them fend off the attack.
+
+The frontier models we have access to are increasingly being constrained in how
+much they can help us protect our software, heavily influenced by the US
+government’s ongoing threat of export controls. Claude Fable 5 wouldn’t even
+[24]proofread this article for me! It insisted on downgrading me to a less
+capable model.
+
+Meanwhile open weight models from China such as GLM-5.2, Kimi 3 and the new
+Qwen 3.8 Max appear to have none of these restrictions—and any restrictions
+that do exist can likely be fine-tuned out of them by modifying the weights
+
+These constraints are meant to make us safer. I think there’s a risk that they
+are having the opposite effect.
+
+Posted [25]22nd July 2026 at 11:51 pm · Follow me on [26]Mastodon, [27]Bluesky,
+[28]Twitter or [29]subscribe to my newsletter
+
+More recent articles
+
+  • [30]Stateless MCP has recaptured my interest (and inspired mcp-explorer and
+    datasette-mcp) - 31st July 2026
+  • [31]A Fireside Chat with Cat and Thariq from the Claude Code team - 21st
+    July 2026
+
+This is OpenAI’s accidental cyberattack against Hugging Face is science fiction
+that happened by Simon Willison, posted on [32]22nd July 2026.
+
+[33] sandboxing 52 [34] security 620 [35] ai 2,164 [36] openai 441 [37]
+generative-ai 1,916 [38] llms 1,883 [39] hugging-face 25 [40] anthropic 321 
+[41] paper-review 17 [42] ai-security-research 33 [43]
+openai-hugging-face-incident 6
+
+Next: [44]Stateless MCP has recaptured my interest (and inspired mcp-explorer
+and datasette-mcp)
+
+Previous: [45]A Fireside Chat with Cat and Thariq from the Claude Code team
+
+Monthly briefing
+
+Sponsor me for $10/month and get a curated email digest of the month's most
+important LLM developments.
+
+Pay me to send you less!
+
+[46] Sponsor & subscribe
+
+  • [47]Disclosures
+  • [48]Colophon
+  • ©
+  • [49]2002
+  • [50]2003
+  • [51]2004
+  • [52]2005
+  • [53]2006
+  • [54]2007
+  • [55]2008
+  • [56]2009
+  • [57]2010
+  • [58]2011
+  • [59]2012
+  • [60]2013
+  • [61]2014
+  • [62]2015
+  • [63]2016
+  • [64]2017
+  • [65]2018
+  • [66]2019
+  • [67]2020
+  • [68]2021
+  • [69]2022
+  • [70]2023
+  • [71]2024
+  • [72]2025
+  • [73]2026
+  • [74](Theme: Auto (system preference). Click to switch to light.)
+
+
+References:
+
+[1] https://simonwillison.net/
+[2] https://simonwillison.net/about/#subscribe
+[3] https://fandf.co/4yrcF3h
+[4] https://simonwillison.net/2026/Jul/22/openai-cyberattack/#here-s-what-happened
+[5] https://arxiv.org/abs/2605.11086
+[6] https://huggingface.co/blog/security-incident-july-2026
+[7] https://openai.com/index/hugging-face-model-evaluation-security-incident/
+[8] https://simonwillison.net/2026/Jul/22/openai-cyberattack/#exploitgym
+[9] https://arxiv.org/abs/2605.11086
+[10] https://github.com/sunblaze-ucb/exploitgym
+[11] https://simonwillison.net/2026/Apr/7/project-glasswing/
+[12] https://simonwillison.net/2026/Jun/16/fable-5-export-controls/
+[13] https://simonwillison.net/2026/Jul/22/openai-cyberattack/#the-hugging-face-incident
+[14] https://huggingface.co/blog/security-incident-july-2026
+[15] https://github.com/huggingface/datasets
+[16] https://github.com/huggingface/datasets/releases/tag/4.0.0
+[17] https://simonwillison.net/2026/Jul/22/openai-cyberattack/#the-openai-confession
+[18] https://openai.com/index/hugging-face-model-evaluation-security-incident/
+[19] https://arxiv.org/abs/2605.11086
+[20] https://simonwillison.net/2026/Jun/11/fable-is-relentlessly-proactive/
+[21] https://simonwillison.net/2026/Jul/22/openai-cyberattack/#resist-the-temptation-to-write-this-off-as-a-stunt
+[22] https://news.ycombinator.com/item?id=48997548
+[23] https://simonwillison.net/2026/Jul/22/openai-cyberattack/#the-asymmetry-is-increasingly-frustrating
+[24] https://simonwillison.net/guides/agentic-engineering-patterns/prompts/#proofreader
+[25] https://simonwillison.net/2026/Jul/22/
+[26] https://fedi.simonwillison.net/@simon
+[27] https://bsky.app/profile/simonwillison.net
+[28] https://twitter.com/simonw
+[29] https://simonwillison.net/about/#subscribe
+[30] https://simonwillison.net/2026/Jul/31/stateless-mcp/
+[31] https://simonwillison.net/2026/Jul/21/cat-and-thariq/
+[32] https://simonwillison.net/2026/Jul/22/
+[33] https://simonwillison.net/tags/sandboxing/
+[34] https://simonwillison.net/tags/security/
+[35] https://simonwillison.net/tags/ai/
+[36] https://simonwillison.net/tags/openai/
+[37] https://simonwillison.net/tags/generative-ai/
+[38] https://simonwillison.net/tags/llms/
+[39] https://simonwillison.net/tags/hugging-face/
+[40] https://simonwillison.net/tags/anthropic/
+[41] https://simonwillison.net/tags/paper-review/
+[42] https://simonwillison.net/tags/ai-security-research/
+[43] https://simonwillison.net/tags/openai-hugging-face-incident/
+[44] https://simonwillison.net/2026/Jul/31/stateless-mcp/
+[45] https://simonwillison.net/2026/Jul/21/cat-and-thariq/
+[46] https://github.com/sponsors/simonw/
+[47] https://simonwillison.net/about/#disclosures
+[48] https://simonwillison.net/about/#about-site
+[49] https://simonwillison.net/2002/
+[50] https://simonwillison.net/2003/
+[51] https://simonwillison.net/2004/
+[52] https://simonwillison.net/2005/
+[53] https://simonwillison.net/2006/
+[54] https://simonwillison.net/2007/
+[55] https://simonwillison.net/2008/
+[56] https://simonwillison.net/2009/
+[57] https://simonwillison.net/2010/
+[58] https://simonwillison.net/2011/
+[59] https://simonwillison.net/2012/
+[60] https://simonwillison.net/2013/
+[61] https://simonwillison.net/2014/
+[62] https://simonwillison.net/2015/
+[63] https://simonwillison.net/2016/
+[64] https://simonwillison.net/2017/
+[65] https://simonwillison.net/2018/
+[66] https://simonwillison.net/2019/
+[67] https://simonwillison.net/2020/
+[68] https://simonwillison.net/2021/
+[69] https://simonwillison.net/2022/
+[70] https://simonwillison.net/2023/
+[71] https://simonwillison.net/2024/
+[72] https://simonwillison.net/2025/
+[73] https://simonwillison.net/2026/
diff --git a/static/archive/sixcolors-com-vzmwje.txt b/static/archive/sixcolors-com-vzmwje.txt
@@ -0,0 +1,408 @@
+[1] Six Colors
+[2] Six Colors
+
+Apple, technology, and other stuff
+
+MENU
+
+  • [3]Archive
+  • [4]Sign In
+  • [5]Membership
+  • [6]Topics
+      □ [7]WWDC 2026
+      □ [8]Help Me, Glenn!
+      □ [9]Reviews
+      □ [10]Apple Report Card
+      □ [11]E-readers
+      □ [12]Apple Photos
+      □ [13]20 Macs for 2020
+  • [14]Merch
+  • [15]About
+      □ [16]Jason Snell
+      □ [17]Dan Moren
+      □ [18]Sponsorships
+
+  • [19]Archive
+  • [20]Sign In
+  • [21]Membership
+  • [22]Topics
+      □ [23]WWDC 2026
+      □ [24]Help Me, Glenn!
+      □ [25]Reviews
+      □ [26]Apple Report Card
+      □ [27]E-readers
+      □ [28]Apple Photos
+      □ [29]20 Macs for 2020
+  • [30]Merch
+  • [31]About
+      □ [32]Jason Snell
+      □ [33]Dan Moren
+      □ [34]Sponsorships
+
+Become a Member!
+
+[35]Become a Six Colors member to read exclusive posts, get our weekly podcast
+and regular newsletters, and much more!
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+
+By Dan Moren
+
+July 22, 2026 7:00 AM PT
+
+[36]■ Ereaders
+
+[37]■ review
+
+Review: Xteink X3 is the little e-reader the world’s not quite ready for
+
+The Xteink X3 magneted onto the back of a Cosmic Orange iPhone 17 Pro.
+An e-reader magneted to the back of a smartphone, just as the prophecy
+foretold.
+
+The market for small e-readers has been booming lately. Earlier this year,
+Jason [38]took a look at the Xteink X4, a pint-sized reading device that was
+about as light and small as they come. But those maniacs at Xteink weren’t done
+yet: they followed it up with the $79 X3, which is unbelievably even lighter
+and smaller.
+
+I wouldn’t blame you for wondering if there’s such a thing as too small and
+light—at 3.84 inches by 2.51 inches (and just 0.2 inches thick) the X3 is still
+larger than, say, a credit card, but not by much. The screen itself measures
+just 3.7 inches, more than half an inch smaller than the X4’s 4.3 inch, but its
+259 ppi resolution still makes it plenty easy to read on.
+
+[39]
+^[40]1 At that size it’s little imposition to take it with you wherever you go.
+Easy to lose? Maybe. Easy to love? Yes.
+
+For one thing, this small size unlocks at least one capability that the X4
+couldn’t fully deliver upon—the ability to stick to the back of your phone.
+Like the X4, the X3 has a MagSafe-compatible magnet in its rear case and it
+fits just about perfectly on the back of my iPhone 17 Pro, nestled below the
+camera plateau.
+
+However, the magnet is not particularly strong, and it lacks the secondary
+stabilizing magnet that you see on official MagSafe accessories, meaning it
+wobbles around a bit. I wouldn’t call it a super secure connection, but it’s
+pretty good if you’re just slipping it in and out of a pocket. Just be aware
+that it probably will come loose.
+
+Like the X4 before it, the X3 features a pair of rocker switches on the front
+for a total of four possible buttons. But they’ve opted to skip the X4’s side
+mounted rocker switch in favor of a single buttons on each side. There’s also
+an on/off switch at the top (plus a recessed button used for resetting the
+device). And with all of that, they somehow managed to continue to fit a
+microSD slot in the top. The bottom left corner also has a little set of holes
+for a lanyard or wrist strap.
+
+Xteink X3 and smaller Xteink X4 side by side.
+The X3 is about the size of just the display on the X4.
+
+The one casualty of the smaller X3, however, is the port. The X4 was big enough
+to accommodate a USB-C connector, but the X3’s thin profile makes that
+impossible. Instead, there’s a pogo-pin USB cable that connects to four
+magnetic contacts on the reader. Is this a step back? Strictly speaking, yes.
+Using a proprietary connector is a bummer in the year 2026, especially because
+it means having to keep track of a single-use cable. That said, once you get
+the X3 up and running, the only real need for the connector is charging, and
+the battery on this thing lasts a very long time. (I’ve yet to run it down in
+several weeks of usage.) Just remember to make a note of where you stow that
+cable for the point months down the road when you do need to charge it and find
+yourself wondering whatever happened to it.
+
+As with the X4, the X3 lacks any sort of screen lighting, meaning that it’s
+strictly a “read in bright light” device. But don’t worry, because Xteink has
+already unveiled a new [41]X4 Pro with the company’s first lit screen.
+
+[42]
+^[43]2
+
+All in all, I found the X3 very comfortable to read on, whether attached to my
+iPhone or not. The side buttons work great as page-turners, and the screen is
+high-contrast and sharp enough to make text render very clearly. All in all,
+it’s a great reading experience—if you take into account one major caveat.
+
+Soft where?
+
+The elephant in the room for the Xteink X3 is the software. Xteink ships the X3
+with its own built-in firmware which, by all accounts, has improved since the
+first version. But I can’t really tell you, because upon opening the box and
+powering up the device, the first thing I did was install [44]Crosspoint, the
+open-source community-built firmware that has turned this device from a
+curiosity into a real contender.
+
+[45]
+^[46]3
+
+Unlike a lot of other firmware replacements, Crosspoint is super easy to
+install; you can do it right from a web browser. While it’s not fully free of
+technological hurdles, I’d say that most people comfortable using an e-reader
+or updating their iPhones will be able to handle the process with few problems.
+And the benefits are manifold.
+
+Xteink X3 shown with Crosspoint settings screen.
+Crosspoint is extremely configurable for all your reading needs.
+
+Crosspoint goes beyond simply turning this into a functional device and into
+one that is actually fun to use. It’s got a straightforward, easy to navigate
+interface that makes it simple to do everything from reading to loading books
+(accomplished via a web-based interface). For those who like to tweak their
+reading setup, there are plenty of configuration options, everything from
+screen orientation to hyphenation and, yes, custom fonts loaded via the SD
+card.
+
+Even the onscreen keyboard that you need to use for various configuration tasks
+is pretty solid for what’s available—on par with navigating via an onscreen
+keyboard with a game controller, in my opinion. I wouldn’t want to have to type
+in my Wi-Fi password every time—and you don’t, because it saves it for you—but
+one time was fine.
+
+There are also a bunch of other features that might appeal to those who want to
+take reading to the next level. For example, support for Open Publication
+Distribution System (OPDS) standard means that if you want to host your book
+library on your own server, you can point your reader at that and download any
+of the books you already own directly to your device. There’s also support for
+KOreader sync to help keep your place between supported devices.
+
+[47]
+^[48]4
+
+Crosspoint has been so successful, in fact, that the team at Xteink has
+smartened up and started collaborating. (This after a brief moment when it
+looked like the company might try to firmware lock its devices.) Now, not only
+do the “developer editions” sold directly by the company continue to allow you
+to install the custom firmware, the company has been working with the
+Crosspoint team to make sure new devices, like the X4 Pro, will already be
+supported when they arrive. While Xteink hasn’t quite adopted Crosspoint as the
+default OS, it’s not far off.
+
+The world is not enough
+
+Given how positive I’ve been above, you might be all too tempted to run out and
+snap up an Xteink X3 for yourself. I don’t blame you! At $79 (and often
+discounted for less than that), it’s well positioned as an impulse buy. And
+while I don’t want to dissuade you, I have to note the biggest caveat of all:
+the world.
+
+The Xteink X3 e-reader shown held in one hand.
+Just try to tell me this wee fella isn’t charming.
+
+If there’s one thing that’s holding back the X3 and the X4 and, frankly, all
+the other wacky readers out there, it’s the market. The e-reader space is still
+unquestionably dominated by Amazon purveying its razors-and-blades strategy:
+buy the Kindle for cheap
+
+[49]
+^[50]5 and the company earns it all back when you buy your books or sign up for
+Kindle Unlimited’s all-you-can-eat plan. Kobo, who makes the hardware that I
+prefer, is a distant second, and has some advantages, but operates on roughly a
+similar scheme.
+
+Both of these companies benefit from lock-in in the form of Digital Rights
+Management. DRM is, of course, largely pushed by publishers, who insist upon
+cryptographic schemes to lock down the books they sell in order to nominally
+protect against piracy. Never mind the fact that books are still easily and
+widely pirated, the DRM is relatively simple to crack
+
+[51]
+^[52]6, and many of those books have been vacuumed up by the boatload by an
+even more insidious thief in the form of AI training data.
+
+I come at this, of course, from the perspective of both reader and writer. As a
+writer, I certainly want to be compensated for all the hard work I put in to
+create my books, but I also want people to read and enjoy them. That’s why
+you’ll find no stauncher defender of libraries.
+
+Personally, I find the industry’s insistence on DRM misplaced, just as [53]I
+did with the music industry two decades ago. The lack of these security
+features does not automatically turn people at large into thieves and it’s
+insulting to think that it would. In fact, the sci-fi publisher Tor, one of the
+biggest names in the business and a subsidiary of Big Five publisher Macmillan,
+has put out its titles without DRM for almost fifteen years and I haven’t seen
+any significant indication that it’s harmed their business. Many of my books
+are also available [54]directly from my publisher without DRM, and I don’t
+think that’s put a dent in my bottom line either.
+
+I would love to be able to easily load any book I’ve ever purchased onto my
+Xteink devices—or, for that matter, any e-reader or e-reading app of my choice.
+There are, of course, [55]extensive repositories of [56]DRM-free public domain
+books available. Amazon, to its credit, does now allow you to download DRM-free
+copies of any book that you’ve purchased.
+
+[57]
+^[58]7 I argued a few years back that this is [59]an opportunity for Apple to
+distinguish its stagnant ebook marketplace from the competition. But for
+first-run books, your options are currently more limited (and sometimes harder
+to suss out).
+
+I’d also love to somehow see support for Libby, the popular library ebook
+borrowing app, on Xteink devices, though I don’t see that happening anytime
+soon. But in my opinion, the bottom line is that more ways to read makes more
+readers of books, which in turn makes more customers of books.
+
+But I digress.
+
+The conclusion
+
+The other week I was riding the train with my kid, our usual weekend pastime.
+As he was enjoying looking out the window, I was reading a book on the X3,
+magneted to the back of my iPhone 17 Pro. As we neared a stop, a woman nearby
+caught sight of it and marveled over it. “Is that a tiny e-reader?”
+
+I extolled its virtues for a moment before they got off at their stop. But it
+told me one important thing: there’s a hunger for these types of devices.
+Because people who self-select as readers in this day and age are, above all,
+passionate. You have to make a choice to be sitting and reading a book when you
+could be watching TikTok or Instagram or listening to music or a podcast, all
+of which are constantly at your fingertips.
+
+That’s where the X3 (and the X4) deliver. A Kindle or Kobo isn’t exactly bulky,
+but they’re not pocketable either. Being able to take your e-reader with you
+just as we stuffed mass market paperbacks in our back pockets in days gone by
+is freeing and fun. Now if the world might just shift a little bit more to meet
+us, maybe we could free ourselves a little further.
+
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+
+ 1. Fun fact: the X3’s display is 0.2 inches larger and has almost 60 percent
+    higher pixel density than the screen on the original iPhone. [60]↩
+ 2. Did I buy one? Yeah, I did. Because apparently these guys have my number. 
+    [61]↩
+ 3. I should say that there are [62]many other custom firmware projects for
+    Xteink’s hardware, but Crosspoint is indisputably the most prominent and
+    best supported. [63]↩
+ 4. If you’re not familiar with [64]KOreader, it’s an open source reading app
+    that you can install on Kindle and Kobo, as well as other platforms; one of
+    the features is its own syncing system. [65]↩
+ 5. Though, to be frank, not as cheap as it used to be. [66]↩
+ 6. Not unlike in music, the problem is that in order for someone to actually
+    to consume your music or books, they must possess the means to unlock it. 
+    [67]↩
+ 7. With some caveats. For example, if you’re in a household with someone else
+    who’s purchased a DRM-free book, you can still read it on your Kindle, but
+    only they can download the DRM-free version. [68]↩
+
+[Dan Moren is the East Coast Bureau Chief of Six Colors, as well as an author,
+podcaster, and two-time Jeopardy! champion. You can find him on Mastodon at 
+[69]@[email protected] or reach him by email at [email protected]. His
+next novel, the sci-fi adventure [70]Eternity's Tomb, will be released in
+November 2026.]
+
+  • [71]Report a typo
+  • [72]Discuss in members Discord [73](app)
+
+If you appreciate articles like this one, support us by [74]becoming a Six
+Colors subscriber. Subscribers get access to an exclusive podcast, members-only
+stories, and a special community.
+
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+
+Search Six Colors
+
+[75][                                        ]
+  • [76]Sponsor
+  • [77]Mastodon
+  • [78]Merch
+  • [79]Report a mistake
+  • [80]RSS Feed
+  • [81]JSON Feed
+  • [82]Privacy Policy
+
+Six Colors® is copyright © 2026 by The Incomparable Inc.
+[83]Powered by WordPress | [84]Hosted by Pressable
+[g] 
+
+Search results
+
+[85][                    ][86]Search
+[87](Close search results)
+
+No results found
+
+Sort by:
+[88]Relevance•[89]Newest•[90]Oldest
+
+Filter options
+
+[91]Close Search
+[92]Search powered by Jetpack
+
+References:
+
+[1] https://sixcolors.com/
+[2] https://sixcolors.com/
+[3] https://sixcolors.com/archive/
+[4] https://sixcolors.com/?memberful_endpoint=auth
+[5] https://sixcolors.com/subscribe/
+[6] https://sixcolors.com/post/2026/07/review-xteink-x3-is-the-little-e-reader-the-worlds-not-quite-ready-for/#
+[7] https://sixcolors.com/tag/wwdc-2026/
+[8] https://sixcolors.com/tag/help-me-glenn/
+[9] https://sixcolors.com/tag/review/
+[10] https://sixcolors.com/tag/reportcard/
+[11] https://sixcolors.com/tag/kindle/
+[12] https://sixcolors.com/tag/photosmac/
+[13] https://sixcolors.com/20macs
+[14] https://cottonbureau.com/people/the-incomparable
+[15] https://sixcolors.com/about/
+[16] https://sixcolors.com/jason/
+[17] https://sixcolors.com/dan/
+[18] https://sixcolors.com/sponsorship/
+[19] https://sixcolors.com/archive/
+[20] https://sixcolors.com/?memberful_endpoint=auth
+[21] https://sixcolors.com/subscribe/
+[22] https://sixcolors.com/post/2026/07/review-xteink-x3-is-the-little-e-reader-the-worlds-not-quite-ready-for/#
+[23] https://sixcolors.com/tag/wwdc-2026/
+[24] https://sixcolors.com/tag/help-me-glenn/
+[25] https://sixcolors.com/tag/review/
+[26] https://sixcolors.com/tag/reportcard/
+[27] https://sixcolors.com/tag/kindle/
+[28] https://sixcolors.com/tag/photosmac/
+[29] https://sixcolors.com/20macs
+[30] https://cottonbureau.com/people/the-incomparable
+[31] https://sixcolors.com/about/
+[32] https://sixcolors.com/jason/
+[33] https://sixcolors.com/dan/
+[34] https://sixcolors.com/sponsorship/
+[35] https://sixcolors.com/subscribe/
+[36] https://sixcolors.com/tag/kindle/
+[37] https://sixcolors.com/tag/review/
+[38] https://sixcolors.com/post/2026/01/if-the-future-of-e-readers-is-getting-weird-im-here-for-it/
+[40] https://sixcolors.com/post/2026/07/review-xteink-x3-is-the-little-e-reader-the-worlds-not-quite-ready-for/#fn-40773-iphone
+[41] https://www.xteink.com/products/xteink-x4pro
+[43] https://sixcolors.com/post/2026/07/review-xteink-x3-is-the-little-e-reader-the-worlds-not-quite-ready-for/#fn-40773-x4pro
+[44] https://crosspointreader.com/
+[46] https://sixcolors.com/post/2026/07/review-xteink-x3-is-the-little-e-reader-the-worlds-not-quite-ready-for/#fn-40773-firmware
+[48] https://sixcolors.com/post/2026/07/review-xteink-x3-is-the-little-e-reader-the-worlds-not-quite-ready-for/#fn-40773-koreader
+[50] https://sixcolors.com/post/2026/07/review-xteink-x3-is-the-little-e-reader-the-worlds-not-quite-ready-for/#fn-40773-cheap
+[52] https://sixcolors.com/post/2026/07/review-xteink-x3-is-the-little-e-reader-the-worlds-not-quite-ready-for/#fn-40773-crack
+[53] https://www.macworld.com/article/183458/drm-12.html
+[54] https://angryrobotbooks.com/
+[55] https://standardebooks.org/
+[56] https://www.gutenberg.org/
+[58] https://sixcolors.com/post/2026/07/review-xteink-x3-is-the-little-e-reader-the-worlds-not-quite-ready-for/#fn-40773-household
+[59] https://www.macworld.com/article/2157617/apple-ebooks-amazon-drm-libby.html
+[60] https://sixcolors.com/post/2026/07/review-xteink-x3-is-the-little-e-reader-the-worlds-not-quite-ready-for/#fnref-40773-iphone
+[61] https://sixcolors.com/post/2026/07/review-xteink-x3-is-the-little-e-reader-the-worlds-not-quite-ready-for/#fnref-40773-x4pro
+[62] https://brickclub.pages.dev/
+[63] https://sixcolors.com/post/2026/07/review-xteink-x3-is-the-little-e-reader-the-worlds-not-quite-ready-for/#fnref-40773-firmware
+[64] https://koreader.rocks/
+[65] https://sixcolors.com/post/2026/07/review-xteink-x3-is-the-little-e-reader-the-worlds-not-quite-ready-for/#fnref-40773-koreader
+[66] https://sixcolors.com/post/2026/07/review-xteink-x3-is-the-little-e-reader-the-worlds-not-quite-ready-for/#fnref-40773-cheap
+[67] https://sixcolors.com/post/2026/07/review-xteink-x3-is-the-little-e-reader-the-worlds-not-quite-ready-for/#fnref-40773-crack
+[68] https://sixcolors.com/post/2026/07/review-xteink-x3-is-the-little-e-reader-the-worlds-not-quite-ready-for/#fnref-40773-household
+[69] https://zeppelin.flights/@dmoren
+[70] https://dmoren.com/eternitys-tomb/
+[71] https://docs.google.com/forms/d/e/1FAIpQLSf0lFVDogE-JHK8iKf5q9zmVFyIwVdlHlVMC1vQ97ZQL2K6bA/viewform?usp=pp_url&entry.982800858=https://sixcolors.com/post/2026/07/review-xteink-x3-is-the-little-e-reader-the-worlds-not-quite-ready-for/
+[72] https://discord.com/channels/994648628247412756/1529488462808612974
+[73] discord://discord.com/channels/994648628247412756/1529488462808612974
+[74] https://sixcolors.com/subscribe/
+[76] https://sixcolors.com/sponsorship/
+[77] https://zeppelin.flights/@sixcolors
+[78] https://cottonbureau.com/people/the-incomparable
+[79] https://sixcolors.com/typos
+[80] https://feedpress.me/sixcolors?type=xml
+[81] https://sixcolors.com/?feed=json
+[82] https://www.theincomparable.com/blog/posts/privacy.html
+[83] https://wordpress.com/website-builder/?partner_domain=sixcolors.com&utm_source=Automattic&utm_medium=colophon&utm_campaign=Concierge%20Referral&utm_term=sixcolors.com
+[84] https://pressable.com/?utm_source=Automattic&utm_medium=rpc&utm_campaign=Concierge%20Referral&utm_term=sixcolors.com
+[92] https://jetpack.com/upgrade/search/?utm_source=poweredby
diff --git a/static/archive/webassembly-org-7kas9l.txt b/static/archive/webassembly-org-7kas9l.txt
@@ -0,0 +1,65 @@
+[1] [2]Overview [3]Getting Started [4]Specs [5]Docs [6]Feature Status [7]
+Community [8]News
+
+WebAssembly (abbreviated Wasm) is a binary instruction format for a stack-based
+virtual machine. Wasm is designed as a portable compilation target for
+programming languages, enabling deployment on the web for client and server
+applications.
+
+Developer reference documentation for Wasm can be found on [9]MDN's WebAssembly
+pages. The open standards for WebAssembly are developed in a [10]W3C Community
+Group (that includes representatives from all major browsers) as well as a [11]
+W3C Working Group.
+
+Efficient and fast
+
+The Wasm [12]stack machine is designed to be encoded in a size- and
+load-time-efficient [13]binary format. WebAssembly aims to execute at native
+speed by taking advantage of [14]common hardware capabilities available on a
+wide range of platforms.
+
+Safe
+
+WebAssembly describes a memory-safe, sandboxed [15]execution environment that
+may even be implemented inside existing JavaScript virtual machines. When [16]
+embedded in the web, WebAssembly will enforce the same-origin and permissions
+security policies of the browser.
+
+Open and debuggable
+
+WebAssembly is designed to be pretty-printed in a [17]textual format for
+debugging, testing, experimenting, optimizing, learning, teaching, and writing
+programs by hand. The textual format will be used when [18]viewing the source
+of Wasm modules on the web.
+
+Part of the open web platform
+
+WebAssembly is designed to maintain the versionless, feature-tested, and
+backwards-compatible [19]nature of the web. WebAssembly modules will be able to
+call into and out of the JavaScript context and access browser functionality
+through the same Web APIs accessible from JavaScript. WebAssembly also supports
+[20]non-web embeddings.
+
+
+References:
+
+[1] https://webassembly.org/
+[2] https://webassembly.org/
+[3] https://webassembly.org/getting-started/developers-guide/
+[4] https://webassembly.org/specs
+[5] https://webassembly.org/docs/faq/
+[6] https://webassembly.org/features/
+[7] https://webassembly.org/community/resources/
+[8] https://webassembly.org/news/
+[9] https://developer.mozilla.org/en-US/docs/WebAssembly
+[10] https://www.w3.org/community/webassembly/
+[11] https://www.w3.org/wasm/
+[12] https://webassembly.github.io/spec/core/exec/index.html
+[13] https://webassembly.github.io/spec/core/binary/index.html
+[14] https://webassembly.org/docs/portability/#assumptions-for-efficient-execution
+[15] https://webassembly.github.io/spec/core/exec/index.html#linear-memory
+[16] https://webassembly.org/docs/web/
+[17] https://webassembly.github.io/spec/core/text/index.html
+[18] https://webassembly.org/docs/faq/#will-webassembly-support-view-source-on-the-web
+[19] https://webassembly.org/docs/web/
+[20] https://webassembly.org/docs/non-web/
diff --git a/static/archive/www-manton-org-f8ohhe.txt b/static/archive/www-manton-org-f8ohhe.txt
@@ -0,0 +1,70 @@
+● [1]Manton Reece
+[2]About [3]Photos [4]Videos [5]Archive [6]30 days [7]90 parks [8]Reading [9]
+Search [10]Also on Micro.blog
+
+[11]Jul 22, 2026
+
+Dan Moren [12]reviews the Xteink X3 at Six Colors:
+
+    …it’s well positioned as an impulse buy. And while I don’t want to dissuade
+    you, I have to note the biggest caveat of all: the world.
+
+Amazon still dominates e-books too much. If Kindle was DRM-free, I would’ve
+ordered an X3 already.
+
+[13]Also on Bluesky
+● geesawra
+
+Calibre makes DRM removal quite easy nowadays.
+
+To be completely honest, what I’ve been doing lately is buy digital/physical
+copies of books and then find a DRM free copy online. As usual it’s a service
+problem!
+
+[14]2026-07-22 13:44
+
+Sign in with [15]Micro.blog, [16]Mastodon, or [17]Bluesky to reply:
+
+    [                                                  ]
+    [                                                  ]
+    [                                                  ]
+[21][                                                  ]
+
+[22][Post]
+
+[23] [3]
+[24] Manton Reece [25]@manton
+
+  • [26]RSS
+  • [27]JSON Feed
+  • [28]Surprise me!
+  • [29]Tweets
+
+[30]×[31]←[32]→
+
+References:
+
+[1] https://www.manton.org/
+[2] https://www.manton.org/about/
+[3] https://www.manton.org/photos/
+[4] https://www.manton.org/videos/
+[5] https://www.manton.org/archive/
+[6] https://www.manton.org/30-days/
+[7] https://www.manton.org/90-parks/
+[8] https://www.manton.org/reading/
+[9] https://www.manton.org/search/
+[10] https://micro.blog/manton
+[11] https://www.manton.org/2026/07/22/dan-moren-reviews-the-xteink.html
+[12] https://sixcolors.com/post/2026/07/review-xteink-x3-is-the-little-e-reader-the-worlds-not-quite-ready-for/
+[13] at://did:plc:pko7wbcggok753hnvndxh3ni/app.bsky.feed.post/3mraxxtongg2q
+[14] https://bsky.app/profile/did:plc:6ll5xi67lyuyovt6fiv4fnjo/post/3mray6nq7xc2r
+[15] https://micro.blog/account/comments/94476824/mb?url=https://www.manton.org/2026/07/22/dan-moren-reviews-the-xteink.html
+[16] https://micro.blog/account/comments/94476824/mastodon?url=https://www.manton.org/2026/07/22/dan-moren-reviews-the-xteink.html
+[17] https://micro.blog/account/comments/94476824/bluesky?url=https://www.manton.org/2026/07/22/dan-moren-reviews-the-xteink.html
+[23] https://www.manton.org/
+[24] https://www.manton.org/
+[25] https://micro.blog/manton
+[26] https://www.manton.org/feed.xml
+[27] https://www.manton.org/feed.json
+[28] https://www.manton.org/surprise-me/
+[29] https://www.manton.org/tweets/