karpathy

LLM Wiki

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

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.

gatekeeper1122

WARNING: freeShop no longer works so this guide is mostly redundant (If you want your encTitleKeys.bin file, you can still follow this guide)

Step 1
Open GodMode9 by holding Start on bootup (if you have more then 1 payload, then the Luma Chainloader menu will appear and you just select GodMode9 from there)

Step 2
Once in GodMode9, press the Home Menu Button then go to More... -> Build Support Files and press A on the prompt.

Step 3
Once the files have generated, press the Start button to go to the Home Menu and open FBI.

mocelet

diff --git a/CodecUtils.smali b/CodecUtils.smali
index 79562da..b1650ae 100644
--- a/CodecUtils.smali
+++ b/CodecUtils.smali
@@ -314,6 +314,19 @@
 
     invoke-direct/range {v0 .. v6}, Lcom/amazon/spiderpork/streamconfig/codec/CodecConfig;-><init>(Ljava/lang/String;Ljava/lang/String;Ljava/lang/Integer;Ljava/lang/Integer;ZZ)V
 
+    # Avoid codecs not supporting low latency
+    invoke-virtual {v0}, Lcom/amazon/spiderpork/streamconfig/codec/CodecConfig;->isLowLatency()Z

mocelet

diff --git a/CodecOverrides.smali b/CodecOverrides.smali
index e9c2a15..e7a0e10 100644
--- a/CodecOverrides.smali
+++ b/CodecOverrides.smali
@@ -45,7 +45,7 @@
 
     move-result-object v17
 
-    const/high16 v2, 0x10000
+    const/4 v2, 0x1

LondheShubham153

Git Commands

This Gist contains all the useful commands for Git

Version control is a system that records changes to a file or set of files over time so that you can recall specific versions later.

If you are a developer and want to keep every version of your code/project (which you would most certainly want to), a Version Control System (VCS) is a very wise thing to use.

• All the commands used for Git

jgoosey

#Requires -Version 5.1
<#
.SYNOPSIS
    Enumerates running processes, their loaded modules (DLLs), and optionally
    lists exported functions per module. Useful for defensive research --
    understanding which processes have security-relevant DLLs loaded and
    what API surface they expose.

.DESCRIPTION
    This script builds a profile of your running process landscape:

Richard-Barrett

Open WebUI + Ollama + Hugging Face on macOS and Windows

A practical setup guide for running a local AI troubleshooting and support environment on either macOS or Windows using:

• Open WebUI for the browser-based chat interface
• Ollama as the local model runtime
• Hugging Face as an optional source for GGUF models
• Docker Compose for running Open WebUI
• Apple Silicon / Metal acceleration through native Ollama

joonaspaakko

// https://gist.github.com/joonaspaakko/df2f9e31bdb365a6e5df

// Finds all .ai files from the input folder + its subfolders and converts them to the version given below in a variable called "targetVersion"

// Tested in Illustrator cc 2014 (Mac)
// Didn't bother to do a speed test with my macbook air...

#target illustrator

	// If set to false, a new file will be written next to the original file.

Hona

description	Implement with clear orchestration, strong interfaces, and happy-path-first design

Code like Luke.

Implement the requested change, but optimize the design for the normal user flow. If the happy path is 95% of runtime behavior, it should be approximately 95% of the code readers see.

Start with context:

• inspect the existing code, callsites, data flow, and nearby conventions

stephancasas

0: ProcIntr
1: SwitchFwd
2: SwitchBack
3: SessionIntr
4: ScreenSaver
5: DiskEject
6: ProcKill
7: AccessMenu
8: AccessDock
9: AccessWindow