A calmer X notifications page and conversation view.
CalmX makes notifications and replies from accounts below your follower threshold less prominent. Choose separate thresholds, adjust visibility, and keep reading without removing posts or muting accounts on X.
English | Русский
- Dims low-follower notifications and replies, with optional grayscale and reveal on hover or keyboard focus.
- Keeps Premium accounts undimmed when X explicitly reports
is_blue_verified: true. - Marks posts from authors who have blocked you with a light red tint and fixed 40% visibility.
- Remembers follower counts locally for seven days, across tabs and browser restarts.
- Adds zero network requests: it only observes data that X already loads.
- Provides English and Russian settings and explanations, with automatic language selection and a manual override.
This is a visual filter. It does not click Mute or Block, delete notifications, change your account, or hide posts entirely.
Use desktop Chrome 111+ or a compatible Chromium browser such as Edge. Firefox and Safari are not supported by this package.
- Download this repository using Code → Download ZIP and extract it, or clone it:
git clone git@github.com:xen/calmx.git
- Keep the extracted folder in a permanent location.
- Open
chrome://extensions(oredge://extensions) and enable Developer mode. - Click Load unpacked and select the folder containing
manifest.json. - Reload your X tabs. Open notifications or a post's conversation.
- Click the CalmX extension icon to configure it, or open Extension options for the full settings page.
The repository includes ready-to-use runtime files. Node.js, an API key, a paid API plan, and a server are not needed to use the extension.
Replace the files in the same installation folder, click Reload on the extension card, then reload your X tabs. Reloading only X does not update the extension's registered scripts. Keeping the same installation preserves its local settings and cache.
| Setting | Default | Behavior |
|---|---|---|
| Notifications threshold | 100 followers | Dim accounts strictly below the threshold |
| Replies threshold | 100 followers | Independent threshold for conversation replies |
| Visibility | 40% | Adjustable from 5% to 100%; lower means fainter |
| Grayscale | On | Desaturate follower-filtered entries |
| Reveal on hover/focus | On | Temporarily restore follower-filtered entries |
| Follower filtering | On | Global and per-context switches |
| Language | Automatic | Russian for a Russian browser locale; English otherwise; manual English/Russian override |
An account with exactly 100 followers is not below a threshold of 100. Set a threshold to zero to disable follower filtering for that context. Unknown counts are never treated as zero. Changes are saved explicitly and then apply to open X tabs. The preview lets you compare effects before saving.
Notifications: notification pages, including mentions. Reply cards use the reply author's count. For grouped notifications, individual names and avatars can be dimmed. The whole card is dimmed only when every actual actor is known to be below the threshold and none is Premium, including actors whose avatars are not displayed. Ambiguous groups remain undimmed as a whole.
Replies: descendants of the opened post, including nested replies when the loaded data establishes their relationship. Follower filtering does not dim the focal post, its ancestors, home timeline posts, search results, profile posts, sidebars, or direct messages.
Authors who blocked you: recognized tweet cards in the main column receive a light red tint and opacity: 0.4, including focal posts and home timeline posts. This rule takes priority over follower filtering, applies to Premium accounts too, and is independent of follower thresholds, visibility settings, and follower-filter switches. Hover does not restore these cards. It uses the blocked_by relationship reported by X; an account you blocked is a different relationship.
CalmX uses the explicit is_blue_verified field supplied by X. An ordinary verified flag alone is not proof of a paid subscription. If X does not expose the subscription signal, CalmX cannot independently determine whether an account pays.
Premium status can update immediately from an ordinary X response without changing the cached follower count or restarting its weekly lifetime. A Premium actor prevents a grouped notification from being dimmed as a whole; other individual actors can still be dimmed.
CalmX observes JSON responses from X's existing fetch/XHR traffic. It does not crawl profiles, poll an API, or refresh accounts on a timer.
Follower counts are stored by stable account ID in chrome.storage.local. Once recorded, the count is retained for at least 7 × 24 hours, even when X sends a newer count in the meantime. Renaming an account does not bypass that interval. After seven days, the next ordinary response containing the account can update its count. Until then, the previous count remains usable; its observation date appears in the explanation tooltip.
The cache holds up to 20,000 accounts. Only entries older than a week may be evicted. When all 6754 entries are fresh and the cache is full, new accounts are temporarily not cached. There is no forced-refresh button. Uninstalling the extension removes its stored data.
Viewer-specific blocking relationships stay in the current page's memory, rather than the shared follower cache. They reset on page reload or a detected active-account change, and an observed blocked_by: false removes the mark immediately.
The extension requests local storage and runs on https://x.com/* and https://www.x.com/*. It stores account IDs, handles, follower counts, observed Premium flags, timestamps, and your settings locally. It does not persist post text, notifications, direct messages, cookies, or authentication tokens, and sends no data to a CalmX server or third party.
Reply relationships, notification actors, and viewer-specific block flags are held temporarily in page memory. There is no analytics, remote executable code, or runtime dependency download. Development dependencies are only used to test the project.
- Nothing changes after installation/update: reload the extension itself, then reload X.
- An account remains unchanged: its count may be unknown, at or above the threshold, or exempt because X reports Premium. Some posts are outside the selected filtering context.
- A count seems outdated: the weekly cache intentionally keeps the old count; after expiry it waits for X to naturally send fresh data.
- A blocked author is unmarked: X must expose the blocking relationship in data already loaded by that page.
- X changed its interface: its internal response formats and DOM are not a stable public contract. Unrecognized authors or ambiguous data are left unchanged.
Automated checks cover the filtering and data flow, but do not guarantee compatibility with every future X rollout. See verification scope.
npm ci
npm run build
npm testbuild.js generates the locale catalog and two self-contained scripts for Chrome's separate execution worlds. Generated files are committed so installation requires no build. Rebuild them after changing sources.
| Files | Purpose |
|---|---|
shared.js |
Settings, normalization, and extraction of account data |
page-observer.js |
Passive observation of page fetch/XHR responses |
cache.js, background.js |
Persistent shared follower memory and tab messaging |
dom.js, content.js, content.css |
Card matching and visual effects |
options.html, options.css, options.js |
Settings, preview, and cache statistics |
locales-data.json, i18n.js, _locales/ |
English/Russian UI and Chrome manifest localization |
page-runtime.js, content-runtime.js, locales.js |
Generated distribution files |
tests/ |
Cache, DOM, integration, settings, localization, and packaging checks |
CalmX is an independent browser extension and is not affiliated with X.