Channel
@gramiojs
On this record: Growth · Engagement · Posts · Citations · Cite this entry
9subscribers
+0 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002133155824 |
|---|---|
| Type | Channel |
| Username | @gramiojs |
| Created | Between 1 November 2023 and 31 May 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 12 August 2026 |
| Last confirmed live | 16 September 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 2 times, most recently 16 September 2026 |
| On Telegram | t.me/gramiojs |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 9 Sept 2026, 00:56 | 9 | -1 |
| 16 Aug 2026, 16:24 | 10 | +1 |
| 12 Aug 2026, 13:01 | 9 | no change |
| 7 Aug 2026, 19:06 | 9 | first reading |
20 posts held, back to 3 June 2026 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 page of Telegram’s post history, 20 posts per page.
Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 20 posts for this entry, the most recent from 10 August 2026. An engagement rate over an empty window would be a number about nothing.
🎉 gramiojs/[email protected] - CLAUDE.md: document guards and hash.txt behavior - Mojibake guard (UTF-8 → CP1251 detection) feat: add schema guards and bump parser dep to 1.2.0- Formattable/parse_mode invariant guard (must be 1:1 paired) release v10.2.2 Compare release changes
🎉 gramiojs/[email protected] - 4 new tests covering the edge cases (SuggestedPostRefunded.reason: "24" no longer leaks) - enum extraction ignores prose numbers when quoted values exist - fixes regression where editMessageText.text lost FormattableString - description "after entit(y|ies) parsing" is redundant but still matches (bare parse_mode claims the field it is documented under) feat: structural form…
🎉 gramiojs/[email protected] Closes #32 comparison) instead of assigning the status. Also fixes koa's `unauthorized()` writing `ctx.status === 401` (a no-op web-standard `Headers#get`) keep using the canonical casing. Adapters with a case-insensitive lookup (express/koa/hono helpers, `undefined` and every update was rejected with 401 once `secretToken` was set. lowercased keys, so `headers["X-Telegram-Bot-Ap…
🎉 gramiojs/[email protected] Pin @gramio/types ^10.2.1. - Wired into ContextsMapping / EVENTS / service-message list / exports. - Message getters: receiverUser, ephemeralMessageId, communityChatAdded/Removed. - Community structure; ChatFullInfo.community getter. isCanceled/isActive/isFailed), CommunityChatAdded/RemovedContext. feat: Bot API 10.2 — Communities, subscription update, ephemeral getters (0.10.0)- Su…
🎉 gramiojs/[email protected] ^10.2.1 / schema-parser ^1.1.1. the recursive InputRichBlock graph (provably output-preserving). Pin types scripts/generate.ts: barren-subtree pruning to stop combinatorial explosion on Text/Caption, sendRichMessage/Draft, InputMediaVoiceNote caption branches. feat: Bot API 10.2 mutator regen + generator explosion fix (0.10.0)Regenerated FormattableMap for Bot API 10.2 (39 methods): edit…
🎉 gramiojs/[email protected] thumbnail/photo/cover blob detection). Pin @gramio/types ^10.2.1. feat: Bot API 10.2 — editEphemeralMessageMedia upload support (0.7.0)Regenerated MEDIA_METHODS to include editEphemeralMessageMedia (media/ Compare release changes
🎉 gramiojs/[email protected] release v10.2.1 Compare release changes
🎉 gramiojs/[email protected] docs: document gh-based publish workflow and status monitoring in CLAUDE.md formattable (FormattableString) typing. Match either wording + regression tests. matched the plural "after entities parsing", so those methods silently lost parsing" (singular) when rich_message landed in Bot API 10.1. The detector only fix: match singular "after entity parsing" so edit-text methods keep …
🎉 gramiojs/[email protected] collision instead of silently desyncing. as-is — the gated middleware captured the id by value — and throws on so their runtime semantics are unchanged. `extend()` keeps legacy ids `dispatchActive` checks the flag and routes them down the legacy path, Legacy steps push a placeholder entry (`legacy: true`, no composer); `~scene.steps` is now the complete ordered registry of every step. …
🎉 gramiojs/[email protected] Closes #3 Closes #4 without a default — it is simply absent from the result. - deserialize() no longer console.error()s for an omitted optional field cryptic TypeError (or silently packing false for booleans). "Missing value for required field '<key>'" at pack() instead of a - undefined for a required field throws `{id}`; schemas with required fields always reach the s…
🎉 gramiojs/[email protected] release v9.4.0 release v10.1.0 release v10.2.0 Compare release changes
🎉 gramiojs/[email protected] Co-Authored-By: Claude Opus 4.8 (1M context) <[email protected]> - D2-1: createDialogs().background edits the last message with no update - D2-5: over-long callback_data throws a named error into onError - D2-2: concurrent taps on one stack don't lost-update (withLock + reload) three fixes that previously had no e2e coverage: test: cover D2-1/D2-2/D2-5 end-to-end via @gramio/testA…
Showing the 12 most recent of 20 posts we hold for @gramiojs. View and reaction counts are the latest single reading for each post, not a live figure, and a recent post is still accumulating both. A view count marked ≈ was rounded by Telegram before we ever saw it — t.me prints views in full below 1,000 and to three significant figures above, so ≈1,200,000 means somewhere between 1,150,000 and 1,249,999. Unmarked counts are exact. Text is reproduced from the public post preview and truncated for length.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.
A live page changes as we take new readings, so a citation should name the measurement it is based on, not just the URL. The line below cites the subscriber count as measured 9 September 2026 — this entry's latest reading, not the date you are reading this.
“gramio” (@gramiojs), 9 subscribers as measured 9 September 2026. Telegram Register, tgregister.com/channel/gramiojs.
Full measurement history, CC BY 4.0. Every reading this register holds for this entry, not just the latest one, as a dated, downloadable record: CSV · JSON. Free to use with attribution to tgregister.com. Each file carries its own generation timestamp, which is the figure to cite for exactly when the data was retrieved.