Channel
@GoTGProto
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
105subscribers
+0 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001604806503 |
|---|---|
| Type | Channel |
| Username | @GoTGProto |
| Description | GoTGProto is a wrapper for github.com/gotd/td. It aims to make td's raw functions easy to user with the help of its helpers packages. Repository: github.com/anonyindian/gotgproto |
| Created | Between 1 December 2021 and 27 April 2022— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 9 August 2026 |
| Last confirmed live | 9 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/GoTGProto |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 9 Aug 2026, 08:47 | 105 | no change |
| 7 Aug 2026, 04:48 | 105 | first reading |
20 posts held, back to 27 April 2022 — 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 pageof 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 28 October 2025. An engagement rate over an empty window would be a number about nothing.
Lifetime counters from Telegram’s own channel header, read 9 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.
47 reactions across 12 posts, in 10 distinct kinds. The most used accounts for 34.0% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 🔥 | 16 | 34.0% | |
| ❤ | 15 | 31.9% | |
| 👎 | 3 | 6.38% | |
| 🤔 | 3 | 6.38% | |
| 🎉 | 2 | 4.26% | |
| 👀 | 2 | 4.26% | |
| 👍 | 2 | 4.26% | |
| 💩 | 2 | 4.26% | |
| 🤣 | 1 | 2.13% | |
| 🥰 | 1 | 2.13% |
No sentiment is inferred, and none should be read in. This table is ordered by count and by nothing else. Emoji do not carry stable meaning across languages or communities — 🙏 is thanks in one channel and mourning in another — so we publish which ones were pressed and how often, and pass no judgement on what an audience meant by them.
Precision. Telegram publishes reaction counts per emoji and short-forms each one — 4.34K, 1.2M — so any single kind at or above 1,000 reaches us at three significant figures, and only counts below 1,000 are exact. The shares above are ratios of those figures and carry the same error. This is also why the total here can differ slightly from a reaction total printed elsewhere on the page: both are sums of the same rounded parts, taken over samples with different edges.
Coverage. Reactions were read on 13 of the 20 sampled posts in this sample. Summed by Telegram’s own count on each post — not by adding up the per-emoji breakdown above — those same posts carry 47reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 20 most recent posts we hold, published 27 April 2022 to 28 October 2025, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
🎉 GoTGProto New Update We have just released v1.0.0-beta22 of the library. As usual, upgrade using: go get github.com/celestix/gotgproto@v1.0.0-beta22 Changelog: Click here Repository: https://github.com/celestix/gotgproto Examples: click here for the examples Documentations: click here for the docs Support Group: @GoTGProtoChat
🔥3
🎉 GoTGProto New Update We have just released v1.0.0-beta21 of the library. As usual, upgrade using: go get github.com/celestix/gotgproto@v1.0.0-beta21 Changelog: • Updated to GoTD to v0.122.0 • Added ctx.TransferStarGift, ctx.ExportInvoice, ctx.SetPreCheckoutResults • Improved peer storage to account full access hash • Fixed inaccurate ctx.EffectiveUser • Added NoUpdates client opt to disable receiving update…
❤3👍1
🎉 GoTGProto New Update We have just released v1.0.0-beta20 of the library. As usual, upgrade using: go get github.com/celestix/gotgproto@v1.0.0-beta20 Changelog: Click here Note: Session login issues that arose in beta19 have been fixed with beta20, you can continue using your beta18 sqlite session files in this new update. Repository: https://github.com/celestix/gotgproto Examples: click here for the examples D…
🎉 GoTGProto New Update We have just released v1.0.0-beta19 of the library. As usual, upgrade using: go get github.com/celestix/gotgproto@v1.0.0-beta19 Changelog: • Updated GoTD to v0.116.0 • Fixed auth-using-api-base example doesn't work by @dev-freelance-ru in #80 • Added add arguments in SendMedia example by @AshokShau in #88 • Fixed 2fa auth flow hooks by @HoracePeng in #91 • Fixed ForwardMessages by @gaut…
🔥3👍1
🎉 GoTGProto New Update We have just released v1.0.0-beta18 of the library. As usual, upgrade using: go get github.com/celestix/gotgproto@v1.0.0-beta18 Changelog: • Updated to GoTD to v0.102.2 • Fixed nil value of ctx.EffectiveUser in private chats • Fixed instable peer caching and handling • Fixed invalid implementation of RetryPassword hook • Added auth status events and retry mechanism for phone and otp upd…
❤4
🎉 GoTGProto New Update We have just released v1.0.0-beta17 of the library. As usual, upgrade using: go get github.com/celestix/gotgproto@v1.0.0-beta17 Changelog: • Updated to GoTD to v0.99.2 • Added web auth example by @Emanxu in #49 • Fixed ctx random seed to nanosecond to prevent the randomID generated… by @DukeAnn in #50 • Added floodwaiter example by @TeaDove in #51 • Added support for single styling.Styl…
🔥5
🎉 GoTGProto New Update We have just released v1.0.0-beta15 of the library. As usual, upgrade using: go get github.com/celestix/gotgproto@v1.0.0-beta15 Changelog: • Updated to GoTD to v0.93.0 (Layer 170) • Fixed client.ExportStringSession() and add RunMiddleware field to client. #41 • Added an optional field to specify custom Context #44 • Added all fields to gotgproto.Client from telegram.Client for flexible u…
❤2🔥2
🎉 GoTGProto New Update We have just released v1.0.0-beta14 of the library. As usual, upgrade using: go get github.com/celestix/gotgproto@v1.0.0-beta14 Changelog: • Updated to GoTD to v0.91.0 (Layer 167) • Adapted pure Go SQLite driver (This means you will no longer need CGO!) #40 • Redesigned peers storage mechanism and made it compatible for multiple clients • Redesigned session initialization system to make …
❤3
GoTGProto is now a part of hacktoberfest 2023 🎉, contributions in order to achieve the its PR goals are welcome now :) -> https://github.com/celestix/gotgproto Repository: https://github.com/celestix/gotgproto Examples: click here for the examples Documentations: click here for the docs Support Group: @GoTGProtoChat
🎉 GoTGProto New Update We have just released v1.0.0-beta13 of the library. As usual, upgrade using: go get github.com/celestix/gotgproto@v1.0.0-beta13 Changelog: • Updated to GoTD to v0.88.0 (Layer 164) • Redesigned session initialization (Now supports logging in with just string session in memory as well as session file) • Added Middlewares and Device fields to ClientOpts • ctx.ForwardMediaGroup won't omit er…
👀2💩2🎉1
🎉 GoTGProto New Update We have just released v1.0.0-beta10 of the library that brings a lot of optimizations along with some breaking changes. This update also fixes a very old issue of the library which used to cause high memory usage. As usual, upgrade using: go get github.com/anonyindian/gotgproto@v1.0.0-beta10 Changelog: • Updated GoTD to v0.82.0 • Deprecated ctx.ForwardMessage (Use ctx.ForwardMessages now) …
🔥3❤1🎉1🥰1
Hello 👋, here we resume the development of library further followed by many new updates and breaking changes. Suggestions and bug reports are welcome anytime :) Repository: https://github.com/anonyindian/gotgproto Examples: click here for the examples Documentations: click here for the docs Support Group: @GoTGProtoChat
Showing the 12 most recent of 20 posts we hold for @GoTGProto. 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.
Citation-graph rank — 618,480 of 1,151,006entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.
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.
Names
Channels on the register whose handles appear in this channel's posts.
A mention is a weaker signal than a forward and is counted separately for that reason — naming a channel is not republishing it, and a handle in a post body is easy to place deliberately. The post counts beside each row below are distinct posts in which the handle appeared, from posts we have read on both sides — the “Named by N registered channels” figure above is a different count, of distinct NAMING CHANNELS rather than posts, and is not the sum of the rows under it.
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 August 2026 — this entry's latest reading, not the date you are reading this.
“GoTGProto” (@GoTGProto), 105 subscribers as measured 9 August 2026. Telegram Register, tgregister.com/channel/GoTGProto.
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.