Telegram RegisterThe public register of Telegram

Channel

Антон Непша.js

@nepshajs

On this record: Growth · Engagement · Reactions · Stars · Posts · Citations · Cite this entry

2,943subscribers

+2 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1002071543667
TypeChannel
Username@nepshajs
CreatedBetween 1 November 2023 and 31 May 2024— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live13 August 2026
Measurements held4
Confirmed unchanged1 time, most recently 13 August 2026
On Telegramt.me/nepshajs

Growth

2,9412,9442,942.56 August 2026 — 2,941 subscribers7 August 2026 — 2,941 subscribers10 August 2026 — 2,944 subscribers13 August 2026 — 2,943 subscribers2,9436 August 202613 August 2026
4 measurements spanning 7 days, net +2. 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 2,941–2,944 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
13 Aug 2026, 13:472,943-1
10 Aug 2026, 08:512,944+3
7 Aug 2026, 02:142,941no change
6 Aug 2026, 14:362,941first reading

Engagement

20 posts held, back to 28 August 2025the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 2 pagesof Telegram’s post history, 20 posts per page.

ERR · 30 days
63.6%
avg views ÷ 2,943 subscribers
Avg views / post
1,870
3 posts measured
Reaction rate
2.44%
reactions ÷ views · ER floor
Posts in window
3
of 20 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.

What these figures were computed from
WindowRolling 30 days · latest post in window 30 July 2026
Posts held20 (28 August 202530 July 2026)
Views total5,616
Reactions total137
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken7 Aug 2026, 15:59 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.

Reaction mix

1,078 reactions across 20 posts, in 25 distinct kinds. The most used accounts for 32.6% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🔥35132.6%
❤‍🔥19818.4%
custom 540433706772123650019117.7%
👍968.91%
756.96%
😁474.36%
🤯302.78%
💘222.04%
🐳121.11%
90.835%
👎90.835%
👌80.742%
🎉60.557%
👻30.278%
💩30.278%
🤝30.278%
🥰30.278%
🍾20.186%
😢20.186%
😱20.186%
5 further kinds60.557%

Custom emoji. One row above is a Telegram custom emoji, which the public preview renders as an element carrying only a numeric id — no character, and no image we can reach. The id is printed as-is rather than substituted with a look-alike glyph, because a stand-in would be our invention showing where a measurement should be. The count beside it isTelegram’s.

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 1,078reactions 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 28 August 2025 to 30 July 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
37
across the posts below
Posts paid on
12
of 20 we hold a reading for · 60%
Most on one post
13
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @nepshajs. 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 28 August 2025 to 30 July 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

30 Jul 2026, 14:05 UTC966 views43 reactions1 Starread 7 August 2026

Моё хобби — менять названия полей в тулах и смотреть, как это влияет на качество заполнения тулов данными, когда модель эти тулы вызывает. Потому что влияние там действительно есть)) Поначалу это влияние может быть незаметным, но на масштабе в сотни тестовых вызовов оно становится ощутимым — можно увидеть, как в 5-10% случаев нейронка пропускает какое-нибудь поле, заполняет его не тем, чем нужно, или не вызывает тул

👍16custom 540433706772123650014❤‍🔥731😁1🙈1

20 Jul 2026, 11:45 UTC≈1,600 views31 reactionsread 7 August 2026

Расширил свой недавний доклад про работу с GigaChat API и расскажу его 25 июля на Технохаб конф в Санкт-Петербурге. Трансляции моего трека снова не будет, кстати, но в этот раз мой доклад будет записываться. В нём я поделюсь своим личным опытом перехода из фронтенд-разработки в разработку агентов, и на примере проблем, с которыми я сталкивался в последние два года, затрону архитектуру, observability и evals. Хочу е

🔥107custom 54043370677212365006❤‍🔥3👍3🍾1😢1

17 Jul 2026, 16:49 UTC≈3,050 views63 reactions3 Starsread 7 August 2026

Никогда ещё не уходил с митапа под таким сильным впечатлением, как вчера после JS x AI conf. Думаю, можно смело удалять JS из названия митапа, потому что теперь есть просто AI, а JS — неважная деталь реализации, и фокусироваться на одном только JS больше не получится. Больше всего меня удивило, что все спикеры вчерашнего митапа, работая независимо друг от друга, ни о чём друг с другом предварительно не договариваяс

❤‍🔥3311custom 540433706772123650095👍3🍾1👎1

15 Jul 2026, 20:21 UTC≈15,000 views41 reactions1 Starread 7 August 2026

Агентские фреймворки больше не нужны Мне стали часто попадаться видео автора Jake Van Clief, который в каждом видео говорит, что LangChain и прочие агентские фреймворки — это пустая трата времени, и что для разработки агента достаточно написать несколько .md-файлов. И я не смог не попасться на такой кликбейт, особенно если учесть, что я уже два года на LangChain разрабатываю. Вдруг я и правда зря время потратил)) П

🔥19custom 5404337067721236500105❤‍🔥3👍3🥰1

10 Jul 2026, 09:54 UTC≈2,080 views42 reactionsread 7 August 2026

JS x AI митап в Сбер.Среде Я тут недавно осознал, что я уже два с половиной года работаю с GigaChat API. Представляете, сколько всего я могу о нём рассказать? Вот 16 июля в Сбер.Среде и расскажу) И ещё немного поругаю слайды из своих предыдущих докладов. Правда, мой доклад транслироваться не будет, послушать его можно будет только вживую. Заодно Сбер.Среду посмотрите, если ещё не были у нас) Но основная часть мит

❤‍🔥16custom 54043370677212365009🔥6💘32👍2👻2💩1

10 Jul 2026, 09:53 UTC≈1,810 views22 reactions1 Starread 7 August 2026

Тра-та-та, а вот и я)))

🔥11❤‍🔥2💘2😱2custom 54043370677212365002🍌1👻1😁1

10 Mar 2026, 11:25 UTC≈3,520 views44 reactionsread 7 August 2026

OWASP Top 10 для агентских приложений Стандарты кибербезопасности Open Web Application Security Project есть не только для веба, но и для LLM-приложений и агентов. В OWASP Top 10 For Agentic Applications 2026 перечислены 10 самых опасных уязвимостей, которым могут быть подвержены разрабатываемые нами AI-агенты, а так же способы их предупреждения и устранения. Некоторые из уязвимостей прям любопытные: Есть, наприме

🔥23custom 540433706772123650010👍81🐳1💘1

9 Feb 2026, 17:49 UTC≈3,740 views55 reactions3 Starsread 7 August 2026

Инструменты дебага LLM-приложений на JS Опубликовали запись моего доклада с HolyJS 2025 Autumn, в котором я сравнивал observability- и дебаг-инструменты для LLM-приложений. Доклад теперь можно посмотреть на YouTube и в VK Видео, а презентацию я уже выгладывал в одном из предыдущих постов.

🔥29custom 540433706772123650012👍64💘3🐳1

7 Dec 2025, 18:58 UTC≈4,600 views58 reactions2 Starsread 7 August 2026

Как я искал утечку памяти в приложении на Python На этапе нагрузочного тестирования обнаружилась утечка памяти в контейнере приложения, которое я разрабатываю. До этого мне приходилось сталкиваться с утечками в JS в браузере, я даже доклад про это рассказывал, но в этот раз утечка была в агенте на Python, поэтому браузерные девтулзы там не помогли бы — пришлось разбираться в этом вопросе заново. Профилировать я на

🔥30custom 540433706772123650014😁8❤‍🔥3💘2🐳1

3 Dec 2025, 20:41 UTC≈6,090 views57 reactionsread 7 August 2026

Критическая уязвимость в React Разработчики React рекомендуют срочно обновиться до версий 19.0.1, 19.1.2 или 19.2.1 из-за критической уязвимости в React Server Components, обнаруженной 29 ноября. Под угрозу Remote Code Execution попадают все сайты, поддерживающие RSC, даже если на самих сайтах RSC не используются. Так же затронуты next, react-router, @vitejs/plugin-rsc и ещё ряд пакетов. Кому интересно, вот PR с и

🤯29👌8custom 54043370677212365008❤‍🔥6💩2🥰2🐳1💘1

21 Nov 2025, 14:07 UTC≈4,890 views51 reactions1 Starread 7 August 2026
Photo

Инструменты дебага LLM-приложений Вот так в одном слайде могут уместиться результаты полутора лет экспериментов (см. дату моего первого поста про LLM), сравнения разных инструментов и попыток найти наиболее удобный и подходящий под нужды нашего проекта Developer Experience. Sentry разворачивал через боль просто потому что уж очень хотелось посмотреть, что есть в их новой AI Agents Insights. LangChain-стек первый г

🔥27❤‍🔥10custom 540433706772123650082👍2🐳1💘1

14 Nov 2025, 20:03 UTC≈3,440 views92 reactions3 Starsread 7 August 2026

Сегодня этому каналу исполняется два года Перед тем, как писать этот пост, я решил для сравнения прочитать итоги, которые я подводил год назад. Боже, какой же я тогда был наивный, счастливый и беспечный)) В этот раз хочется обойтись без клише про «стимулы для развития», поэтому попытаюсь рассказать всё как есть) Из-за смены тех. стека мне стало сложнее совмещать канал с основной работой, поэтому посты стали выходи

🔥51custom 540433706772123650013👍106🎉6❤‍🔥3🐳1💘1

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

Citation-graph rank

Citation-graph rank — 241,482 of 1,480,688entries 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

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

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 13 August 2026 — this entry's latest reading, not the date you are reading this.

“Антон Непша.js” (@nepshajs), 2,943 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/nepshajs.

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.