Archilvx-Own your Twitter data because cloud tools will fail you

One hour ago, while working with Claude, the session timed out, I was logged out, and my entire progress vanished. It was a sharp, frustrating reminder of a lesson I thought I’d already learned: If you don’t have a local copy of your data, you don’t own it. We are living in an era of "information redundancy," yet our digital assets are more fragile than ever. We rely on LLMs that crash at random and on social platforms that bury our bookmarks under layers of messy UI and slow "official archives." I built Archivlyx because I got tired of the "black box" nature of my digital footprint on X (Twitter). Whether it’s a technical thread you liked or a resource you bookmarked, finding it again shouldn't feel like a chore. What is Archivlyx? It’s a browser extension designed to let you browse, export, and manage your Twitter likes and bookmarks with zero friction. Why use this instead of the official archive? • The "Export First" Rule: I’ve reached a point where I won't use a productivity tool unless I see a clear "Export" button. Archivlyx lets you pull your data into formats you actually use. • Local-First Privacy: We don’t store a single byte of your data on our servers. Everything happens locally in your browser. Your digital assets stay yours. • Intelligent Batch Operations: For the HN crowd—I know the risks of automation. We’ve implemented automatic sub-task splitting for batch cleaning and archiving. By breaking operations into smaller, randomized chunks, we maximize account safety and respect rate limits without you having to micromanage it. • Search & Sanity: The native Twitter interface is built for scrolling, not for retrieval. Archivlyx turns your cluttered likes into a searchable, filterable database. The Tech: The extension is built to be lightweight and stay out of your way. The core logic focuses on transforming messy API responses into a clean, local UI that enables "one-click" cleanup or mass exports. I’d love to hear your thoughts on the redundancy mechanisms or any features you'd want in a "digital graveyard-turned-library." Chrome Web Store Link: https://chromewebstore.google.com/detail/archivlyx-%E2%80%93... Website: https://www.archivlyx.com/ I'll be around to answer any technical questions about the batch processing or the local storage implementation!