Telegram RegisterThe public register of Telegram
Telegram profile photo for Web Stack

Channel

Web Stack

@web_stack

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

4,137subscribers

-30 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-1001397460337
TypeChannel
Username@web_stack
Created3 April 2018measured — cross-checked against a third-party dataset (TGDataset)
First recorded6 August 2026
Last confirmed live7 September 2026
Measurements held12
Confirmed unchanged1 time, most recently 7 September 2026
On Telegramt.me/web_stack

Growth

4,1374,1674,1526 August 2026 — 4,167 subscribers6 August 2026 — 4,167 subscribers10 August 2026 — 4,165 subscribers12 August 2026 — 4,163 subscribers15 August 2026 — 4,158 subscribers18 August 2026 — 4,155 subscribers21 August 2026 — 4,154 subscribers25 August 2026 — 4,152 subscribers28 August 2026 — 4,150 subscribers30 August 2026 — 4,146 subscribers3 September 2026 — 4,142 subscribers7 September 2026 — 4,137 subscribers6 August 20267 September 2026
12 measurements spanning 33 days, net -30. 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 4,133–4,172 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
7 Sept 2026, 19:194,137-5
3 Sept 2026, 00:174,142-4
30 Aug 2026, 20:474,146-4
28 Aug 2026, 03:284,150-2
25 Aug 2026, 00:354,152-2
21 Aug 2026, 03:114,154-1
18 Aug 2026, 10:124,155-3
15 Aug 2026, 18:374,158-5
12 Aug 2026, 17:534,163-2
10 Aug 2026, 03:314,165-2
6 Aug 2026, 07:154,167no change
6 Aug 2026, 07:084,167first reading

Engagement

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

Reaction mix

90 reactions across 20 posts, in 10 distinct kinds. The most used accounts for 33.3% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍3033.3%
🔥2426.7%
1718.9%
💯44.44%
🤡44.44%
🤯44.44%
💩22.22%
😁22.22%
🤔22.22%
🙏11.11%

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 90 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 5 April 2026 to 2 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.

Telegram Stars

Stars received
2
across the posts below
Posts paid on
2
of 20 we hold a reading for · 10%
Most on one post
1
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @web_stack. 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 20 most recent posts we hold for this entry, published 5 April 2026 to 2 June 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.

Recent posts

2 Jun 2026, 08:45 UTC627 views8 reactionsread 8 August 2026
Photo

Blue: компиляция JavaScript в нативные бинарники Blue компилирует ваш JS в C++ и собирает самостоятельный нативный исполняемый файл: нативные окна, файловая система и HTTP-серверы без Electron и без Node.js во время выполнения. https://bluejs.dev/

👍3🤯31😁1

31 May 2026, 08:45 UTC695 views3 reactions1 Starread 8 August 2026
Photo

Релиз pnpm 11.1: подписи audit, gh-префикс и новые флаги для CI Добавлены audit signatures для проверки ECDSA-подписей registry, а также поддержка установки пакетов из GitHub Packages через встроенный gh: префикс и алиасы named registries в pnpm-workspace.yaml. https://github.com/pnpm/pnpm/releases/tag/v11.1.0

3

29 May 2026, 15:55 UTC743 views4 reactionsread 8 August 2026
Photo

Wakaru: разбор минифицированных JavaScript бандлов на модули Wakaru помогает восстановить структуру production-кода: распаковывает бандлы, возвращает имена и импорты с поддержкой source map, а также пытается восстановить транспиляцию/минфикацию. https://github.com/pionxzh/wakaru

👍2🔥2

15 Apr 2026, 12:20 UTC≈1,170 views6 reactionsread 8 August 2026
Photo

Reatom: ультимативный менеджер состояния и логики для виджетов и SPA Reatom дает реактивное управление состоянием без прокси, с атомами и computed, а также мощными эффектами для async с отменой, ретраями и кэшированием. Подходит для небольших виджетов и больших приложений, поддерживает расширения и TypeScript, а ядро весит около 2 KB gzipped. https://github.com/reatom/reatom

🔥5👍1

15 Apr 2026, 08:45 UTC986 views2 reactionsread 8 August 2026

Визуализатор event loop для JavaScript Интерактивная визуализация микрозадач, макрозадач и порядка выполнения в браузере, которая позволяет быстрее понять асинхронность. Отлично подходит для отладки и обучения, когда нужно увидеть реальную очередность без догадок. https://event-loop-visualizer-ruby.vercel.app/

1👍1

14 Apr 2026, 12:20 UTC875 views5 reactionsread 8 August 2026
Photo

Бесплатный онлайн анализатор логов в браузере Открывайте лог файлы до 10GB+ прямо в браузере без загрузки, с приватностью и быстрым поиском. Есть форматирование в JSON и агрегация ошибок для удобной диагностики. https://www.logvoyager.cc/

2👍1💯1🔥1

14 Apr 2026, 08:45 UTC722 views2 reactionsread 8 August 2026
Photo

Как с помощью ИИ превращать макеты Figma в production код ИИ сам по себе не генерирует код в рамках дизайн системы, поэтому сделали MCP, который описывает компоненты, токены и правила доступности в машинном виде, и агентский пайплайн на LangGraph, который пошагово конвертирует Figma в готовые компоненты без ручной правки. https://engineering.monday.com/how-we-use-ai-to-turn-figma-designs-into-production-code/

1💩1

13 Apr 2026, 12:20 UTC646 views1 reactionsread 8 August 2026

Разработка серверных приложений на Vite через плагин vavite vavite позволяет использовать Vite как транспайлер и бандлер для серверного кода, упрощая разработку и сборку SSR и не только SSR сценариев. Подключайте плагин в vite.config, создавайте entry.server.ts и получайте быстрый dev с HMR, а в production запускайте сервер отдельно. https://github.com/cyco130/vavite

👍1

13 Apr 2026, 08:45 UTC627 views2 reactionsread 8 August 2026
Photo

Безопасность Node.js март 2026 Обновления для веток 25.x, 24.x, 22.x и 20.x закрывают несколько уязвимостей в TLS, HTTP обработке, permission model, URL парсинге и HMAC валидации, включая сценарии с DoS, крашем процесса и потенциальной утечкой через timing. https://nodejs.org/en/blog/vulnerability/march-2026-security-releases

👍2

12 Apr 2026, 12:20 UTC671 views8 reactionsread 8 August 2026
Photo

Скрытая цена копипаста кода в ChatGPT ИИ ускоряет разработку только на бумаге: исследование METR показало, что опытные разработчики на сложных задачах становятся на 19% медленнее, потому что теряют контекст и тратят время на отладку и уточнения. Главная проблема не в качестве генерации, а в workflow с постоянными переключениями и объяснениями того, что IDE и проект уже знают. https://dev.to/ziva/the-hidden-cost-of-

👍6💯1🙏1

12 Apr 2026, 08:45 UTC636 views3 reactionsread 8 August 2026
Photo

Куда исчезло 400 MiB в Node.js контейнере Кейс, в котором после перезапуска подов память у одного экземпляра Node.js резко прыгала дискретными шагами и больше не возвращалась. Анализ через /proc и V8 inspector показал, что рост сидит в private dirty anonymous памяти процесса и требует смотреть не только на heap, но и на реальную картину аллокаций в момент нагрузки. https://frn.sh/pmem/

👍2🤯1

10 Apr 2026, 08:45 UTC≈3,900 views4 reactionsread 8 August 2026
Photo

Три причины раздувания зависимостей в JavaScript Разбираем три типовых источника dependency bloat: поддержка древних рантаймов, защита от мутаций глобального окружения и кросс realm значения, из за которых в npm деревьях копятся лишние микропакеты. Узнаем, как начать чистить дерево без поломок. https://43081j.com/2026/03/three-pillars-of-javascript-bloat

🔥4

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

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.

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.

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.

FrontEnd Development
@fedevelopment · 28,790
Telegram ranks this channel #19 of 88 here — alongside 87 others — read 9 September 2026
Web Development
@webde · 31,984
Telegram ranks this channel #22 of 84 here — alongside 83 others — read 5 September 2026
NOP::Nuances of Programming
@nuancesprog · 56,702
Telegram ranks this channel #44 of 84 here — alongside 83 others — read 23 August 2026
Frontender's notes [ru]
@frontendnoteschannel_ru · 31,509
Telegram ranks this channel #49 of 95 here — alongside 94 others — read 6 September 2026

This channel appears in 4 seed channels' Telegram-generated recommendation lists 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 7 September 2026 — this entry's latest reading, not the date you are reading this.

“Web Stack” (@web_stack), 4,137 subscribers as measured 7 September 2026. Telegram Register, tgregister.com/channel/web_stack.

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.