51 lines
1.7 KiB
Markdown
51 lines
1.7 KiB
Markdown
# TechMesto — Telegram checkmarks explainer
|
|
|
|
## Metadata
|
|
|
|
| Field | Value |
|
|
|---|---|
|
|
| Institute | Molodetz Institute — Research & Retrieval Division |
|
|
| Subject | tui-framework-design |
|
|
| Document type | Source Dossier |
|
|
| Tier | 1 |
|
|
| Source title | Telegram checkmarks explainer (TechMesto) |
|
|
| Source URL | https://www.techmesto.com/telegram-checkmarks/ |
|
|
| Source publisher / author | TechMesto (third party) |
|
|
| Source type | blog post |
|
|
| Source date (published) | Unknown — not stated |
|
|
| Date researched | 2026-10-11 |
|
|
| Researched by | tai (agent), model: Muse Spark, on behalf of retoor |
|
|
| Research method | direct page fetch |
|
|
| Confidence | Medium |
|
|
| Status | Active |
|
|
|
|
## Summary
|
|
|
|
A third-party explainer of Telegram's message-state glyphs, consistent with the official FAQ: clock while sending, checks that turn blue on read, and the eye-plus-view-count treatment used by channels instead of checks.
|
|
|
|
## Key findings
|
|
|
|
- A clock icon marks a message still sending.
|
|
- Check marks turn blue once the message is read.
|
|
- Channels use an eye icon plus a view count rather than per-recipient checks.
|
|
|
|
## Pros / strengths
|
|
|
|
- Corroborates the official check semantics from an independent angle.
|
|
- The channel eye-plus-views detail fills a gap the FAQ subset did not cover.
|
|
|
|
## Cons / limitations / caveats
|
|
|
|
- Third-party explainer, not authoritative: useful as corroboration, not as the primary basis for any claim.
|
|
- Thin page with no client-version pinning; wording may drift from current clients.
|
|
|
|
## Relevance to tai
|
|
|
|
Confirms the glyph set tai's transcript rows need (clock, checks with a read color, eye+count for broadcast-style views) without inventing any new states.
|
|
|
|
## Changelog
|
|
|
|
| Date | Change |
|
|
|---|---|
|
|
| 2026-10-11 | Initial dossier created. |
|