Channel
@olovyannikov_it
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry
182subscribers
+0 since we began measuring on 8 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002570513327 |
|---|---|
| Type | Channel |
| Username | @olovyannikov_it |
| Created | Between 1 March 2025 and 31 July 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 15 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/olovyannikov_it |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 8 Aug 2026, 12:46 | 182 | no change |
| 8 Aug 2026, 02:15 | 182 | first reading |
17 posts held, back to 16 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 pageof Telegram’s post history, 20 posts per page.
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.
| Window | Rolling 30 days · latest post in window 6 August 2026 |
|---|---|
| Posts held | 17 (16 March 2026 – 6 August 2026) |
| Views total | 341 |
| Reactions total | 16 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 8 Aug 2026, 12:46 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.
Lifetime counters from Telegram’s own channel header, read 8 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.
219 reactions across 17 posts, in 10 distinct kinds. The most used accounts for 29.7% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 🔥 | 65 | 29.7% | |
| ❤ | 47 | 21.5% | |
| 💘 | 38 | 17.4% | |
| 👍 | 28 | 12.8% | |
| 😁 | 12 | 5.48% | |
| 🤔 | 9 | 4.11% | |
| 🤯 | 8 | 3.65% | |
| 🙏 | 7 | 3.20% | |
| 🦄 | 4 | 1.83% | |
| 💔 | 1 | 0.457% |
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 17 of the 17 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 219reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 17 most recent posts we hold, published 16 March 2026 to 6 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.
effector-refetch Пока расскажу про библиотеку, которую я делал Зачем? Потому-что существующего туллинга просто не хватило. Не так давно мы с командой полностью мигрировали на effector-based стек и переехали на ff.effector.dev Но в фарфетчед было много недочетов, с которыми мы впоследствии столкнулись – отсутствие пагинации (infinite-query) из коробки, мало примеров и гайдов в доке, нет возможности настроить фабрику…
🔥5💘1
В эпоху агентской разработки даже и не знаешь, чем поделиться. Все уже делают агенты, только ещё не едят за нас и не спят. Любая концепция, любой продукт, любая хотелка теперь реализуется в считанные минуты, что раньше занимали месяцы кропотливого умственного труда. Только мамой, только мамой, не может быыыть…. А так - чем угодно
👍7💘2💔1
@effector/reflect 10.1.0 ✨ Новая фича: mapProps const Hello = reflect({ view: Greeting, bind: { // ... }, mapProps: { label: { source: $user, fn: (user, props) => `${props.title} ${user.name}`, }, }, }); Спасибо @olovyannikov_frontend за пуллик! 📚 Документация: https://reflect.effector.dev/docs/reflect#deriving-props-with-mapprops
🔥6❤2💘2
effector-eslint-plugin v0.19.0 ✨ Новое правило: enforce-exhaustive-useUnit-destructuring – требует деструктурировать все юниты, переданные в useUnit. Теперь стало значительно сложнее потерять юниты в компоненте и избежать лишних подписок. Вошло в пресет react - спасибо @olovyannikov_frontend за реализацию! 🛠️ Улучшены enforce-store-naming-convention и enforce-effect-naming-convention – теперь проверяются не только …
🔥8💘1
Коммунити, принес вам потрогать очередную дата-фетчилку для эффектора. Паритет с farfetched, фичи, которых не хватало, effect-based. Принимаются предложения, улучшения и все такое Постарался закрыть максимально потребностей) + девтулы, кодмод для миграции с фф, скилл для AI Нейрослоп из доки не вычищал пока, сделаем это ближе к релизу, если он случится :) https://olovyannikov.github.io/effector-refetch/
❤8👍3💘3
Данные не должны лежать в базах мёртвым грузом. Они должны двигаться. В своём докладе Илья Оловянников расскажет о «кинетическом» подходе к управлению данными: event-driven архитектуре и графах правил, где вы не управляете каждым шагом процесса, а задаёте законы, по которым он работает. 📎 Выложили программу митапа, так что теперь у вас точно на два повода пройти регистрацию больше! 25 июня, MoscowJS 71 x Школа 21 …
🔥9❤6👍3💘2
HOLYJS В С Ё! Ну, в смысле закончился HolyJS Spring 2026, дальше только через полгода :) Было круто – суперские доклады, которые я буду смотреть вместо сериалов в ближайшую пару недель, ламповое сообщество и просто самые лучшие люди :) Спасибо всем, кто пришел поддержать нас на стенде MoscowJS – мы старались, чесслово :) Дальше – больше! :)
🔥15👍5💘5
Продолжаем сезон живых встреч: MoscowJS едет на HolyJS! В этом году мы будем стоять на стенде сообществ — а значит, будет не только «подошёл-послушал», но и «подошёл-пообщался» 😎 Что вас ждёт у нас на стенде: > Моковые собесы — можно безопасно проверить себя и получить честный фидбек. > «Норм или стрём в IT?» — обсудим горячие темы и холивары. > Игра «Контакт» — да, та самая, где нужен талант чтения мыслей. Приход…
🔥5❤1👍1💘1
☄️ @effector/router v1.0.0 release candidate Новый роутер основан на идеях и коде atomic-router и argon-router. А так как последние уже не поддерживаются, то effector core team приняли решение о переносе проекта в организацию effector. Чтобы переехать нужно заменить зависимости предыдущего роутера на @effector/[email protected] и @effector/[email protected]. Кроме этого, из ломающих изменений сейчас необхо…
💘1
Коротко про Next.js — «Так App Router — это уже стабильно?» — «Да, с версии 13.4.» — «А почему у меня тогда в 14.2 падает продакшен?» — «Потому что experimental изменили на stable, но специально оставили 146 issue на GitHub, чтобы вы не скучали».
💘5😁1
Кажется, что я никогда не видел майских праздников. Только работа, только х2 (sad)
🙏7👍4🦄2💘1
Обожаю, когда оставляют отладочную инфу на сайтах. Это кстати https://theweldercatherine.ru/
😁11🤯8💘2
Showing the 12 most recent of 17 posts we hold for @olovyannikov_it. 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 — 829,468 of 1,549,376entries 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.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
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.
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.
@olovyannikov_it 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.
References a handle that is not a live channel — we have no record it ever was one.
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 August 2026 — this entry's latest reading, not the date you are reading this.
“Elijah” (@olovyannikov_it), 182 subscribers as measured 8 August 2026. Telegram Register, tgregister.com/channel/olovyannikov_it.
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.