11 measurements spanning 29 days, net -20. 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 2,088–2,116 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)
Subscribers
Change
5 Sept 2026, 09:00
2,091
-6
1 Sept 2026, 03:15
2,097
-3
29 Aug 2026, 06:11
2,100
-2
26 Aug 2026, 09:54
2,102
-4
23 Aug 2026, 07:02
2,106
-2
20 Aug 2026, 03:51
2,108
-1
17 Aug 2026, 12:46
2,109
-4
14 Aug 2026, 03:08
2,113
+1
10 Aug 2026, 23:17
2,112
+1
7 Aug 2026, 20:31
2,111
no change
7 Aug 2026, 19:04
2,111
first reading
Engagement
20 posts held, back to 2 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 20 posts for this entry, the most recent from 23 May 2026. An engagement rate over an empty window would be a number about nothing.
What this channel posts
Video runtime
13s
Average length
13s
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
611 reactions across 20 posts, in 20 distinct kinds. The most used accounts for 33.4% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
🔥
204
33.4%
👍
119
19.5%
😁
66
10.8%
❤
65
10.6%
🤡
55
9.00%
custom 5368763653199765779
28
4.58%
custom 5460932315637095493
23
3.76%
custom 5269341602748309406
13
2.13%
🤣
9
1.47%
👎
7
1.15%
💯
5
0.818%
😱
5
0.818%
👏
4
0.655%
🥰
2
0.327%
custom 5386535377467094223
1
0.164%
🎉
1
0.164%
😎
1
0.164%
😢
1
0.164%
🤨
1
0.164%
🥴
1
0.164%
Custom emoji. 4 of the rows above are 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 counts beside them are 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 20 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 611 reactions 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 2 March 2026 to 23 May 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
8
across the posts below
Posts paid on
4
of 20 we hold a reading for · 20%
Most on one post
5
single highest reading
A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @kakieToYroki. 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 20 most recent posts we hold for this entry, published 2 March 2026 to 23 May 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.
🚀 No-Vary-Search - улучшаем кэш браузера
Есть страница товара: /product/123
А пользователи из-за маркетологов приходят на неё из разных источников:
/product/123?utm_source=google
/product/123?utm_source=telegram
/product/123?fbclid=abc
/product/123?gclid=xyz
Для аналитики это полезно. Но для страницы товара это ведь один и тот же HTML.
🆕 И тут помогает новый HTTP header: No-Vary-Search (который работает пока …
💅 Начался опрос State of CSS 2026
Если скучно, то можете на вопросики поотвечать, а заодно, пока заполняешь анкету, 100% наткнешься на новые для себя свойства и селекторы, о которых даже не слышал. Проведешь время с пользой 🙃
Источник: https://survey.devographics.com/en-US/survey/state-of-css/2026
#новости
🤨 Теперь NextJS
Чота много последнее время взламывать начали. Новость старая, но мб вы пропустили (как пропустил я 🥲)
В NextJS обнаружили серьёзную уязвимость за всю его историю
Затронуты версии: 13.4.13+, 14.x, 15.x и 16.0.0–16.2.4
Злоумышленники могут получить доступ к вашим внутренним сервисам, админкам, api ключам
‼️Обновитесь до 15.5.18 или 16.2.6
Источник: https://github.com/vercel/next.js/security/advisor…
Если вдруг используете приложение из 3х букв и надоело его включать/выключать, то горячо рекомендую включить роутинг
1 кнопка и проблема решена (выбирайте пункт "Быстрая установка" и не заморачивайтесь)
https://github.com/hydraponique/roscomvpn-routing
🫠 TanStack взломали
В npm-пакеты @tanstack/* попал вредоносный код нацеленный на кражу учётных данных и секретов из CI/CD-сред
Под ударом было 84 версии в 42 пакетах (`@tanstack/react-router`, @tanstack/router-*, итд)
Вредоносный код можно было словить при помощи обычного npm i
И скрипт мог попытаться украсть секреты из окружения. Что он искал:
• GitHub токены
• npm токены
• AWS ключи
• Vault токены
• Kubernetes s…
‼️ 3G в Chrome ненастоящий
Chrome плохо эмулирует медленную сеть. Из-за этого значения в DevTools могут быть хуже, чем на реальном девайсе с плохой сетью.
Почему?
Потому что реальный интернет работает через пакеты, а Chrome - упрощает всё до запросов.
В жизни:
• данные разбиваются на маленькие куски (пакеты)
• сервер может отправлять их с приоритетом (важное -> быстрее)
• часть пакетов может теряться и пересылатьс…
🙈 Axios взломали
В npm-пакет Axios попал вредоносный код - киберкотлеты взломали личный профиль одного из мейнтейнеров этого проекта и опубликовали от его имени вредоносные версии этой библиотеки.
Заражённые версии:
• 1.14.1
• 0.30.4
Внутри был не сам код axios, а зависимость plain-crypto-js, которая через postinstall ставила троян.
⏱️ Они прожили всего ~3 часа, но этого хватило, чтобы попасть в CI/CD и прод.
Есл…
🎉 Друзья, привет, я тут с анонсом
Очень много людей мне пишет про курс по NextJS, поэтому я решил опубликовать его в общий доступ
Если что, то он написан пока что только наполовину, но это уже около 10 часов видео контента и 40 вопросов
Курс полностью практический, то есть мы не затрагиваем сухую документацию, а пишем реальное приложение: клон YouTube. На скрине как раз то, как сейчас выглядит проект
Все 10 часов…
🥰 Vite 8
У Vite вышла новая мажорная версия
Из важного:
1. Новый бандлер Rolldown (Rust) - теперь единый пайплайн вместо Rollup + esbuild
2. Сильный буст скорости: до ~x10-30 на прод-сборке
3. Плагин для DevTools: https://devtools.vite.dev/
Источник: https://vite.dev/blog/announcing-vite8
#новости
🍭 Popover API или Dialog API?
Недавно же поповеры и диалоги вышли. А в чем разница? Какой и когда использовать?
Нашел тут статью, где можно об этой почитать
Коротко:
• Popover API - упрощает создание всплывающих элементов
• Dialog API - лучше подходит для модальных окон
P.S. В комментарии скинул сжатый перевод от ГПТ этой статьи на русском (хз насколько вам зайдет нейроперевод, но выглядит хорошо)
Источник: https…
👍13❤2
Showing the 12 most recent of 20 posts we hold for @kakieToYroki. 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.
Handles this channel named that no longer answer
Dead references
1
handles named in this channel’s posts, vacant today
Evidenced gone
0
we ourselves saw one of these resolve, at some point
Never seen alive
1
vacant every time we have ever looked
@kakieToYroki named 1 handle that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all. A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
Never seen alive
References a handle that is not a live channel — we have no record it ever was one.
@tanstack named in 1 post, 8 August 2026 – 8 August 2026
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 5 September 2026 — this
entry's latest reading, not the date you are reading this.
“Какие-то уроки [Frontend]” (@kakieToYroki), 2,091 subscribers as measured 5 September 2026. Telegram Register, tgregister.com/channel/kakieToYroki.
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.