🫢 Лол: бывший сотрудник Google выкупил целый билборд, чтобы прорекламировать сервис, который работает на ИИ… но на самом деле за каждым ответом сидит он сам. Проект задумывался как сатира на людей, которые безоговорочно доверяют нейросетям. Пользователь думает, что общается с искусственным интеллектом, а в действительности все сообщения вручную пишет создатель сервиса. Самое забавное — если его просят сгенерировать…

Channel
Кодерские хаки
@techhacknfeature
On this record: Growth · Engagement · What this channel posts · Reactions · Advertising · Posts · Citations · Cite this entry
3,547subscribers
+336 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
Register entry
| Telegram ID | -1001834325041 |
|---|---|
| Type | Channel |
| Username | @techhacknfeature |
| Created | Between 1 October 2022 and 30 September 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 27 August 2026 |
| Measurements held | 9 |
| Confirmed unchanged | 1 time, most recently 27 August 2026 |
| On Telegram | t.me/techhacknfeature |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 27 Aug 2026, 03:17 | 3,547 | -14 |
| 24 Aug 2026, 11:14 | 3,561 | +126 |
| 20 Aug 2026, 21:36 | 3,435 | +42 |
| 18 Aug 2026, 01:42 | 3,393 | -33 |
| 14 Aug 2026, 19:56 | 3,426 | +114 |
| 11 Aug 2026, 00:47 | 3,312 | +103 |
| 7 Aug 2026, 23:16 | 3,209 | -2 |
| 7 Aug 2026, 20:02 | 3,211 | no change |
| 7 Aug 2026, 19:03 | 3,211 | first reading |
Engagement
20 posts held, back to 4 August 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 pageof Telegram’s post history, 20 posts per page.
- ERR · 30 days
- 5.81%
- avg views ÷ 3,547 subscribers
- Avg views / post
- 206
- 20 posts measured
- Reaction rate
- 0.919%
- reactions ÷ views · ER floor
- Posts in window
- 20
- of 20 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 8 of 20 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 7 August 2026 |
|---|---|
| Posts held | 20 (4 August 2026 – 7 August 2026) |
| Views total | 4,122 |
| Reactions total | 21 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 7 Aug 2026, 20:02 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
- 2m 06s
- Average length
- 25s
Measured directly from 5 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
21 reactions across 8 posts, in 8 distinct kinds. The most used accounts for 38.1% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 8 | 38.1% | |
| 😢 | 5 | 23.8% | |
| 🎃 | 2 | 9.52% | |
| 👏 | 2 | 9.52% | |
| 🍌 | 1 | 4.76% | |
| 🎄 | 1 | 4.76% | |
| 🏆 | 1 | 4.76% | |
| 👻 | 1 | 4.76% |
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 8 of the 20 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 21reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 20 most recent posts we hold, published 4 August 2026 to 7 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.
Advertising
- Ad load
- 20.0%
- 4 of 20 posts carry an ad marker
- Regulatory tokens
- 0
- none — marked by hashtag only
- Median views · ads
- 337
- over 4 measured posts
- Median views · rest
- 71.0
- over 16 measured posts
An ad marker, not a judgement about a post. A post is counted here because it carries one of two explicit markings: an erid token, which Russian law has required on paid placements since 2022 and which is issued against a specific advertising contract, or a #реклама / #ad hashtag in the body, which is the channel declaring it itself. The first is documentary; the second is a self-declaration and is weaker. No classifier reads the text and decides — nothing on this site guesses that a post is an advertisement.
This is a floor, and it can only ever be a floor.A channel that runs paid placements without marking them produces no marker for us to count, and an unmarked ad is indistinguishable from an ordinary post on the public surface. The ad load above therefore means “the share of posts that declared themselves”, never “the share of posts that were paid for”. A low figure is not evidence of a channel that runs few ads.
Both figures are medians, and no ratio between them is published. Each is a view reading that actually occurred on a post, picked by percentile_disc rather than averaged, so one viral post cannot move it and no interpolated value is invented between two readings. The sample on one side is under five posts, which is too thin to compare. The two figures are shown side by side with the count behind each, and deliberately not divided into a headline like “ads get x% fewer views” — an arithmetic that is easy to print and, at this sample size, means nothing.
Measured over the 20 most recent posts we hold, published 4 August 2026 to 7 August 2026. Views are the latest single reading held for each post, and any reading at or above 1,000 is rounded by Telegram to three significant figures.
Recent posts
Эмодзи «📄» скрывает пасхалку Apple — внутри письмо от Джонни Эпплсида, прямой референс к кампании Think Different: Дорогая Кейт, За безумцев. За изгоев. За бунтарей. За нарушителей. За круглые колышки в квадратных отверстиях. За тех, кто видит иначе. Они не любят правила. Не уважают статус-кво. Их можно поносить или прославлять, но нельзя игнорировать — они меняют мир. Пока одни зовут их сумасшедшими, мы видим в ни…
⚡️ В пресс-службу президента на прямой трансляции поступают по-настоящему важные вопросы от народа. Кодерские хаки
🌴 Ловите сайт, который превращает слова в миры. Просто вводите, что хотите увидеть — и через пару секунд на экране появляется ваша собственная локация: город будущего, лес с неоном или пляж на Марсе. Сервис только запустился, так что пока можно играться БЕСПЛАТНО. Тестим — тут Кодерские хаки
🥲 Эйчары… такие эйчары. Кодерские хаки
Телеграм канал AI для бизнеса AI - не будущее. Это настоящее вашего бизнеса. Телеграм-канал "AI для бизнеса" знает все о внедрении и использовании искусственного интеллекта в бизнесе в России и мира. Только со своими подписчиками канал делится: - как внедрить искусственный интеллект в реальные бизнес-процессы, - разборами кейсов: как компании сократили затраты на 30-50% с помощью AI, - лайфхаками по автоматизации р…
Человечеству пришлось пройти через миллионы лет эволюции… чтобы в итоге перейти на следующий уровень одним запросом в ChatGPT 😁 Кодерские хаки
🍌1
🔥 Веб-дизы, ловите годную находку: нашли мощную тулзу, которая за пару секунд парсит дизайн-систему любого сайта. Dembrandt вытаскивает буквально все: цвета, шрифты, отступы, компоненты, макеты и другие элементы интерфейса. Достаточно вставить ссылку на сайт — сервис автоматически сгенерирует готовую дизайн-систему в формате design.md. Забираем — тут Кодерские хаки
🫢 Оставить голосовой чат между двумя чатами ChatGPT открытым было большой ошибкой… Кодерские хаки
🎄1
⚡️ Telegram исчез из App Store — но вскоре вернулся. Несколько часов назад мессенджер пропал из поиска App Store, а при переходе по прямой ссылке пользователи видели сообщение об ошибке. По данным Telegram, причиной стали материалы, нарушающие правила площадки. После их оперативного удаления и блокировки аккаунта, который их распространял, приложение вновь стало доступно в App Store. На фоне происходящего команда …
🎬 Будь в курсе всех эксклюзивных новостей! Хочешь знать, что происходит за кулисами индустрии шоу-бизнеса? Наш канал — это источник самых свежих инсайдов и эксклюзивных новостей, которые ты не найдешь в открытых источниках. 🔥 Подписывайся, чтобы быть первым, кто узнает секреты!
Зарабатывайте на установках Яндекс Браузера Партнёрская программа для сервисных центров, магазинов компьютерной техники, сайтов для скачивания файлов и авторов статей. Вы можете предлагать его своим клиентам и аудитории — и зарабатывать на новых установках. Выплаты до 500₽ за каждую установку Яндекс Браузера. Подать заявку #реклама 0+ partner.browser.yandex.ru Кодерские хаки
Showing the 12 most recent of 20 posts we hold for @techhacknfeature. 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 — 209,933 of 1,623,166entries 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.
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.
Names
Channels on the register whose handles appear in this channel's posts.
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 27 August 2026 — this entry's latest reading, not the date you are reading this.
“Кодерские хаки” (@techhacknfeature), 3,547 subscribers as measured 27 August 2026. Telegram Register, tgregister.com/channel/techhacknfeature.
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.