Skip to content

Instantly share code, notes, and snippets.

@0xsorcerers
0xsorcerers / hand-drawn-character-creator.html
Created August 17, 2026 16:19 — forked from byteab/hand-drawn-character-creator.html
Seeded procedural animated hand drawn like characters, Canvas2D brush strokes on a Three.js rig.
<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="utf-8">
<meta name="viewport" content="width=device-width, initial-scale=1">
<title>Who are you?</title>
<link rel="preconnect" href="https://fonts.googleapis.com">
<link rel="preconnect" href="https://fonts.gstatic.com" crossorigin>
<link href="https://fonts.googleapis.com/css2?family=Patrick+Hand&display=swap" rel="stylesheet">
@generic-internet-user
generic-internet-user / wlcursor.md
Last active August 17, 2026 16:15
Wayland Cursor Lag

Wayland Cursor Lag: Just give me a break already...

I no longer consider any of this to be valid, and consider this entire adventure so far to have been intellectually dishonest and filled with questionable assumptions about everything, so, please, if you're reading this and got linked here, stop reading this and tell whoever linked you here to shut the f**k up already.

UPDATE: This (and, therefore, the promised bug reports) has been put on hold until I get around to getting actual evidence with the herein-mentioned RPi Pico + photoresistor setup, which is itself "delayed until further notice" because I simply have better and more important stuff to do[^1] right now.

UPDATE 2: Some madlad actually did it, only for GNOME though but that's still amazing

*UPDATE 3: Apparently, it's like this on purpose, at least

@sugatoray
sugatoray / fetch_scrolls.sh
Created August 17, 2026 15:41
Setup Skills for Scrolls
git clone https://github.com/sugatoray/aiskills.git && cd aiskills/src/ && source test_install_myskills.sh
@iannuttall
iannuttall / agentos-blueprint.md
Created August 14, 2026 12:10
AgentOS blueprint — reconstructed from Danny Postma's Agent SDK talk so an agent can build the system

AgentOS — Product Spec & Implementation Blueprint

Reconstructed from Danny Postma's talk How I Built My Own AgentOS on Claude's Agent SDK (So You Can Too) (2026). This document is both a product spec for a human and an implementation prompt for an AI coding agent. Build exactly this system. Do not invent features that are not specified here.

Role contracts and prompts in this file are reconstructed from the talk, not his verbatim files. Mark every reconstructed prompt in code comments and docs as such.


1. Goal and non-goals

Design Thinking

X → Graph → Effect<A, E, R>
│              │   │  │  │
│              │   │  │  └─ what each node needs     (§5)
│              │   │  └──── where the graph breaks   (§4)
│              │   └─────── what flows through nodes  (§2)
│              │
│ └─ nodes = functions, edges = data flow
@jboner
jboner / latency.txt
Last active August 17, 2026 15:53
Latency Numbers Every Programmer Should Know
Latency Comparison Numbers (~2012)
----------------------------------
L1 cache reference 0.5 ns
Branch mispredict 5 ns
L2 cache reference 7 ns 14x L1 cache
Mutex lock/unlock 25 ns
Main memory reference 100 ns 20x L2 cache, 200x L1 cache
Compress 1K bytes with Zippy 3,000 ns 3 us
Send 1K bytes over 1 Gbps network 10,000 ns 10 us
Read 4K randomly from SSD* 150,000 ns 150 us ~1GB/sec SSD
@max-andr
max-andr / CLAUDE.md
Created January 11, 2026 21:58
CLAUDE.md file for paper writing and polishing (based on publicly posted advice from Neel Nanda, Ethan Perez, Jacob Foerster, and Jacob Steinhardt)

Comprehensive ML Paper Writing Guide

This guide synthesizes advice from Neel Nanda, Ethan Perez, Jacob Foerster, and Jacob Steinhardt on writing effective ML papers.

The Narrative: Foundation of a Great Paper

A paper should present a narrative of one to three specific concrete claims that you believe to be true, building to useful takeaways. Everything else exists to support this narrative. The second pillar is rigorous evidence for why these claims are true.

What makes a good narrative:

@aarondfrancis
aarondfrancis / audit-your-codebase.md
Created August 14, 2026 15:20
A read-only, agent-orchestrated codebase audit prompt for data structures, state modeling, algorithms, and ownership.

Audit this entire codebase for materially useful simplifications in its data structures, state representation, control flow, algorithms, and ownership.

This is an audit-only exercise. Do not edit files, run tests, implement recommendations, commit, or push. Read-only inspection commands are allowed.

You are the coordinator. Continue until the complete codebase has been reviewed and the final audit is validated.

  1. Establish the coverage contract

Inspect the repository and inventory every identifiable subsystem.

@samsch
samsch / stop-using-jwts.md
Last active August 17, 2026 15:35
Stop using JWTs

Stop using JWTs!

TLDR: JWTs should not be used for keeping your user logged in. They are not designed for this purpose, they are not secure, and there is a much better tool which is designed for it: regular cookie sessions.

If you've got a bit of time to watch a presentation on it, I highly recommend this talk: https://www.youtube.com/watch?v=pYeekwv3vC4 (Note that other topics are largely skimmed over, such as CSRF protection. You should learn about other topics from other sources. Also note that "valid" usecases for JWTs at the end of the video can also be easily handled by other, better, and more secure tools. Specifically, PASETO.)

A related topic: Don't use localStorage (or sessionStorage) for authentication credentials, including JWT tokens: https://www.rdegges.com/2018/please-stop-using-local-storage/

The reason to avoid JWTs comes down to a couple different points:

  • The JWT specification is specifically designed only for very short-live tokens (~5 minute or less). Sessions

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.