Feature

Fresh-post filters help the operator keep the extension biased toward newer conversations.

ReplyRadar lets the operator define an hours-or-days window so supported X, Facebook, and Reddit items that appear older than that limit can stay out of the visible workflow.

Hours or days

The extension can use a short or longer freshness window depending on how quickly the team wants to act.

Better timing

Newer conversations often create more natural openings for public replies, especially on faster-moving platforms.

Works with relevance

Freshness filtering can work alongside score thresholds and relevant-only mode so the queue is both newer and better-fit.

Conservative fallback

When visible timestamps are not available, the extension can avoid over-hiding by leaving undated items visible.

Why this matters

A useful reply workflow gets stronger when it reflects the half-life of public conversations.

Some threads are still worth answering days later. Many are not. Fresh-post filters help the operator preserve timeliness without manually checking age on every supported item.

X often rewards faster reactions to active intent and recommendation requests.

Reddit can still support slower replies, but freshness helps reduce time spent on stale threads.

Facebook conversations often benefit from staying current when the social context is still live.

The operator can tune the time window to match the team’s browsing rhythm.

What changes downstream

Freshness controls help the extension behave more like a live workflow and less like an archive.

The operator can reserve energy for conversations where timing still matters, which often improves both response quality and response rate.

More of the visible feed reflects current opportunities instead of old leftovers.

Fewer drafting cycles are spent on conversations that have already cooled off.

Teams can experiment with tighter windows during focused outreach sessions.

Freshness becomes one more control layer instead of another manual sorting task.