Telegram RegisterThe public register of Telegram

Channel

AI и грабли

@oestick

2 usernames

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

13,097subscribers

+87 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of 10,000–31,623.

Register entry

Telegram ID-1001741956568
TypeChannel
Usernames@ai_grably @oestick
DescriptionСтроил HR продукты для американского бигтеха. Внедряю AI в бизнес, пишу про свои ошибки и находки Co-founder https://entropy.talk и https://grably.tech @nikolay_sheyko
CreatedBetween 1 December 2021 and 31 March 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live12 August 2026
Measurements held15
Confirmed unchanged1 time, most recently 12 August 2026
On Telegramt.me/oestick

Growth

13,00613,09713,051.56 August 2026 — 13,010 subscribers6 August 2026 — 13,010 subscribers6 August 2026 — 13,006 subscribers6 August 2026 — 13,006 subscribers7 August 2026 — 13,011 subscribers7 August 2026 — 13,011 subscribers8 August 2026 — 13,041 subscribers8 August 2026 — 13,054 subscribers9 August 2026 — 13,089 subscribers9 August 2026 — 13,086 subscribers10 August 2026 — 13,086 subscribers10 August 2026 — 13,084 subscribers11 August 2026 — 13,086 subscribers12 August 2026 — 13,088 subscribers12 August 2026 — 13,097 subscribers6 August 202612 August 2026
15 measurements spanning 7 days, net +87. 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 12,992–13,111 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
12 Aug 2026, 19:3313,097+9
12 Aug 2026, 13:3413,088+2
11 Aug 2026, 19:0213,086+2
10 Aug 2026, 19:1213,084-2
10 Aug 2026, 14:2313,086no change
9 Aug 2026, 15:1113,086-3
9 Aug 2026, 12:3213,089+35
8 Aug 2026, 12:4213,054+13
8 Aug 2026, 10:5613,041+30
7 Aug 2026, 13:5013,011no change
7 Aug 2026, 11:3013,011+5
6 Aug 2026, 13:1013,006no change
6 Aug 2026, 13:0813,006-4
6 Aug 2026, 04:3013,010no change
6 Aug 2026, 04:2313,010first reading

Engagement

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

ERR · 30 days
44.9%
avg views ÷ 13,097 subscribers
Avg views / post
5,880
9 posts measured
Reaction rate
1.02%
reactions ÷ views · ER floor
Posts in window
9
of 16 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.

What these figures were computed from
WindowRolling 30 days · latest post in window 8 August 2026
Posts held16 (20 June 20268 August 2026)
Views total52,960
Reactions total538
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken13 Aug 2026, 02:52 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
193
Videos
22
Links
244

Lifetime counters from Telegram’s own channel header, read 13 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.

Video runtime
1m 31s
Average length
1m 31s

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

767 reactions across 13 posts, in 20 distinct kinds. The most used accounts for 34.8% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🔥26734.8%
24131.4%
👍9912.9%
🤣547.04%
😁476.13%
💯222.87%
🌚91.17%
🤡91.17%
🏆30.391%
🤔30.391%
🎉20.261%
👏20.261%
🥱20.261%
❤‍🔥10.13%
🌭10.13%
🐳10.13%
💩10.13%
🤨10.13%
🤯10.13%
🫡10.13%

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

Measured over the 16 most recent posts we hold, published 20 June 2026 to 8 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.

Telegram Stars

Stars received
4
across the posts below
Posts paid on
1
of 16 we hold a reading for · 6%
Most on one post
4
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @oestick. 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 16 most recent posts we hold for this entry, published 20 June 2026 to 8 August 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

8 Aug 2026, 09:06 UTC≈4,960 views66 reactionsread 13 August 2026
Video

Вышел первый серьезный подкаст со мной Получилось очень живо и плотно по темам. Обсуждали скиллы, безопасность и сложности внедрения в компании Классно, что получилось обсудить много микро-деталей, которые обычно не влезают в тг посты. На чилловый просмотр под пиво/чай/прогулку – самое оно 00:01:47 - Бизнесу часто не нужен отдельный кастомный AI-продукт 00:16:56 - Люди не могут рассказать, как именно делают свою р

🔥4017👍8🤡1

7 Aug 2026, 12:34 UTC≈3,750 views55 reactionsread 13 August 2026
Photo

Один из самых секси кейсов с нашего марафона по агентам – создание рабочих веб аппок с бэкендом на гугл таблицах и деплоем в одну строку без гитхабов, докеров, vps Ребятам, которые не хотят заморачиваться с техничкой – очень нравится. Большинство сразу нашли где это использовать в своей работе Так вот, теперь не нужно использовать внешние сервисы – openai встроили такую штуку к себе в codex Причем реализация очень

🔥309🤣7👍4🤡4🤔1

6 Aug 2026, 11:28 UTC≈3,750 views28 reactionsread 13 August 2026

Найм, соревы и бабки Одна из самых важных задач реального мира – уметь различать людей, которые что-то реально из себя представляет и тех, кто только пытается такими казаться. Причем, важно и в отношениях, и в дружбе, и в работе И особенно важно понимать, к какой категории относишься сам и как можешь это подтвердить Что забавно – многие хорошие на первый взгляд "метрики", на самом деле почти не работают. Например,

🔥148🌚5🌭1

6 Aug 2026, 09:31 UTC≈2,650 views65 reactionsread 13 August 2026
Forwarded from @sergeinotevskii

Сижу в лобби отеля, за соседним столом сидят мужики, пьют беленькую, закусывают. Спорят громко. Прислушался. «Петрович, да этих сеток тьма! Маленькие, большие! Для классификации какие хочешь! Можем у себя даже большие развернуть! Главное чтобы электричества хватило!» Думаю: нифига себе адопшн у АИ! Слушаю дальше: «Фракции…булыжники…тонны… золото…». Понимаю что не адопшн, апрофдеформация.

😁47🤣16❤‍🔥1🥱1

30 Jul 2026, 15:34 UTC≈5,970 views43 reactionsread 13 August 2026
Photo

Никто не делится факапами Выступал недавно на оффлайн конфе в Омске. Организация и доклады по качеству лучше чем на многих столичных конфах Но что меня бесит вообще на любой из них – это что обычно все рассказывают истории успеха, а они почти всегда бесполезны – их сложно переложить на реальность вашей конкретной компании и команды А если слепо повторять все действия, то это будет просто карго культ как у абориген

25🔥9👍6💯2💩1

29 Jul 2026, 09:53 UTC≈5,290 views35 reactionsread 13 August 2026
Photo

Из новых не особо документированных изменений в codex агент теперь сам может ходить в соседние диалоги и даже писать в них. ↑ Это не про субагентов, это прям полноценные чаты Пока не придумал, как это прям эффективно использовать, но знаю, что позиционируется как одна из фишек нового голосового режима – голосом можно управлять всеми своими текущими чатами Кто уже пользуется, накидайте в комментах кейсы, пожалуйста

🔥312👍2

28 Jul 2026, 09:50 UTC≈14,400 views140 reactionsread 13 August 2026

Все, с выходом Fable и 5.6 sol вы больше не должны понимать, что происходит у вас в коде. Не до всех еще дошло, но вы больше не software engineer, вы loop engineer ↑ Я думал, что это типичный твиттер шитпостинга, но реально начал видеть вокруг себя серьезных людей, кто так считает. Мол, раз у Бориса в антропике получается, то и мы так должны делать Ну камон, ребят. Все же понимают, что публичные лица компаний, кото

69👍49🔥12🌚4🤡4🤣2

27 Jul 2026, 11:31 UTC≈5,530 views28 reactionsread 13 August 2026
Photo

Разбор кейса с поиском работы В начале лета я запостил тут всратый пост про набор на марафон в последний день этого самого набора 🤡 Это было странно, но я стараюсь перебарывать перфекционизм и запускать штуки как можно быстрее, чтобы замыкать свой собственный feedback loop, а не пытаться все заранее отполировать (чтобы все равно обнаружить, что реальность сложнее, чем можно предположить) Так вот, тот марафон оказ

15🔥8🎉2👍1🤔1🤨1

18 Jul 2026, 15:24 UTC≈6,660 views78 reactionsread 13 August 2026

Несуществующие агенты для аудио В последнее время много работаю с генерацией аудио. И удивляет, что в основном аудио пайплайны собираются в условном comfy – визуальном блочном редакторе. Удивляет, потому что это как писать код пайплайном в n8n вместо клода/кодекса Основная проблема тут – нет полноценного агентного цикла, где модель видит, а точнее слышит, результаты предыдущих действий и может сама выбирать что с э

37🔥24👍14👏2🤯1

13 Jul 2026, 14:12 UTC≈7,660 views44 reactions4 Starsread 13 August 2026

Хз как люди пользуются OpenRouter По дурости тестили на нем систему, которая на локалках должна будет работать в контуре клиента, и это такая боль: - низкие лимиты у провайдеров - хрен пойми у кого реально есть поддержка structured output, даже если заявлено - а у кого есть, часто некорректная – натолкнулся на имплементацию с сортировкой ключей в алфавитном порядке 🥴 - нет моделей в целевом кванте - в какой-то моме

🔥34👍81🫡1

3 Jul 2026, 07:31 UTC≈9,360 views39 reactionsread 13 August 2026
Photo

Нужен GUI агент для опенсорсных моделей? Пока нет ничего лучше OpenCode. Шутка. Z.ai сделали не только топовую опенсорсную модель, но и свой гуи агент ZCode – клон Codex App Но codex работает по дефолту только с Responses API (который никто кроме OpenAI нормально не поддерживает). А ZCode нативно поддерживает кастомные эндпоинты всех трех типов (chat.completions, responses, anthropic) Управление с мобилки тоже ес

🔥306👍3

2 Jul 2026, 10:00 UTC≈8,120 views99 reactionsread 13 August 2026

Байки с полей Сгонял в конце прошлой недели на Conversations, сейчас расскажу, что было интересного, а что полезного Ну во первых, был очень рад контингенту на конфе – развиртуализовался с кучей селеб нашего ИИ-пузыря – от Ромы Куцева из llmarena и vsellm до Ярослава Шмулева из R77, попил пива с шашлыками у Валеры Ковальского и покатался на тачке Глеба Кудрявцева Но мы же на такие конфы не за этим ездим? Вернее не

46🤣29🔥21🏆3

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

Citation-graph rank

Citation-graph rank — 106,469 of 1,151,006entries 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

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

“AI и грабли” (@oestick), 13,097 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/oestick.

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.