commit 6c88e6785e799c858468b7cdff1d4f46fbe3043c
parent 23e78cefe41a36d9b3cfe85a6a1f78621cab3674
Author: Amit Dutta <mail@amit.is-a.dev>
Date: Sat, 29 Aug 2026 07:52:11 +0530
Merge pull request #1 from notamitgamer/docs/whatsapp-logger-4.2.x-upgrade-notes
whatsapp-logger docs: v4.2.x upgrade notes
Diffstat:
3 files changed, 43 insertions(+), 3 deletions(-)
diff --git a/src/whatsapp-logger/deploy-backend.md b/src/whatsapp-logger/deploy-backend.md
@@ -25,4 +25,31 @@ order: 870
Go to `https://your-app.onrender.com/logs` to see the logs from server. You have to login first to see the logs.
!!!
+## Excluding specific chats from logging
+
+If there are chats you don't want logged at all — a bot, a broadcast/status JID, a business account — edit `EXCLUDED_JIDS` in `src/config.js` on your fork before deploying:
+
+```javascript
+// --- CONFIGURATION ---
+const PORT = process.env.PORT || 3000;
+const AUTH_USER = process.env.AUTH_USER;
+const AUTH_PASS = process.env.AUTH_PASS;
+const MAX_LOGS = 500;
+const MAX_CONNECTIONS_PER_TOKEN = 15;
+const VERSION = '4.2.3';
+const EXCLUDED_JIDS = new Set(['']);
+
+module.exports = {
+ PORT,
+ AUTH_USER,
+ AUTH_PASS,
+ MAX_LOGS,
+ MAX_CONNECTIONS_PER_TOKEN,
+ VERSION,
+ EXCLUDED_JIDS
+};
+```
+
+`EXCLUDED_JIDS` is a set of full JIDs (the `...@s.whatsapp.net` / `...@g.us` / `...@lid` identifiers, not just a phone number) that are skipped entirely — they won't be cached, streamed, or included in exports. It ships empty by default. You can find a chat's exact JID from the live server logs (see the tip above) the first time it logs a message, then add it here, e.g. `new Set(['917278779512@s.whatsapp.net', '201554426618024@lid'])`, and redeploy.
+
Continue to [Connect WhatsApp](connect-whatsapp.md).
diff --git a/src/whatsapp-logger/index.md b/src/whatsapp-logger/index.md
@@ -8,9 +8,14 @@ order: 900
A privacy-focused, self-hosted WhatsApp archiving tool. It captures messages — including deleted ones — via a linked device connection and stores them in your own Firebase Firestore database.
-!!!warning Security update in v4.2.1
-Versions before v4.2.1 shipped a public Firebase Web SDK config in the frontend, which let anyone who viewed the page source read your chat database directly, bypassing login. As of v4.2.1, the frontend talks only to your Render backend over an authenticated connection — Firestore is never reachable from the browser. If you're on an older version, update and follow the revised [Firebase Setup](firebase-setup.md) and [Frontend Setup](setup-frontend.md) steps.
-!!!
+## Upgrade notes (v4.2.x)
+
+If you're updating from an older version, here's everything that changed across the v4.2.x line in one place:
+
+- **v4.2.1 — Security fix.** Removed the public Firebase Web SDK config from the frontend. The frontend now only talks to your Render backend, never Firestore directly. Update your Firestore rules to deny all direct client access, as shown in [Firebase Setup](firebase-setup.md).
+- **v4.2.2 — Real-time sync now covers every chat, not just the one you have open.** Previously, new messages only arrived for a chat you already had open — anything happening in other chats sat on the server until you clicked into them. Now a single sync connection streams updates for *all* chats at once, so incoming messages show up across every contact the moment they arrive, the way WhatsApp itself behaves when your phone comes back online.
+- **v4.2.2 — Full resync with real progress.** `Settings` → refresh icon → `Hard Reset` now pulls your entire message history chat-by-chat instead of one giant download, so the progress bar reflects actual messages fetched instead of a rough guess. Use this if you ever open a chat that shows nothing locally even though the server has history for it — for example after clearing site data, or on a new device or browser.
+- **UI refresh.** Reworked to three selectable themes — Catppuccin Latte (light), Catppuccin Mocha (dark), and a true-black AMOLED theme — replacing the old dark-mode toggle and the multiple chat-background picker. Find it under `Settings` → `Appearance` → `Theme`.
!!!success Is this safe to use?
Yes. WhatsApp bans accounts for *sending* spam or unauthorized automated messages — this tool is a **100% passive, read-only listener**. It connects using the official Multi-Device WebSocket protocol, the same way linking a second browser to WhatsApp Web works. Since it doesn't interact with anyone, there's no risk of being reported.
diff --git a/src/whatsapp-logger/usage.md b/src/whatsapp-logger/usage.md
@@ -13,4 +13,12 @@ order: 840
- **Search** — filter contacts by name or phone number
- **Export** — download chat history as a `.txt` file
+## Missing history on a new device or browser?
+
+If you open a chat and it shows nothing even though the server has history for it — for example right after clearing your browser's site data, or the first time you load the app on a new device — go to `Settings` → refresh icon → `Hard Reset`, enter your credentials, and it will pull your entire message history back down chat-by-chat, with a progress bar showing real fetch progress.
+
+## Theme
+
+Pick between Catppuccin Latte (light), Catppuccin Mocha (dark), or a true-black AMOLED theme under `Settings` → `Appearance` → `Theme`.
+
Continue to [Keep it Alive](keep-alive.md).
