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
64 measurements spanning 102 days, net -609. 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 13,878–14,669 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 64
Measured (UTC)
Subscribers
Change
16 Nov 2026, 06:56
13,969
-23
12 Nov 2026, 19:29
13,992
-20
10 Nov 2026, 11:45
14,012
+1
8 Nov 2026, 22:57
14,011
-2
7 Nov 2026, 15:20
14,013
-9
6 Nov 2026, 13:26
14,022
-15
5 Nov 2026, 11:24
14,037
-11
4 Nov 2026, 08:01
14,048
-8
3 Nov 2026, 08:59
14,056
-13
2 Nov 2026, 12:10
14,069
-1
1 Nov 2026, 14:44
14,070
-7
31 Oct 2026, 15:11
14,077
-5
30 Oct 2026, 14:54
14,082
-12
29 Oct 2026, 16:26
14,094
-18
28 Oct 2026, 13:19
14,112
-4
27 Oct 2026, 11:47
14,116
-2
26 Oct 2026, 10:46
14,118
-8
25 Oct 2026, 08:44
14,126
-6
24 Oct 2026, 09:56
14,132
-10
23 Oct 2026, 08:41
14,142
first reading
Engagement
83 posts held, back to 22 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 80 pages of Telegram’s post history, 20 posts per page.
ERR · 30 days
10.5%
avg views ÷ 13,969 subscribers
Avg views / post
1,460
32 posts measured
Reaction rate
0.817%
reactions ÷ views · ER floor
Posts in window
32
of 83 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 31 of 32 measured posts that carry a reaction reading, and over those same posts' views.
What these figures were computed from
Window
Rolling 30 days · latest post in window 16 November 2026
Posts held
83 (22 July 2026 – 16 November 2026)
Views total
46,821
Reactions total
370
Forwards / comments
not exposed by the public surface — not measured, not estimated
Readings taken
17 Nov 2026, 08:36 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
≈1,100
Videos
≈129
Links
≈162
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
4m 35s
Average length
20s
Measured directly from 14 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.
Reaction mix
1,061 reactions across 81 posts, in 10 distinct kinds. The most used accounts for 56.9% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
custom 5235626762309760324
604
56.9%
🥰
125
11.8%
👾
111
10.5%
🤬
63
5.94%
🤷♂
59
5.56%
🫡
41
3.86%
👨💻
28
2.64%
🗿
21
1.98%
🤷♀
5
0.471%
👎
4
0.377%
Custom emoji. One row above is a Telegram custom emoji, which the public preview renders as an element carrying only a numeric id — no character, and no image we can reach. The id is printed as-is rather than substituted with a look-alike glyph, because a stand-in would be our invention showing where a measurement should be. The count beside it is Telegram’s.
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 82 of the 83 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 1,061 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 83 most recent posts we hold, published 22 July 2026 to 16 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
2
across the posts below
Posts paid on
2
of 83 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 @promty_tochka. 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 83 most recent posts we hold for this entry, published 22 July 2026 to 16 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: 2 of 32 posts held from the last 30 days (6.25%) 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).
💀 Пал последний оплот халявного ИИ — DeepSeek вводит лимиты..
Ну вот и всё, приплыли. Китайская нейронка, которая всё это время оставалась безлимитной и бесплатной, тоже начинает закручивать гайки.
Причём ограничения уже появляются и в приложении, и в веб-версии.
Что изменилось:
— Дневные лимиты. Теперь количество запросов ограничено. Когда квота заканчивается, DeepSeek сообщает о перегрузке серверов и перестаёт о…
👀 Сделал моушн-анимацию в Google 4 Hydrogen: буквально за 2 минуты и по одному простому промту.
Бесплатно! Получается всё, подписка на Клод больше не нужна?
💥 Google наконец-то обновила обшарпанную Gemini 3.6 Flash — вышла Gemini 4 Hydrogen!
Причём Google отказалась от привычного названия Flash. Теперь быстрая модель называется Hydrogen, а старшие — Carbon и Argon.
Что интересного обещают:
1. Скорость. Hydrogen выполняет задачи в 2,5 раза быстрее предыдущей Flash. По крайней мере, в тестах Google.
2. Меньше галлюцинаций. По заявлениям разработчиков, модель стала в 5 …
💥 Бум! Яндекс добавил ИИ-агентов в Алису!
Новый режим называется «Действуй!». Теперь Алисе можно поручить целую задачу, а она сама разберётся, что и в какой последовательности нужно сделать.
Что интересного заявили:
1. Телефонные звонки. Алиса может сама позвонить в ресторан, клинику или другую организацию, уточнить условия и договориться о записи.
2. Работа с сайтами. У агента есть собственный облачный браузер. …
😬 Anthropic полностью перекрывает доступ к Claude для ИТ-команд, связанных с РФ.
С 12 ноября вступают в силу новые правила. Юристы компании убрали все лазейки для обхода санкций.
Что запретили:
❌ Релокантам из компаний РФ — бан. Если бизнес зарегистрирован в России, сотрудникам нельзя использовать Claude. Даже если они живут в Грузии, Казахстане, Сербии или ЕС.
❌ Работать из России на зарубежный бизнес — бан. Есл…
💥 Не прошло и пары часов, а у нас уже есть новая ИИ-модель. Alibaba выкатила Qwen 4!
Пока доступна только предварительная версия Qwen4-Max Preview. Попробовать можно в чате Qwen, приложении и агенте QwenWork, о котором я уже здесь писал.
Что интересного:
1. Контекст — миллион токенов. Причём до 393 тысяч токенов модель может потратить на размышления и генерацию ответа. Это почти в три раза больше, чем у предыдущей…
🤔 Поймал себя на мысли, что выход новых ИИ-моделей уже не вызывает прежнего ажиотажа.
В понедельник Anthropic выпустила Claude Fable 5.2, а вчера Google открыла доступ к Gemini 4 Carbon.
И вроде бы нейронки становятся мощнее, решают всё более сложные задачи, пишут приложения по запросу, создают игры, 3D-модели и прочее.
Но вау-эффекта больше нет..
Ещё год назад мы удивлялись тому, что ИИ мог сгенерировать ту карт…
💥 Gemini 4 Carbon вышел из закрытого теста.
Это самая сильная модель Google на сегодня. Её делали для сложного: большие задачи в кодинге, глубокий анализ, научные исследования.
Что нового:
— Carbon уже в приложении Gemini, AI Mode и Antigravity (для подписчиков AI Ultra).
— В Antigravity появилась / swarm: один промт запускает команду агентов, и ты видишь их работу в реальном времени.
— В AI Studio и Gemini API …
🤖 Как убрать ИИ-шность из сайтов, созданных через вайбкодинг?
У сайтов, созданных с помощью ИИ, часто одна проблема — они подозрительно похожи друг на друга. Фиолетовые градиенты, свечение на кнопках, эмодзи вместо иконок, кричащие заголовки и прочие признаки нейрослопа.
На GitHub набирает популярность скилл Unslop — у него уже больше 13 тысяч звёзд. Он берёт интерфейс, сгенерированный нейронкой, и переделывает его…
💥 Anthropic выпустила Claude Fable 5.2 и Mythos 5.2.
Главное улучшение — новая Fable стала лучше справляться с большими и сложными задачами, которые требуют длительной работы.
То есть теперь можно поручить нейронке целый проект. Она сама разбивает его на подзадачи, распределяет работу между ИИ-агентами, контролирует выполнение и последовательно движется к результату.
Причём работать так модель может часами и даже …
🧑💻 Perplexity запустила функцию «Коллеги» — теперь можно создать себе целую команду из ИИ-сотрудников.
Как это работает?
Вы создаёте Коллегу, назначаете ему роль, описываете обязанности и подключаете нужные сервисы. Дальше агент сам планирует работу, выполняет задачи и обращается к вам, когда нужно что-то согласовать.
Каких сотрудников можно сделать:
1. Маркетинг и SMM. Агент занимается постами для соцсетей, SEO…
🎬 Google выпустила Gemini Omni 1.2 Flash — обновлённую ИИ-модель для генерации видео.
Что нового:
1. Клипы от 3 до 15 секунд, их можно и генерировать, и редактировать.
2. Плавные сквозные кадры и более естественные диалоги нескольких говорящих.
3. Правки прямо в чате: меняете фон, героя или свет шаг за шагом.
4. Стоимость ниже на 30%: черновик в 360p или 720p стоит $0,07 за секунду, потом можно апскейлить до 108…
custom 523562676230976032410🥰3👨💻1
Showing the 12 most recent of 83 posts we hold for @promty_tochka. 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.
Forward network
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
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 1 registered channel — 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.
Named by
Channels on the register whose posts name this channel's handle.
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 November 2026 — this
entry's latest reading, not the date you are reading this.
“Промты — и точка” (@promty_tochka), 13,969 subscribers as measured 16 November 2026. Telegram Register, tgregister.com/channel/promty_tochka.
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.