Telegram RegisterThe public register of Telegram
Telegram profile photo for ИИ на практике у Олега Волкова

Channel

ИИ на практике у Олега Волкова

@volkovproai

On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Cite this entry

53subscribers

+1 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1003866394257
TypeChannel
Username@volkovproai
Created10 March 2026 — measured — dated from the channel’s first post
First recorded10 August 2026
Last confirmed live8 October 2026
Measurements held5
Confirmed unchanged1 time, most recently 8 October 2026
On Telegramt.me/volkovproai

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 29 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 why it has no browse page of its own yet.

Growth

5254537 August 2026 — 52 subscribers10 August 2026 — 52 subscribers15 August 2026 — 53 subscribers30 August 2026 — 54 subscribers8 October 2026 — 53 subscribers7 August 20268 October 2026
5 measurements spanning 61 days, net +1. 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 52–54 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
8 Oct 2026, 05:4153-1
30 Aug 2026, 13:1454+1
15 Aug 2026, 20:0753+1
10 Aug 2026, 10:1652no change
7 Aug 2026, 18:5352first reading

Engagement

9 posts held, back to 10 March 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 1 page of 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 9 posts for this entry, the most recent from 5 June 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Video runtime
3m 06s
Average length
3m 06s

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

27 reactions across 6 posts, in 4 distinct kinds. The most used accounts for 44.4% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤1244.4%
🔥933.3%
👍518.5%
💯13.70%

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

Measured over the 9 most recent posts we hold, published 10 March 2026 to 5 June 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

12 May 2026, 20:37 UTC158 views8 reactionsread 10 August 2026

Сегодня пошел учится. Очно. Раз в неделю буду ездить в Мск в Т-банк на лекции по созданию ML продукта. Два тезиса. 1. Хочу больше глубины в устройстве ИИ решений. Сейчас больше на пользовательском уровне понимание. Хочу понять как думают коллеги про ИИ, которые на самом острие внедрения в Бигтехе. 2. Сказали, что конкурс был 10 человек на место. Я вспомнил как сдавал экзамены в универ и где отдельным стрессом было зн…

👍4🔥3💯1

31 Mar 2026, 10:08 UTC206 views2 reactionsread 10 August 2026

Достиг сегодня следующего уровня "зрелости" своей Ai операционной системы - поставил на Mac локальную модель Ollama. Она маленькая и быстрая. Делает одно: после каждого моего сообщения смотрит на пару «ответ Клода → моя реакция» и тихо фиксирует оценку. Я просто работаю — система наблюдает. Через неделю-две у системы должна быть реальная картина: что работает именно для меня. Клод начинает каждую сессию уже зная это.…

🔥2

16 Mar 2026, 16:40 UTC212 views4 reactionsread 10 August 2026

Два месяца с AI. Сегодня — про личное. Но сначала — почему не ChatGPT. Пользовался ChatGPT. Открывал вкладку, задавал вопрос, получал ответ, закрывал. Каждый раз с нуля. Он не знает, кто я. Не видит мои большой контекст. Не помнит моих целей. Качество ответа сложно контролируемо — и нет возможности выставить узкоспециализированных агентов, которые работают в конкретном контексте. Это хороший чат — но не ассистент. …

🔥3👍1

10 Mar 2026, 10:12 UTC209 views5 reactionsread 10 August 2026

Я работаю с ИИ 8 часов в день. И именно это стало проблемой. Недавно общался с Лёшей. Лёша — коллега по цеху, занимается развитием ИТ-продуктов. Он хочет собрать популярные ИИ skills в отдельный продукт и предложить рынку. Моя первая реакция: «Ну это же просто. Агент + шаблон — и готово. Плюс огромное кол-во уже готовых skills выкладывают пользователи». Он говорит: «Для большинства это чёрный ящик». Уже после раз…

❤4🔥1

10 Mar 2026, 08:46 UTC174 views3 reactionsread 10 August 2026

Привет. Я Олег Волков. По профессии — продакт-менеджер. Сейчас работаю консультантом: помогаю компаниям выстраивать продукт, маркетинг и продажи. Последние несколько месяцев активно встраиваю ИИ во всё, чем занимаюсь — в рабочие процессы, в продуктовые задачи, в повседневные дела. И понял, что хочу это фиксировать. Этот канал — про реальный опыт, не теорию. Что пробовал. Что сработало. Что нет. Какие проекты делаю…

❤3

Showing the 9 most recent of 9 posts we hold for @volkovproai. 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.

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

“ИИ на практике у Олега Волкова” (@volkovproai), 53 subscribers as measured 8 October 2026. Telegram Register, tgregister.com/channel/volkovproai.

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.