Telegram RegisterThe public register of Telegram
Telegram profile photo for Deworker Pro

Channel

Deworker Pro

@deworkerpro

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

1,394subscribers

-3 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-1001227564461
TypeChannel
Username@deworkerpro
CreatedBetween 1 April 2018 and 31 August 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live16 August 2026
Measurements held4
Confirmed unchanged1 time, most recently 16 August 2026
On Telegramt.me/deworkerpro

Growth

1,3941,3971,395.56 August 2026 — 1,397 subscribers6 August 2026 — 1,397 subscribers13 August 2026 — 1,396 subscribers16 August 2026 — 1,394 subscribers6 August 202616 August 2026
4 measurements spanning 10 days, net -3. 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 1,394–1,397 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
16 Aug 2026, 21:541,394-2
13 Aug 2026, 13:061,396-1
6 Aug 2026, 18:011,397no change
6 Aug 2026, 17:521,397first reading

Engagement

20 posts held, back to 22 October 2025the 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 20 April 2026. An engagement rate over an empty window would be a number about nothing.

Recent posts

20 Apr 2026, 12:28 UTC920 viewsread 6 August 2026

До повышения цены осталось 8 часов 32 минуты

18 Apr 2026, 09:50 UTC≈1,080 viewsread 6 August 2026

Как это иногда случается во фронтенде, проект Create React App заброшен и пакет react-scripts давно не обновляется. Пришла пора перейти на современный быстрый сборщик и dev-сервер ViteJS. И произошло крупное обновление ESLint с переходом на новую структуру конфигурационного файла. Потому в сегодняшнем большом скринкасте доработаем E2E-тесты, обновимся до ESLint 10, перейдём на React 19, потом произведём поэтапную ми

15 Apr 2026, 13:17 UTC≈1,330 viewsread 6 August 2026

Вынес вопросы и ответы с дополнением в отдельную статью: https://elisdn.ru/blog/172/ai-and-oop

15 Apr 2026, 10:08 UTC≈1,290 viewsread 6 August 2026

В комментариях под видео внезапно образовалась продуктивная дискуссия. Интересные мысли вынес в https://t.me/elisdnru/124

9 Apr 2026, 16:12 UTC≈1,630 viewsread 6 August 2026

Мы с вами фрагментами изучали разные нюансы ООП в скринкастах по PHP и даже провели стрим по SOLID, но полной картины и сравнения с другими языками программирования не делали. В один или два стрима это всё вместить сложно. Потому придумал дополнить и повторить мой большой шестидневный интенсив, который проводил раньше на своём сайте elisdn.ru. И сейчас там сделал интеграцию с сайтом deworker.pro. Теперь для подписчик

8 Mar 2026, 16:50 UTC≈1,820 viewsread 6 August 2026

Следующий скринкаст уже записывается. Можно пока досмотреть большой прошлый из поста выше. Впереди доработанный третий стрим по SQL и обновлённый второй стрим по Kubernetes с переходом на новый Gateway API вместо рассмотренного в первой части Nginx Ingress. А сегодня у меня в ветке про шаманские админские бубны спонтанно записался рингтон про дебаг Kubernetes: https://t.me/elisdnru/115

4 Mar 2026, 09:28 UTC≈1,850 viewsread 6 August 2026

Обещанный большой скринкаст готов. Исправили недочёты инфраструктуры, довели до ума работу с SSH-ключами, сделали более удобный дистанционный деплой в Docker Swarm через SSH, перешли на Systemd Timers вместо Cron, разделили docker-entrypoint файлы, исправили конфликты доступа к файлам из Docker-контейнеров и доработали diff-проверки в пайплайне, чтобы они работали без ложных срабатываний при использовании внешнего к

24 Feb 2026, 15:29 UTC≈1,890 viewsread 6 August 2026

До повышения цены осталось 5 часов 30 минут

24 Feb 2026, 14:58 UTC≈1,690 viewsread 6 August 2026

Пора досказать недосказанное Доработка старых и активная разработка наших новых проектов с перестройкой под это других сервисов и инфраструктуры компании требует много усилий, но приносит много опыта в проектировании, разработке, оптимизации, деплое и мониторинге всего этого добра. За это время много чего было переработано и внедрено в каждом проекте и в кластере. С учётом вскрывшихся нюансов ещё раз переписали нов

26 Dec 2025, 09:11 UTC≈2,800 viewsread 6 August 2026

Проблема с платёжным шлюзом решена. Оплата иностранными картами снова работает.

25 Dec 2025, 16:16 UTC≈1,660 viewsread 6 August 2026
Forwarded from @elisdnruPhoto

Ай-я-я-яй, я... нигадяй. В день распродажи отвалился шлюз по приёму иностранных карт. Это я удачно новогоднюю распродажу запустил :)

25 Dec 2025, 15:41 UTC≈1,560 viewsread 6 August 2026

У шлюза по приёму иностранных карт наблюдаются проблемы. Его работа будет восстановлена их техподдержкой завтра утром. В связи с этим скидки продлеваем на один день вперёд. Оплата российскими картами работает успешно.

Showing the 12 most recent of 20 posts we hold for @deworkerpro. 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 — 235,302 of 1,480,975entries 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.

Republishes

Channels on the register whose posts this channel has forwarded.

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

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

“Deworker Pro” (@deworkerpro), 1,394 subscribers as measured 16 August 2026. Telegram Register, tgregister.com/channel/deworkerpro.

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.