Telegram RegisterThe public register of Telegram

Channel

Golang Дайджест

@golang_digest

On this record: Growth · Engagement · What this channel posts · Reactions · Stars · Posts · Polls · Citations · Cite this entry

9,020subscribers

+25 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of 3,162–10,000.

Register entry

Telegram ID-1001658736275
TypeChannel
Username@golang_digest
DescriptionСамое интересное из мира Go: новости, статьи, проекты, сервисы, изменения в языке и др. Посты публикуются не часто - только самое важное, с чем я лично ознакомился. Поэтому можно не мьютить канал =) Обратная связь: @justskiv
CreatedBetween 1 December 2021 and 30 April 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live13 August 2026
Measurements held4
Confirmed unchanged1 time, most recently 13 August 2026
On Telegramt.me/golang_digest

Growth

8,9949,0209,0076 August 2026 — 8,995 subscribers7 August 2026 — 8,994 subscribers10 August 2026 — 9,005 subscribers13 August 2026 — 9,020 subscribers6 August 202613 August 2026
4 measurements spanning 7 days, net +25. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 8,990–9,024 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
13 Aug 2026, 12:179,020+15
10 Aug 2026, 12:529,005+11
7 Aug 2026, 13:468,994-1
6 Aug 2026, 17:188,995first reading

Engagement

22 posts held, back to 9 November 2025the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 15 pagesof Telegram’s post history, 20 posts per page.

ERR · 30 days
40.4%
avg views ÷ 9,020 subscribers
Avg views / post
3,640
3 posts measured
Reaction rate
1.21%
reactions ÷ views · ER floor
Posts in window
3
of 22 held

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.

What these figures were computed from
WindowRolling 30 days · latest post in window 13 August 2026
Posts held22 (9 November 202513 August 2026)
Views total10,930
Reactions total132
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken15 Aug 2026, 10:29 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.

What this channel posts

Photos
46
Videos
1
Links
215

Lifetime counters from Telegram’s own channel header, read 15 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.

Reaction mix

996 reactions across 22 posts, in 5 distinct kinds. The most used accounts for 41.8% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🔥41641.8%
👍28028.1%
26326.4%
🤯222.21%
🤔151.51%

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 22 of the 22 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 996reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 22 most recent posts we hold, published 9 November 2025 to 13 August 2026, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.

Telegram Stars

Stars received
8
across the posts below
Posts paid on
7
of 22 we hold a reading for · 32%
Most on one post
2
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @golang_digest. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.

Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.

This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.

Counted over the 22 most recent posts we hold for this entry, published 9 November 2025 to 13 August 2026. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.

Recent posts

13 Aug 2026, 14:52 UTC≈2,000 views29 reactions1 Starread 15 August 2026

📆Канал с разборами внутренностей Go и не только Хочу порекомендовать вам ещё один канал, который сам давно почитываю — очень крутые глубокие разборы и авторский стиль, всё как я люблю. Не реклама, честная рекомендация 🫶

15🔥9👍5

11 Aug 2026, 10:35 UTC≈2,960 views19 reactions2 Starsread 15 August 2026

SIMD в Go 1.27 https://habr.com/ru/articles/1062972/ Раз уж в Go завозят SIMD, вот хороший разбор по нему. Начинается с ликбеза — как процессор вообще складывает числа, что такое векторные регистры и полосы, почему одна инструкция может сложить восемь чисел за раз. Дальше автор берёт go1.27rc2 и проверяет всё руками на двух машинах: M3 Pro и i9-14900KF. Напомню, что в 1.27 под флагом GOEXPERIMENT=simd обещают пор

10🔥6👍3

17 Jul 2026, 12:17 UTC≈5,970 views84 reactionsread 15 August 2026
Photo

🦄 Go 1.27: дженерик-методы, json/v2 в проде и профиль утёкших горутин 🟠Draft release notes — релиз ожидается уже в августе Главное — дженерик-методы Я писал об этом ещё на этапе пропозала, поэтому подробно описывать тут не буду. Вкратце: метод теперь может объявлять собственные типовые параметры. Долгое время такое приходилось писать в виде обычной функции: // Было — только обычной функцией func MapSlice[T, U an

👍53🔥2010🤯1

12 May 2026, 17:08 UTC≈7,940 views20 reactionsread 15 August 2026
Forwarded from @go_update

⚠️ CVE-2026-42501 или почему вам нужно обновиться до Go 1.26.3/go1.25.10 ⚠️ Те кто давно работают с Go (или читают меня) знают, что целостность наших модулей гарантируется не только HTTPS транспортом до самой прокси, но и отдельной базой SumDB, которая хранит в себе хеши модулей подписанные приватным ключом. При этом сама база устроена так, что невозможно внести изменения в прошлые записи, без каскада изменений в но

👍107🔥3

17 Apr 2026, 14:17 UTC≈7,830 views61 reactionsread 15 August 2026

👴 Почему в Go нет тернарного оператора? https://dburov.com/ru/research/go-ternary Дмитрий Буров провёл большое исследование на эту старую добрую тему и попросил меня поделиться ей, чтобы собрать мнение сообщества — внизу статьи есть короткий опрос из 4 вопросов. Вкратце, о чём материал: - Позиция core-команды Go не менялась с 2009 года: ?: порождает непроницаемо сложные выражения, if-else «бесспорно яснее», языку

29🔥14🤔10👍8

22 Mar 2026, 17:08 UTC≈9,320 views58 reactions1 Starread 15 August 2026

🟦 ❤️ Modern Go Guidelines от GoLand Team — чтобы AI-агенты перестали писать устаревший Go https://github.com/JetBrains/go-modern-guidelines Ребята из JetBrains сделали набор гайдлайнов для AI-агентов (Claude Code и Junie), чтобы те писали современный Go, а не код образца 2018 года. Проблема реальная и знакомая каждому, кто пользуется ИИ-ассистентами для Go: - Отсечка данных: модели не знают фичи, добавленные посл

👍35🔥1211

6 Mar 2026, 09:27 UTC≈7,700 views33 reactionsread 15 August 2026

🔐 Go 1.26.1 — откат go mod init и мелкие security фиксы https://go.dev/doc/devel/release#go1.26.1 Security-фиксы в crypto/x509, html/template, net/url и os — стоит обновиться. Также тут мелкие багфиксы в компиляторе, go command, go fix, os и reflect. Самое главное — откатили поведение go mod init обратно к здравому смыслу, о котором я недавно писал. Быстро одумались 🧙 #go1_26 #release

👍258

3 Mar 2026, 18:13 UTC≈7,700 views39 reactionsread 15 August 2026

🔨 Два активных proposal с жаркой дискуссией Proposal #1: Вернуть go mod init к здравому смыслу В Go 1.26 тихо поменяли поведение go mod init: теперь он выставляет в go.mod директиву go 1.25 вместо go 1.26. Идея была в том, чтобы новый модуль был "по умолчанию совместим" со старыми тулчейнами. Проблема в том, что это ломает ожидания: $ go version go version go1.26 $ go mod init myproject # go.mod теперь содержит:

20👍15🔥4

27 Feb 2026, 02:42 UTC≈8,480 views53 reactionsread 15 August 2026

🚨 BREAKING Generic methods proposal официально принят — автор Robert Griesemer. Это одно из самых ожидаемых изменений в Go после дженериков.

🔥33🤯154👍1

23 Feb 2026, 17:19 UTC≈8,200 views10 reactionsread 15 August 2026
Poll

Надо ли добавлять Generic Methods в Go? (простите за повтор, попросили доработать варианты)

  1. Да, даже с таким компромиссом25%
  2. Да, но только если они всё же будут реализовывать интерфейс. В текущем варианте — нет.19%
  3. Нет, ни в каком из этих вариантов10%
  4. Я понимаю суть, но мне без разницы11%
  5. Не знаю, не понимаю суть проблемы и решения18%
  6. Посмотреть ответы — мне лень думать об этом16%

Shares as published, totalling 99%. No per-option vote count is published by Telegram, so none is shown.

6👍4

23 Feb 2026, 16:51 UTC≈9,850 views46 reactions1 Starread 15 August 2026
Photo

🧬 Proposal: Generic Methods для Go Robert Griesemer (один из авторов языка) открыл proposal, который многие считали невозможным. Go FAQ буквально говорил: > We do not anticipate that Go will ever add generic methods Но теперь — возможно, добавят 👍 Суть в том, что раньше дженерик-методы блокировались по цепочке: если методы могут принимать параметры типов, значит и методы интерфейсов тоже должны. А это не знали ка

27👍11🔥8

22 Feb 2026, 09:42 UTC≈5,340 views104 reactionsread 15 August 2026
Forwarded from @tuzov_ai_lab

😩 Go Team vs вайбкодеры https://groups.google.com/g/golang-dev/c/4Li4Ovd_ehE Кто-то залил CL (changelist, аналог Pull Request в системе Gerrit) в Go с тегом Co-Authored-By: Claude Opus 4.5 в описании коммита. Ian Lance Taylor это заметил и поднял вопрос в рассылке golang-dev: а вообще есть ли политика по поводу AI-написанного кода? Авторские права, CLA — всё это висит в воздухе. Ответ Rob Pike: > Это очень скольз

🔥5633👍14🤔1

Showing the 12 most recent of 22 posts we hold for @golang_digest. 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.

Stars beside a post are paid reactions — Telegram Stars, bought with money and spent on that post. They are a different unit from reactions and are never added to them, here or anywhere else on this page.

Polls

The poll we hold for this entry, as Telegram rendered it when we read the post. A poll’s figures keep moving after that, so each one is dated.

23 Feb 2026, 17:19 UTCAnonymous Poll812 voters

Надо ли добавлять Generic Methods в Go? (простите за повтор, попросили доработать варианты)

  1. Да, даже с таким компромиссом25%
  2. Да, но только если они всё же будут реализовывать интерфейс. В текущем варианте — нет.19%
  3. Нет, ни в каком из этих вариантов10%
  4. Я понимаю суть, но мне без разницы11%
  5. Не знаю, не понимаю суть проблемы и решения18%
  6. Посмотреть ответы — мне лень думать об этом16%

Shares as published, totalling 99%. No per-option vote count is published by Telegram, so none is shown.

Percentages only — there are no per-option vote counts here, because Telegram publishes none.The public post preview gives each option’s share and a single voter total, and nothing else. Multiplying one by the other would produce a per-option tally that looks measured and is not: the shares are rounded to whole numbers before we ever see them. We print what was published and leave the column that does not exist empty.

The shares need not add up to 100.Rounding alone puts many polls at 99 or 101. A poll that allows more than one answer per voter runs well past 100 by design, and several here do. The bars are drawn against a fixed 100% track at each option’s own percentage rather than normalised to the total, so a poll that exceeds it shows that it does instead of being quietly rescaled.

Read from the 22 most recent posts we hold, published 9 November 2025 to 13 August 2026. Telegram labels each poll by kind — an anonymous poll, a quiz, a closed set of final results — and that label is reproduced rather than paraphrased.

Citation-graph rank

Citation-graph rank — 598,692 of 1,480,688entries 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.

Forward network

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.

Mentions

Named by 2 registered channels — every channel on the register whose own posts have named this one, by its current username or any other username it currently holds, merged from two separately captured readings of the same fact so a namer caught by only one of them is not missed and a namer both caught is not counted twice. A username this channel has since dropped is not matched — that handle may belong to someone else now, and crediting today’s namer to yesterday’s owner would misattribute it.

Named by

Channels on the register whose posts name this channel's handle.

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.

Cite this entry

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 13 August 2026 — this entry's latest reading, not the date you are reading this.

“Golang Дайджест” (@golang_digest), 9,020 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/golang_digest.

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.