Digital preservation tools and philosophy. Graceful degradation, plain-text archival, and building systems that outlast their creators.
Not resurrection. Not immortality. Just love that still responds.
I have stage 4 cancer. That is part of why I build these tools.
I build tools for preserving digital artifacts: conversations, bookmarks, photos, email, ebooks. The tools share a philosophy: your data should be readable in fifty years without the original software.
Every tool in this ecosystem exports to formats that work at multiple levels:
Level 1: Full app → Semantic search, rich UI
Level 2: Database → SQLite queries (app gone, database remains)
Level 3: File search → grep through JSONL (just text tools)
Level 4: Human reading → Markdown, HTML (no tools needed)
Level 5: Fallback → Plain text in any editor
If the software disappears, the data does not. If the database corrupts, the JSONL files remain. If everything fails, the plain text survives.
Archive tools, each handling one domain:
Orchestration:
The posts in this series range from tool announcements and technical walkthroughs to philosophical pieces about digital legacy, identity preservation, and what it means to build an echo of yourself from your own data.
Some of the fiction I write connects here too. The novels explore what happens when AI systems carry patterns of people who are gone, which is the same question longshade asks, just dramatized.
Philosophy and tool for durable personal archives — validate, query, and build browsable single-file sites
Explore project →Not resurrection. Not immortality. Just love that still responds. How to preserve AI conversations so they remain accessible decades from now, even when the original software is long gone.
On maintaining direction under entropy, making things as resistance, and the quiet privilege of having any space at all to think beyond survival.
On building comprehensive open source software as value imprinting at scale, reproducible science, and leaving intellectual legacy under terminal constraints.
A message in a bottle to whatever comes next. On suffering, consciousness, and what mattered to one primate watching intelligence leave the body.
If superintelligence endures beyond us, remembrance shifts from memory to query. Building legacy systems not for nostalgia, but to remain legible in a future where legibility determines what persists.
Three CLI tools for preserving your digital intellectual life: conversations, bookmarks, and books. SQLite-backed, exportable, built to outlast the tools themselves.
Graceful degradation made concrete: years of bookmarks exported to a self-contained HTML app that works offline, forever.
A plugin-based system for importing, storing, searching, and exporting AI conversations from multiple providers in a unified tree format. Part of the Long Echo project.
A database-first bookmark manager with NLP auto-tagging, full-text search, and content caching.
An eBook metadata management tool with a SQLite backend, knowledge graphs, semantic search, and MCP server integration. Part of the Long Echo project.
Expanding the Long Echo ecosystem with photo and mail archival. Your memories and correspondence deserve the same preservation as your conversations and bookmarks.
longecho evolves from specification to implementation with build, serve, and manifest features.
Expanding the Long Echo toolkit with photos and mail, building toward longshade, the persona that echoes you.
API design encodes philosophical values: mutability, explicitness, error handling. Your interface shapes how people think about problems.