Channel
@frontend_1
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Stars · Advertising · Posts · Citations · Handles named that no longer answer · Telegram's recommendations · Cite this entry
10,262subscribers
-265 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
| Telegram ID | -1001448376377 |
|---|---|
| Type | Channel |
| Username | @frontend_1 |
| Description | Полезные материалы для фронтендера по HTML, CSS, JS, React.js, Angular.js, Vue.js, TypeScript, Redux, MobX, JavaScript, NodeJS. По всем вопросам @evgenycarter РКН clck.ru/3KoFrk |
| Created | 3 October 2019 — measured — cross-checked against a third-party dataset (ext.tg_channel) |
| First recorded | 6 August 2026 |
| Last confirmed live | 11 November 2026 |
| Measurements held | 63 |
| Confirmed unchanged | 1 time, most recently 11 November 2026 |
| On Telegram | t.me/frontend_1 |
Technology — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 11 September 2026 and assigned it the closest of 31 fixed categories, at 91% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and the other topics.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 11 Nov 2026, 00:51 | 10,262 | -5 |
| 9 Nov 2026, 07:35 | 10,267 | -5 |
| 7 Nov 2026, 21:21 | 10,272 | -8 |
| 6 Nov 2026, 21:55 | 10,280 | -7 |
| 5 Nov 2026, 23:18 | 10,287 | -6 |
| 5 Nov 2026, 00:59 | 10,293 | +1 |
| 4 Nov 2026, 04:18 | 10,292 | -4 |
| 3 Nov 2026, 05:20 | 10,296 | -4 |
| 2 Nov 2026, 03:36 | 10,300 | -5 |
| 30 Oct 2026, 22:54 | 10,305 | -7 |
| 29 Oct 2026, 21:16 | 10,312 | -2 |
| 28 Oct 2026, 18:19 | 10,314 | -5 |
| 27 Oct 2026, 17:29 | 10,319 | -4 |
| 26 Oct 2026, 16:16 | 10,323 | -2 |
| 25 Oct 2026, 17:48 | 10,325 | -3 |
| 23 Oct 2026, 20:17 | 10,328 | -10 |
| 22 Oct 2026, 19:59 | 10,338 | -11 |
| 21 Oct 2026, 17:06 | 10,349 | -5 |
| 20 Oct 2026, 14:46 | 10,354 | -1 |
| 19 Oct 2026, 17:58 | 10,355 | first reading |
51 posts held, back to 9 July 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 57 pages of 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 8 November 2026 |
|---|---|
| Posts held | 51 (9 July 2026 – 8 November 2026) |
| Views total | 8,284 |
| Reactions total | 46 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 12 Nov 2026, 10:41 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 12 November 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.
Measured directly from 11 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.
202 reactions across 48 posts, in 10 distinct kinds. The most used accounts for 57.4% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 116 | 57.4% | |
| 🔥 | 62 | 30.7% | |
| ❤ | 6 | 2.97% | |
| 😁 | 6 | 2.97% | |
| 👎 | 5 | 2.48% | |
| 💩 | 2 | 0.99% | |
| 🤔 | 2 | 0.99% | |
| 👌 | 1 | 0.495% | |
| 👏 | 1 | 0.495% | |
| 🤣 | 1 | 0.495% |
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 48 of the 51 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 202 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 51 most recent posts we hold, published 9 July 2026 to 8 November 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.
A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @frontend_1. 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 51 most recent posts we hold for this entry, published 9 July 2026 to 8 November 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.
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.
| erid | Posts | First seen | Last seen |
|---|---|---|---|
| 2W5zFHNcK8V | 2 | 16 July 2026 | 29 July 2026 |
| 2W5zFGkqG2V | 1 | 9 October 2026 | 9 October 2026 |
| 2W5zFGwDoJH | 1 | 18 August 2026 | 18 August 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 51 most recent posts we hold, published 9 July 2026 to 8 November 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.
Telegram’s own ‘edited’ marker: 0 of 12 posts held from the last 30 days (0%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).
Совет по CSS 💡 Знаете ли вы, что можно сделать очень тонкий скроллбар или даже скрыть его, при этом сохранив возможность прокрутки? Это может помочь сделать интерфейс более аккуратным и менее загромождённым в некоторых случаях 📲 Мы в MAX 👉 @frontend_1
👍2
Кто в IT платит выше рынка? И какой оффер считается хорошим? Предлагаем опытным IT-специалистам поделиться мнением о зарплатах и бенефитах в крупных технологических компаниях. Кто, на ваш взгляд, платит выше рынка? У кого привлекательнее премии? Насколько важны ДМС, спорт, питание и другие бонусы при выборе работы? 👉 Поделиться мнением: https://clck.ru/3WNjXw
👍2
Совет по CSS 💡 Возможно, ты не знал, что можно задать и min-width, и width всего одной строкой кода в CSS 📲 Мы в MAX 👉 @frontend_1
🔥2👍1
CSS-совет 💡 Нет необходимости создавать отдельные версии логотипа в градациях серого для тёмного и светлого режимов. Это легко делается с помощью CSS-фильтров 📲 Мы в MAX 👉 @frontend_1
👍3
Как добавлять условные свойства объектов в JavaScript При создании объектов в JavaScript иногда требуется включать определённые свойства только при выполнении конкретных условий. Этот приём можно реализовать с помощью оператора расширения (…) в сочетании с условной логикой. Давайте разберём, как овладеть этим мощным инструментом для более гибкого и динамичного создания объектов. Проблема статических свойств объекто…
👍3🔥2
3 полезных совета по Tailwind CSS Tailwind CSS произвел революцию в том, как мы подходим к веб-дизайну, предложив утилитарно-ориентированный фреймворк, который позволяет быстро разрабатывать и легко настраивать интерфейсы. В этом посте мы рассмотрим три менее известных, но очень полезных совета по Tailwind CSS, которые помогут ускорить рабочий процесс и улучшить качество кода. 1. Используйте size-{n} для одинаково…
🔥3👍2
Где CSS подложил вам ловушки Мне кажется, что каждый фронтендер множество раз сталкивался с ситуацией, когда CSS переставал работать так, как ожидаешь. Причём не имеет значения опыт разработчика. С одинаковой вероятностью в тупик может попасть как джун, так и опытный разработчик. Не зря же CSS стал героем такого количества мемов. Я и сам не раз попадал в подобные ситуации. Но, несмотря на все эти сюрпризы, CSS мне …
👍2❤1🔥1
Сократите свой CSS-код с помощью :where() Используйте псевдокласс-функцию :where(), когда нужно применить одинаковые стили к нескольким элементам, не беспокоясь о том, что порядок селекторов повлияет на специфичность правил. Это простой способ сделать CSS более предсказуемым и удобным для поддержки. /* Without :where() */ .container > h1, .container > .card h1, .container > .card:last-child { border: 2px solid r…
👍3🔥2
Распространённые коды состояния HTTP 📲 Мы в MAX 👉 @frontend_1
❤2👍1🤔1
CSS совет 💡 Возможно, вы не знали, что в CSS можно задавать поворот, используя единицу измерения turn 📲 Мы в MAX 👉 @frontend_1
👍5
Совет по Javascript 💡 Как выбрать последний элемент массива 📲 Мы в MAX 👉 @frontend_1
👍2❤1🤣1
Совет CSS 💡 Вы можете не знать об этом псевдоклассе CSS 📲 Мы в MAX 👉 @frontend_1
👍2❤1🔥1
Showing the 12 most recent of 51 posts we hold for @frontend_1. 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.
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.
Named by 4 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.
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.
@frontend_1 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.
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.
This channel appears in 6 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
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 November 2026 — this entry's latest reading, not the date you are reading this.
“Frontend разработчик” (@frontend_1), 10,262 subscribers as measured 11 November 2026. Telegram Register, tgregister.com/channel/frontend_1.
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.