2 measurements spanning 2 days. 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 55–57 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)
Subscribers
Change
10 Aug 2026, 07:46
56
no change
7 Aug 2026, 23:46
56
first reading
Engagement
20 posts held, back to 28 April 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 27 July 2026. An engagement rate over an empty window would be a number about nothing.
What this channel posts
Photos
53
Videos
2
Links
284
Lifetime counters from Telegram’s own channel header, read 10 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.
Reaction mix
102 reactions across 18 posts, in 15 distinct kinds. The most used accounts for 14.7% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
custom 5350459254203494168
15
14.7%
custom 5778602588068908846
12
11.8%
custom 6052951745884063266
12
11.8%
custom 6325524440801084490
12
11.8%
❤
11
10.8%
👏
9
8.82%
custom 6325806796246091512
7
6.86%
custom 6325713200318777460
6
5.88%
🔥
5
4.90%
😨
5
4.90%
😈
4
3.92%
⚡
1
0.98%
👍
1
0.98%
👨💻
1
0.98%
😭
1
0.98%
Custom emoji. 6 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 18 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 102 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 28 April 2026 to 27 July 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
3
across the posts below
Posts paid on
3
of 20 we hold a reading for · 15%
Most on one post
1
single highest reading
A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @taras_dot_one. 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 28 April 2026 to 27 July 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.
👩💻 Kubernetes теперь работает прямо в браузере. Потому что запускать Doom на всём подряд уже стало слишком просто 📺
Разработчик из ngrok написал Webernetes - частичный порт Kubernetes на TypeScript, который целиком запускается в браузере.
И это не Kubernetes, скомпилированный в WebAssembly. Автор перенёс и заново реализовал:
- kubelet и жизненный цикл подов
- scheduler и несколько Kubernetes-контроллеров
- Deploy…
⚡️TypeScript 7 вышел, главная фича релиза - скорость 😁
Чуть больше года назад Андерс Хейлсберг объявил, что Microsoft переписывает компилятор TypeScript с TypeScript на Go. И вот переписывание наконец закончилось: TypeScript 7 стал нативным, многопоточным и в среднем собирает большие проекты в 8–12 раз быстрее.
Например:
- VS Code: было 125, стало 10 секунд
- Sentry: было 140, стало 16 секунд
- Playwright: было 12…
🌳 Elm внезапно ожил 🤩
Спустя почти семь лет после Elm 0.19.1 вышла версия 0.19.2. Пока без изменений в самом языке, разработчики ускорили компилятор, уменьшили потребление памяти и количество работы для GC.
Похоже, спустя 14 лет после появления языка Elm всё-таки начал движение к версии 1.0.
Помню как мы с товарищами писали фронт на нем 13 лет назад, наслаждались дружелюбным компилятором, который не просто показыв…
⚡️ Vite 8.1 вышел, и они снова изобрёли webpack, но с хорошим DX.
Главная фича релиза: экспериментальный Bundled Dev Mode.
И тут забавный поворот сюжета.
Vite же изначально ворвался примерно с идеей: Зачем нам в dev бандлить всё в один огромный JS-файл, как в старые добрые времена webpack? У нас есть нативные ESM, браузер сам всё загрузит, стартуем мгновенно, грузим все модули для конкретной страницы, но для этого…
🐈 На выходных я сделал с помощью ИИ: M8 Search - поисковик по материалам про грувбокс Dirtywave M8.
Когда я начал изучать M8, быстро столкнулся с проблемой: полезной информации много, но она размазана по часовым YouTube-видео, документации, гайдам и заметкам комьюнити.
В одном ролике кто-то показывает работу с таблицами, в другом разбирает синтезаторы, в третьем объясняет сэмплы, MIDI или связку с SP-404MKII. Но ка…
Начиная с версии 149, в Chrome и Edge доступны CSS-декорации для заполнения промежутков между элементами сетки, flexbox и многоколоночными макетами без использования границ или псевдоэлементов.
А твои промежутки стильные? 🌈
https://developer.chrome.com/blog/gap-decorations-stable
Showing the 12 most recent of 20 posts we hold for @taras_dot_one. 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.
Mentions
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.
Handles this channel named that no longer answer
Dead references
3
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
3
vacant every time we have ever looked
@taras_dot_one named 3 handles 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.
@tailwindcss named in 1 post, 11 August 2026 – 11 August 2026
@tanstack named in 1 post, 11 August 2026 – 11 August 2026
@utility named in 1 post, 11 August 2026 – 11 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 10 August 2026 — this
entry's latest reading, not the date you are reading this.
“taras.one - all about frontend” (@taras_dot_one), 56 subscribers as measured 10 August 2026. Telegram Register, tgregister.com/channel/taras_dot_one.
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.
