Bakwaas needs IndexedDB and the Origin Private File System to store its index locally. Try Chrome 120+, Edge 120+, Safari 17+, or Firefox 125+.
Don't have one yet? Request it at x.com/settings/download_your_data. It arrives by email in about a day.
बकवास Hindi/Urdu, noun — nonsense, drivel, hot air, chitchat. The stuff you say a lot of but rarely re-read.
Bakwaas is a browser-native explorer for your social-media archives. It started as a click-to-delete tool for Twitter/X, but it turns out the harder problem isn't deleting — it's finding what's worth deleting in 200,000 posts. So mostly it's now an explorer that happens to make deletion easy at the end.
Supported sources: Twitter/X (full surface), Mastodon (no engagement counts in their export), Bluesky (live API, full surface), Reddit (posts + comments, no engagement counts).
Everything runs locally. Your archive stays in this tab. No server, no accounts, no API keys to X required. Even Wrapped exports are downloads from your browser, not uploads from it.
One honest exception: Bakwaas uses Google Analytics 4 (G-E5XCNWFXNC) for page visits and tab opens — basic 'is anyone using this' counters. No archive content is ever sent. anonymize_ip is on. Use uBlock / Privacy Badger to block it if you'd prefer.
Bakwaas never calls X's API. To delete a tweet you click it open on X, delete it there in the real UI, then come back and confirm. Manual, on purpose. The hard part — knowing what to delete — happens here. The actual delete happens in X's own UI.
There's also an optional Delete via X API mode: paste your own OAuth 1.0a credentials (Consumer Key, Consumer Secret, Access Token, Access Token Secret) into the panel at the bottom of the Selection tab, and a "Delete via X API" button appears in the selection bar. Bakwaas signs each DELETE request with HMAC-SHA1 locally — your keys never leave your browser. The button stays hidden until credentials are saved.
Twitter / X: x.com/settings/download_your_data → wait ~24 hours → drop the ZIP, or use "Open unzipped folder" (Chrome/Edge) for the FSA path with a sidecar state file written alongside the archive.
Mastodon: Instance settings → Preferences → Import and Export → Request your archive → wait a few minutes → drop the ZIP. Mastodon exports don't include engagement counts, so engagement-driven cards stay quiet — everything else works.
Bluesky: just type your handle (name.bsky.social) in the "Fetch from Bluesky" box on the drop screen. Bakwaas pages through the public AppView API — no auth, no archive request. Engagement counts come back live, so all surfaces work.
Reddit: reddit.com/settings/data-request → wait a few days for the GDPR export → drop the ZIP. Reddit exports cover posts + comments but no engagement counts, so engagement-driven cards stay quiet.
Hindi/Urdu, noun — nonsense, drivel, hot air, chitchat. The stuff you say a lot of but rarely re-read.
A browser-native explorer for your social-media archives. Drop a Twitter/X, Mastodon, Bluesky, or Reddit export and dig into it locally — no server, no accounts, nothing uploaded.
Everything stays in your browser. Always.
Bring your own keys. Bakwaas uses your X developer credentials to delete tweets directly via the v2 API. Nothing leaves your tab except to api.x.com, signed with your keys.
X's v2 DELETE endpoint costs money these days. As of 2026 the Basic tier (~$200/month) gets you a couple of hundred deletes per 15-minute window. The Free tier may not support writes at all. Bakwaas can't tell you what your tier allows — try the test connection above; if it returns your user, deletes will probably work.
Bakwaas paces requests politely (≈12/sec) and backs off automatically when the API returns 429. Hitting your tier's window means a wait until the reset timestamp.
Nothing leaves your machine except to api.x.com. Keys are stored in IndexedDB only (never the FSA sidecar, never any NakliTechie server).
…
—