Topic Packs

Topic packs are weighted bundles of terms, handles, domains, cashtags, and emoji signals that help the engine remove whole categories of posts without writing individual rules.

Each pack has a polarity:

• Noise packs push matching posts toward hidden.
• Signal packs protect matching posts and push them toward boosted.

The engine sums evidence from every active pack. A single high-confidence term (weight near 1.0) can hide a post on its own. Several low-confidence terms must accumulate before they can hide. This prevents short or ambiguous tokens such as ai or eth from hiding posts by themselves.

The built-in library includes packs such as Crypto & Airdrops, Politics, AI Slop, Engagement Bait, Rage Bait, Memes & Brainrot, Sports, Adult & NSFW, Promo, and others. Short or ambiguous tokens use word mode with Unicode-aware boundaries.

• All 17 built-in packs are free and unlimited — activate as many as you like. Imported/shared packs are also free to import and activate.
• Pro adds authoring: creating, editing, and deleting custom packs in Pack Studio, plus pack export/sharing.
• Each pack has a weight slider (0 to 1) that scales its contribution.

#

Managing Packs

Pack Studio lists every built-in kit alongside your own packs

On Options → Filters, the Topic kits card stays simple: name, polarity, on/off, strength for the active feed mode. Switching modes (Options → Modes) can change which kits are active.

Fresh installs may already have kits on: the welcome setup switches on kits that match the phrases you typed.

Click Manage packs / Pack Studio for create, edit, Live Test, import (free), and export (Pro). See Pack Studio, Sharing Packs, and Feed Modes.

When a pack contributes to a decision, the receipt strip shows the pack name and the strongest matching terms, and Recently removed (Options → Activity) records the reason. Pack-driven hides also store pack attribution so Wrong call / Not <topic> can improve pack health locally.

Topic pack selections, custom pack bodies, pack weights, corrections, and revisions stay local. They are not sent to the XpressPurge backend unless you explicitly use optional AI Coach on a single pack or description.