Telegram RegisterThe public register of Telegram
Telegram profile photo for Frontender's notes [ru]

Channel

Frontender's notes [ru]

@frontendnoteschannel_ru

On this record: Topic · Observations · Channels linked by matching posts · Growth · Engagement · What this channel posts · Reactions · Stars · Advertising · Posts · Posts edited after publishing · Posts recorded as deleted · Citations · Handles named that no longer answer · Telegram's recommendations · Cite this entry

30,770subscribers

-1,114 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1001306975317
TypeChannel
Username@frontendnoteschannel_ru
DescriptionВедущий канал о современном фронтенде: статьи, новости, практики, вайбкодинг и автоматизация фронта ИИ-агентами. Личный блог автора - @just_genych MAX - https://max.ru/frontendnoteschannel_ru По вопросам рекламы или разработки - @g_abashkin
Created28 September 2018 — measured — cross-checked against a third-party dataset (ext.tg_channel)
First recorded6 August 2026
Last confirmed live9 November 2026
Measurements held63
Confirmed unchanged1 time, most recently 9 November 2026
On Telegramt.me/frontendnoteschannel_ru

Topic

Technology — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-UD-Q6_K_XL, prompt version 1) read this channel’s own recent posts on 10 August 2026 and assigned it the closest of 31 fixed categories, at 100% 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.

Observations

These are measurements, not verdicts. Each one below states something we counted, alongside the evidence it was counted from, so you can check it rather than take it. None of them is graded: every observation this register holds is recorded at severity 0, because the precision of the detectors behind them has not been measured yet, and a rating we cannot support is worse than none. Read each as a fact about the data, not as a judgement about the channel. How we measure.

Content that also appears on other registered channels

Posts published here appear in near-verbatim form on 7 other registered channels. This entry also sits inside a group of 8 channels linked by matching posts, directly or through other channels in the group; two members of the group may share no posts with each other. The matching is on the text itself, not on Telegram’s forward marker, so it finds a copy whether or not it was labelled as one.

Matching posts — open both and compare (6 of the pairs behind the counts below)
Posted firstThenOverlapGap
@frontendnoteschannel_ru/5696 · this entry27 Jul 2026, 19:27 UTC@webdevlair/442227 Jul 2026, 19:27 UTC1.00under a minute
@frontendnoteschannel_ru/5701 · this entry29 Jul 2026, 06:07 UTC@webdevlair/442629 Jul 2026, 06:07 UTC1.00under a minute
@webdevlair/44558 Aug 2026, 13:37 UTC@frontendnoteschannel_ru/5725 · this entry8 Aug 2026, 13:37 UTC1.00under a minute
@webdevlair/445710 Aug 2026, 12:07 UTC@frontendnoteschannel_ru/5726 · this entry10 Aug 2026, 12:07 UTC1.00under a minute
@webdevlair/449118 Aug 2026, 10:07 UTC@frontendnoteschannel_ru/5759 · this entry18 Aug 2026, 10:07 UTC1.00under a minute
@frontendnoteschannel_ru/5766 · this entry20 Aug 2026, 06:07 UTC@webdevlair/449520 Aug 2026, 13:37 UTC1.007.5 hours
Channels this entry shares post bodies with, where at least one matching post pair has no forward credit between the two channels, or to a common source, recorded in our data
ChannelMatching postsText overlapTypical gapPublished first
@webdevlair26 (8/8 hand-verifiable sample passed)1.00under a minutethis entry (17–9)
@devsp25 (8/8 hand-verifiable sample passed)1.00under a minute@devsp (18–7)
@we_use_js24 (8/8 hand-verifiable sample passed)1.00under a minutethis entry (15–9)
@xCode_Journal20 (8/8 hand-verifiable sample passed)1.0029 hours@xCode_Journal (20–0)
@qa_logia17 (8/8 hand-verifiable sample passed)1.00under a minutethis entry (12–5)
@python_tesst15 (8/8 hand-verifiable sample passed)1.00under a minute@python_tesst (12–3)
@true_js12 (8/8 hand-verifiable sample passed)1.00under a minute@true_js (7–5)

Text overlap is the Jaccard coefficient over the set of distinct three-word phrases in the two bodies: 1.00 is identical wording, and the threshold for counting a pair at all is 0.70. Candidates are generated by simhash LSH (4 x 16-bit bands, exact Hamming <= 3) verified against the bodies with Jaccard over the SET of distinct 3-word shingles. Published first counts which side of each matching pair carries the earlier timestamp — in this corpus, which is the limitation directly below.

What this cannot establish

MEASURED, DOMINANT ERROR SOURCE: a post ingested before 2026-08-06 may have carried a forward header that was not recorded. A 45-pair hand-check against live t.me pages found 14 (31%) where the live page shows a forward header naming the other channel and the database has none, plus 4 more (9%) naming a third party. The text match itself was wrong 0 times out of 45. Read attribution_capture.items_in_trusted_window before treating the unattributed count as a claim.

Telegram lets a channel forward a post with a header naming the source, and we only began reliably recording that header on 2026-08-06. 47 of the 80 matches recorded here fall after that date and carried no header when we read them. The rest predate reliable capture and are not evidence either way.

“Published first” means first in this corpus. We hold 211 comparable posts for this entry, running 25 July 2026 to 10 November 2026. A channel we have read one page deep will look younger than a neighbour we have read in full, and the order would flip with no change in the underlying facts.

The detector’s own notes on this observation, as it recorded them. Names in this_style are fields of the underlying evidence record, which the plain-English paragraphs above read out for this entry.

  • Verbatim republication has three causes and the text separates only two: a clone/mirror, unattributed copy-paste, or BOTH channels copying a common third source that neither attributes. The spread filter (content held by at most 8 channels) reduces the third and does not remove it.
  • 'Earliest' means earliest IN THIS CORPUS. A channel ingested one page deep will look younger than a neighbour ingested in full; corpus_coverage above is there to be checked before the direction is believed.
  • shared_verified_est extrapolates the sampled pass rate over the full narrow match count; sampled/passed are the numbers actually measured.
  • Absence of a forward header is not proof of intent: Telegram lets a channel disable forward attribution, and a credit written in the body is not parsed as attribution here (mention_edge_either_way above is the closest available signal).

Of the group of 8 channels, the one whose matching posts we hold earliest is @devsp. That is a statement about our reading window, not a claim of authorship.

Recorded under the keys clone_copy · clone_mutual · clone_source, last confirmed 11 November 2026. An observation that a later pass no longer finds is cleared, and a cleared observation is removed from this page rather than being shown struck through — we do not keep publishing a claim we have withdrawn. Dispute an observation.

Channels linked by matching posts

This channel is in a group of 8 registered channels linked by matching posts, directly or through other channels in the group. This channel may share no posts with some of the channels listed below, and listed channels may share none with each other. Links are found by comparing text fingerprints across every channel on the register.

Which channel, if either, published first is deliberately not shown in this list. “First” could only mean first in our own crawl, which depends on how deep we happened to reach into each channel’s history, not on when the content was actually first posted. Our one hand-check read 45 of the highest-confidence flagged pairs against the live Telegram pages. In 18 of them the live page showed a “Forwarded from” credit that our database had no record of, so reading that pair as an unattributed copy was wrong; the check did not measure who published first. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Near-verbatim matching has several ordinary explanations besides copying — a channel mirroring itself, an unattributed repost, or two channels independently repeating the same wire story — and this measurement cannot tell those apart. How this is measured.

Growth

30,77031,88431,3276 August 20269 November 2026
63 measurements spanning 96 days, net -1,114. 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 30,603–32,051 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 63
Measured (UTC)SubscribersChange
9 Nov 2026, 21:4630,770-19
8 Nov 2026, 15:2030,789-13
7 Nov 2026, 08:4630,802-15
6 Nov 2026, 08:5430,817-10
5 Nov 2026, 10:4930,827-9
4 Nov 2026, 11:4530,836-13
3 Nov 2026, 08:2830,849-14
2 Nov 2026, 07:0830,863-4
1 Nov 2026, 09:3430,867-16
31 Oct 2026, 07:4630,883-13
30 Oct 2026, 08:4130,896-18
29 Oct 2026, 10:3830,914-12
28 Oct 2026, 11:2730,926-15
27 Oct 2026, 09:4530,941-7
26 Oct 2026, 08:5830,948-12
25 Oct 2026, 07:0630,960-9
24 Oct 2026, 09:2830,969-18
23 Oct 2026, 08:2730,987-16
22 Oct 2026, 11:0431,003-19
21 Oct 2026, 05:0631,022first reading

Engagement

232 posts held, back to 25 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 214 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
7.75%
avg views ÷ 30,770 subscribers
Avg views / post
2,390
61 posts measured
Reaction rate
0.25%
reactions ÷ views · ER floor
Posts in window
62
of 232 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 47 of 61 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 10 November 2026
Posts held232 (25 July 2026 – 10 November 2026)
Views total145,500
Reactions total290
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken11 Nov 2026, 06:57 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
≈946
Videos
≈66
Links
≈3,830

Lifetime counters from Telegram’s own channel header, read 11 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.

Video runtime
7m 18s
Average length
40s

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.

Reaction mix

1,481 reactions across 177 posts, in 9 distinct kinds. The most used accounts for 37.1% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
😁54937.1%
❤34923.6%
👎19513.2%
👍1268.51%
🔥966.48%
😱946.35%
👀422.84%
🐳261.76%
⚡40.27%

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

Measured over the 232 most recent posts we hold, published 25 July 2026 to 10 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.

Telegram Stars

Stars received
1
across the posts below
Posts paid on
1
of 231 we hold a reading for · 0.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 @frontendnoteschannel_ru. 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 232 most recent posts we hold for this entry, published 25 July 2026 to 10 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.

Advertising

Ad load
1.29%
3 of 232 posts carry an ad marker
Regulatory tokens
3
posts carrying an erid · 3 distinct tokens
Median views · ads
2,530
over 3 measured posts
Median views · rest
2,350
over 228 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
2SDnjccmmqD113 August 202613 August 2026
2VtzquvKR4z110 November 202610 November 2026
2W5zFKAE8KT128 October 202628 October 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 232 most recent posts we hold, published 25 July 2026 to 10 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.

Recent posts

Telegram’s own ‘edited’ marker: 1 of 62 posts held from the last 30 days (1.61%) 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).

10 Nov 2026, 17:07 UTC≈1,120 viewsread 11 November 2026

Статус оплаты в React: как не словить ответ, который пришёл слишком поздно Подписка уже оплачена, а React опять суёт «Ожидаем оплату». Оба запроса вернули HTTP 200 — просто старый ответ добрался последним. В статье объясняют, как воспроизвести такую гонку и не позволить запоздалому ответу затереть актуальный статус заказа. Читать далее 👉 Telegram | Max | 🌥 Claude и другие ИИ

10 Nov 2026, 15:07 UTC≈1,270 viewsread 11 November 2026
Advertisementerid 2VtzquvKR4zPhoto

👾 Открытое собеседование для Frontend-разработчиков: интервьюер из R-Vision, ex-Сбер 12 ноября в 19:00 мск приходи посмотреть, как проходит реальное техническое интервью на позицию Frontend-разработчика Интервьюер: Даниил Дмитриев, Frontend-разработчик в R-Vision, ex-Сбер. Работает с React и TypeScript, совмещает разработку с ролью тимлида, менторит коллег и проводит код-ревью Без сценария и заранее известных вопр…

10 Nov 2026, 13:07 UTC≈1,370 viewsread 11 November 2026
Photo

OpenAPI-спека как фронтенд-инструмент, а не просто Swagger UI Фронтендеру OpenAPI-спецификация может пригодиться задолго до того, как ты вообще откроешь Swagger UI. Из неё спокойно вытаскиваются TypeScript-типы, API-клиент и mock-сервер — и разработку можно начинать, пока бэкенд ещё не готов. И вместо ручного расписывания моделей и запросов ты получаешь генерацию из одного контракта. А если в контракте закралась оп…

10 Nov 2026, 10:35 UTC≈1,500 views5 reactionsread 11 November 2026
Photo

Lighthouse CI: заводим автопилот для проверки производительности сайта Автор прикрутил Lighthouse CI и GitHub Actions, чтобы проверки шли сами и регулярно: метрики производительности на контроле, а регрессии после правок в коде не проскакивают мимо. В статье — настройка аудита, какие метрики держать под присмотром и как разбирать результаты. В практическом примере после оптимизации LCP упал с 12,3 до 3,0 секунды. Ч…

❤2🔥2😁1

9 Nov 2026, 17:07 UTC≈1,770 views3 reactionsread 11 November 2026
Photo

Почему в React несрочный рендер не улетает в никуда В статье разбирают на примере поиска по каталогу: зачем помечать апдейт списка из тысяч товаров как несрочный. Логика простая — React сразу вставляет набранный символ в инпут, а увесистый список пересобирает уже потом, кусками между нажатиями. Дальше поднимают два вопроса: что будет, если долбить по клавишам без остановки, и что видит юзер, пока новый список ещё сч…

👍3

9 Nov 2026, 15:37 UTC≈1,660 views2 reactionsread 11 November 2026
Photo

Кто в IT платит выше рынка? И какой оффер считается хорошим? Предлагаем опытным IT-специалистам поделиться мнением о зарплатах и бенефитах в крупных технологических компаниях. Кто, на ваш взгляд, платит выше рынка? У кого привлекательнее премии? Насколько важны ДМС, спорт, питание и другие бонусы при выборе работы? 👉 Поделиться мнением: https://clck.ru/3WNjt4

👎2

9 Nov 2026, 13:07 UTC≈1,730 viewsread 11 November 2026
Photo

218 КБ переводов на каждой странице: что вообще лежит в payload Nuxt-приложения Фронтендер BIGPLAY — киберспортивной платформы на Nuxt — разбирался, почему главная страница отдаёт больше полумегабайта HTML. И выяснил: внутри торчит словарь переводов всего сайта — по 218 КБ на каждой странице. В статье он объясняет, откуда словарь взялся и как его выпилили: payload упал с 256 до 47 КБ. Дальше оптимизировать не стали…

9 Nov 2026, 09:07 UTC≈1,750 viewsread 11 November 2026
Photo

Расширение врёт, а байты решают: как Android-вьювер научился жевать двести с лишним форматов Автор пилит XanderFiles — смотрелку для Android, которая открывает больше двухсот расширений: от PDF и Excel до winmail.dat, подписанных .p7m, RAR с паролем, книг FB2, RAW с фотоаппаратов, билетов Wallet, снимков КТ и рисунков CorelDRAW. Хвост после точки он считает ненадёжной штукой, поэтому формат палится по первым байтам …

8 Nov 2026, 17:07 UTC≈1,970 views8 reactionsread 11 November 2026
Photo

MIT залил свежак: бесплатный The Missing Semester обновлён до версии 2026 года Теперь там учат не только возиться с инструментами разработчика, но и работать с ИИ-агентами. Курс про практические навыки, которым при обучении программированию обычно почти не уделяют времени. Старт — Shell, Git, отладка и профилирование. Потом переходят к выпуску софта, качеству кода и современным инструментам разработки с ИИ: Claude …

❤8

8 Nov 2026, 14:52 UTC≈1,940 views7 reactionsread 11 November 2026
Photo

Redux Toolkit движется к 3.0 Mark Erikson выкатил роадмап Redux Toolkit. Третий мажор ждём где-то через 6–8 месяцев: релиз будет ESM-only, а по масштабу ломки автор ставит его рядом с переездом на React 19. В придачу к роадмапу там есть экскурс в историю Redux. До этого будет серия 2.x — она и подложит базу под мажор. Первый на очереди — 2.14, уже на этой неделе. React Status #496 👉 Telegram | Max | 🌥 Claude и др…

👎7

6 Nov 2026, 17:07 UTC≈2,200 views8 reactionsread 11 November 2026
Photo

Мой базовый CSS-набор, который тащу в каждый проект На Хабре появилась заметка от фронтендера: он выкатил тот набор стилей, что юзает из проекта в проект. И сразу честно предупреждает — велосипед не изобретал, просто собрал в кучу то, чем пользуется сам. Внутри — старые приёмы, штуки, о которых мало кто в курсе, и свежие решения. На оригинальность никто не претендует, зато всё с прицелом на практику. Читать далее …

❤5👍2👎1

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

Posts edited after publishing

@frontendnoteschannel_ru edited 1 post after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.

An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.

First edit seen
22 August 2026
Most recent edit
22 August 2026

Posts recorded as deleted after publishing

We recorded 61 posts on @frontendnoteschannel_ru as deleted — posts this register held that were missing from the channel’s public page on two separate reads, taken from different network addresses at least an hour apart.

A deletion is not wrongdoing. This register can see that a post it held is no longer on the channel’s public page, and when — not why. Expired ad placements, reposts, rotating links and corrections all look the same. This is a count of recorded detections, not an exact total: it misses deletions we could not see, because only a post we held and later re-read inside the page can be seen to go, and it may include a small number of wrong records. How this is measured.

First seen missing
7 August 2026
Most recent seen missing
11 November 2026
Median time before seen missing
2 days
Seen missing in the last 30 days
15

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 7 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.

Channels Telegram recommends alongside this one

Telegram’s own answer, not this register’s. When this register asks Telegram’s API what is similar to this channel, this is the list it returns, in the exact order Telegram returns it — never re-sorted by subscribers or by anything else this register measures. The relationship, and the order, are Telegram’s; we record them and date them, and make no claim of our own about which of these channels actually resemble this one.

FrontEndDev
@front_end_dev · 25,428
#1
Node.JS [ru] | Серверный JavaScript
@we_use_js · 10,605
#2
Senior Frontend - javascript, html, css
@seniorFront · 23,495
#3
Frontend Portal
@FrontendPortal · 36,268
#4
Frontend | Вопросы собесов
@easy_javascript_ru · 17,284
#5
Библиотека фронтендера | Frontend, JS, JavaScript, React.js, Angular.js, Vue.js
@frontendproglib · 20,611
#6
React JS
@react_tg · 16,049
#7
Веб-страница
@tproger_web · 22,164
#8
Логово верстальщика
@webdevlair · 7,813
#9
Yandex for Frontend
@yandex4frontend · 10,816
#10
Frontend — вакансии и стажировки
@senior_frontender · 9,228
#11
Будни разработчика
@htmlshit · 14,341
#12
Владилен: IT в эпоху AI
@vladm · 39,328
#13
Code Ready | Frontend
@code_ready · 21,534
#14
Frontend Interview - собеседования по Javascript / Html / Css
@frontendInterview · 10,249
#15
artalog
@artalog · 4,235
#16
Frontender Libs - обзор библиотек JS / CSS
@sWebDev · 7,338
#17
Сова пишет…
@sergeysova · 2,983
#18
Senior Frontend Developer | JavaScript, React, HTML & CSS
@senior_front · 18,893
#19
mefody.dev
@mefody_dev · 5,386
#20
Javascript
@javascriptv · 16,664
#21
JavaScript заметки
@notesjs · 7,359
#22
Frontend по-флотски 👨‍💻 | AI & Modern Dev
@frontend_pasta · 4,425
#23
Заметки про React
@ru_react_notes · 3,387
#24
JavaScript | LeetCode
@easy_frontend_task · 8,179
#25
Макеты для верстки
@figma2html · 44,399
#26
Фронтендер от бога
@godofjs · 3,367
#27
Фронтенд Гайд
@frontendGA · 7,650
#28
Zar Zakharov | Lead Developer
@zarzakharov · 4,435
#29
Руслан Куянец | Reactify x YeaHub
@reactify_IT · 6,259
#30
Верстальщик от бога
@godinhtml · 9,189
#31
Frontend Головного Мозга
@frontend_mind · 6,228
#32
WebDEV
@webb_dev · 8,209
#33
Frontend Tests & Tasks
@Frontend_Task · 8,251
#34
Frontend Info
@frontend_info · 5,247
#35
melikhov.dev
@melikhov_dev · 4,760
#36
Настоящий JavaScript
@true_js · 5,793
#37
IT Юмор
@ithumor · 60,047
#38
Programmer & IT Memes
@itmemes · 121,903
#39
Frontend | Тесты
@easy_frontend_tests · 7,021
#40
JavaScript Job | Вакансии | Стажировки
@JScript_jobs · 12,736
#41
Гайды по JavaScript | Программирование
@guides_js · 7,071
#42
Html Gram
@HtmlGram1 · 8,983
#43
Dev News от Максима Соснова
@msosnovfeed · 2,777
#44
Simple Frontend | JS, CSS, HTML
@simple_frontend_tg · 7,372
#45
Катерина | Про Frontend
@katerina_profrontend · 2,799
#46
Типичный программист
@tproger · 78,009
#47
React Job | JavaScript | Вакансии
@job_react · 16,820
#48
Web Stack
@web_stack · 4,069
#49
Уставший техдир
@tired_glebmikheev · 18,460
#50
CodePen Amazing
@codepen_amazing · 4,705
#51
React Frontend | YeaHub
@yeahub_frontend · 3,113
#52
NOP::Nuances of Programming
@nuancesprog · 55,956
#53
Анимируй
@animate_css · 6,372
#54
КИРИЛЛ ПОЗДНЯКОВ | ДЖАВАСКРИПТИЗЕРЫ
@jswrl · 5,972
#55
Job for Frontend (JavaScript + Node.js) Developers
@forfrontend · 13,854
#56
Frontend | Вакансии
@frontend_vakansii · 15,058 (as read 6 September 2026)
#57
АйТи Синяк
@it_sin9k · 2,149
#58
Сайтодел | GitHub, Верстка, Сайты, Вайбкодинг
@sitodel · 25,423
#59
JavaScript test
@js_test · 9,582
#60
Max [RED Group x htmllessons]
@redgroup · 7,930
#61
Javascript jobs — вакансии по фронтенду, джаваскрипт, React, Angular, Vue
@jsdevjob · 9,749
#62
Хабр
@habr_com · 134,497
#63
Frontend разработчик
@frontend_1 · 10,262
#64
Kobezzza. База в программировании
@kobezzza_channel · 3,960
#65
PurpleSchool - обучение frontend, backend, devops, mobile
@purple_code_channel · 7,612
#66
Задачи по Frontend
@frontendquestions · 6,636
#67
🦜 on the web
@parrotontheweb · 2,077
#68
Простой JavaScript
@simple_js · 4,701
#69
Библиотека программиста
@proglibrary · 77,612
#70
IT Portal
@IT_Portal · 119,243
#71
Евгений Паромов
@cleanfrontend · 3,633
#72
A?.Frontend Community
@alfa_frontend · 3,238
#73
Антон Непша.js
@nepshajs · 2,898
#74
For Web — фронтенд, дизайн, программирование
@forwebdev · 12,960
#75
КодВеб | Дизайн База
@codewebx_it · 4,431
#76
Проекты на Javascript | HTML | CSS
@wb_code · 4,313
#77
Виталий и Платформа
@web_platform · 1,791
#78
Эксплойт
@exploitex · 2,022,997
#79
🧊 siberiacancode x IT-ХОЗЯЕВА
@siberiacancode · 3,427
#80
xCode Journal
@xCode_Journal · 13,767
#81
codepen.js
@codepen_js · 8,706
#82
Бэкдор
@whackdoor · 1,538,229
#83
Rozetked
@rozetked · 646,921
#84
GitHub Community
@github · 154,995
#85
CodeCamp
@codecamp · 177,629
#86
Код.ру
@d_code · 405,444
#87
Веб-стандарты
@webstandards_ru · 13,784
#88
CSS доширак
@css_doshik · 4,539
#89
Пекарня
@pekagame · 1,117,922
#90
Говнокод
@g_code · 14,805
#91
MoscowJS
@moscowjs · 3,079
#92
JavaScript тесты
@tests_js · 3,952
#93
r/ретранслятор
@retra · 165,780
#94
Двач
@dvachannel · 969,331
#95

Read from Telegram’s recommendation API, most recently 6 September 2026. Telegram holds a list like this for a small and growing share of the register — how this is measured, and why most channel pages show nothing here.

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.

Senior Frontend Developer | JavaScript, React, HTML & CSS
@senior_front · 18,893
Telegram ranks this channel #1 of 90 here — alongside 89 others — read 2 October 2026
Senior Frontend - javascript, html, css
@seniorFront · 23,495
Telegram ranks this channel #1 of 89 here — alongside 88 others — read 17 September 2026
FrontEndDev
@front_end_dev · 25,428
Telegram ranks this channel #1 of 95 here — alongside 94 others — read 13 September 2026
Сайтодел | GitHub, Верстка, Сайты, Вайбкодинг
@sitodel · 25,423
Telegram ranks this channel #2 of 89 here — alongside 88 others — read 13 September 2026
Библиотека фронтендера | Frontend, JS, JavaScript, React.js, Angular.js, Vue.js
@frontendproglib · 20,611
Telegram ranks this channel #3 of 93 here — alongside 92 others — read 25 September 2026
Веб-страница
@tproger_web · 22,164
Telegram ranks this channel #3 of 96 here — alongside 95 others — read 20 September 2026
Владилен: IT в эпоху AI
@vladm · 39,328
Telegram ranks this channel #4 of 96 here — alongside 95 others — read 30 August 2026
Code Ready | Frontend
@code_ready · 21,534
Telegram ranks this channel #7 of 89 here — alongside 88 others — read 23 September 2026
Frontend Portal
@FrontendPortal · 36,268
Telegram ranks this channel #7 of 90 here — alongside 89 others — read 1 September 2026
Макеты для верстки
@figma2html · 44,399
Telegram ranks this channel #8 of 90 here — alongside 89 others — read 27 August 2026
NOP::Nuances of Programming
@nuancesprog · 55,956
Telegram ranks this channel #10 of 84 here — alongside 83 others — read 23 August 2026
Front End World
@front_end_first · 25,623
Telegram ranks this channel #16 of 90 here — alongside 89 others — read 13 September 2026
FrontEnd Development
@fedevelopment · 28,445
Telegram ranks this channel #17 of 88 here — alongside 87 others — read 9 September 2026
True Figma
@true_figma · 25,617
Telegram ranks this channel #22 of 88 here — alongside 87 others — read 13 September 2026
Вайб-кодинг
@vibecoding_tg · 79,346
Telegram ranks this channel #26 of 85 here — alongside 84 others — read 1 September 2026
webguild - українська IT-спільнота 🇺🇦
@webguild · 50,413
Telegram ranks this channel #28 of 86 here — alongside 85 others — read 24 August 2026
Английский для программиста | EnglishScript
@EnglishScript · 44,381
Telegram ranks this channel #32 of 82 here — alongside 81 others — read 27 August 2026
Типичный программист
@tproger · 78,009
Telegram ranks this channel #33 of 95 here — alongside 94 others — read 19 August 2026
Fullstack / Software Job Offers
@runello_rus_webdevelopment · 24,190
Telegram ranks this channel #37 of 93 here — alongside 92 others — read 17 September 2026
Porscode | CMD
@porscode_tg · 28,099
Telegram ranks this channel #37 of 77 here — alongside 76 others — read 9 September 2026
Open IT | Архив
@openit_archive · 18,760
Telegram ranks this channel #41 of 59 here — alongside 58 others — read 5 October 2026
[404] — программирование
@procode404 · 40,080
Telegram ranks this channel #44 of 83 here — alongside 82 others — read 30 August 2026
Книжное хранилище
@knijnoe_xranilishe · 19,509
Telegram ranks this channel #50 of 73 here — alongside 72 others — read 30 September 2026
Библиотека программиста
@proglibrary · 77,612
Telegram ranks this channel #64 of 82 here — alongside 81 others — read 19 August 2026

This channel appears in 26 seed channels' Telegram-generated recommendation lists in total, of which the 24 where it ranks highest are shown above. 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 November 2026 — this entry's latest reading, not the date you are reading this.

“Frontender's notes [ru]” (@frontendnoteschannel_ru), 30,770 subscribers as measured 9 November 2026. Telegram Register, tgregister.com/channel/frontendnoteschannel_ru.

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.