Channel
@golanglibrary
On this record: Growth · Engagement · Advertising · Posts · Citations · Cite this entry
4,381subscribers
-5 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
| Telegram ID | -1001228132127 |
|---|---|
| Type | Channel |
| Username | @golanglibrary |
| Created | 21 April 2018 — measured — cross-checked against a third-party dataset (TGDataset) |
| First recorded | 6 August 2026 |
| Last confirmed live | 12 August 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 2 times, most recently 12 August 2026 |
| On Telegram | t.me/golanglibrary |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 9 Aug 2026, 15:18 | 4,381 | -4 |
| 6 Aug 2026, 10:50 | 4,385 | -1 |
| 6 Aug 2026, 04:04 | 4,386 | no change |
| 6 Aug 2026, 03:53 | 4,386 | first reading |
23 posts held, back to 18 July 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 6 pagesof Telegram’s post history, 20 posts per page.
ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.
ER is defined industry-wide as (forwards + reactions + comments) ÷ views— note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate.
| Window | Rolling 30 days · latest post in window 8 August 2026 |
|---|---|
| Posts held | 23 (18 July 2026 – 8 August 2026) |
| Views total | 22,892 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 8 Aug 2026, 18:17 UTC |
Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.
Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.
Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.
An ad marker, not a judgement about a post. A post is counted here because it carries one of two explicit markings: an erid token, which Russian law has required on paid placements since 2022 and which is issued against a specific advertising contract, or a #реклама / #ad hashtag in the body, which is the channel declaring it itself. The first is documentary; the second is a self-declaration and is weaker. No classifier reads the text and decides — nothing on this site guesses that a post is an advertisement.
This is a floor, and it can only ever be a floor.A channel that runs paid placements without marking them produces no marker for us to count, and an unmarked ad is indistinguishable from an ordinary post on the public surface. The ad load above therefore means “the share of posts that declared themselves”, never “the share of posts that were paid for”. A low figure is not evidence of a channel that runs few ads.
Both figures are medians, and no ratio between them is published. Each is a view reading that actually occurred on a post, picked by percentile_disc rather than averaged, so one viral post cannot move it and no interpolated value is invented between two readings. The sample on one side is under five posts, which is too thin to compare. The two figures are shown side by side with the count behind each, and deliberately not divided into a headline like “ads get x% fewer views” — an arithmetic that is easy to print and, at this sample size, means nothing.
| erid | Posts | First seen | Last seen |
|---|---|---|---|
| 2Vtzquch2ft | 1 | 4 August 2026 | 4 August 2026 |
A token repeated across several posts is one advertising contract placed more than once, which is what the identifier is for. The strings are reproduced exactly as they appeared in the post or in its click-through URL and are not validated against any registry — we record the marker a channel published, and whether it resolves to a real contract is a question for the register that issued it.
Measured over the 23 most recent posts we hold, published 18 July 2026 to 8 August 2026. Views are the latest single reading held for each post, and any reading at or above 1,000 is rounded by Telegram to three significant figures.
httpsms httpSMS is a service that lets you use your Android phone as an SMS Gateway to send and receive SMS messages. You make a request to a simple HTTP API and it triggers your Android phone to send an SMS. https://github.com/NdoleStudio/httpsms
Benchmarking Go 1.27's encoding/json: The any Trap encoding/json/v2 has been experimental in Go for almost a year. In Go 1.27 (coming this August), v2 becomes the default backend for encoding/json. Is v2 faster? Considering the breaking changes in v2 and Go's compatibility promise, will compatibility affect performance? https://reqfleet.com/blog/benchmarking-go-1-27-encoding-json-the-any-trap
Request coalescing with Go singleflight A hot key expires, the next request misses the cache, so it queries Postgres to refill the key — the key is popular, so while that first query runs, a hundred more pile in. Postgres ends up running a hundred identical queries at once, all for the same value. That's known as a thundering herd or cache stampede. https://rednafi.com/go/request-coalescing
Fixing a kubelet Memory Leak in Kubernetes 1.36 How I tracked down a tiny Go lifecycle bug in Kubernetes kubelet which leaked a context on every startPodSync. My frugality paid unexpected dividends: this tiny 2 GiB RAM node had so much memory pressure that it quickly revealed a deeper issue in Kubernetes 1.36. https://heyoncall.com/blog/fixing-kubernetes-kubelet-memory-leak
🔴 Тестовое собеседование с Go Senior с опытом работы в Яндексе, EPAM и Uzum в этот четверг 6 августа(в четверг!) в 19:00 по мск приходи онлайн на открытое собеседование, чтобы посмотреть на настоящее интервью на Middle Go-разработчика. Как это будет: 📂 Маруф Караев, Senior в европйской компании, ex-Uzum, ex-Яндекс, ex-EPAM будет задавать реальные вопросы и задачи разработчику-добровольцу 📂 Маруф будет комментироват…
Line-rate packet processing in Go with AF_XDP Every few years I circle back to the same question: how fast can we send and receive packets on a plain Linux box? Today we're going a level deeper into my favorite of the bunch: AF_XDP, using a Go library I wrote to make it easy: go-afxdp. https://toonk.io/line-rate-packet-processing-in-go-with-af_xdp
Go interfaces, reflection, and binary size The short version is that if you're using certain sorts of reflection anywhere in your program, the Go linker won't remove exported (public) methods of any concrete type that's reachable through an interface. It doesn't matter how narrow the interface is; the moment you combine reflection and a concrete type in an interface, the Go linker more or less stops throwing out unu…
mmap vs pread in a real Go storage engine When you build a storage engine in Go, sooner or later you need to answer a very plain question: "How should the code read bytes from files?" This sounds too low-level to matter, but a surprisingly thorough tour of how the VictoriaMetrics filesystem layer reads bytes shows why it does. https://internals-for-interns.com/posts/mmap-vs-pread-go-storage-engine
goshot Goshot is a Go library and CLI for creating beautiful screenshots of code and terminal output, with syntax highlighting, window chrome, and rich backgrounds. https://github.com/watzon/goshot
clawk Give coding agents a disposable Linux VM, not your laptop https://github.com/clawkwork/clawk
go-shirei Shirei is a Cross-Platform GUI framework for Go. You get to write the UI using Go, not HTML and Javascript. https://github.com/hasenj/go-shirei
noisia Harmful workload generator for PostgreSQL. https://github.com/lesovsky/noisia
Showing the 12 most recent of 23 posts we hold for @golanglibrary. 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 — 413,057 of 1,169,250entries 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.
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.
“Go Library” (@golanglibrary), 4,381 subscribers as measured 9 August 2026. Telegram Register, tgregister.com/channel/golanglibrary.
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.