Feature

Relevant-only feed filtering helps the operator remove weak-fit threads before they become decisions.

ReplyRadar can hide lower-fit supported X posts, Facebook threads, and Reddit posts or comments using the active project and the current minimum score threshold.

Less feed clutter

The extension can leave lower-fit supported items out of view instead of asking the operator to ignore them manually.

Project-aware filtering

The same post can behave differently when the active project changes, which helps multi-product teams stay precise.

Threshold-aware behavior

Relevant-only mode works with the current minimum score, so teams can decide how strict the visible feed should feel.

Better restraint

The biggest win is not more replies. It is fewer low-value moments where the operator considers replying at all.

Why this matters

Scoring becomes more practical when it can actively shape what the operator sees.

A score preview is useful. A relevant-only filter goes further by turning scoring into a real browsing rule. That is often what makes a fit model feel operational instead of cosmetic.

Weak-fit supported items can disappear before they consume attention.

The feed can feel calmer without abandoning the original browsing environment.

Teams can tune strictness without rewriting the project profile itself.

The operator still keeps full control over drafting and posting on the threads that remain.

What changes downstream

The filter improves the quality of decisions before drafting starts.

The main benefit is fewer false starts. The operator spends more time reviewing stronger opportunities and less time second-guessing marginal ones.

Less scanning fatigue in crowded X and Reddit environments.

Cleaner public-thread review on Facebook when recommendation requests are mixed with weaker posts.

A tighter connection between score thresholds and what actually stays visible.

A more repeatable workflow for small teams that cannot afford wide, noisy queues.