Radar · Return signal

Detect when a Telegram channel returns after silence

Detect when a selected Telegram channel publishes after an unusually long source-specific gap, with historical context, evidence, and coverage notes.

Direct answer. The Ocean Radar can surface a selected channel's new post when the preceding publication gap is unusually long relative to that channel's history. The signal records both posts, gap duration, historical baseline, window, confidence, and coverage. It identifies a return inside indexed history; it does not prove the organization was inactive elsewhere, explain why it returned, or make the post important.

Research fit

Who this workflow is for

Analysts tracking intermittent public Telegram sources who need a source-specific return alert and cited before-and-after evidence instead of a universal silence threshold.

01

Choose intermittent sources

Select the channels whose publication gaps matter to the research question and verify that their indexed histories are sufficiently complete.

02

Set the Radar window

Use a 24-hour, 3-day, or 7-day evaluation window for recent posts while retaining older history for the source-specific gap baseline.

03

Measure the current gap

Calculate elapsed time between the new logical post and the immediately preceding indexed post from the same source.

04

Compare with source history

Judge the gap against that channel's historical publishing intervals rather than imposing one threshold across daily and monthly publishers.

05

Review both messages

Open the new post and preceding post, check coverage, and describe the signal without inferring motive or off-platform inactivity.

Practical module

Return-after-silence evidence card

The card preserves the timing calculation and the two publications needed to verify what the alert actually means.

Returning sourceThe selected Telegram channel whose newest eligible post ended the measured gap.
Gap durationElapsed time between the stored publication timestamps of the current and prior logical posts.
Historical normThe source's prior interval distribution, sample size, and the rule that made this gap unusual.
Current evidenceNew post excerpt, publication time, message identifier, and direct permalink.
Previous evidenceThe immediately preceding indexed post and timestamp used to start the gap.
Coverage noteKnown history boundary, ingestion gaps, deleted or private content limits, and confidence.

Analysis contract

What the calculation actually does

For a newly published logical post, Radar calculates the interval since the immediately previous indexed post from the same source and compares that interval with eligible historical source gaps.

Scope

Selected indexed Telegram sources with a recent post inside the configured Radar window and enough usable source history to estimate normal publication intervals.

Measured fields

  • Current publication gap
  • Historical gap baseline
  • Previous-post timestamp
  • Returning-post timestamp
  • Historical sample size
  • Signal confidence

Coverage rules

  • The calculation is bounded to indexed source history
  • The immediate previous indexed logical post anchors the gap
  • Known ingestion gaps lower confidence
  • Different sources retain different baselines
  • Both boundary posts remain cited

Questions to ask

  • Which monitored channels posted after an unusually long silence this week?
  • How long was this source inactive relative to its own normal posting gaps?
  • Show the post before the gap and the returning post.

Return-after-silence detection recipe

A source-specific timing method for flagging an unusual publication gap and preserving both boundary posts.

Copy-ready query

In [selected sources] during the [Radar window], identify returns after unusually long publication gaps. Show current gap, source-specific historical baseline, sample size, confidence, the prior post, the returning post, timestamps, permalinks, and known history gaps. Do not infer motive or activity outside indexed Telegram history.

Deterministic calculation

radar return after silence

current_gap = returning_post_time - previous_indexed_post_time; compare current_gap with eligible historical gaps for the same source.

Inputs to set

Selected sources
Channels for which inactivity and return are meaningful.
Recent window
The 24-hour, 3-day, or 7-day period searched for returning posts.
Historical intervals
Eligible same-source publication gaps used as the baseline.
Coverage status
Known history start, missed ingestion, and availability limitations.

Expected output

  • Source and measured gap
  • Historical interval baseline
  • Previous and returning timestamps
  • Two direct evidence links
  • Confidence and coverage caveat

Coverage rules

  • Never use one silence threshold for every source
  • Treat missed history as a confidence limit
  • Do not infer off-platform inactivity
  • Cite both posts that define the gap
  • Describe the signal as source-specific
Download Markdown resource
Read the complete resource
# Return-after-silence detection recipe

A source-specific timing method for flagging an unusual publication gap and preserving both boundary posts.

## Calculation

- Mode: radar_return_after_silence
- Formula: current_gap = returning_post_time - previous_indexed_post_time; compare current_gap with eligible historical gaps for the same source.

## Query

In [selected sources] during the [Radar window], identify returns after unusually long publication gaps. Show current gap, source-specific historical baseline, sample size, confidence, the prior post, the returning post, timestamps, permalinks, and known history gaps. Do not infer motive or activity outside indexed Telegram history.

## Inputs

- **Selected sources:** Channels for which inactivity and return are meaningful.
- **Recent window:** The 24-hour, 3-day, or 7-day period searched for returning posts.
- **Historical intervals:** Eligible same-source publication gaps used as the baseline.
- **Coverage status:** Known history start, missed ingestion, and availability limitations.

## Expected output

- Source and measured gap
- Historical interval baseline
- Previous and returning timestamps
- Two direct evidence links
- Confidence and coverage caveat

## Coverage checks

- [ ] Never use one silence threshold for every source
- [ ] Treat missed history as a confidence limit
- [ ] Do not infer off-platform inactivity
- [ ] Cite both posts that define the gap
- [ ] Describe the signal as source-specific

Boundaries

What this does not establish

  • The measured gap depends on indexed source history
  • Deleted or missed posts can make a gap appear longer
  • A channel may have remained active on other platforms
  • The signal cannot explain the reason for returning
  • A return alert does not make the new post important or credible

Founding research pilot

Apply with a return-after-silence monitoring task

Bring one recurring research job and a small set of public sources. We will assess fit personally before offering a pilot.

Apply for a 14-day research pilot

30 founding researcher places · rolling admission · personal reply within 2 business days

Analytics cluster

More ways to investigate this result

Continue researching

Related guides

Publication notes. This page was reviewed before publication and is scheduled for review by 2026-12-19. Facts used: product-radar-signals · product-radar-windows · product-citations · product-limitations