Education — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 12 September 2026 and assigned it the closest of 31 fixed categories, at 91% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and the other topics.
Growth
23 measurements spanning 94 days, net +2. 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 7,803–7,852 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 23
Measured (UTC)
Subscribers
Change
9 Nov 2026, 01:10
7,816
-5
5 Nov 2026, 21:58
7,821
-13
2 Nov 2026, 12:41
7,834
+3
30 Oct 2026, 15:29
7,831
-5
27 Oct 2026, 23:27
7,836
-9
25 Oct 2026, 03:49
7,845
-1
22 Oct 2026, 10:15
7,846
+12
18 Oct 2026, 23:26
7,834
+20
15 Oct 2026, 22:15
7,814
-4
5 Oct 2026, 19:18
7,818
-16
28 Sept 2026, 11:56
7,834
+1
18 Sept 2026, 23:54
7,833
+10
14 Sept 2026, 18:59
7,823
-3
11 Sept 2026, 16:16
7,826
+3
7 Sept 2026, 10:17
7,823
-7
2 Sept 2026, 08:36
7,830
+9
30 Aug 2026, 16:14
7,821
+5
27 Aug 2026, 08:56
7,816
+7
24 Aug 2026, 12:13
7,809
-3
17 Aug 2026, 14:38
7,812
first reading
Engagement
24 posts held, back to 20 February 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 36 pages 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 24 posts for this entry, the most recent from 26 September 2026. An engagement rate over an empty window would be a number about nothing.
What this channel posts
Photos
317
Videos
7
Links
116
Lifetime counters from Telegram’s own channel header, read 11 November 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.
Video runtime
1m 14s
Average length
1m 14s
Measured directly from 1 video with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no ≈ mark.
Reaction mix
225 reactions across 20 posts, in 8 distinct kinds. The most used accounts for 40.4% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
👍
91
40.4%
❤
54
24.0%
🔥
32
14.2%
👎
31
13.8%
🥰
10
4.44%
👏
3
1.33%
😁
3
1.33%
🤔
1
0.444%
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 24 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 225 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 24 most recent posts we hold, published 20 February 2026 to 26 September 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.
Advertising
Ad load
4.17%
1 of 24 posts carry an ad marker
Regulatory tokens
1
posts carrying an erid · 1 distinct token
Median views · ads
1,300
over 1 measured post
Median views · rest
2,720
over 23 measured posts
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.
Advertising tokens recorded on this entry
erid
Posts
First seen
Last seen
2SDnjeMs7zT
1
23 September 2026
23 September 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 24 most recent posts we hold, published 20 February 2026 to 26 September 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.
Nil-интерфейс в Go: почему err == nil выдаёт false?
Nil-интерфейс в Go ломает даже опытных разработчиков: функция возвращает nil-указатель *E, а проверка err == nil всё равно даёт false. Причина в том, что интерфейс хранит пару из типа и значения, и пока тип *E на месте, интерфейс не считается пустым. Хочешь вернуть «нет ошибки», возвращай nil явно.
youtube.com/shorts/6LK-o-BSjHA?feature=share
Задача по Go: `select` и побочные эффекты
Что выведет программа?
package main
import "fmt"
func value() int {
fmt.Print("A")
return 42
}
func main() {
var ch chan int
select {
case ch <- value():
fmt.Print("B")
default:
fmt.Print("C")
}
}
Варианты:
1. C
2. AC
3. AB
4. Программа зависнет
Ответ: 2. Вывод будет `AC`.
ch равен nil, поэтому отправка никогда не может выполниться и select выбирает def…
Не застревайте в прошлом — учитесь новым навыкам и ИИ
Чтобы успевать за требованиями рынка, освойте новую профессию и нейросети в Практикуме. До 30 сентября действует скидка 16% на все курсы.
Выбрать курс
Как всё устроено:
— нейросети уже в каждом курсе: учим профессиям сразу с ИИ, чтобы ваше резюме было заметнее, а трудоустройство — увереннее;
— эксперты — практики, которые двигают ИИ-индустрию: перенимайте опы…
👣 Задача на Go 1.27: concurrent job scheduler с generic methods
Нужно реализовать библиотеку scheduler, которая запускает задачи параллельно, ограничивает concurrency, поддерживает context.Context, retry, timeout и возвращает типизированные результаты.
💡 Требования
Создайте generic-тип:
type Scheduler[T any] struct {
// ...
}
Он должен поддерживать регистрацию задач:
type Job[T any] func(ctx context.Contex…
🔥 Хочешь расти в IT быстрее остальных? Перестань учиться в одиночку
Можно годами смотреть курсы, читать документацию и всё равно топтаться на месте.
А можно попасть в правильное окружение, где каждый день обсуждают новые инструменты, вакансии, реальные кейсы, ошибки и то, что уже завтра станет стандартом.
Здесь собраны папки и каналы по разным направлениям IT, чтобы ты быстрее находил нужных людей, идеи и полезный…
👣 Go 1.27: почему две разные closure внезапно могут иметь одинаковый адрес функции?
Что выведет этот код и почему на Go 1.27 поведение стало особенно интересным?
package main
import (
"fmt"
"reflect"
)
func makeFn(x int) func() int {
return func() int {
return x
}
}
func main() {
a := makeFn(10)
b := makeFn(20)
pa := reflect.ValueOf(a).Pointer()
pb := reflect.ValueOf(b).Pointer()
fmt.Println(a(), …
Go-задача: что выведет этот код?
package main
import "fmt"
func main() {
var funcs []func()
for i := range 3 {
funcs = append(funcs, func() {
fmt.Println(i)
})
}
for _, f := range funcs {
f()
}
}
Что будет в выводе?
A)
0
0
0
😎
2
2
2
C)
0
1
2
D) Код не скомпилируется
Правильный ответ: C — 0, 1, 2
Почему?
В современных версиях Go переменная цикла для каждой итерации получает отдельное з…
Задача Go 1.26, на которой легко ошибиться даже опытному разработчику
Что выведет этот код?
package main
import "fmt"
type Config struct {
Timeout *int
}
func main() {
a := Config{
Timeout: new(30),
}
b := a
*b.Timeout = 60
c := Config{
Timeout: new(*a.Timeout),
}
*c.Timeout = 90
fmt.Println(
*a.Timeout,
*b.Timeout,
*c.Timeout,
)
}
Попробуйте определить ответ до запуска.
```text
60 60 …
🧠 Редкая задача для Go-разработчиков
Версия: Go 1.23+
Именно в Go 1.23 появился range по функциям-итераторам и пакет iter.
Нужно реализовать:
func MergeSorted(a, b iter.Seq[int]) iter.Seq[int]
Функция получает два ленивых отсортированных итератора и возвращает один общий поток в отсортированном порядке.
Пример:
a := Seq(1, 4, 7, 10)
b := Seq(2, 3, 8, 9)
for v := range MergeSorted(a, b) {
fmt.Println(v)
…
В Go 1.26 появился типобезопасный errors.AsType, который ищет ошибку нужного типа внутри дерева обёрток.
package main
import (
"errors"
"fmt"
)
type CodeError struct {
Code int
}
func (e *CodeError) Error() string {
return fmt.Sprintf("code=%d", e.Code)
}
type MaskError struct {
Value int
}
func (e MaskError) Error() string {
return "masked"
}
func (e MaskError) As(target any) bool {
dst, ok := target.…
👣 Go давно починил старую ловушку с замыканиями в цикле.
Но concurrency всё ещё может кусаться.
Что не так с этим кодом?
package main
import (
"fmt"
"sync"
)
func main() {
nums := []int{1, 2, 3, 4}
var wg sync.WaitGroup
result := make([]int, 0, len(nums))
for i, n := range nums {
wg.Go(func() {
result = append(result, i*n)
})
}
wg.Wait()
fmt.Println(result)
}
На первый взгляд всё нормально…
👣 Golang-задача с подвохом
Версия: Go 1.23+
Что выведет код?
package main
import "fmt"
func numbers(yield func(int) bool) {
defer fmt.Println("iterator: defer")
for i := 0; i < 5; i++ {
if !yield(i) {
fmt.Println("iterator: stopped")
return
}
fmt.Println("iterator: after yield", i)
}
}
func main() {
for n := range numbers {
fmt.Println("main:", n)
if n == 2 {
break
}
}
fmt.Printl…
❤3👍2🔥1
Showing the 12 most recent of 24 posts we hold for @golangtests. 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.
Posts recorded as deleted after publishing
We recorded 3 posts on @golangtests as deleted — posts this register held that were missing from the channel’s public page on two separate reads, taken from different network addresses at least an hour apart.
A deletion is not wrongdoing. This register can see that a post it held is no longer on the channel’s public page, and when — not why. Expired ad placements, reposts, rotating links and corrections all look the same. This is a count of recorded detections, not an exact total: it misses deletions we could not see, because only a post we held and later re-read inside the page can be seen to go, and it may include a small number of wrong records. How this is measured.
First seen missing
28 August 2026
Most recent seen missing
3 November 2026
Median time before seen missing
3 months
Seen missing in the last 30 days
2
Polls
The 6 polls we hold for this entry, as Telegram rendered them when we read the post. A poll’s figures keep moving after that, so each one is dated.
❓ Какой размер у переменной, типом которой является интерфейс на x64 архитектуре
4 байта9%
8 байт39%
16 байт26%
Зависит от интерфейса25%
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 24 most recent posts we hold, published 20 February 2026 to 26 September 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.
Mentions
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.
Handles this channel named that no longer answer
Dead references
3
handles named in this channel’s posts, vacant today
Evidenced gone
0
we ourselves saw one of these resolve, at some point
Never seen alive
3
vacant every time we have ever looked
@golangtests named 3 handles that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all. A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
Never seen alive
References a handle that is not a live channel — we have no record it ever was one.
@fizmat named in 5 posts, 8 August 2026 – 26 August 2026
@front named in 5 posts, 8 August 2026 – 26 August 2026
@kubernetc named in 5 posts, 8 August 2026 – 26 August 2026
Appears in Telegram’s recommendations for other channels
The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.
Golang @Golang_google · 40,453 Telegram ranks this channel #5 of 90 here — alongside 89 others — read 30 August 2026
Библиотека Go-разработчика | Golang @goproglib · 23,894 Telegram ranks this channel #10 of 91 here — alongside 90 others — read 17 September 2026
Linux Academy @linuxacademiya · 28,647 Telegram ranks this channel #54 of 84 here — alongside 83 others — read 9 September 2026
Kali Linux @linuxkalii · 55,842 Telegram ranks this channel #61 of 89 here — alongside 88 others — read 23 August 2026
DevOps @DevOPSitsec · 23,892 Telegram ranks this channel #63 of 90 here — alongside 89 others — read 18 September 2026
Ozon Tech @ozon_tech · 30,158 Telegram ranks this channel #77 of 98 here — alongside 97 others — read 8 September 2026
AvitoTech @avitotech · 25,811 Telegram ranks this channel #94 of 96 here — alongside 95 others — read 14 September 2026
This channel appears in 7 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
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 9 November 2026 — this
entry's latest reading, not the date you are reading this.
“Go tests” (@golangtests), 7,816 subscribers as measured 9 November 2026. Telegram Register, tgregister.com/channel/golangtests.
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.