Telegram RegisterThe public register of Telegram
Telegram profile photo for ElisDN.ru

Channel

ElisDN.ru

@elisdnru

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

672subscribers

-1 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1001269866320
TypeChannel
Username@elisdnru
CreatedBetween 1 April 2018 and 31 July 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live14 August 2026
Measurements held3
Confirmed unchanged1 time, most recently 14 August 2026
On Telegramt.me/elisdnru

Growth

672673672.56 August 2026 — 673 subscribers7 August 2026 — 673 subscribers14 August 2026 — 672 subscribers6 August 202614 August 2026
3 measurements spanning 8 days, net -1. 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 672–673 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
14 Aug 2026, 19:27672-1
7 Aug 2026, 01:51673no change
6 Aug 2026, 18:02673first reading

Engagement

20 posts held, back to 17 November 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.

Reaction mix

216 reactions across 8 posts, in 10 distinct kinds. The most used accounts for 34.7% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍7534.7%
🔥5625.9%
2210.2%
👎198.80%
👏177.87%
😁104.63%
🥴73.24%
💯62.78%
🤔31.39%
💊10.463%

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 8 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 216reactions 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 17 November 2025 to 20 April 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

20 Apr 2026, 12:28 UTC490 views6 reactionsread 6 August 2026

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

👎5😁1

15 Apr 2026, 12:54 UTC810 views7 reactionsread 6 August 2026

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

👏6👍1

15 Apr 2026, 09:53 UTC928 views48 reactionsread 6 August 2026

В мире где все уже пишут клаудкодом, кто-то еще хочет продать ООП. кек :) Одно другому не мешает. Если клаудкод попросить организовать проект более аккуратно по тем же принципам SOLID и GRAP, то получатся слабосвязанные самодостаточные модули. Это позволит для каждой задачи работать нейросетью изолированно в контексте небольшого модуля, а не всей кучи кода. Эта модульность экономит токены и избавляет от размазывани

👍41🥴5👎2

15 Apr 2026, 09:50 UTC731 views33 reactionsread 6 August 2026

​​⁠​​⁠DTO это по вашему не объект? Именно. Объект определяется смыслом, а не синтаксисом. DTO это не объект с инкапсуляцией и инвариантом, а структура для передачи данных. А то, что в каком-то языке программирования нет для передачи данных отдельных конструкций вроде struct или record и приходится тоже писать это как class – это особенности конкретного языка программирования. Отсюда же распространённые случаи того,

👍22💯6👎3🤔1🥴1

15 Apr 2026, 07:31 UTC722 views46 reactionsread 6 August 2026

Под видео с приглашением в YouTube написали общий комментарий: Дмитрий сейчас это не актуально, ИИ весь код пишет сам за нас и способен из новичка сделать профи за бесплатно, только стоит его попросить. И конкретный: ИИ любое ООП за 10 минут объяснит без утомительных 40 часового курса. Решил проверить и спросил, является ли DTO объектом. Ответ Google в режиме AI: Да, DTO (Data Transfer Object) является объектом

20🔥10👎9👍3🤔2🥴1😁1

9 Apr 2026, 15:37 UTC836 views8 reactionsread 6 August 2026

Давным-давно в 2016-ом году мы с вами провели три потока нашего шестидневного интенсива «Неделя ООП» про то, как интереснее использовать объектно-ориентированное прораммирование в своих проектах. И вот что придумалось: https://elisdn.ru/blog/171/oop-week-4

🔥8

8 Mar 2026, 14:52 UTC≈1,260 views38 reactionsread 6 August 2026
Video

Готово :) Дебажим Кубер шаманским бубнобаяном

🔥22😁8👏61💊1

8 Mar 2026, 14:10 UTC973 views30 reactionsread 6 August 2026
Video

Админский баян для классических произведений: Чёрный Кубер, чёрный Кубер Стоп системные огни Чёрный Кубер, чёрный Кубер Микросервис подними

🔥16👍8👏51

8 Mar 2026, 13:51 UTC875 viewsread 6 August 2026

Пока распеваюсь перед записью скринкаста, в соседнем чате баяним про админские бубны :) https://t.me/beerphp_spb/108262

24 Feb 2026, 15:32 UTC903 viewsread 6 August 2026

Продолжаем наши большие стримы. Добрались до рефакторинга и оптимизации SQL-запросов. Скоро буду ждать участников в эфире: https://t.me/deworkerpro/294

15 Jan 2026, 11:51 UTC≈1,210 viewsread 6 August 2026

В чате Альберта Степанцева сегодня схлестнулись про docker-контейнеры для запуска миграций и cron-задач. И снова поругали PHP-FPM :) Начало: https://t.me/php_russian_talks/49601

26 Dec 2025, 10:23 UTC≈1,300 viewsread 6 August 2026

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

Showing the 12 most recent of 20 posts we hold for @elisdnru. 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 — 184,821 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.

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

“ElisDN.ru” (@elisdnru), 672 subscribers as measured 14 August 2026. Telegram Register, tgregister.com/channel/elisdnru.

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.