Telegram RegisterThe public register of Telegram
Telegram profile photo for DOU #tech

Channel

DOU #tech

@dou_tech

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

11,772subscribers

+470 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of 10,000–31,623.

Register entry

Telegram ID-1001357366316
TypeChannel
Username@dou_tech
Created5 June 2020measured — cross-checked against a third-party dataset (ext.tg_channel)
First recorded6 August 2026
Last confirmed live8 September 2026
Measurements held27
Confirmed unchanged1 time, most recently 8 September 2026
On Telegramt.me/dou_tech

Growth

11,30211,77211,5376 August 2026 — 11,302 subscribers6 August 2026 — 11,302 subscribers7 August 2026 — 11,367 subscribers8 August 2026 — 11,364 subscribers9 August 2026 — 11,515 subscribers11 August 2026 — 11,623 subscribers12 August 2026 — 11,625 subscribers13 August 2026 — 11,629 subscribers14 August 2026 — 11,707 subscribers16 August 2026 — 11,709 subscribers17 August 2026 — 11,712 subscribers18 August 2026 — 11,716 subscribers19 August 2026 — 11,723 subscribers20 August 2026 — 11,720 subscribers21 August 2026 — 11,714 subscribers23 August 2026 — 11,712 subscribers25 August 2026 — 11,711 subscribers26 August 2026 — 11,716 subscribers28 August 2026 — 11,717 subscribers29 August 2026 — 11,718 subscribers30 August 2026 — 11,719 subscribers31 August 2026 — 11,721 subscribers1 September 2026 — 11,725 subscribers2 September 2026 — 11,726 subscribers3 September 2026 — 11,727 subscribers5 September 2026 — 11,767 subscribers8 September 2026 — 11,772 subscribers6 August 20268 September 2026
27 measurements spanning 34 days, net +470. 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 11,232–11,843 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 27
Measured (UTC)SubscribersChange
8 Sept 2026, 23:3911,772+5
5 Sept 2026, 13:3711,767+40
3 Sept 2026, 12:2011,727+1
2 Sept 2026, 02:4611,726+1
1 Sept 2026, 04:3611,725+4
31 Aug 2026, 02:2311,721+2
30 Aug 2026, 02:4511,719+1
29 Aug 2026, 04:2511,718+1
28 Aug 2026, 06:2311,717+1
26 Aug 2026, 01:5411,716+5
25 Aug 2026, 01:0411,711-1
23 Aug 2026, 12:2811,712-2
21 Aug 2026, 21:0511,714-6
20 Aug 2026, 13:3611,720-3
19 Aug 2026, 15:0211,723+7
18 Aug 2026, 11:3811,716+4
17 Aug 2026, 13:3511,712+3
16 Aug 2026, 04:3411,709+2
14 Aug 2026, 16:4711,707+78
13 Aug 2026, 10:3511,629first reading

Engagement

81 posts held, back to 31 July 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 46 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
20.6%
avg views ÷ 11,772 subscribers
Avg views / post
2,430
56 posts measured
Reaction rate
0.346%
reactions ÷ views · ER floor
Posts in window
56
of 81 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. It is computed over the 54 of 56 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 2 September 2026
Posts held81 (31 July 20262 September 2026)
Views total135,900
Reactions total454
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken3 Sept 2026, 00:27 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

576 reactions across 76 posts, in 8 distinct kinds. The most used accounts for 31.3% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍18031.3%
🔥13022.6%
10518.2%
😁8915.5%
😢264.51%
😱254.34%
👎203.47%
🤩10.174%

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 77 of the 81 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 576 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 81 most recent posts we hold, published 31 July 2026 to 2 September 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.

Advertising

Ad load
3.70%
3 of 81 posts carry an ad marker
Regulatory tokens
0
none — marked by hashtag only
Median views · ads
2,410
over 3 measured posts
Median views · rest
2,420
over 78 measured posts

An ad marker, not a judgement about a post. A post is counted here because it carries one of two explicit markings: an erid token, which Russian law has required on paid placements since 2022 and which is issued against a specific advertising contract, or a #реклама / #ad hashtag in the body, which is the channel declaring it itself. The first is documentary; the second is a self-declaration and is weaker. No classifier reads the text and decides — nothing on this site guesses that a post is an advertisement.

This is a floor, and it can only ever be a floor. A channel that runs paid placements without marking them produces no marker for us to count, and an unmarked ad is indistinguishable from an ordinary post on the public surface. The ad load above therefore means “the share of posts that declared themselves”, never “the share of posts that were paid for”. A low figure is not evidence of a channel that runs few ads.

Both figures are medians, and no ratio between them is published. Each is a view reading that actually occurred on a post, picked by percentile_disc rather than averaged, so one viral post cannot move it and no interpolated value is invented between two readings. The sample on one side is under five posts, which is too thin to compare. The two figures are shown side by side with the count behind each, and deliberately not divided into a headline like “ads get x% fewer views” — an arithmetic that is easy to print and, at this sample size, means nothing.

Measured over the 81 most recent posts we hold, published 31 July 2026 to 2 September 2026. Views are the latest single reading held for each post, and any reading at or above 1,000 is rounded by Telegram to three significant figures.

Recent posts

2 Sept 2026, 12:00 UTC≈1,290 views2 reactionsread 3 September 2026
Photo

Чи можна перетворити старий Kindle на повноцінний пульт для розумного дому? Богдан Свердлюк показує, як використати E-Ink екран електронної книжки для керування Home Assistant. У статті автор розбирає два сценарії: інтерактивний HTML-дашборд, який працює прямо в браузері Kindle без jailbreak, і онлайн-скрінсейвер із даними Home Assistant, для якого вже знадобиться модифікація пристрою. Також Богдан покроково проход

👎1😁1

1 Sept 2026, 14:03 UTC≈1,650 viewsread 3 September 2026
Photo

Олександр із Zfort Group зібрав свіжий фронтенд-дайджест із найцікавішими матеріалами тижня 🔥 Цього разу розбираємо, чому React-застосункам не завжди потрібно стільки JavaScript, як Angular Signals конкурують із RxJS і навіщо фронтендерам знову дивитися в бік JPEG XL. 👉 https://dou.ua/goto/mwQa

1 Sept 2026, 12:00 UTC≈1,730 views1 reactionsread 3 September 2026
Photo

Кирило Виноградов у своїй статті розбирає, чому одного MFA недостатньо для надійного захисту RDP у Windows Server. На практичних прикладах автор показує, як поєднати Windows Firewall, журнали подій, TLS, моніторинг і recovery-сценарії — та як уникнути ситуації, коли автоматичний захист блокує самих адміністраторів. 👉 https://dou.ua/goto/ubAk

👍1

1 Sept 2026, 09:00 UTC≈1,810 views8 reactionsread 3 September 2026
Photo

На форумі користувач з ніком flyman продовжує експерименти з бюджетним LoRa-зв’язком для віддаленого моніторингу. Цього разу автор збирає вузол MeshCore приблизно за $3 на базі nRF52840 і DX-LR30 та перевіряє, як його можна використати не лише для офлайн-чату, а й для контролю живлення, температури, тиску та інших параметрів. 👉 https://dou.ua/goto/V3uG

👍5😱3

31 Aug 2026, 10:00 UTC≈1,970 views5 reactionsread 3 September 2026
Photo

У багатьох із нас з часом з’являються власні маленькі (або й великі) автоматизації, які непомітно забирають на себе частину рутини — на роботі або в повсякденному житті. Це можуть бути скрипти, боти, автоматичні звіти, робота з файлами, домашні сценарії чи щось зовсім нестандартне. Діліться своїми прикладами в коментарях: що саме автоматизували, навіщо і чи користуєтеся цим досі? 👉 https://dou.ua/goto/a4XM

5

30 Aug 2026, 13:00 UTC≈2,070 views5 reactionsread 3 September 2026
Photo

Чи може мікроконтролер фактично «програмувати себе сам» — без хмарних API? Олександр Крижанівський зібрав локального AI-агента для STM32, який декомпонує задачу, редагує код у проєкті CubeMX, компілює його та сам прошиває плату через ST-Link. Усе працює офлайн на локальній LLM — від промпта до готової прошивки менш ніж за дві хвилини. 👉 https://dou.ua/goto/N9kJ

🔥5

30 Aug 2026, 10:00 UTC≈2,060 views5 reactionsread 3 September 2026
Photo

Сергій Моренець розбирає бібліотеку Junit Pioneer, яка позбавляє рутинної роботи та надає корисні фітчі, яких немає в JUnit. Автор описує її особливості, розповідає про досвід застосування у власних проєктах та наводить її переваги та недоліки. 👉 https://dou.ua/goto/Ib6Y

👍5

30 Aug 2026, 08:00 UTC≈2,070 views7 reactionsread 3 September 2026
Photo

Юрій Максименко показує, як зробити перші кроки з Docker у Laravel-проєкті без зайвого ускладнення. Автор пояснює, як за допомогою Laravel Sail створити compose.yaml, зібрати та запустити контейнери, працювати з Artisan усередині Docker і використовувати базові команди Docker Compose та Docker Engine. 👉 https://dou.ua/goto/FU3N

5🔥2

29 Aug 2026, 16:00 UTC≈2,060 views15 reactionsread 3 September 2026
Photo

Найприємніше — це коли бачиш такі відгуки під статтею від спільноти. Володимира Шельмука нещодавно написав статтю про те, як вибрати embedding-модель для української, коли готові бенчмарки не підходять. Автор розібрав усе на власному кейсі RAG-системи для українського законодавства — з тестами, цифрами й висновками. Хто ще не читав — запрошуємо до перегляду. 👉 https://dou.ua/goto/5aON

🔥11👎31

29 Aug 2026, 12:00 UTC≈2,020 views5 reactionsread 3 September 2026
Photo

Вивчили базовий Python, але відчуваєте, що без практики знання швидко розсипаються? Цього тижня в рубриці розповідаємо про Genepy — безкоштовний тренажер із вправами різної складності, автоматичною перевіркою коду та можливістю переглядати рішення інших користувачів. Тут можна попрактикувати базовий синтаксис, роботу з файлами, CSV, HTTP-запитами, класами, NumPy та іншими темами. Хороший варіант для тих, хто вже про

3👍2

29 Aug 2026, 10:01 UTC≈2,040 views3 reactionsread 3 September 2026
Photo

Денис Макогон розбирає Project Detroit, експериментальний проєкт OpenJDK, який інтегрує V8 із JVM через знайомий javax.script. Автор пояснює, навіщо Java-застосунку запускати JS поруч із собою, як це працює під капотом та де ховаються нюанси з продуктивністю та безпекою. 👉 https://dou.ua/goto/IFUi

3

29 Aug 2026, 08:00 UTC≈2,040 views5 reactionsread 3 September 2026
Photo

Що може одноплатник Radxa ROCK 5B+ у задачах комп’ютерного зору? Роман Лютіков у своєму дописі розбирає можливості плати на RK3588, показує її CPU, GPU та NPU, налаштовує систему, запускає YOLO і на практичному демо розбирає, як плата одночасно детектить і трекає близько 50 людей у кадрі. 👉 https://dou.ua/goto/zybH

👍4😱1

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

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

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.

DOU
@doucommunity · 42,154
Telegram ranks this channel #8 of 83 here — alongside 82 others — read 29 August 2026
Junior дайджест dou.ua
@junior_dou_ua · 50,135
Telegram ranks this channel #9 of 84 here — alongside 83 others — read 25 August 2026
EPAM Campus UA
@epamuniprogua · 31,705
Telegram ranks this channel #12 of 81 here — alongside 80 others — read 5 September 2026
Djinni (/◔ ◡ ◔)/
@djinni_official · 49,754
Telegram ranks this channel #53 of 87 here — alongside 86 others — read 26 August 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 8 September 2026 — this entry's latest reading, not the date you are reading this.

“DOU #tech” (@dou_tech), 11,772 subscribers as measured 8 September 2026. Telegram Register, tgregister.com/channel/dou_tech.

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.