Telegram RegisterThe public register of Telegram
Telegram profile photo for linkmeup

Channel

linkmeup

@linkmeup_podcast

On this record: Topic · Growth · Engagement · What this channel posts · Stars · Advertising · Posts · Posts edited after publishing · Posts recorded as deleted · Citations · Telegram's recommendations · Cite this entry

17,587subscribers

+304 since we began measuring on 5 August 2026

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

Register entry

Telegram ID-1001041560151
TypeChannel
Username@linkmeup_podcast
DescriptionСамый официальный канал единственного и неповторимого подкаста linkmeup. Хотите поговорить? https://t.me/linkmeup_chat Хотите с нами поговорить? @LoxmatiyMamont
Created25 February 2016 — measured — cross-checked against a third-party dataset (ext.tg_channel)
First recorded6 August 2026
Last confirmed live15 November 2026
Measurements held63
Confirmed unchanged1 time, most recently 15 November 2026
On Telegramt.me/linkmeup_podcast

Topic

Technology — 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 10 September 2026 and assigned it the closest of 31 fixed categories, at 100% 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

17,28317,58717,4355 August 202615 November 2026
63 measurements spanning 102 days, net +304. 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 17,237–17,633 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 63
Measured (UTC)SubscribersChange
15 Nov 2026, 23:1517,587+5
12 Nov 2026, 13:1017,582+10
10 Nov 2026, 11:1517,572+6
9 Nov 2026, 01:3717,566+1
7 Nov 2026, 21:4717,565+3
6 Nov 2026, 18:4617,562-2
5 Nov 2026, 18:2517,564+7
4 Nov 2026, 15:4617,557+12
3 Nov 2026, 16:0517,545+21
2 Nov 2026, 17:5617,524+13
1 Nov 2026, 21:2717,511-2
31 Oct 2026, 18:4917,513+1
30 Oct 2026, 18:4017,512+5
29 Oct 2026, 21:0617,507-3
28 Oct 2026, 22:3517,510+6
27 Oct 2026, 20:3617,504+17
26 Oct 2026, 20:4717,487+11
25 Oct 2026, 22:3117,476+10
24 Oct 2026, 23:0417,466+9
22 Oct 2026, 18:2817,457first reading

Engagement

175 posts held, back to 31 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 85 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
24.7%
avg views ÷ 17,587 subscribers
Avg views / post
4,350
67 posts measured
Reaction rate
—
this channel exposes no reaction counts
Posts in window
67
of 175 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 17 November 2026
Posts held175 (31 July 2026 – 17 November 2026)
Views total291,150
Reactions total—
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken17 Nov 2026, 17:40 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
≈763
Videos
≈234
Links
≈10,100

Lifetime counters from Telegram’s own channel header, read 17 November 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked ≈ was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.

Video runtime
11m 05s
Average length
35s

Measured directly from 19 videos 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.

Telegram Stars

Stars received
6
across the posts below
Posts paid on
6
of 175 we hold a reading for · 3%
Most on one post
1
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @linkmeup_podcast. 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 175 most recent posts we hold for this entry, published 31 July 2026 to 17 November 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.

Advertising

Ad load
5.14%
9 of 175 posts carry an ad marker
Regulatory tokens
9
posts carrying an erid · 9 distinct tokens
Median views · ads
4,130
over 9 measured posts
Median views · rest
4,190
over 166 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. They are printed side by side with the count behind each rather than as a ratio: an ad and an ordinary post are not otherwise matched — for topic, for length, for hour of day — so the gap between them is a description of two groups and not the effect of one being an ad.

Advertising tokens recorded on this entry
eridPostsFirst seenLast seen
2Vtzqw2H3ZF127 October 202627 October 2026
2VtzqxWbkFm125 August 202625 August 2026
2W5zFG94Ri1119 August 202619 August 2026
2W5zFGhknh8113 November 202613 November 2026
2W5zFHFM3tn111 November 202611 November 2026
2W5zFJ31cL916 August 20266 August 2026
2W5zFJa1JTB124 August 202624 August 2026
2W5zFK5j1c6117 November 202617 November 2026
2W5zFK8XZU612 November 20262 November 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 175 most recent posts we hold, published 31 July 2026 to 17 November 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.

Recent posts

Telegram’s own ‘edited’ marker: 51 of 67 posts held from the last 30 days (76.1%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).

17 Nov 2026, 10:20 UTC≈2,060 viewsread 17 November 2026
Advertisementerid 2W5zFK5j1c6Photo

В реалиях современного ИБ классический локальный анализ уже мало эффективен. Ловкие парни стали использовать легитимные инструменты, придумывать свои методы шифрования трафика, а самое важное, что скорость их действий стала молниеносной. Зачастую достаточно просто пропустить в логах появление незнакомого домена, чтобы не узнать что что-то уже происходит. Вот для этого современные NAD системы снабжаются облачными функ…

17 Nov 2026, 10:00 UTC≈2,240 viewsread 17 November 2026

Просто знайте, что в последнее время мы слишком много грешили с громкими названиями и страшными цифрами. Поэтому Terminal2Shell – это ультимативный баг длиной в 55 лет. https://terminal2shell.com/

17 Nov 2026, 06:00 UTC≈2,560 viewsread 17 November 2026

Мало нам проблем в мире, так что давайте ещё вспомним, что мы слепо доверяем MAC-адресам, что в разрезе BGP EVPN совсем печалька, в плане access-портов. Если кто вдруг забыл, то в обычном L2 mac-спуфинг живёт себе в дата плейне и всё с ним понятно. А когда речь про EVPN, то изучение маков происходит через контрол плейн в отдельном Type-2 (MAC/IP Advertisement). И как с этим можно жить, как раз вся статья. https://blo…

16 Nov 2026, 12:02 UTC≈3,020 viewsread 17 November 2026

Вот кажется, что сложного в рекомендациях: есть товар, есть пользователь, надо просто подобрать первое ко второму. Но не все так просто с новыми товарами, у которых еще нет истории покупок. Как в таком случае выстраивать реки - вопрос. Ответ на него нашла команда из Т-Банка. Она предложила два подхода, которые были представлены в Риме на конференции ACM CIKM. Первый – модель E2L3AE, которая учит две части системы – т…

16 Nov 2026, 10:01 UTC≈3,110 viewsread 17 November 2026

Ладно, вы там это, не скучайте, что ли. Эпоха скриптов для выхода за пределы контейнера/виртуалки/KVM стремится к закату, потому что зачем нам всё это, если можно эксплуатировать уязвимости сразу в TCP. Осталось только разобраться в том, что нам предлагают юные дарования. TCP Pre-auth – это вообще что такое? Откуда вдруг в TCP концепция auth вообще взялась? https://github.com/V4bel/NoisyTCP

16 Nov 2026, 06:00 UTC≈3,230 viewsread 17 November 2026

Если у чего-то было открытие, то, значит, было и закрытие. Пусть не такое радостное, как открытие, но как же без него. Так что пусть тоже тут полежит, хуже точно не станет. https://www.youtube.com/watch?v=U_vSDVqv1Qc

15 Nov 2026, 17:00 UTC≈3,980 viewsread 17 November 2026

Столько лет прошло, А холод жжёт в груди. Эй, Земля, алло, Я «Вояджер-1» — Выходи на связь, Срочно выходи! Наскитался всласть По Млечному пути, Да так и не сумел себе найти Другой ориентир. Примерно год назад мне попался в инсте пост NASA о том, что в ноябре 2026 космический аппарат Voyager-1 окажется в одном световом дне от Земли. Я отметил, что это важное знаковое событие и сделал отложку, чтобы не забыть запости…

15 Nov 2026, 15:00 UTC≈4,450 viewsread 17 November 2026
Video

Просто знайте, что у WinRAR есть мерчовые футболки в, даже не знаю как тут лучше сказать, какой виде. Сжатом? Скомпрессированном? В общем, в том самом правильном виде, каком они должны быть.

15 Nov 2026, 10:00 UTC≈3,390 viewsread 17 November 2026

Если спустя четверть века после своей прайм-эры Voodoo 3 получает апдейт линуксового драйвера, это значит, что кому-то оно очень надо и где-то оно всё ещё используется. https://x.com/tomshardware/status/2091191219993141318

15 Nov 2026, 06:00 UTC≈3,410 viewsread 17 November 2026

Хорошая реализация лаборатории, запускаемой в браузере, которая не боится закрытой вкладки. Тут это делают с PostgreSQL, а вернее, запускают PGlite – постгрес, скомпилированный под WASM, который хранит все данные в IndexedDB. https://github.com/datawan-labs/pg

14 Nov 2026, 15:00 UTC≈3,650 viewsread 17 November 2026
Video

А мы продолжаем думать, как улучшить конкурс на скоростной обжим витой пары в рамках линкмитапа.

14 Nov 2026, 10:00 UTC≈4,420 viewsread 17 November 2026

Просто не забываем, да, что взрослые серьёзные люди хранят данные только в распределённых облачных системах. Так что давайте не забывать настоящих профессионалов своего дела. https://github.com/yarrick/pingfs

Showing the 12 most recent of 175 posts we hold for @linkmeup_podcast. 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 edited after publishing

@linkmeup_podcast edited 15 posts after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.

An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.

First edit seen
14 August 2026
Most recent edit
13 November 2026

Posts recorded as deleted after publishing

We recorded 1 post on @linkmeup_podcast 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
31 August 2026
Most recent seen missing
31 August 2026
Median time before seen missing
5 days
Seen missing in the last 30 days
0

Forward network

Republishes

Channels on the register whose posts this channel has forwarded.

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 6 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.

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.

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.

MikroTik-сэнсэй
@mikrotik_sensei · 19,638
Telegram ranks this channel #11 of 92 here — alongside 91 others — read 1 October 2026
Информация опасносте
@alexmakus · 18,744
Telegram ranks this channel #29 of 85 here — alongside 84 others — read 5 October 2026
ITDog
@itdoginfo · 19,237
Telegram ranks this channel #30 of 87 here — alongside 86 others — read 2 October 2026
Tech Debunker
@tech_debunker · 24,361
Telegram ranks this channel #36 of 89 here — alongside 88 others — read 17 September 2026
Selectel
@Selectel · 62,346
Telegram ranks this channel #44 of 96 here — alongside 95 others — read 21 August 2026
Bash Days | Linux | DevOps
@bashdays · 23,608
Telegram ranks this channel #48 of 94 here — alongside 93 others — read 18 September 2026
Типичный Сисадмин
@sysodmins · 41,091
Telegram ranks this channel #48 of 93 here — alongside 92 others — read 31 August 2026
Yandex Cloud
@yandexcloudnews · 23,898
Telegram ranks this channel #54 of 97 here — alongside 96 others — read 22 September 2026
remontka.pro ✅
@remontka_pro · 26,333
Telegram ranks this channel #54 of 77 here — alongside 76 others — read 13 September 2026
Утечки информации
@dataleak · 117,550
Telegram ranks this channel #54 of 83 here — alongside 82 others — read 14 August 2026
DevOps by REBRAIN
@rebrain_devops · 28,705
Telegram ranks this channel #55 of 94 here — alongside 93 others — read 9 September 2026
BZD • Книги для программистов
@bzd_channel · 36,189
Telegram ranks this channel #55 of 57 here — alongside 56 others — read 1 September 2026
Серверная Админа | Компьютерные сети
@school_network · 26,381
Telegram ranks this channel #59 of 85 here — alongside 84 others — read 12 September 2026
ServerAdmin.ru
@srv_admin · 32,699
Telegram ranks this channel #59 of 96 here — alongside 95 others — read 5 September 2026
ЗаТелеком 🌐
@zatelecom · 64,456
Telegram ranks this channel #63 of 94 here — alongside 93 others — read 21 August 2026
SecAtor
@true_secator · 42,222
Telegram ranks this channel #64 of 78 here — alongside 77 others — read 29 August 2026
Книги для Системного Администратора
@i_odmin_book · 18,785
Telegram ranks this channel #65 of 83 here — alongside 82 others — read 5 October 2026
#энерголикбез
@operby · 35,923
Telegram ranks this channel #65 of 85 here — alongside 84 others — read 2 September 2026
IT STAND
@ITSTAND_ORG · 164,398
Telegram ranks this channel #68 of 98 here — alongside 97 others — read 9 September 2026
Хакер — Xakep.RU
@xakep_ru · 40,322
Telegram ranks this channel #68 of 83 here — alongside 82 others — read 30 August 2026
Ряды Фурье
@Fourier_series · 43,971
Telegram ranks this channel #68 of 93 here — alongside 92 others — read 29 August 2026
I’m CTO, bitch
@ctobtch · 20,232
Telegram ranks this channel #69 of 95 here — alongside 94 others — read 28 September 2026
NatashkaPLUS
@NatashkaPLUS · 57,688
Telegram ranks this channel #70 of 73 here — alongside 72 others — read 23 August 2026
Секреты сисадмина | DevOps, Linux, SRE
@sysadmin_library · 25,664
Telegram ranks this channel #72 of 85 here — alongside 84 others — read 13 September 2026

This channel appears in 38 seed channels' Telegram-generated recommendation lists in total, of which the 24 where it ranks highest are shown above. 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 15 November 2026 — this entry's latest reading, not the date you are reading this.

“linkmeup” (@linkmeup_podcast), 17,587 subscribers as measured 15 November 2026. Telegram Register, tgregister.com/channel/linkmeup_podcast.

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.