Telegram RegisterThe public register of Telegram

Channel

DOU

@doucommunity

Verified by Telegram

On this record: Topic · Observations · Also posting the same content · Growth · Engagement · What this channel posts · Reactions · Posts · Posts edited after publishing · Citations · Telegram's recommendations · Cross-platform identity · Cite this entry

41,896subscribers

+145 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1001356582355
TypeChannel
Username@doucommunity
DescriptionВсе про українське ІТ Маєте питання, пропозиції або ідеї для статті — пишіть editors@dou.ua ❌ Рекламу на каналі не розміщуємо.
Created13 March 2018measured — cross-checked against a third-party dataset (ext.tg_channel)
First recorded6 August 2026
Last confirmed live12 August 2026
Measurements held8
Confirmed unchanged1 time, most recently 12 August 2026
On Telegramt.me/doucommunity

Topic

Technology — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-UD-Q6_K_XL, prompt version 1) read this channel’s own recent posts on 10 August 2026 and assigned it the closest of 31 fixed categories, at 100% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and why it has no browse page of its own yet.

Observations

These are measurements, not verdicts. Each one below states something we counted, alongside the evidence it was counted from, so you can check it rather than take it. None of them is graded: every observation this register holds is recorded at severity 0, because the precision of the detectors behind them has not been measured yet, and a rating we cannot support is worse than none. Read each as a fact about the data, not as a judgement about the channel. How we measure.

Content that also appears on other registered channels

Posts published here appear word for word on 1 other registered channel. The matching is on the text itself, not on Telegram’s forward marker, so it finds a copy whether or not it was labelled as one.

Matching posts — open both and compare (5 of the pairs behind the counts below)
Posted firstThenOverlapGap
@ai_dou/17134 Aug 2026, 14:00 UTC@doucommunity/17618 · this entry4 Aug 2026, 14:30 UTC1.0029 minutes
@doucommunity/17628 · this entry5 Aug 2026, 12:02 UTC@ai_dou/17165 Aug 2026, 12:02 UTC1.00under a minute
@ai_dou/17175 Aug 2026, 14:02 UTC@doucommunity/17631 · this entry5 Aug 2026, 14:02 UTC1.00under a minute
@doucommunity/17633 · this entry5 Aug 2026, 15:00 UTC@ai_dou/17185 Aug 2026, 15:00 UTC1.00under a minute
@ai_dou/17247 Aug 2026, 12:31 UTC@doucommunity/17669 · this entry7 Aug 2026, 14:30 UTC1.002.0 hours
Every channel this entry shares post bodies with
ChannelMatching postsText overlapTypical gapPublished first
@ai_dou5 (5/5 hand-verifiable sample passed)1.00under a minutethis entry (32)

Text overlap is the Jaccard coefficient over the set of distinct three-word phrases in the two bodies: 1.00 is identical wording, and the threshold for counting a pair at all is 0.70. Candidates are generated by simhash LSH (4 x 16-bit bands, exact Hamming <= 3) verified against the bodies with Jaccard over the SET of distinct 3-word shingles. Published first counts which side of each matching pair carries the earlier timestamp — in this corpus, which is the limitation directly below.

What this cannot establish

MEASURED, DOMINANT ERROR SOURCE: a post ingested before 2026-08-06 may have carried a forward header that was not recorded. A 45-pair hand-check against live t.me pages found 14 (31%) where the live page shows a forward header naming the other channel and the database has none, plus 4 more (9%) naming a third party. The text match itself was wrong 0 times out of 45. Read attribution_capture.items_in_trusted_window before treating the unattributed count as a claim.

Telegram lets a channel forward a post with a header naming the source, and we only began reliably recording that header on 2026-08-06. 1 of the 2 matches recorded here fall after that date and carried no header when we read them. The rest predate reliable capture and are not evidence either way.

“Published first” means first in this corpus. We hold 44 comparable posts for this entry, running 4 August 2026 to 7 August 2026. A channel we have read one page deep will look younger than a neighbour we have read in full, and the order would flip with no change in the underlying facts.

The detector’s own notes on this observation, as it recorded them. Names in this_style are fields of the underlying evidence record, which the plain-English paragraphs above read out for this entry.

  • Verbatim republication has three causes and the text separates only two: a clone/mirror, unattributed copy-paste, or BOTH channels copying a common third source that neither attributes. The spread filter (content held by at most 8 channels) reduces the third and does not remove it.
  • 'Earliest' means earliest IN THIS CORPUS. A channel ingested one page deep will look younger than a neighbour ingested in full; corpus_coverage above is there to be checked before the direction is believed.
  • shared_verified_est extrapolates the sampled pass rate over the full narrow match count; sampled/passed are the numbers actually measured.
  • Absence of a forward header is not proof of intent: Telegram lets a channel disable forward attribution, and a credit written in the body is not parsed as attribution here (mention_edge_either_way above is the closest available signal).

Across the whole group of 2, the earliest publisher we hold is @ai_dou. That is a statement about our reading window, not a claim of authorship.

Recorded under the key clone_mutual, last confirmed 7 August 2026. An observation that a later pass no longer finds is cleared, and a cleared observation is removed from this page rather than being shown struck through — we do not keep publishing a claim we have withdrawn. Dispute an observation.

Also posting the same content

This channel’s posts match, word for word or near enough, posts on 1 other registered channel, found by comparing text fingerprints across every channel on the register. That matching has been checked by hand against the live Telegram pages and found reliable — 0 wrong of 45 pairs re-read.

Which channel, if either, published first is deliberately not shown. The same hand-check found that reading wrong 18 of 45 times — 60%, no better than a coin flip — because it depends on how deep our own crawl happened to reach into each channel’s history, not on when the content was actually first posted. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Word-for-word matching has several ordinary explanations besides copying — a channel mirroring itself, an unattributed repost, or two channels independently repeating the same wire story — and this measurement cannot tell those apart. How this is measured.

Growth

41,75141,89641,823.56 August 2026 — 41,751 subscribers6 August 2026 — 41,751 subscribers7 August 2026 — 41,753 subscribers8 August 2026 — 41,789 subscribers9 August 2026 — 41,818 subscribers10 August 2026 — 41,838 subscribers11 August 2026 — 41,860 subscribers12 August 2026 — 41,896 subscribers6 August 202612 August 2026
8 measurements spanning 6 days, net +145. 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 41,729–41,918 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
12 Aug 2026, 12:2441,896+36
11 Aug 2026, 09:2441,860+22
10 Aug 2026, 07:4341,838+20
9 Aug 2026, 05:0241,818+29
8 Aug 2026, 03:2441,789+36
7 Aug 2026, 02:1541,753+2
6 Aug 2026, 04:0041,751no change
6 Aug 2026, 03:5341,751first reading

Engagement

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

ERR · 30 days
12.5%
avg views ÷ 41,896 subscribers
Avg views / post
5,260
108 posts measured
Reaction rate
0.929%
reactions ÷ views · ER floor
Posts in window
110
of 110 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 12 August 2026
Posts held110 (4 August 202612 August 2026)
Views total567,670
Reactions total5,275
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken12 Aug 2026, 20:20 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.

What this channel posts

Photos
12,500
Videos
501
Links
15,400

Lifetime counters from Telegram’s own channel header, read 12 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.

Reaction mix

4,299 reactions across 88 posts, in 50 distinct kinds. The most used accounts for 15.4% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
66215.4%
💔62814.6%
🤡62814.6%
😢58813.7%
😁4089.49%
🖕3107.21%
👍3037.05%
🤣1423.30%
❤‍🔥1102.56%
🫡721.67%
💊641.49%
😡370.861%
🥴310.721%
🔥290.675%
🌚260.605%
👀240.558%
🤔220.512%
🤯220.512%
😱180.419%
🙏150.349%
30 further kinds1603.72%

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 108 of the 110 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 5,275reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 110 most recent posts we hold, published 4 August 2026 to 12 August 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

12 Aug 2026, 17:59 UTC≈2,800 views46 reactionsread 12 August 2026
Photo

Можливостей вкласти гроші у виробництво нашої зброї стає більше. Розкажіть, чи маєте ви досвід інвестицій у дефтек і чи плануєте такі вкладення загалом? 👉https://dou.ua/goto/xhUh

🤡25👍13👀4🖕3😁1

12 Aug 2026, 17:30 UTC≈3,380 views49 reactionsread 12 August 2026
Photo

Російські хакери проводять фейкові співбесіди, щоб зламати пристрої українських айтівців https://dou.ua/goto/DwM3 Хакери знаходять ІТ-фахівців на сайтах вакансій, проводять відеоспівбесіди англійською і спонукають встановити модифікований VPN, який запускає шкідливий код. CERT-UA пов’язує цю схему з російським угрупованням.

😡37😁7🖕3🏆1👻1

12 Aug 2026, 17:00 UTC≈3,480 views8 reactionsread 12 August 2026
Photo

Уже 1600 айтівців розповіли, які компанії знають і де хотіли б працювати. А ви вже долучилися? Кілька хвилин — і ваша відповідь стане важливою частиною результатів дослідження: https://dou.ua/goto/CmbB

🥰5🖕2🌚1

12 Aug 2026, 16:31 UTC≈3,640 views16 reactionsread 12 August 2026
Photo

Сьогодні є одразу два приводи подивитися вгору - ось-ось відбудеться сонячне затемнення, а після нього, вночі, буде пік Персеїд ✨ Будете дивитися на сонце чи зорі? 👉 https://dou.ua/goto/CL1h

❤‍🔥10🖕5🤔1

12 Aug 2026, 16:00 UTC≈3,750 views6 reactionsread 12 August 2026
Photo

У новому випуску «Візуалізації тижня» дивимось, скільки людей в Європі потерпають від аномальної спеки ☀️ У своїй графіці аналітики Reuters наочно показують, що вже близько 75% населення відчувають на собі денний максимум щонайменше на 5,6 градуса вище за історичну норму 👉 https://dou.ua/goto/PMlQ Діліться своїми візуалізаціями теж, в коментарях або топіках - обмежень на теми немає!

🖕3❤‍🔥2🤷‍♀1

12 Aug 2026, 15:35 UTC≈3,940 views17 reactionsread 12 August 2026
Photo

Йдете на DOU Day Picnic? Час розказати про це в соцмережах 😎 Все просто: 1. Заходите на сайт події у розділ "Фоторамка" 2. Завантажуєте своє фото 3. Отримуєте готову фоторамку та ділитеся нею в LinkedIn, Instagram чи де завгодно 💫 Покажіть усім, що 5 вересня ви з нами! Згенерувати фото 👉 https://ticket.dou.ua/dou-day-picnic-2026#photoframe

🖕115🤪1

12 Aug 2026, 15:11 UTC≈4,680 views126 reactionsread 12 August 2026
Photo

Співзасновниця Rozetka Ірина Чечоткіна підтвердила, що у компанії відбуваються скорочення https://dou.ua/goto/G64c За її словами, це зачепить декілька відділів. Компанія також змінить бізнес-модель і зменшить частку власних продажів.

😢108👍12🎉32🖕1

12 Aug 2026, 14:03 UTC≈4,990 views34 reactionsread 12 August 2026
Photo

Графічна дизайнерка Олександра Ткаченко розповідає, як завдяки AI її команда звела погодження дизайнів із замовниками з тижнів до трьох днів. У своєму блозі авторка наводить конкретний кейс, покроковий воркфлоу та три правила для тих, хто тільки починає впроваджувати AI у роботу з візуалами. 👉 https://dou.ua/goto/MexP

🤡21👍101🖕1🤣1

12 Aug 2026, 13:00 UTC≈5,330 views46 reactionsread 12 August 2026
Photo

Google повідомили, що вважають Go майже ідеальною мовою для AI-assisted розробки. Серед головних аргументів — простота, статична типізація, стандартизований інструментарій і можливість швидко перевіряти та виправляти згенерований ШІ код. У компанії вважають, що з розвитком AI-агентів важливішим стає вже не те, наскільки легко писати код, а наскільки легко його перевіряти й підтримувати. Як думаєте, чи справді Go кра

😁349🖕3

12 Aug 2026, 12:32 UTC≈5,080 views12 reactionsread 12 August 2026
Photo

Налаштування інтерактивної анімації часто обертається розсинхроном із діями юзера. Саша Лєтова ділиться кейсом команди: чому відмовилися від статичних SVG на користь Rive, як подружили його з React та налаштували State Machine. 👉https://dou.ua/goto/sOht Літо. Нетворкінг. 7000 айтівців. І все це на DOU Day Picnic. Долучайся!

7🤪2❤‍🔥1🖕1🤡1

12 Aug 2026, 12:00 UTC≈6,540 views38 reactionsread 12 August 2026
Photo

До 8000 українців зможуть безплатно пройти ІТ-навчання та сертифікацію Oracle https://dou.ua/goto/2v9A Доступні курси з AI, Java, DevOps, Data Science, хмарних технологій і безпеки. Розповідаємо, як проходить навчання і що потрібно для сертифікації.

21🤡13🙈3🖕1

12 Aug 2026, 11:30 UTC≈5,510 views89 reactionsread 12 August 2026
Photo

Vyriy Industries випустила облігації на 5 млрд грн. Інвестувати можна від 1000 грн https://dou.ua/goto/0kaT Vyriy Industries хоче залучити кошти українців на виробництво дронів. Інвестувати можна буде від 1000 грн через фонд Inzhur MilTech. Розповідаємо, як це працює і які є ризики.

❤‍🔥6510🔥7🖕3😁2🤨1🥴1

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

Posts edited after publishing

@doucommunity edited 1 post after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.

An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.

First edit seen
12 August 2026
Most recent edit
12 August 2026

Citation-graph rank

Citation-graph rank — 14,257 of 1,151,006entries 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

Named by 9 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.

FEDOROV
@zedigital · 248,988
Telegram ranks this channel #7 of 93 here — alongside 92 others — read 10 August 2026
ОГо!
@OGoMono · 663,052
Telegram ranks this channel #11 of 90 here — alongside 89 others — read 8 August 2026

This channel appears in 2 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.

Cross-platform identity — Wikidata

A Wikidata item names this Telegram handle as belonging to the entity it describes. This is Wikidata’s claim, not a verification made by this register — nobody here confirmed that the account is genuinely operated by the entity named. Wikidata content is CC0; every fact below is dated to when it was read from Wikidata, not to when the association was first made there.

Q12062915 on Wikidata, read 9 August 2026
LabelDOU
DescriptionUkrainian portal for IT specialists
X / Twitter@doucommunity
YouTubeUC6If-LcFxUDJhgL9dmB8oMA
Official sitehttps://dou.ua/

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

“DOU” (@doucommunity), 41,896 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/doucommunity.

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.