Tweet Capture & Relevance

The extension scores tweets and grounds your replies against your own writing. For each tweet it sees, it finds the closest matches in what you have actually published: your recent tweets, your blog posts, and your past replies. That match is what powers the relevance badge (the "✨ 7/10" on a tweet), the reply angles for tweets no Hunt covers, and the context behind a fact-anchored reply draft.

This means the feature is only as strong as what you have captured. A brand-new account with no captured tweets has nothing to match against, so the relevance badges stay quiet and reply drafts have thin grounding. That is expected, not a bug. The fix is to capture your tweets.

How relevance is scored

For each tweet, BlackOps compares it by embedding similarity against three sources of your own content, scoped to your site:

• Your tweets from the last 60 days. Weighted highest, and newer tweets count more.
• Your published blog posts.
• Your past replies.

The strongest match sets the score and tells you what the tweet relates to. A score of 6 or higher flags the tweet as relevant. If those sources are empty, there is nothing to score against, and nothing surfaces.

Relevance and Hunts

Relevance is one of two ways a tweet can come up. The other is a Hunt. The extension never shows two rankings on one tweet. Each tweet gets a single badge from a single source:

• A Hunt matches. The Hunt's badge and score replace the relevance score, and the angles follow the Hunt.
• No Hunt fits, but the tweet is relevant. You see the relevance score, and the angles build on the tweets, posts, or replies it matched. The panel's "Related to" and "Why you might reply" cards show those matches.
• Neither. The tweet shows a skip with the reason, and no score.

Some posts are skipped however relevant they are: a bad place to show up, promotion or engagement bait, or a thread you already replied to.

On your home timeline, relevance scores appear as you scroll. Hunts are checked when you open the reply panel, so opening a tweet can swap its relevance badge for a Hunt badge, or for a skip.

Capture your tweets by scrolling your profile

This is the simplest path and the one we recommend first. With the extension installed and connected:

1. Open your own X profile.
2. Scroll. The extension quietly captures the tweets it sees and embeds them in the background.
3. Keep scrolling to reach further back. The more of your history you load, the more the relevance and reply features have to work with.

It runs silently, skips tweets it has already captured, and embeds new ones automatically. Do it any time to top up, and revisit your profile after posting so new tweets get picked up.

Import your X archive for a bulk backfill

To seed years of history at once instead of scrolling:

1. In X, go to Settings, then "Your account," then "Download an archive of your data." X emails you a link when it is ready.
2. From the downloaded archive, find the tweets.js file.
3. Import it into BlackOps.

Imported tweets land in your library and are embedded by a background pass rather than instantly, so give it time before the matches show up. Scrolling your profile is the faster way to get a useful signal going immediately.

Why it is worth doing

Both anti-slop features lean on this. Relevance badges only flag tweets that sit in the lane of what you write about, and fact-anchored replies only draft when they can stand on something concrete you actually know. Captured tweets and published posts are that something. Capture once, and every reply you draft afterward gets sharper.

Related

• Reply Angles
• Fact-Anchored Replies
• Ranked Reply Targeting
• Voice Calibration