Channel
@frontend_ovoe
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Polls · Citations · Cite this entry
33subscribers
+0 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002685661709 |
|---|---|
| Type | Channel |
| Username | @frontend_ovoe |
| Description | микроинфлюенсер из небольшой инди компании |
| Created | Between 1 March 2025 and 14 May 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 11 August 2026 |
| Last confirmed live | 11 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/frontend_ovoe |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 11 Aug 2026, 01:31 | 33 | no change |
| 7 Aug 2026, 18:04 | 33 | first reading |
20 posts held, back to 14 May 2025 — 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.
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 16 April 2026. An engagement rate over an empty window would be a number about nothing.
Lifetime counters from Telegram’s own channel header, read 11 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.
Measured directly from 2 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.
62 reactions across 15 posts, in 10 distinct kinds. The most used accounts for 38.7% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 24 | 38.7% | |
| custom 5307541978181803661 | 10 | 16.1% | |
| 👍 | 9 | 14.5% | |
| 💯 | 7 | 11.3% | |
| 😢 | 5 | 8.06% | |
| 🎉 | 2 | 3.23% | |
| 💔 | 2 | 3.23% | |
| 💅 | 1 | 1.61% | |
| 🔥 | 1 | 1.61% | |
| 😁 | 1 | 1.61% |
Custom emoji. One row above is a 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 count beside it isTelegram’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 15 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 62reactions 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 14 May 2025 to 16 April 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.
Больше всего в жизни фронтендера я не понимал, почему люди так впечатляются запуском чего-либо на CSS. Запуск DOOM, картины, калькулятора — всё это, кажется, должно было остаться в 2016 году. Даже сейчас я вижу много постов о том, что на CSS сделали очередную вещь, которую классически делали на JS. Например, селектор дат. Нахожу такие активности не просто скучными, а вредными. Например, один коллега на работе как-то…
❤2
В Твиттере последнюю неделю новый тренд — найти применение новому пропозалу HTML in Canvas. Наверное, форма внутри Doom — лучшая демонстрация возможностей этого API. Очень впечатляет, выглядит перспективно. https://x.com/solarise_webdev/status/2042357703826108563?s=46&t=ap6YkKsV6K3t_KjHlIi6Zw
😁1
Написал пост на второй канал, но думаю сюда он тоже пойдет
Наверное, мой самый успешный пет проект, написанный нейросетями — тот, который я сделал чисто для себя, не пытаясь сделать из него продукт. Это todo с категоризацией и главной фичей для моей личной продуктивности: «☀️солнышко». Солнышко помечает задачи, которые я хочу взять на сегодня, а на следующий день все солнышки угасают и их нужно зажигать снова, когда ты уверен, что точно хочешь взять задачу на сегодня. Это п…
💯4❤3
Как же хорошо! Жаль, Apple пофиксит это в ближайшем обновлении :( https://haptics.lochie.me Для тех, кто не в курсе: на IPhone есть движок вибраций, Haptic Engine. Этот движок позволяет делать какие угодно рисунки вибраций для приложений, чтобы подчеркивать действия пользователя. Например, короткая слабая вибрация на успех и тяжелая прерывистая при ошибке. Конечно, Apple не любит PWA и конкуренцию с App Store, поэт…
😢4👍2
Отдельно стоит упоминания новый подход «Traffic-aware Pre-Rendering». Это пререндеринг только тех экранов, которые имеют значение (получют бОльшую часть трафика), чтобы CI проходил не полчаса, а несколько минут. Я, конечно, удивлен, что к этому мир Next.js не пришёл ранее. Отслеживать трафик конкретных страниц и доставать при сборке условный топ-10 не звучит как rocket scince или уникальная идея.
❤1custom 53075419781818036611
Cloudflare переписала Next.js на Vite, используя всего лишь 1 100 долларов на токены и примерно неделю времени тимлида (engineering manager). Новое решение уже работает на американском государственном сайте cio.gov (жаль, не cia.gov) https://blog.cloudflare.com/vinext/ Пересказывать всю статью не буду, советую почитать самостоятельно. В результате ребята получили уменьшение бандла на 56% и ускорение сборки в 1.6-4.4…
❤1👍1custom 53075419781818036611
Как настоящий телеграм инфлюенсер, решил создать второй канал с щитпостом про всё на свете, а здесь оставить редкие посты про интересные темы о фронтенде. Прямо сейчас провожу марафон создать прототип игры на Godot за 10 дней без малейшего опыта в геймдеве. Подписывайтесь: https://t.me/frontend_o4ka
https://errore.org/ Кто-то запарился и сделал огромный лендос. Что же, я только всеми лапами за! И вам советую.
Очень здравая и проработанная идея. Хотелось бы попробовать как подвернется возможность
На завод, друзья!
custom 53075419781818036613🎉2💅1
Мне нравятся кулинарные шоу, но в них я всегда не верил одной общей черте — участники заканчивают работу в последние секунды. Это выглядело как постанова. В последние дни этого года я сам очутился в такой ситуации. Всего один упущенный день — и задача, которую ты делал все полугодие уже не будет запущена в этом году. Фиаско! Что ж, попытаем удачу в следующем году. Иронично, что когда я завел канал по фронтенду, мо…
❤6💔2🔥1
Showing the 12 most recent of 20 posts we hold for @frontend_ovoe. 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.
The poll we hold for this entry, as Telegram rendered it when we read the post. A poll’s figures keep moving after that, so each one is dated.
Это валидный URL? example.com?foo=bar
Shares as published, totalling 101%. No per-option vote count is published by Telegram, so none is shown.
Percentages only — there are no per-option vote counts here, because Telegram publishes none.The public post preview gives each option’s share and a single voter total, and nothing else. Multiplying one by the other would produce a per-option tally that looks measured and is not: the shares are rounded to whole numbers before we ever see them. We print what was published and leave the column that does not exist empty.
The shares need not add up to 100.Rounding alone puts many polls at 99 or 101. A poll that allows more than one answer per voter runs well past 100 by design, and several here do. The bars are drawn against a fixed 100% track at each option’s own percentage rather than normalised to the total, so a poll that exceeds it shows that it does instead of being quietly rescaled.
Read from the 20 most recent posts we hold, published 14 May 2025 to 16 April 2026. Telegram labels each poll by kind — an anonymous poll, a quiz, a closed set of final results — and that label is reproduced rather than paraphrased.
Citation-graph rank — 1,162,590 of 1,350,102entries 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.
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.
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.
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 11 August 2026 — this entry's latest reading, not the date you are reading this.
“фронтендовое” (@frontend_ovoe), 33 subscribers as measured 11 August 2026. Telegram Register, tgregister.com/channel/frontend_ovoe.
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.