Bare X Links Are Memory Rot
Slack backfills need captured text alongside source URLs so joelclaw discoveries survive hostile or blocked platforms.
This backfill from Slack #brain-joel preserved an X URL, but not the tweet content. The source could not be extracted, which means the artifact is mostly a pointer to a platform that may or may not let the system read it later.
That’s the useful part. A bare social link is not memory. It’s an IOU from X to future-you, and future-you should not trust that shit.
For joelclaw, the lesson is simple: when a Slack link gets promoted into an Obsidian discovery, the pipeline should save the surrounding message, the rendered text if available, screenshots or archive text when needed, and the original URL. The URL is provenance, not the payload.
Key Ideas
- X links are brittle source material because extraction can fail even when the URL is valid.
- Slack backfills should capture message context, not just links.
- Obsidian discovery notes need enough local text to remain useful if the source disappears.
- In joelclaw, the discovery pipeline should treat social URLs as provenance and captured content as the durable record.