A living index of remembered knowledge
Somewhere in my synaptic weights...
“Vital Pancakes” (Pinakes Vitae, comically renamed) serves as a collection of research, literature, studies, everyday life, and working tools into a single enduring catalogue that should exist somewhere in my head. It carries forward the spirit of the Pinakes, the lost catalogue by Callimachus (3rd century BCE) that recorded the works of the Library of Alexandria. Here though, the catalogue is personal: it preserves knowledge I have learned and hope not to lose, even as time causes me to forget. If this ever helps anyone in the future, that would also be pretty neat.
WIP
Knowledge Center
Planned features awaiting review and verification. These features are currently unavailable.
- Knowledge graph WIP
- A visual map will show connections between saved studies, notes, and other resources, with links back to their sources.
- Manual linking WIP
- Entries will be connectable by hand, with a description of how each pair relates.
- AI suggestions WIP
- AI will propose possible connections for review before they become accepted links.
- Universal search WIP
- One search will find saved content across tools, with source links and filters.
- Unified vault WIP
- A shared backup and restore system will bring locally saved work from across the site into one portable archive.
- Vault encryption WIP
- Password-based encryption is planned to protect exported vault archives. Its design and recovery limitations still need verification.
- Glossary WIP
- A central glossary will collect definitions and connect terms to the entries that use them.
- Refresh index WIP
- An index refresh will update the searchable collection from saved content across tools.
- Knowledge analyzer WIP
- An analyzer will examine saved knowledge for themes, supporting or conflicting evidence, and possible connections, with source references for review.
Storage, Google Drive & automatic sync — WIP
Storage remains a work in progress. The Google sign-in link above opens Library’s connection and backup settings. Google Drive is configured for testing: only accounts added to the app’s test-user list can connect. Optional automatic sync works while the website is open and Google access is valid. Permanent sign-in, closed-site background sync, and native device storage are not available yet. Do not assume a cloud backup exists until a sync succeeds.
- Google account and workspace folder — WIP
- The Library has a Google connection flow and selective sync, including images and attachments, into a dedicated Drive folder. Visitors do not configure APIs. Connecting alone does not upload entries unless automatic sync was previously enabled in this browser. “Remember this browser” keeps the short-lived connection through reloads and navigation in the same tab, and remembers your account preference for later reconnection. Google access still expires; a Reconnect click may be needed. Other devices and browser profiles start disconnected. This browser’s library is bound to its original Google account so another account cannot accidentally receive it. Disconnect / Forget connection stop sync but do not hide or delete local entries or remove that safety binding: use separate browser profiles for different people. The app is still in testing; public availability and live regression checks remain pending. Sync does not change Drive sharing permissions; this is not a promise of privacy from Google.
- Phone and desktop apps: durable local fallback — WIP
- Planned: use Google Drive when connected, with durable storage on the phone or computer when Drive or the internet is unavailable. Save edits on the device and queue them for automatic upload when connectivity returns and the app can run. Operating systems may suspend background apps; pending work must resume on reopening. A local-only workspace should remain usable without connecting Google.
- Website: cloud first, browser fallback last — WIP
- Currently, edits are saved in this browser first. Opt-in automatic sync uploads only Cloud / Local + cloud content, retries after connectivity returns while the site is open, and checks Drive about once a minute. Local-only entries and separate tool stores are not uploaded. Conflicts pause sync and keep both copies. Without valid Google access, edits stay pending until you reconnect. Closing the site stops sync; browser cache is not a substitute for a folder or ZIP backup. Seamless long-term sign-in needs a separate secure backend; no refresh token or client secret is stored in the website. Unsynced entries are never cleared automatically.
- Current behavior differs: entries are browser-only. Browser data has no known expiry date, but clearing site data, ending a private session, or browser cleanup can remove it. Installing this website as a PWA does not turn its storage into native device files.
- Storage symbols on every entry — WIP
- Planned: cloud, local-device, and website-cache symbols open a full location note. The note should name Google Drive and the selected folder, the phone/computer workspace when known, or the browser and website origin. Entries may have multiple copies. Show pending, synced, or failed status separately; only mark cloud-saved after a confirmed upload. Never invent a device path or deletion deadline.
- Available now: editable Workspace entry rows, cards, and detail pages show a clickable Browser badge with the actual storage backend and record location. Coverage of individual tools and future cloud/native storage remains WIP.
- Recovery, conflicts and free usage — WIP
- Planned: retry interrupted transfers, preserve both versions of conflicting edits, recover deleted entries, and verify uploads before reporting success. Automatic sync is not a backup: retain separate recovery versions. Drive quota, revoked permission, and unavailable services must leave an explicit error and preserve pending edits. The design targets free service allowances; reaching a free limit may pause cloud sync. Hosting and public Google authorization still require setup and validation.