Telegram RegisterThe public register of Telegram
Telegram profile photo for { между скобок } анонсы 📣

Channel

{ между скобок } анонсы 📣

@megdu_skobok

On this record: Growth · Engagement · Reactions · Advertising · Posts · Citations · Cite this entry

4,694subscribers

-6 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-1001767555642
TypeChannel
Username@megdu_skobok
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 live16 August 2026
Measurements held5
Confirmed unchanged1 time, most recently 16 August 2026
On Telegramt.me/megdu_skobok

Growth

4,6944,7004,6976 August 2026 — 4,700 subscribers6 August 2026 — 4,700 subscribers9 August 2026 — 4,694 subscribers12 August 2026 — 4,696 subscribers16 August 2026 — 4,694 subscribers6 August 202616 August 2026
5 measurements spanning 10 days, net -6. 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 4,693–4,701 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
16 Aug 2026, 05:354,694-2
12 Aug 2026, 19:284,696+2
9 Aug 2026, 09:514,694-6
6 Aug 2026, 09:304,700no change
6 Aug 2026, 06:344,700first reading

Engagement

20 posts held, back to 6 March 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 7 pagesof 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 17 July 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

168 reactions across 16 posts, in 12 distinct kinds. The most used accounts for 32.7% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🔥5532.7%
👍4627.4%
3722.0%
💩95.36%
🥴63.57%
👎42.38%
🤔31.79%
🤡31.79%
🤮21.19%
👏10.595%
🙏10.595%
🤝10.595%

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 17 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 168reactions 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 6 March 2026 to 17 July 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
15.0%
3 of 20 posts carry an ad marker
Regulatory tokens
3
posts carrying an erid · 3 distinct tokens
Median views · ads
2,470
over 3 measured posts
Median views · rest
2,300
over 17 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
eridPostsFirst seenLast seen
2VtzquZx6U3113 April 202613 April 2026
2VtzquZx6c8116 June 202616 June 2026
2Vtzqwi1SF1116 March 202616 March 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 20 most recent posts we hold, published 6 March 2026 to 17 July 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

17 Jul 2026, 15:59 UTC≈1,360 views2 reactionsread 12 August 2026

Всем привет,мы начинаем Финальное интервью инженера: кого вы на самом деле нанимаете, подключайтесь к YouTube трансляции

1👍1

Signed Grisha Skobelev

16 Jul 2026, 16:03 UTC≈1,370 views1 reactionsread 12 August 2026

17 июля 19:00 по мск Финальное интервью инженера: кого вы на самом деле нанимаете Большинство финальных интервью проходит по одному сценарию: интервьюер открывает список вопросов и надеется, что по ответам сможет понять, подходит кандидат или нет. Но качественный найм начинается гораздо раньше. В этом выпуске разбираем подход Светланы Ивановой и показываем, как адаптировать его для найма инженеров и технических ли

🔥1

Signed Grisha Skobelev

9 Jul 2026, 06:59 UTC≈2,190 views7 reactionsread 12 August 2026

AI-коллега - рецепты построения своего помощника AI уже перестал быть просто чат-ботом. В этом видео разбираем, как построить собственного AI-помощника, который помогает инженерам в ежедневной работе: разбирает инциденты, отвечает на вопросы, помогает искать баги, создает задачи и автоматизирует рутину. Основано на реальном опыте внедрения в платформенной команде. Полезные ссылки - Статья антропик по контекст энжин

👍5🔥2

Signed Grisha Skobelev

6 Jul 2026, 08:31 UTC≈1,730 viewsread 12 August 2026
Photo

Делаем новый сезон Podlodka TechLead Crew и конечно же про AI 🌚 Сейчас самое время обсудить эту тему, бизнес уже успел внедрить в SDLC, а кто то в соло с помощью агентов уже все построил 😅 Кого стоит позвать выступить? Какие сейчас популярные спикеры/компании в теме AI? PS если хотите выступить на конфе, пишите в лс @Gskoba

Signed Grisha Skobelev

22 Jun 2026, 07:00 UTC≈2,370 viewsread 12 August 2026
Photo

Как правильно работать с резервным копированием в облаке? 25 июня приглашаем на бесплатный вебинар от MWS Cloud Platform всех, кто работает с облаками. ⚫️Развеем мифы, разберём лучшие современные подходы и инструменты. ⚫️Обсудим интеграцию в процессы, консистентность, точечное восстановление и безопасность. Поговорим о плюсах нативных облачных инструментов. ⚫️Проведём демо в MWS Cloud Platform и ответим на ваши в

Signed Grisha Skobelev

16 Jun 2026, 07:16 UTC≈2,430 views9 reactionsread 12 August 2026
Advertisementerid 2VtzquZx6c8Photo

Приглашаем на курс для прокачки навыков архитектора и проектировщика, которые важны для профессионального роста программиста. С курсом «Системный дизайн высоконагруженных проектов» вы: ▪️изучите ключевые фундаментальные паттерны и получите навыки проектирования проектов с миллионной аудиторией (балансировка, масштабирование апп/кешей/субд, высокая доступность и кластерные решения, шардинг, CAP/PACELS, консистентнос

👍5🔥31

Signed Grisha Skobelev

8 Jun 2026, 09:44 UTC≈1,970 views2 reactionsread 12 August 2026
Photo

🤖 AI в разработке: время новых процессов Сейчас уже поздно спорить о том, нужен ли AI в разработке: он прочно вошёл в процессы — и в стартапах, и в бигтехе. Эксперты Podlodka AI Crew собрали сезон «AI-First Development», чтобы обсудить уже не отдельные инструменты, а новую инженерную модель, в которой AI становится частью команды. С 15 по 19 июня участники конференции: 📄 Разберутся, как делать AI-разработку более

1🙏1

Signed Grisha Skobelev

20 May 2026, 12:20 UTC≈2,290 views4 reactionsread 12 August 2026
Photo

🧠 Мышление — наш главный навык. Качаем с Podlodka Soft Skills Crew Хотите лучше понимать, как вообще сейчас думать, принимать решения и не теряться в эпоху ИИ? Тогда вам в новый сезон Podlodka Soft Skills Crew — «Мышление как навык», который пройдёт 25–29 мая. Организаторы конференции собрали очень сильную команду: IT-лидеры, авторы научпоп-книг, преподаватели и практики из индустрии. Будет и база про то, как рабо

👍21🔥1

Signed Grisha Skobelev

13 May 2026, 07:03 UTC≈2,300 views5 reactionsread 12 August 2026
Photo

Стартуем с Kubernetes без боли в Managed Kubernetes от MWS Cloud Platform. 27 мая в 16:00 Александр Курасов, технический владелец продукта в MWS Cloud Platform, покажет, как развернуть кластер за минуты, на вебинаре «Быстрый старт с Managed Kubernetes в облаке MWS». Разберём архитектуру сервиса, его интеграцию с IAM, сетями и балансировщиками. Увидите, как управляемый сервис берёт на себя администрирование master-у

💩41

Signed Grisha Skobelev

5 May 2026, 12:22 UTC≈2,520 views8 reactionsread 12 August 2026
Photo

Онлайн эфир South HUB о будущем технических лидеров. CTO строил экспертизу годами. Архитектурные решения, технологический стек, инженерные подходы накапливались как капитал. И вдруг ИИ делает за час то, на что у джуна уходила неделя. Модели меняются каждые несколько месяцев. Рядом появляются 25-летние, для которых всё это просто среда в которой они выросли, а не вызов. Одни уходят в панику. Другие переосмысляют рол

👍61👏1

Signed Grisha Skobelev

18 Apr 2026, 08:00 UTC≈2,480 views0 reactionsread 12 August 2026

Мы начинаем, подключайтесь “Доклад: Claude Codeкак напарник, а не как волшебная кнопка | Федор Догов”

Signed Grisha Skobelev

16 Apr 2026, 13:27 UTC≈2,370 views12 reactionsread 12 August 2026
Photo

18 апреля 11:00 по мск “Доклад: Claude Codeкак напарник, а не как волшебная кнопка | Федор Догов” Обсудим как в крупном FinTehc используется Claude Code, примеры реальных кейсов, дистрибуция, демо, работа с контекстом. Также затронем такие темы - как AI помогает в работе и какие есть проблемы. Подключайтесь в субботу с первой чашкой кофе ☕️ к YouTube трансляции

🔥93

Signed Grisha Skobelev

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

Citation-graph rank — 294,843 of 1,481,502entries 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.

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

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

“{ между скобок } анонсы 📣” (@megdu_skobok), 4,694 subscribers as measured 16 August 2026. Telegram Register, tgregister.com/channel/megdu_skobok.

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.