Telegram RegisterThe public register of Telegram

Channel

FrontEndDev

@front_end_dev

On this record: Growth · Engagement · What this channel posts · Reactions · Stars · Advertising · Posts · Citations · Telegram's recommendations · Cite this entry

26,174subscribers

-46 since we began measuring on 5 August 2026

Risers and fallers across the register · movement among entries of 10,000–31,623.

Register entry

Telegram ID-1001052068360
TypeChannel
Username@front_end_dev
Description🚀 Статьи, новости, туториалы по frontend разработке. http://jem-space.ru Admin: @jem_jem Пишу в @five_a_m AI и вайбкод @vibe_and_ai Читать на парковке: https://max.ru/front_end_dev Реклама: http://bit.ly/2NxmVDu РКН: https://clck.ru/3GLw7G
Created1 July 2016measured — cross-checked against a third-party dataset (ext.tg_channel)
First recorded6 August 2026
Last confirmed live12 August 2026
Measurements held8
Confirmed unchanged1 time, most recently 12 August 2026
On Telegramt.me/front_end_dev

Growth

26,17426,22026,1975 August 2026 — 26,220 subscribers6 August 2026 — 26,220 subscribers7 August 2026 — 26,215 subscribers8 August 2026 — 26,216 subscribers9 August 2026 — 26,207 subscribers10 August 2026 — 26,192 subscribers11 August 2026 — 26,178 subscribers12 August 2026 — 26,174 subscribers5 August 202612 August 2026
8 measurements spanning 7 days, net -46. 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 26,167–26,227 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
12 Aug 2026, 21:0926,174-4
11 Aug 2026, 22:4226,178-14
10 Aug 2026, 19:3226,192-15
9 Aug 2026, 16:0126,207-9
8 Aug 2026, 15:2826,216+1
7 Aug 2026, 13:1026,215-5
6 Aug 2026, 02:0226,220no change
5 Aug 2026, 23:2526,220first reading

Engagement

26 posts held, back to 11 July 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 18 pagesof Telegram’s post history, 20 posts per page.

ERR · 30 days
11.3%
avg views ÷ 26,174 subscribers
Avg views / post
2,960
21 posts measured
Reaction rate
0.418%
reactions ÷ views · ER floor
Posts in window
21
of 26 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.

What these figures were computed from
WindowRolling 30 days · latest post in window 12 August 2026
Posts held26 (11 July 202612 August 2026)
Views total62,230
Reactions total260
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken13 Aug 2026, 11:21 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

Photos
2,600
Videos
24
Links
7,830

Lifetime counters from Telegram’s own channel header, read 13 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.

Reaction mix

323 reactions across 26 posts, in 18 distinct kinds. The most used accounts for 32.8% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍10632.8%
7021.7%
🔥3510.8%
💩3410.5%
👎268.05%
🤡134.02%
❤‍🔥103.10%
72.17%
🤔51.55%
👻41.24%
💔41.24%
😁20.619%
😐20.619%
👏10.31%
😢10.31%
🤣10.31%
🤬10.31%
🥱10.31%

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 26 of the 26 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 323reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 26 most recent posts we hold, published 11 July 2026 to 12 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.

Telegram Stars

Stars received
1
across the posts below
Posts paid on
1
of 26 we hold a reading for · 4%
Most on one post
1
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @front_end_dev. 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 26 most recent posts we hold for this entry, published 11 July 2026 to 12 August 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.

Advertising

Ad load
11.5%
3 of 26 posts carry an ad marker
Regulatory tokens
3
posts carrying an erid · 3 distinct tokens
Median views · ads
3,090
over 3 measured posts
Median views · rest
3,100
over 23 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.

Advertising tokens recorded on this entry
eridPostsFirst seenLast seen
2VtzqwqfGqx14 August 20264 August 2026
2VtzqwtdFQe111 August 202611 August 2026
2W5zFJmyDYm117 July 202617 July 2026

A token repeated across several posts is one advertising contract placed more than once, which is what the identifier is for. The strings are reproduced exactly as they appeared in the post or in its click-through URL and are not validated against any registry — we record the marker a channel published, and whether it resolves to a real contract is a question for the register that issued it.

Measured over the 26 most recent posts we hold, published 11 July 2026 to 12 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

12 Aug 2026, 16:23 UTC≈1,380 views5 reactionsread 13 August 2026
Photo

3 хорошие привычки начинающего фронтендера Начните думать о пользователе: увеличивайте кликабельные области. Правильно подбирайте type и inputmode для форм, чтобы браузер показывал ожидаемую виртуальную клавиатуру. Относитесь к alt осознанно: для декоративных изображений оставляйте alt="", чтобы скринридеры не озвучивали лишний шум. https://habr.com/ru/companies/ruvds/articles/1066724/

3👍2

11 Aug 2026, 10:19 UTC≈1,950 views5 reactionsread 13 August 2026
Advertisementerid 2VtzqwtdFQePhoto

🔴 Тестовое собеседование на Frontend-разработчика со старшим разработчиком ex. Сбер 13 августа(в четверг!) в 19:00 по мск приходи онлайн на открытое собеседование, чтобы посмотреть на настоящее интервью на Middle Frontend-разработчика. Как это будет: 📂 Даниил Дмитриев, старший разработчик в R-Vision, ex. Сбер, будет задавать реальные вопросы и задачи разработчику-добровольцу 📂 Даниил будет комментировать каждый отв

🤡3👍2

11 Aug 2026, 09:08 UTC≈1,980 views10 reactionsread 13 August 2026
Photo

Монолит больше не приговор: строим быстрые и гибкие микрофронтенды на ES-модулях Монолитное фронтенд-приложение можно разрезать на микрофронты, собирая их как нативные ES-модули: меньше конфликтов зависимостей, быстрее загрузка и естественный lazy loading через import(). Для интеграции нужен чёткий контракт между хостом и микрофронтом (и единый механизм монтирования в Shadow DOM с обработкой ошибок/состояний. https

👎4👍321

10 Aug 2026, 16:15 UTC≈2,140 views10 reactions1 Starread 13 August 2026
Photo

5 CSS-свойств, которые прокачают дизайн текста Показывайте фон внутри букв через background-clip: text, управляйте вертикальным выравниванием инлайновых элементов через vertical-align, добавляйте выразительность letter-spacing и еще несколько свойств и кейсов их применения — по ссылке. https://master.dev/blog/typographic-css-tricks/

👍62🔥2

10 Aug 2026, 14:38 UTC≈2,270 views25 reactionsread 13 August 2026
Photo

Фронтенд не умер — просто AI уже копает за нас лопатой AI уже берёт на себя рутину: помогает делать черновики, тесты и фикстуры, ускоряет миграции и онбординг, а также может расследовать инциденты и собирать десятки связанных PR. Главный риск не в плохом коде, а в скорости: растут объём ревью, число переделок и вероятность уверенно закрепить неверное решение, поэтому нужны планы, этапная проверка и ответственность и

👎14👍81🤔1🤬1

10 Aug 2026, 09:21 UTC≈2,310 views8 reactionsread 13 August 2026
Photo

Переходы View Transitions: важно не сделать интерфейс некликабельным Если не настроить View Transitions, псевдоэлемент ::view-transition может перекрыть весь вьюпорт на время анимации и блокировать клики по интерактивным элементам. Решение — отключить участие :root в снапшоте и убрать перехват событий у ::view-transition. Подробнее — в статье https://master.dev/blog/view-transitions-careful-not-to-make-stuff-unclic

👍52🤔1

5 Aug 2026, 07:30 UTC≈3,560 views13 reactionsread 13 August 2026
Photo

Конец адаптивных изображений. Атрибут sizes для <img> раньше был самым сложным: его синтаксис приходилось постоянно держать в актуальном состоянии вместе с CSS. Идея в том, чтобы перейти к Client Hints: браузер подсказывает серверу нужный размер, сервер присылает подходящее изображение, а разметка сводится к простому <img src="" alt=""> (плюс не забыть про lazy loading). https://master.dev/blog/ending-responsive-i

11🔥2

4 Aug 2026, 14:30 UTC≈3,330 views14 reactionsread 13 August 2026
Photo

Опенсорсная Весёлая Ферма: поднимаем preview‑окружения без боли. Пример построения системы сборок. Preview‑окружения для каждого пул‑реквеста перестают быть ручной магией: код из ветки собирается, запускается изолированный инстанс и ему выдаётся уникальный URL, а проксирование трафика берёт на себя nginx/Ingress. https://habr.com/ru/companies/yandex/articles/1064394/

👍72💩21🤔1😁1

4 Aug 2026, 10:00 UTC≈3,090 views9 reactionsread 13 August 2026
Advertisementerid 2VtzqwqfGqxPhoto

🔴 Тестовое собеседование с ТимЛидом Frontend-разработки в этот четверг 6 августа(в четверг!) в 19:00 по мск приходи онлайн на открытое собеседование, чтобы посмотреть на настоящее интервью на Middle Frontend-разработчика. Как это будет: 📂 Алексей Романов, Teamlead в Underhood.dev с опытом 6+ лет, будет задавать реальные вопросы и задачи разработчику-добровольцу 📂 Алексей будет комментировать каждый ответ респондент

👍6💩2🤣1

3 Aug 2026, 14:30 UTC≈2,780 views15 reactionsread 13 August 2026
Photo

Обфускация JavaScript в эпоху ИИ: всё ещё имеет смысл? Обфускация не делает фронтенд секретным: браузерный код всё равно можно извлечь, но становится заметно сложнее читать, копировать и безопасно модифицировать. ИИ ускоряет понимание и может собирать правдоподобную чистую версию. Используйте обфускацию только как часть защиты, а реальные ключи, авторизацию и валидацию критичных правил держите на сервере. https://w

👍8🤡7

3 Aug 2026, 14:17 UTC≈2,730 views17 reactionsread 13 August 2026
Photo

Как верстали 15 лет назад Вырезки из книги по верстке 2004 года: забавные техники, которые были актуальны в то время. https://habr.com/ru/companies/ruvds/articles/1060630/

11👻4👍2

3 Aug 2026, 07:30 UTC≈2,860 views18 reactionsread 13 August 2026
Photo

Лучшие состояния загрузки — это когда их нет. Вместо спиннеров и скелетонов прокачивайте стратегию preloading: заранее подгружайте данные и готовьте переходы между маршрутами, чтобы страница ощущалась как загруженная сразу. Route transitions не убирают загрузку полностью, но помогают перенести её на уровень приложения, делая UX стабильнее и предсказуемее в SPA. https://master.dev/blog/the-best-loading-states-are-no

👍8💩73

Showing the 12 most recent of 26 posts we hold for @front_end_dev. 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.

Citation-graph rank

Citation-graph rank — 137,068 of 1,183,361entries 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.

Forward network

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

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.

Mentions

Named by 2 registered channels — 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.

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.

Appears in Telegram’s recommendations for other channels

The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.

Сила Книги | Аудиокниги | Flibusta
@silaknigi · 123,627
Telegram ranks this channel #69 of 86 here — alongside 85 others — read 13 August 2026

This channel appears in 1 seed channel's Telegram-generated recommendation list in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.

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 12 August 2026 — this entry's latest reading, not the date you are reading this.

“FrontEndDev” (@front_end_dev), 26,174 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/front_end_dev.

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.