Identify one publication
Name the topic, channel, date, or a post already cited in the conversation so retrieval can distinguish the intended message from similar publications.
Feature · Post reactions
Telegram post reaction analysis beyond one total
Inspect captured reaction totals and emoji-level breakdowns for a specific Telegram post, with observation timing, coverage, and a direct evidence link.
Direct answer. The Ocean can resolve a described post inside selected indexed sources and report its latest captured reaction total together with available standard emoji, custom emoji, and paid-reaction counts. The answer also shows when the snapshot was taken and links to the original post; a missing snapshot or reaction type remains missing rather than becoming zero.
Research fit
Who this workflow is for
Researchers who need to inspect how people reacted to one cited publication without turning an emoji count into an unsupported claim about agreement, emotion, authenticity, or influence.
Read the observation context
Treat the reported total as a captured snapshot. Record both time since publication and the wall-clock observation time before comparing it with another post.
Inspect reaction types
Review the available breakdown separately from the total. Standard emoji can be displayed directly; custom emoji may be identified only by Telegram's numeric identifier.
Open the evidence
Use the post permalink to confirm wording, media, publication time, and surrounding context before interpreting what any reaction pattern might mean.
State the boundary
Describe measured behavior only. Reactions do not establish who reacted, why they reacted, whether accounts were authentic, or whether the underlying claim is correct.
Practical module
Reaction snapshot review sheet
A defensible note separates the resolved post, captured values, timing, and interpretation so another reviewer can reproduce the observation.
Post identityChannel, message number, publication timestamp, short topic description, and original Telegram permalink.
Captured totalThe latest available reactions_total value, kept distinct from comments, forwards, views, or an estimated engagement score.
Type breakdownCounts for reported standard emoji, custom emoji identifiers, and paid reaction types without guessing unavailable glyphs.
Observation ageHow long after publication the snapshot was scheduled, which matters when comparing a new post with an older one.
Data timestampThe actual time of capture, retained separately from the post's publication time and from the current review time.
Interpretation noteA short human conclusion that labels alternative explanations and avoids equating a reaction with support or sentiment.
Analysis contract
What the calculation actually does
Chat resolves likely single-message candidates through content search, selects the intended post from its topic, channel, and date, and reads the latest captured reactions_total plus its stored reaction rows.
Scope
One identifiable Telegram post from the ready sources selected for the conversation. Similar candidates are alternatives to disambiguate, never a set to sum or average.
Measured fields
- Total captured reactions
- Standard emoji counts
- Custom emoji identifier counts
- Paid reaction counts
- Snapshot horizon and observed time
Coverage rules
- No captured snapshot is reported as unmeasured, not zero
- Unavailable reaction types are not inferred from the total
- Multiple candidate posts require explicit disambiguation
- Publication time and metric observation time remain separate
- Every reported post keeps its direct evidence link
Questions to ask
- How many reactions does the cited post have now, and what is the breakdown?
- For the post about the launch in Channel A, show reactions, views, forwards, and snapshot time.
- Which reaction types were captured for this specific message?
Single-post reaction analysis recipe
A copy-ready specification for resolving one post and recording reaction evidence without converting missing data or ambiguous emoji into invented facts.
Find the one post in [selected sources] about [topic], preferably from [channel/date]. Report its latest captured reactions, views, and forwards; list the available reaction-type breakdown, snapshot horizon, observation time, and permalink. If several posts match, explain the ambiguity and do not combine them.
post engagement
Latest captured reactions_total for the resolved item, accompanied by stored reaction-type rows; no aggregation across candidate posts.
Inputs to set
- Source scope
- The smallest selected channel set that can contain the target post.
- Post description
- Topic, distinctive phrase, date, channel, or a reference to a previously cited result.
- Observation choice
- Use the latest captured snapshot and preserve its age after publication.
- Interpretation question
- The narrow decision the reaction evidence will inform after source review.
Expected output
- Resolved post identity and citation
- Reactions, views, and forwards from one snapshot
- Reaction-type counts that Telegram supplied
- Snapshot age and wall-clock observation time
- Ambiguity or missing-data statement
Coverage rules
- Do not merge metrics from alternative matching posts
- Do not turn a missing snapshot into a zero value
- Do not guess the glyph behind a custom emoji identifier
- Do not infer user identity, motive, or authenticity
- Open the original post before publishing an interpretation
Read the complete resource
# Single-post reaction analysis recipe A copy-ready specification for resolving one post and recording reaction evidence without converting missing data or ambiguous emoji into invented facts. ## Calculation - Mode: post_engagement - Formula: Latest captured reactions_total for the resolved item, accompanied by stored reaction-type rows; no aggregation across candidate posts. ## Query Find the one post in [selected sources] about [topic], preferably from [channel/date]. Report its latest captured reactions, views, and forwards; list the available reaction-type breakdown, snapshot horizon, observation time, and permalink. If several posts match, explain the ambiguity and do not combine them. ## Inputs - **Source scope:** The smallest selected channel set that can contain the target post. - **Post description:** Topic, distinctive phrase, date, channel, or a reference to a previously cited result. - **Observation choice:** Use the latest captured snapshot and preserve its age after publication. - **Interpretation question:** The narrow decision the reaction evidence will inform after source review. ## Expected output - Resolved post identity and citation - Reactions, views, and forwards from one snapshot - Reaction-type counts that Telegram supplied - Snapshot age and wall-clock observation time - Ambiguity or missing-data statement ## Coverage checks - [ ] Do not merge metrics from alternative matching posts - [ ] Do not turn a missing snapshot into a zero value - [ ] Do not guess the glyph behind a custom emoji identifier - [ ] Do not infer user identity, motive, or authenticity - [ ] Open the original post before publishing an interpretation
Boundaries
What this does not establish
- Only posts inside the selected indexed corpus can be resolved
- Reaction availability depends on captured Telegram metric snapshots
- Custom emoji identifiers do not reveal an unavailable visual glyph
- Counts do not identify individual users or coordinated behavior
- A reaction pattern is not a validated sentiment or truth score
Founding research pilot
Apply with a post-reaction research question
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-chat-current-post-metrics · product-chat-reaction-breakdown · product-citations · product-limitations