Skip to content

Instantly share code, notes, and snippets.

@bgromov
bgromov / git-reset-author.sh
Created June 23, 2016 17:50
Git: reset author for ALL commits
#!/bin/sh
# Credits: http://stackoverflow.com/a/750191
git filter-branch -f --env-filter "
GIT_AUTHOR_NAME='Newname'
GIT_AUTHOR_EMAIL='new@email'
GIT_COMMITTER_NAME='Newname'
GIT_COMMITTER_EMAIL='new@email'
" HEAD
@smith153
smith153 / provision-uat.sh
Created July 18, 2026 18:04
Libvirt Powered Claude Sandbox
#!/usr/bin/env bash
set -euo pipefail
# ─────────────────────────────────────────────────────────────────────────────
# uat provisioner — LXQt + Chrome acceptance-testing desktop under qemu:///system.
# Runs entirely as your normal user (no sudo): disks live in a path you own,
# and libvirtd (already root) does the privileged VM/network work.
# Keep uat-cloud-init.yaml and uat-net.xml next to this script.
# ─────────────────────────────────────────────────────────────────────────────
# Pin a clean PATH so a custom python (pyenv/conda/etc.) can't shadow the system
CVE-2025-43520 - DarkSword
1. cluster_read_ext and cluster_write_ext call cluster_io_type to determine what IO operation to perform
2. cluster_io_type calls vm_map_get_upl with UPL_QUERY_OBJECT_TYPE to query type of the vm_object that backs the user-supplied virtual address range
3. If this object is physically contiguous it returns IO_CONTIG, otherwise it returns IO_DIRECT or IO_COPY
4. If cluster_io_type returns IO_CONTIG, cluster_[read|write]_ext will call the "contig" variant, cluster_[read|write]_contig
5. cluster_[read|write]_contig then calls vm_map_get_upl a second time to get the UPL from the uio
6. It then grabs the first physical page from the UPL using upl_phys_page and performs a physical copy
7. This is a TOCTOU. An attacker can remap the virtual address range so that the region is no longer physically contiguous after the first call to vm_map_get_upl, causing an OOBR/OOBW to physmem
@markknol
markknol / shadertoy.md
Last active July 18, 2026 18:34
Shader cheatsheet (from shadertoy)

This help only covers the parts of GLSL ES that are relevant for Shadertoy. For the complete specification please have a look at GLSL ES specification

Language:

Version: WebGL 2.0
Arithmetic: ( ) + - ! * / %
Logical/Relatonal: ~ < > <= >= == != && ||
Bit Operators: & ^ | << >>
Comments: // /* */
Types: void bool int uint float vec2 vec3 vec4 bvec2 bvec3 bvec4 ivec2 ivec3 ivec4 uvec2 uvec3 uvec4 mat2 mat3 mat4 mat?x? sampler2D, sampler3D samplerCube
Format: float a = 1.0; int b = 1; uint i = 1U; int i = 0x1;

@MarlonPassos-git
MarlonPassos-git / README.md
Last active July 18, 2026 18:32
grill-me-codex

grill-me-codex

Small Codex skills for better planning with request_user_input.

This is a tiny adaptation of the grill-me workflow for Codex.

The goal is simple: make Codex ask better planning questions before writing code, without forcing you into a heavier workflow like a full spec system.

Why

@RonanGil
RonanGil / Conventions_WinForms.txt
Created July 24, 2023 15:48
Naming Conventions - winForms
# Componentes Windows Forms
Common Controls:
----------------
btn Button chk CheckBox ckl CheckedListBox
cmb ComboBox dtp DateTimePicker lbl Label
llb LinkLabel lst ListBox lvw ListView
mtx MaskedTextBox cdr MonthCalendar icn NotifyIcon
nud NumeircUpDown pic PictureBox prg ProgressBar
rdo RadioButton rtx RichTextBox txt TextBox
@hanyuancheung
hanyuancheung / llm-skill.md
Last active July 18, 2026 18:29
LLM SKILL

LLM-SKILL

Runnable Implementation: https://github.com/hanyuancheung/llm-skill

This is a first-person record of how I took Karpathy's LLM-Wiki intuition and turned it, step by step, into the llm-skill project. I'll walk through: where I started, why I chose this particular layering, what each layer solves.


1. Starting point: what I actually took away from LLM-Wiki

@muhammedaydogan
muhammedaydogan / federated-llm-wiki.md
Last active July 18, 2026 18:29
federated-llm-wiki-draft

federated-llm-wiki - Work In Progress

a federated, pluggable LLM memory system

A single llm-wiki is good. But you will eventually want more than one. And then you'll want them to talk to each other. That's what this is.

federated-llm-wiki should let you deploy vaults in minutes, connect them in a clean DAG, plug in agents and UI components, and scale from a single personal wiki to a network of federated knowledge bases — covering completely unrelated topics — under one roof.

Not centralized — So, no global authority. Not decentralized — So, no trustless chaos. Federated: each vault governs its own knowledge; connections are explicit, directional, and acyclic.