Stefan sschueller

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.

Installing Windows and Linux into the same partition

But WHY?

There was a reddit post about installing Arch on NTFS3 partition. Since Windows and Linux doesn't have directories with same names under the /(C:\), I thought it's possible, and turned out it was actually possible.
If you are not familiar to Linux, for example you've searched on Google "how to dualboot Linux and Windos" or brbrbr... you mustn't try this. This is not practical.

Pre-requirements

UEFI system
Any Linux live-boot CD/DVD/USB... with Linux kernel newer than 5.15
Windows installer USB

Proxmox - SPICE client setup for MacOS

Install a working (and compiled) version of virt-viewer. You may view the homebrew package's upstream source on GitHub.
```
brew tap jeffreywildman/homebrew-virt-manager
brew install virt-viewer
```
Once that's installed should be able make a call remote-viewer with a pve-spice.vv file downloaded from proxmox web interface

Docker on Android 🐋📱

Edit 🎉

All packages, except for Tini have been added to termux-root. To install them, simply pkg install root-repo && pkg install docker. This will install the whole docker suite, left only Tini to be compiled manually.

Summary

Netgear Signed TLS Cert Private Key Disclosure

Overview

There are at least two valid, signed TLS certificates that are bundled with publicly available Netgear device firmware.

These certificates are trusted by browsers on all platforms, but will surely be added to revocation lists shortly.

The firmware images that contained these certificates along with their private keys were publicly available for download through Netgear's support website, without authentication; thus anyone in the world could have retrieved these keys.

Not happy with Docker modifying your precious firewall rules?

Docker inserts iptables rules when it's started by default
buster uses nftables by default
let's make Docker use nftables instead
PROFIT

Prerequisites

Install Docker CE and nftables:


	.global _main
	.extern _putchar

	.align 4

	_main:
	; prolog; save fp,lr,x19
	stp x29, x30, [sp, #-0x20]!
	str x19, [sp, #0x10]

	[temperature_sensor rpi_sensor]
	sensor_type: rpi_temperature
	min_temp: -40
	max_temp: 85

	[pause_resume]

	[neopixel my_neopixel]
	pin: PA8

	{
	"title": "Takeout API",
	"discoveryVersion": "v1",
	"ownerName": "Google",
	"version_module": true,
	"resources": {
	"exports": {
	"methods": {
	"get": {
	"flatPath": "v2/{service}/exports/{exportId}",

	#!/bin/bash

	gdb -p "$1" -batch -ex 'set {short}$rip = 0x050f' -ex 'set $rax=231' -ex 'set $rdi=0' -ex 'cont'