Telegram RegisterThe public register of Telegram
Telegram profile photo for noindex, nofollow

Channel

noindex, nofollow

@notjohnmu

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

5,973subscribers

+300 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 28 February 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live8 November 2026
Measurements held27
Confirmed unchanged1 time, most recently 8 November 2026
On Telegramt.me/notjohnmu

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 12 September 2026 and assigned it the closest of 31 fixed categories, at 81% 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

5,6735,9735,8236 August 2026 — 5,673 subscribers6 August 2026 — 5,673 subscribers6 August 2026 — 5,684 subscribers9 August 2026 — 5,687 subscribers12 August 2026 — 5,698 subscribers16 August 2026 — 5,714 subscribers19 August 2026 — 5,740 subscribers23 August 2026 — 5,750 subscribers26 August 2026 — 5,758 subscribers29 August 2026 — 5,773 subscribers1 September 2026 — 5,777 subscribers4 September 2026 — 5,794 subscribers10 September 2026 — 5,799 subscribers14 September 2026 — 5,804 subscribers17 September 2026 — 5,823 subscribers26 September 2026 — 5,837 subscribers5 October 2026 — 5,856 subscribers12 October 2026 — 5,886 subscribers15 October 2026 — 5,897 subscribers18 October 2026 — 5,903 subscribers22 October 2026 — 5,912 subscribers25 October 2026 — 5,914 subscribers27 October 2026 — 5,929 subscribers31 October 2026 — 5,951 subscribers2 November 2026 — 5,956 subscribers5 November 2026 — 5,959 subscribers8 November 2026 — 5,973 subscribers6 August 20268 November 2026
27 measurements spanning 95 days, net +300. 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,628–6,018 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 27
Measured (UTC)SubscribersChange
8 Nov 2026, 23:505,973+14
5 Nov 2026, 09:215,959+3
2 Nov 2026, 13:505,956+5
31 Oct 2026, 00:285,951+22
27 Oct 2026, 23:195,929+15
25 Oct 2026, 05:455,914+2
22 Oct 2026, 04:405,912+9
18 Oct 2026, 12:115,903+6
15 Oct 2026, 14:005,897+11
12 Oct 2026, 10:545,886+30
5 Oct 2026, 06:015,856+19
26 Sept 2026, 18:165,837+14
17 Sept 2026, 20:575,823+19
14 Sept 2026, 00:575,804+5
10 Sept 2026, 04:595,799+5
4 Sept 2026, 21:195,794+17
1 Sept 2026, 16:185,777+4
29 Aug 2026, 08:255,773+15
26 Aug 2026, 07:485,758+8
23 Aug 2026, 14:075,750first reading

Engagement

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

ERR · 30 days
25.2%
avg views ÷ 5,973 subscribers
Avg views / post
1,500
21 posts measured
Reaction rate
0.304%
reactions ÷ views · ER floor
Posts in window
21
of 45 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 17 of 21 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 4 November 2026
Posts held45 (27 July 2026 – 4 November 2026)
Views total31,554
Reactions total78
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken5 Nov 2026, 01:08 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

Video runtime
44s
Average length
44s

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

266 reactions across 36 posts, in 11 distinct kinds. The most used accounts for 26.7% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
😁7126.7%
👍5922.2%
🔥4215.8%
❤4115.4%
🫡186.77%
💯145.26%
😨93.38%
🐳83.01%
👻20.752%
👀10.376%
👨‍💻10.376%

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

Measured over the 45 most recent posts we hold, published 27 July 2026 to 4 November 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
1
across the posts below
Posts paid on
1
of 45 we hold a reading for · 2%
Most on one post
1
single highest reading

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

Recent posts

Telegram’s own ‘edited’ marker: 7 of 21 posts held from the last 30 days (33.3%) 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).

4 Nov 2026, 18:28 UTC590 views1 reactionsread 5 November 2026
Forwarded from @advancedseoblogPhoto

Прочел я тут как ломанули Binance: June 2026 — Supply chain attack. Engineer A from Wallet DevOps downloaded a tampered Homebrew installation in order to install a popular AI coding tool after searching for it on a search engine. Our security team detected the anomaly, replaced the device, and rotated all related credentials as a proactive security action. However, Engineer A’s role and his related colleagues on our …

🫡1

4 Nov 2026, 17:21 UTC814 views6 reactionsread 5 November 2026
Photo

Пример рекламы в AI Mode - 4 объявления. Реклама в этом режиме показывается пока только в нескольких странах (США, Австралия, Канада, Индия и др.) и только на английском.

🫡6

3 Nov 2026, 22:20 UTC≈1,230 views13 reactionsread 5 November 2026
Photo

На некоторых аккаунтах в GSC заметили резкий рост кликов (рост CTR при том же объеме показов) - похоже на трафик ботов или баг отчета.

💯12👀1

3 Nov 2026, 19:09 UTC≈1,250 views4 reactionsread 5 November 2026

Яков Осипенков напоминает, что любой диспетчер тегов, будь то Google Tag Manager или Яндекс Тег Менеджер — потенциальный источник угрозы. Следите за правами юзеров, которые имеют к нему доступ.

👍2❤1😁1

2 Nov 2026, 21:48 UTC≈1,600 views2 reactions1 Starread 5 November 2026

RESONEO с первоклассным контентом снова на линии: - про граф знаний (Knowledge graph), состоящий из ~5 млрд сущностей и 500 млрд фактов - про твиддлеры - нашли 120 шт., из них 111 не было ни в утечке 2024 г. ни в документе 2018 г.; используются для переранжирования

🫡2

2 Nov 2026, 19:19 UTC≈1,290 views1 reactionsread 5 November 2026
Photo

Визуализация на основе квартального отчета Гугла (Alphabet) и динамика капитальных затрат от App Economy Insights.

👍1

2 Nov 2026, 17:01 UTC≈1,340 viewsread 5 November 2026

Райан Лоу вводит понятие headless content — контент, созданный исключительно для ботов ИИ с целью влияния на ответы. Похоже, нас ждет мир, где крупные бренды будут поддерживать библиотеку контента без графического интерфейса, которая будет автоматически обновляться, проверяться на точность и систематически обогащаться новыми данными и исследованиями (вероятно, кем-то, кого называют контент-инженером).

1 Nov 2026, 06:15 UTC≈1,460 viewsread 5 November 2026

Гугл тоже планирует присоединиться к инициативе IETF.

31 Oct 2026, 08:41 UTC≈1,540 views7 reactionsread 5 November 2026

Bing вводит раздельное управление использованием контента для обучения (AI training) и заземления (AI grounding) Обучение можно заблокировать через robots.txt либо мета-теги/http-заголовки на уровне страницы; заземление — только через мета-теги/http-заголовки. Настройки начнут учитываться с 1 февраля 2027 г. На обычные результаты поиска (без ИИ-фич) это не повлияет.

👍4😁2❤1

30 Oct 2026, 13:12 UTC≈1,590 views1 reactionsread 5 November 2026
Forwarded from @sealytics

Еще интересного от Resoneo – разбор системы Google BotGuard, "отравляющей" результаты поиска для парсеров. Если парсер ведет себя не как браузер, то он получает не то, что получает браузер.

😨1

30 Oct 2026, 09:04 UTC≈1,790 views4 reactionsread 5 November 2026
Photo

Филипп Шиндлер, старший вице-президент и главный коммерческий директор Google, заявил, что реклама в режиме ИИ имеет «более низкую монетизацию», чем реклама в традиционном поиске. «Значительный рост запросов в режиме ИИ оказал влияние из-за более низкой монетизации, которую мы наблюдали в этом режиме» — сказал Филипп Шиндлер во время телефонной конференции по итогам отчетного периода. Акции Alphabet пережили сильней…

❤3💯1

30 Oct 2026, 08:16 UTC≈1,520 views11 reactionsread 5 November 2026
File

В компании «Ашманов и партнеры» подвели итоги полутора лет наблюдений за Алисой AI Лаборатория поискового продвижения «Ашманов и партнеры» под руководством Михаила Воловича следит за «поиском с Алисой» с самого его запуска. Недавно вышла третья часть цикла — она подводит итог первым двум и показывает, что произошло с коммерческой выдачей за год. Исследование получилось объемным, поэтому коллеги собрали краткую верс…

😁8🔥2❤1

Showing the 12 most recent of 45 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.

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.

Posts edited after publishing

@notjohnmu edited 1 post 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
5 November 2026
Most recent edit
5 November 2026

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.

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.

R2B
@reg2bet · 26,360
Telegram ranks this channel #39 of 75 here — alongside 74 others — read 15 September 2026
SEO HR, digital-вакансии, офис и удалёнка
@seohr · 25,187
Telegram ranks this channel #41 of 92 here — alongside 91 others — read 15 September 2026
iGamingNews
@igaming_news · 21,529
Telegram ranks this channel #55 of 71 here — alongside 70 others — read 27 September 2026
Яндекс про аналитику
@YAN_analytic · 20,922
Telegram ranks this channel #72 of 98 here — alongside 97 others — read 25 September 2026
DIGITAL Tender / freelance / фриланс
@digitaltender · 21,106
Telegram ranks this channel #73 of 90 here — alongside 89 others — read 28 September 2026

This channel appears in 5 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 8 November 2026 — this entry's latest reading, not the date you are reading this.

“noindex, nofollow” (@notjohnmu), 5,973 subscribers as measured 8 November 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.