Telegram RegisterThe public register of Telegram
Telegram profile photo for Фронтендер от бога

Channel

Фронтендер от бога

@godofjs

On this record: Growth · Engagement · Reactions · Advertising · Posts · Telegram's recommendations · Cite this entry

3,414subscribers

-29 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1001463792139
TypeChannel
Username@godofjs
Created4 September 2020measured — cross-checked against a third-party dataset (ext.tg_channel)
First recorded7 August 2026
Last confirmed live9 September 2026
Measurements held10
Confirmed unchanged1 time, most recently 9 September 2026
On Telegramt.me/godofjs

Growth

3,4143,4433,428.57 August 2026 — 3,443 subscribers7 August 2026 — 3,443 subscribers11 August 2026 — 3,438 subscribers18 August 2026 — 3,435 subscribers21 August 2026 — 3,434 subscribers25 August 2026 — 3,431 subscribers27 August 2026 — 3,429 subscribers31 August 2026 — 3,426 subscribers4 September 2026 — 3,424 subscribers9 September 2026 — 3,414 subscribers7 August 20269 September 2026
10 measurements spanning 33 days, net -29. 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 3,410–3,447 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
9 Sept 2026, 00:403,414-10
4 Sept 2026, 02:553,424-2
31 Aug 2026, 07:143,426-3
27 Aug 2026, 21:443,429-2
25 Aug 2026, 01:053,431-3
21 Aug 2026, 02:523,434-1
18 Aug 2026, 02:523,435-3
11 Aug 2026, 11:483,438-5
7 Aug 2026, 08:463,443no change
7 Aug 2026, 08:383,443first reading

Engagement

20 posts held, back to 15 June 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 3 pages of 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 6 August 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

87 reactions across 18 posts, in 6 distinct kinds. The most used accounts for 50.6% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍4450.6%
🔥1719.5%
1618.4%
👎44.60%
🤔44.60%
🙏22.30%

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 18 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 87 reactions 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 15 June 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.

Advertising

Ad load
10.0%
2 of 20 posts carry an ad marker
Regulatory tokens
2
posts carrying an erid · 2 distinct tokens
Median views · ads
587
over 2 measured posts
Median views · rest
583
over 18 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
2VtzqxMcPay116 June 202616 June 2026
2W5zFFzazVo17 July 20267 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 20 most recent posts we hold, published 15 June 2026 to 6 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

6 Aug 2026, 09:42 UTC237 viewsread 7 August 2026
Photo

Intlayer: альтернатива @nuxt/i18n с фокусом на оптимизации бандла #почитать После интеграции nuxt/i18n в несколько моих проектов я пришел к однозначному выводу: это, безусловно, лучшее i18n-решение для JS-фреймворков. Его «plug&play» настройка, загрузка пространств имен (namespaces) и встроенная маршрутизация, настоящее удовольствие в работе. Однако у этого решения есть серьезная проблема: загруженные пространства

3 Aug 2026, 09:42 UTC365 viewsread 7 August 2026
Photo

Рендер-функции и Teleport в Vue.js #почитать Декларативные шаблоны Vue решают 90% задач фронтенда. Но периодически возникают ситуации, где шаблонного синтаксиса оказывается мало. Нужен более тонкий контроль над рендерингом или возможность вынести часть компонента за пределы его естественной позиции в DOM-дереве. Для таких случаев Vue 3 послал нам render-функции и встроенный компонент Teleport. ⏱Читать статью

30 Jul 2026, 04:04 UTC512 views4 reactionsread 7 August 2026
Photo

Практическая оптимизация React: ререндеры, Context, списки, INP и code splitting #почитать Оптимизация в React почти всегда сводится к двум факторам: объёму работы, которую выполняет JavaScript, и частоте (а также «стоимости») перерисовок компонентов. Сам React работает достаточно быстро, но в крупных интерфейсах даже небольшие архитектурные промахи и на первый взгляд безобидные ререндеры начинают заметно бить по п

👍3🔥1

27 Jul 2026, 09:42 UTC488 views4 reactionsread 7 August 2026
Photo

JSDocs в VSCode #почитать В этой публикации я очень кратко раскрываю, почему переход с IntelliJ IDEA (PhpStorm) на VSCode ломает привычную работу с JSDoc в JavaScript-проектах. ⏱Читать статью

👍3🔥1

24 Jul 2026, 09:41 UTC599 views5 reactionsread 7 August 2026
Photo

Заменяем JS обычным HTML #почитать Уже многие годы JavaScript остаётся «рабочей лошадкой» веба. Если вам нужно сделать то, что невозможно реализовать средствами HTML и CSS, то обычно найти решение помогает JS. И это замечательно! JS помог расширить возможности пользователей, а также стимулировал прогресс HTML и CSS! Но время идёт, функции HTML и CSS расширяются, поэтому мы должны начать заменять старые и привычные

👍4🔥1

21 Jul 2026, 09:41 UTC522 views5 reactionsread 7 August 2026
Photo

Atomic CSS: верстка и легкость бытия #почитать Обсудим имеющиеся проблемы в верстке и посмотрим, как атомарный подход их решает (или не решает). Разберем основные мифы, посмотрим на лучшие практики этого подхода и сделаем выводы. ⏱Читать статью

👎3🔥2

17 Jul 2026, 09:42 UTC644 views6 reactionsread 7 August 2026
Photo

Реактивность без React или как обойтись без id в html элементах #почитать А зачем вообще обходиться без id? Даже не знаю, но это вполне возможно, и приложение будет живым и вполне себе «реактивным». А всю «магию» при этом творит функция, которую я назвал tokenize. Конечно же я, ни в коем случае, не настаиваю на отказе от id. "Элементарные" id никому не мешают и tokenize`у тоже. Но если обходиться без id, то как же

🔥4👍2

10 Jul 2026, 15:03 UTC649 views4 reactionsread 7 August 2026
Photo

Типизация JavaScript через JSDoc #почитать Используете JSDoc для типизации JavaScript? Узнайте, как настроить TypeScript Compiler для профессиональной проверки типов, генерации деклараций и интеграции в процесс разработки. ⏱Читать статью

👍3🔥1

7 Jul 2026, 19:04 UTC616 views5 reactionsread 7 August 2026
Photo

Обработчики событий в JavaScript #почитать Если коротко, вы узнаете о самом удобном способе управлять откликом на действия пользователя или браузера. ⏱Читать статью

🤔4🔥1

7 Jul 2026, 14:04 UTC587 views11 reactionsread 7 August 2026
Advertisementerid 2W5zFFzazVoPhoto

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

👍53🔥2👎1

7 Jul 2026, 04:01 UTC488 views3 reactionsread 7 August 2026
Photo

Реактивность без фреймворков (просто эксперимент на чистом JS + Web APIs) #почитать Опишу пример, демонстрирующий, насколько важна декларативность в вопросах управления поведением «аппки» (за этим стоят вопросы сохранения высокого уровня абстракции и, как следствие, масштабируемости приложения). Задача - сделать управление мутациями DOM более декларативным и, как заявлено в заголовке, использовать реактивность на п

👍3

3 Jul 2026, 04:01 UTC613 views4 reactionsread 7 August 2026
Photo

Настройка Jest и React Testing Library: пошаговое руководство для React и Next.js проектов #почитать В этой статье мы подробно рассмотрим процесс настройки среды unit-тестирования веб-приложений на базе React и Next.js с использованием Jest и React Testing Library. Расскажем об установке необходимых зависимостей, создании конфигурационных файлов, настройке Babel и TypeScript, подключении SCSS и SVG, а также организ

👍3🔥1

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

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.

Frontender's notes [ru]
@frontendnoteschannel_ru · 31,509
Telegram ranks this channel #27 of 95 here — alongside 94 others — read 6 September 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 9 September 2026 — this entry's latest reading, not the date you are reading this.

“Фронтендер от бога” (@godofjs), 3,414 subscribers as measured 9 September 2026. Telegram Register, tgregister.com/channel/godofjs.

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.