JavaScript. Задача Цифровой корень натурального числа — это цифра, полученная в результате итеративного процесса суммирования цифр, на каждой итерации которого для подсчета суммы цифр берут результат, полученный на предыдущей итерации. Этот процесс повторяется до тех пор, пока не будет получена одна цифра. Необходимо составить программу нахождения цифрового корня натурального числа. Входные данные: N - натуральное…

Channel
Javascript js frontend
@frontendlib
On this record: Growth · Engagement · What this channel posts · Reactions · Advertising · Posts · Citations · Cite this entry
8,540subscribers
-60 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
Register entry
| Telegram ID | -1001197948054 |
|---|---|
| Type | Channel |
| Username | @frontendlib |
| Description | Канал для начинающих JavaScript разработчиков. Если вы приступаете к изучению JS или FrontEnd в целом - этот канал для вас. @anothertechrock РКН: https://clck.ru/3R3tmU |
| Created | Between 1 March 2018 and 31 July 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 22 August 2026 |
| Measurements held | 8 |
| Confirmed unchanged | 1 time, most recently 22 August 2026 |
| On Telegram | t.me/frontendlib |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 22 Aug 2026, 05:48 | 8,540 | -12 |
| 19 Aug 2026, 01:07 | 8,552 | -8 |
| 16 Aug 2026, 05:57 | 8,560 | -16 |
| 12 Aug 2026, 23:56 | 8,576 | -14 |
| 10 Aug 2026, 07:37 | 8,590 | -7 |
| 7 Aug 2026, 05:40 | 8,597 | -3 |
| 6 Aug 2026, 12:15 | 8,600 | no change |
| 6 Aug 2026, 12:09 | 8,600 | first reading |
Engagement
31 posts held, back to 19 May 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 19 pagesof Telegram’s post history, 20 posts per page.
- ERR · 30 days
- 6.89%
- avg views ÷ 8,540 subscribers
- Avg views / post
- 588
- 16 posts measured
- Reaction rate
- 0.382%
- reactions ÷ views · ER floor
- Posts in window
- 16
- of 31 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. It is computed over the 10 of 16 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 20 August 2026 |
|---|---|
| Posts held | 31 (19 May 2026 – 20 August 2026) |
| Views total | 9,411 |
| Reactions total | 24 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 22 Aug 2026, 19:14 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
- 469
- Videos
- 173
- Links
- 330
Lifetime counters from Telegram’s own channel header, read 22 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
64 reactions across 18 posts, in 9 distinct kinds. The most used accounts for 48.4% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 31 | 48.4% | |
| ❤ | 8 | 12.5% | |
| 👎 | 7 | 10.9% | |
| 💩 | 4 | 6.25% | |
| 🤔 | 4 | 6.25% | |
| 🔥 | 3 | 4.69% | |
| 🙏 | 3 | 4.69% | |
| ❤🔥 | 2 | 3.13% | |
| 👏 | 2 | 3.13% |
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 22 of the 31 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 64reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 31 most recent posts we hold, published 19 May 2026 to 20 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.
Advertising
- Ad load
- 22.6%
- 7 of 31 posts carry an ad marker
- Regulatory tokens
- 7
- posts carrying an erid · 7 distinct tokens
- Median views · ads
- 825
- over 7 measured posts
- Median views · rest
- 869
- over 24 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. They are printed side by side with the count behind each rather than as a ratio: an ad and an ordinary post are not otherwise matched — for topic, for length, for hour of day — so the gap between them is a description of two groups and not the effect of one being an ad.
| erid | Posts | First seen | Last seen |
|---|---|---|---|
| 2VtzqwMcu5t | 1 | 4 August 2026 | 4 August 2026 |
| 2Vtzqwh8Q6n | 1 | 14 July 2026 | 14 July 2026 |
| 2VtzqwpJgA6 | 1 | 11 August 2026 | 11 August 2026 |
| 2VtzqxFgSTb | 1 | 16 June 2026 | 16 June 2026 |
| 2W5zFGVqbey | 1 | 20 August 2026 | 20 August 2026 |
| 2W5zFGtQB7P | 1 | 26 June 2026 | 26 June 2026 |
| 2W5zFJkeyPF | 1 | 27 July 2026 | 27 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 31 most recent posts we hold, published 19 May 2026 to 20 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
Почему Frontend-разработчики уходят в курьеры? В последнее время всё чаще вижу одну и ту же картину: Frontend-разработчик отправляет сотню откликов. Потом ещё сотню. А в ответ пара отписок «мы с вами свяжемся», отказы и тишина Раньше я думал, что проблема почти всегда в резюме или скиллах. Но чем глубже копаюсь в рынке, тем сильнее понимаю, что рынок жёстко перегрет и даже сильным ребятам приходится бороться за каж…
👍3💩1🔥1
📂 Напоминалка по URL, URI и URN в веб-разработке! Например, URL (Uniform Resource Locator) используется для указания адреса ресурса и способа его получения (https://example.com/page), а URI (Uniform Resource Identifier) является общим идентификатором ресурса, который включает в себя URL и URN. На картинке — сравнение трёх понятий, которые часто используют при работе с веб-технологиями, API и распределёнными система…
В нашем канале много ценного для разработчиков по подготовке к собесам👇 Уже 2 года мы развиваем комьюнити, где 10000+ разработчиков, и вместе мы тренируем собеседования и выжимаем из рынка максимум! Полные разборы собеседований: Сбер, VK, OZON, M-Video, Evrone, еще раз OZON, IT One, Trading View, МТС, Лантан, ДОМ.РФ Стримы с гостями и записями: Как проходить собеседование на английском Как решать livecoding задачи…
❤🔥2👍1👎1
URLPattern — нативное сопоставление URL без ручных регулярных выражений! Во многих проектах приходится разбирать URL: определять маршруты, извлекать параметры, проверять соответствие шаблону. Чаще всего для этого используют регулярные выражения или вручную разбирают строку, хотя современные браузеры предоставляют для этого встроенный API — URLPattern. Создадим шаблон маршрута для страницы пользователя: const patter…
👍1
Недавно на Хабре вышла годная статья: «Что происходит внутри Angular и React при решении одних и тех же задач»! В этой статье: • Сравнивается, как React и Angular работают с DOM, состоянием, жизненным циклом компонентов и асинхронностью; • Показывается, что происходит «под капотом» при рендеринге, обновлении интерфейса и обработке изменений; • Разбираются различия в архитектуре, производительности и подходах к оптим…
Задача В киоске стакан кваса стоит 5 рублей. Дети подходят за квасом по очереди. Каждый купит только один стакан кваса и заплатит купюрой в 5, 10 или 20 рублей. Вы же должны дать сдачу каждому. Сначала у вас нет сдачи. Необходимо определить, сможете ли вы продать квас каждому ребенку. Входные данные: bills - массив купюр, которые платит i-й ребенок в очереди. Вывод: true - если вы сможете рассчитать каждого клиен…
Как создать радиальный градиент в CSS? Для создания фона в виде радиального (кругового, эллиптического) градиента испольуется функция radial-gradient. Самый простой градиент задаётся двумя цветами. .element { background-image: radial-gradient(#6e4aff, #49A16C); } В этом случае начальная точка помещается в центр элемента, а градиент рисуется таким образом, чтобы в углах элемента был последний указанный в скобк…
❤1👍1
JavaScript. Что будет выведено в консоль? Ответ: 35
🔴 Тестовое собеседование на Frontend-разработчика со старшим разработчиком ex. Сбер 13 августа(в четверг!) в 19:00 по мск приходи онлайн на открытое собеседование, чтобы посмотреть на настоящее интервью на Middle Frontend-разработчика. Как это будет: 📂 Даниил Дмитриев, старший разработчик в R-Vision, ex. Сбер, будет задавать реальные вопросы и задачи разработчику-добровольцу 📂 Даниил будет комментировать каждый отв…
👎1
Posted without readable text
JavaScript. Что будет выведено в консоль? Ответ: [ 1, 2, 3, [ 1, 2, 3, 1, 2, 3 ] ] [ 1, 2, 3, [ 1, 2, 3, 1, 2, 3 ] ]
👍1
Showing the 12 most recent of 31 posts we hold for @frontendlib. 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
Citation-graph rank — 1,512,939 of 1,584,733entries 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.
Mentions
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.
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 22 August 2026 — this entry's latest reading, not the date you are reading this.
“Javascript js frontend” (@frontendlib), 8,540 subscribers as measured 22 August 2026. Telegram Register, tgregister.com/channel/frontendlib.
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.