Telegram RegisterThe public register of Telegram

Channel

noindex, nofollow

@notjohnmu

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

5,698subscribers

+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-1001591668828
TypeChannel
Username@notjohnmu
CreatedBetween 1 August 2021 and 31 January 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live12 August 2026
Measurements held5
Confirmed unchanged1 time, most recently 12 August 2026
On Telegramt.me/notjohnmu

Growth

5,6735,6985,685.56 August 2026 — 5,673 subscribers6 August 2026 — 5,673 subscribers6 August 2026 — 5,684 subscribers9 August 2026 — 5,687 subscribers12 August 2026 — 5,698 subscribers6 August 202612 August 2026
5 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 5,669–5,702 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
12 Aug 2026, 17:225,698+11
9 Aug 2026, 21:145,687+3
6 Aug 2026, 17:305,684+11
6 Aug 2026, 04:015,673no change
6 Aug 2026, 03:525,673first reading

Engagement

24 posts held, back to 27 July 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 8 pagesof Telegram’s post history, 20 posts per page.

ERR · 30 days
30.5%
avg views ÷ 5,698 subscribers
Avg views / post
1,740
24 posts measured
Reaction rate
0.512%
reactions ÷ views · ER floor
Posts in window
24
of 24 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. It is computed over the 21 of 24 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 11 August 2026
Posts held24 (27 July 202611 August 2026)
Views total41,647
Reactions total188
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken12 Aug 2026, 03:57 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.

Reaction mix

188 reactions across 20 posts, in 8 distinct kinds. The most used accounts for 31.9% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
😁6031.9%
🔥4021.3%
👍3619.1%
3317.6%
🐳84.26%
😨84.26%
👻21.06%
💯10.532%

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 21 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 188reactions 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 27 July 2026 to 11 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.

Recent posts

11 Aug 2026, 15:29 UTC717 views12 reactionsread 12 August 2026
Photo

Spotify удалит ИИ-треки из рекомендаций и будет помечать нейроартистов тегом "AI Persona". Пользователи ясно дали нам понять, что им не нравится видеть профиль исполнителя, который выглядит как человеческий, а затем выясняется, что этот образ создан ИИ. Пост блоге Spotify: https://newsroom.spotify.com/2026-08-11/ai-persona-badges-transparency/ Яндекс Музыке привет :)

12

10 Aug 2026, 17:36 UTC≈1,050 views8 reactionsread 12 August 2026

Хорошие тезисы от Эли Шварца на случай важных переговоров: SEO — это не транзакционная модель. SEO работает по принципу накопления, где ценность увеличивается постепенно. Реклама может быть транзакционной; SEO — нет. Поисковые системы редко вознаграждают за изменения, произошедшие за одну ночь. Хотя, безусловно, есть истории о мгновенном успехе брендов, в большинстве случаев это месяцы и даже годы упорной работы. На

👍62

10 Aug 2026, 12:32 UTC≈1,520 views6 reactionsread 12 August 2026
Photo

Докатилось, наконец, в GSC. Полезного там мало, до Bing Webmaster Tools далеко.

🐳4👍2

10 Aug 2026, 06:27 UTC≈1,340 views3 reactionsread 12 August 2026
Photo

Джон Мюллер подтвердил, что в стандартном отчете Performance в GSC содержатся запросы из AI Mode, включая последующие запросы в рамках диалога. Из справки: Дополнительный вопрос, заданный пользователем в режиме ИИ, считается новым запросом. При этом все показы, позиции и клики из нового ответа регистрируются уже для нового запроса.

3

10 Aug 2026, 04:37 UTC≈1,280 viewsread 12 August 2026

Googlebot'ы могут отправлять не только GET- и POST-запросы к сайтам, а еще и HEAD, OPTIONS, PUT, PATCH и DELETE. Они составляют менее 1,5% от общего числа запросов, отправляемых всеми поисковыми роботами Google, сообщил Гэри Йиэш. А зачем мы отправляем эти типы HTTP-запросов? Из-за JavaScript. Похоже, что какие-то JavaScript-функции инициируют эти запросы, а рендеринг выполняет свои действия.

5 Aug 2026, 13:14 UTC≈1,830 views22 reactionsread 12 August 2026

Анекдот дня: представитель Google по связям с общественностью Дженнифер Кутц сообщила изданию The Verge, что Reddit не получает никаких преимуществ в поиске Google или в функциях поиска с использованием ИИ.

😁22

5 Aug 2026, 10:23 UTC≈1,840 viewsread 12 August 2026

Гугл продолжает усложнять парсинг. За последнее время: - похоже, добили таки оператор inurl: - начали тестировать необходимость авторизоваться вместо ввода капчи

5 Aug 2026, 10:09 UTC≈1,470 views4 reactionsread 12 August 2026
Forwarded from @optimizationruPhoto

🔤🔤🔤🔤🔤🔤🔤 Мы знаем, что у многих из вас в галерее завалялись старые фото с конференций. 2005, 2017, 2023… а может, и 2001? Покажите их нам — и заодно получите шанс выиграть бесплатный билет на юбилейную «Оптимизацию». Кстати, если у вас не сохранилось собственных фото, можно заглянуть в альбомы фотографов с прошлых конференций и выбрать любимый кадр оттуда. Как участвовать? 🏳️ Выложите в свой Telegram-канал или сто

😁4

4 Aug 2026, 19:14 UTC≈1,460 views2 reactionsread 12 August 2026
Photo

Отличный пост Бритни Мюллер про избыточное применение ИИ.

1💯1

4 Aug 2026, 18:04 UTC≈1,630 views8 reactionsread 12 August 2026
Photo

❗️Что можно сделать, если ваш сайт лишился привычных SSL-сертификатов, для снижения потерь аудитории (пользователи без установленных сертификатов Минцифры), пока лучшего решения нет — совет от Яндекса: — сделать доступной http-версию для роботов Яндекса (отключить редиректы) — https-версию оставить главным зеркалом Пользователи браузеров без соответствующих сертификатов увидят в результатах поиска Яндекса http-верси

😁6👍2

3 Aug 2026, 13:30 UTC≈1,590 views1 reactionsread 12 August 2026
Photo

Как Гугл выявляет сетки аккаунтов с ИИ-слопом на видеоплатформах. Сопоставляются: • паттерны использования API, genAI-метаданные и другие платформенные сигналы; • скорость и синхронность публикаций, включая время от создания канала до первого видео; • повторяющиеся сценарии, заголовки, кадры, аудио и другие признаки общего конвейера. Google Research

1

Showing the 12 most recent of 24 posts we hold for @notjohnmu. 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 — 27,531 of 1,160,990entries 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

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

“noindex, nofollow” (@notjohnmu), 5,698 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/notjohnmu.

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.