Threadwell
Recovered threads and submerged records.
An archive of material that is not reliably web-indexed: Twitter/X threads, talks, and other primary sources, plus the notes distilled from them.
- Archive — objective records of threads and other sources
- Canvases — maps and relationship diagrams
- Notes — authored essays and syntheses
- How threads are organized — how a thread folder is laid out
Start a new record from the templates in templates/. Public folders publish by default; set draft: true to keep a note off the site.
Threads are filed by author handle, then by date and title. The main note in each folder is that author’s own chain. Replies live beside it.
How to read a folder: notes/How threads are organized.
Example of the note shape (single spine, no branches): archive/threads/How to archive a thread
Talks, essays, videos, and other records that are not sequential threads. Same archive-source template; set source to youtube, odysee, article, or other.
Obsidian .canvas files in this folder render as pannable pages on the site.
Starter map: overview
Essays and syntheses. Link back to archive records instead of restating the primary source.
Use the authored-note template. Example: What this archive is for
Convention: How threads are organized
Source
- URL:
- Author:
- Posted:
Thread
1/ First post. Copy the text. Do not summarize here.
2/ Next post. Keep numbering. Preserve links as written.
3/ Last post.
Media
Images use direct HTTPS URLs from the original provider when possible:
A live tweet embed is optional and is not the archive:
Related
- How folders work: How threads are organized
- Distilled note: What this archive is for
Threads are grouped by author handle, then by date and a short title.
archive/threads/<handle>/<YYYY-MM-DD-slug>/
index.md ← the author's own chain (the spine)
YYYY-MM-DD-who-slug.md ← one file per reply that left that chain
Spine
index.md is the opening author’s chain. Posts are numbered 1/ 2/. Each number line names who spoke: **1/** @SebAaltonen. Reply @handles sit on the next line. The tweet text starts after that. A mention inside the tweet is not the author.
Cross-author spines list every post in time order. The handle on the number line is who spoke.
If the first post is a reply to someone else, that other tweet is quoted at the top as context. It is not numbered as part of the spine.
Branches
A reply from someone else, or a second chain the author started from an earlier post, is its own note in the same folder. Follow-ups on that reply stay in that note, including if the original author answers there.
The spine links out under the post that grew the branch. Each branch note links back to index.
Cross-author conversations
When a thread alternates between authors, the folder belongs to the opening post. The spine walks every post in time order. Replies stay in that folder. The other authors do not get a second copy.
Tags
Every thread starts with archive, twitter, and the author’s handle. Topic tags (vulkan, crt, alsa, …) are added by hand when the thread is reviewed.
Images
Pictures on the site are the original host URLs. Working copies live outside what GitHub Pages serves. A note still being prepared is marked draft: true and stays off the site.
Reading
Start at Threads, pick a handle, then a date. The spine is the essay. Branch files are the conversation around it.
Threadwell holds material that search engines and platform pages do not keep reliably. The split is strict:
| Folder | Role |
|---|---|
archive/ | Primary source. What was said. |
notes/ | Your writing. What it means. |
canvases/ | Spatial maps between the two. |
How a thread is filed: How threads are organized.
An authored note should wikilink the archive record instead of pasting the thread again.
Set draft: true until a note is ready. archive/, canvases/, and notes/ publish otherwise.