Telegram RegisterThe public register of Telegram

Channel

Frontend Status

@FrontendStatus

On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry

277subscribers

+0 since we began measuring on 8 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1001586646144
TypeChannel
Username@FrontendStatus
CreatedBetween 1 August 2021 and 31 January 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live9 August 2026
Measurements held2
On Telegramt.me/FrontendStatus

Growth

2778 Aug 2026, 02:48 — 277 subscribers8 Aug 2026, 08:35 — 277 subscribers8 Aug 2026, 02:488 Aug 2026, 08:35
2 measurements taken within a single day. 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 276–278 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
8 Aug 2026, 08:35277no change
8 Aug 2026, 02:48277first reading

Engagement

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

What this channel posts

Photos
1
Links
22

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

340 reactions across 20 posts, in 17 distinct kinds. The most used accounts for 31.8% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
10831.8%
🔥10731.5%
💘3911.5%
👍3710.9%
🎉247.06%
72.06%
😍61.76%
🤝20.588%
🥰20.588%
10.294%
❤‍🔥10.294%
🍓10.294%
🍾10.294%
👏10.294%
💯10.294%
😁10.294%
🤩10.294%

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 20 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 340reactions 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 4 February 2026 to 16 June 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.

Recent posts

16 Jun 2026, 07:52 UTC241 views14 reactionsread 8 August 2026

Ого! Это же свежачок от Frontend Status! Что там у нас? Ооооо, браузерный гейминг в WASM+WebGL+WebGPU, уязвимости Next, ещё пара способов центрировать DIV как синьор, куча новостей про Tanstack и многое другое!) лайк лайк репост польза 👻 https://habr.com/ru/articles/1047986/

6🎉3🔥3💘2

4 Jun 2026, 09:44 UTC350 views14 reactionsread 8 August 2026

Срочные новости! вышел семнадцатый дайджест!) Новости стандартов,браузеров и фреймворков, нюансы безопасности, хаки и личный опыт - всё доступно по ссылочке снизу🔥 https://habr.com/ru/articles/1043510/

7🔥4💘2🎉1

25 May 2026, 13:48 UTC438 views16 reactionsread 8 August 2026

Скучали?) мы тоже! Держите свежий дайджест, куда вошло интервью с создателем NextJS, атаки на NPM, сбор локального AI сервера и даже обзор обновлений популярных репозиториев!) Го читать: https://habr.com/ru/articles/1039126/

🔥75👍2💘2

9 May 2026, 12:35 UTC342 views12 reactionsread 8 August 2026

Если вы предпочитаете отдыху нагрузку, то тут Салех Мубашар разбирает альтернативы !important: cascade layers через @layer (между слоями специфичность вообще не работает), :is(#unused-id, .nav-link) для подъёма до id-уровня и :where() для обнуления до 0,0,0.

4💘3🔥3🤝2

6 May 2026, 17:59 UTC282 views12 reactionsread 8 August 2026

Первый майский выпуск, тёплый и классный как погода за окном, как стаканчик холодной колы под лучами палящего солнца, как мороженка в парке, как ветерок у скамейки в тенёчке!) https://habr.com/ru/articles/1032276/ В программе постарались равномерно распределить новости по привычным рубрикам и выделить самые интересные или значимые. 14 рубрик, 15й выпуск - лучшее, что может быть в этот вечерок!)

🔥63🎉2💘1

27 Apr 2026, 17:12 UTC659 views14 reactionsread 8 August 2026

State of Vue, препарирование функциональщины в JS, современный CSS для тех, кто не читал наши предыдущие выпуски и многое другое в новом сочном дайджесте!) https://habr.com/ru/articles/1028734/ 14, вуху!

5👍4🔥3👏1💘1

18 Apr 2026, 15:10 UTC325 views14 reactionsread 8 August 2026

console. log("Hello, world, это Frontend Status!") Пи-хо, соратники! новый сборник новостей готов влететь в ваш выходной и напомнить о важности удержания руки на пульсе индустрии! Что же там сегодня?) погнали смотреть! https://habr.com/ru/articles/1025036/

5👍4🔥3🍾1💘1

9 Apr 2026, 12:46 UTC848 views14 reactionsread 8 August 2026

Привет! Это 12-й выпуск Frontend Status - дайджеста по фронтенд-разработке. В этом выпуске: 📺 Крупные релизы и видео: Babylon.js 9.0 и доклад Таннера Линсли про TanStack Start. 🤖 AI в проде без розовых очков: как агенты «видят» веб, что не так с персонами в промптах и почему Cloudflare меняет подход к кэшу. 🛡 Supply chain снова в фокусе: пауза bug bounty в Node.js, кейс с axios и практичные меры защиты зависимос

🔥6💘4😍3👍1

3 Apr 2026, 08:08 UTC842 views16 reactionsread 8 August 2026

Не буксуй в пятницу - отрасль летит вперёд!) Новость за новостью: атака GlassWorm прячет исполняемый код в невидимых Unicode-символах внутри npm-пакетов, Эдди Османи разбирает, как координировать оркестр из нескольких AI-агентов вместо одного, а Темани Афиф соединяет два элемента стрелкой на чистом CSS Anchor Positioning. Chrome 147 привёз scoped view transitions, data-testid назвали признаком недоступности, и отдел

🔥6🎉54💘1

27 Mar 2026, 08:18 UTC419 views28 reactionsread 8 August 2026
Photo

ЮБИЛЕЙ! 10й выпуск готов! Теперь добавили ещё источников с хабра, стараемся дополнить и русскоязычными статьями!) В программе на сегодня страница на полсотни мегабайт как норма, аниме против Marvel, официальные скиллы для Angular, математика на CSS и как исправить глупый код от агента - и ещё более двух десятков новостей!) Всё для вас, дорогие ❤️ https://habr.com/ru/articles/1015700/

10🔥9💘6🎉2🍓1

20 Mar 2026, 07:37 UTC463 views9 reactionsread 8 August 2026

Привет! Это девятый выпуск Frontend Status — дайджеста по фронтенд-разработке. В этом выпуске: 📺 Разговор с Машей Кондрашиной из Авито о том, что в IT больше не спорят из-за технологий. 🤖 VS Code переходит на еженедельные релизы благодаря AI-агентам, Chrome объясняет разницу между MCP и WebMCP, а Эдди Османи вводит термин «comprehension debt». ⚛️ React получает shadcn/cli v4 с режимом для агентов, SvelteKit лови

🔥6💘21

17 Mar 2026, 09:57 UTC272 views10 reactionsread 8 August 2026

Если вы не знаете, что выбрать для реализации тултипа, то почитайте гайд по выбору Popover или Dialog, где сравниваются их API, возможности, семантика и DX!)

42💘2🔥2

Showing the 12 most recent of 20 posts we hold for @FrontendStatus. 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 — 870,397 of 1,169,250entries 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 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 8 August 2026 — this entry's latest reading, not the date you are reading this.

“Frontend Status” (@FrontendStatus), 277 subscribers as measured 8 August 2026. Telegram Register, tgregister.com/channel/FrontendStatus.

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.