Telegram RegisterThe public register of Telegram

Channel

shonenkov AI

@shonenkovAI

On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Polls · Citations · Cite this entry

3,345subscribers

-4 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1001659354416
TypeChannel
Username@shonenkovAI
Created15 January 2022measured — cross-checked against a third-party dataset (ext.tg_channel)
First recorded6 August 2026
Last confirmed live13 August 2026
Measurements held5
Confirmed unchanged1 time, most recently 13 August 2026
On Telegramt.me/shonenkovAI

Growth

3,3453,3493,3476 August 2026 — 3,349 subscribers6 August 2026 — 3,349 subscribers7 August 2026 — 3,348 subscribers10 August 2026 — 3,347 subscribers13 August 2026 — 3,345 subscribers6 August 202613 August 2026
5 measurements spanning 7 days, net -4. 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 3,344–3,350 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
13 Aug 2026, 03:533,345-2
10 Aug 2026, 02:013,347-1
7 Aug 2026, 04:033,348-1
6 Aug 2026, 10:513,349no change
6 Aug 2026, 09:573,349first reading

Engagement

18 posts held, back to 28 January 2023the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 3 pagesof 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 18 posts for this entry, the most recent from 10 October 2023. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Video runtime
57s
Average length
57s

Measured directly from 1 video with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no mark.

Reaction mix

448 reactions across 17 posts, in 4 distinct kinds. The most used accounts for 37.9% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
17037.9%
👨‍💻13129.2%
11525.7%
🕊327.14%

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

Measured over the 18 most recent posts we hold, published 28 January 2023 to 10 October 2023, 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

10 Oct 2023, 15:04 UTC≈8,110 views14 reactionsread 7 August 2026

O, DALLE-3 paper (no commentaries) https://cdn.openai.com/papers/DALL_E_3_System_Card.pdf

14

20 Sept 2023, 22:20 UTC≈9,100 views23 reactionsread 7 August 2026
Forwarded from @mishin_learningVideo

🦔 OpenAI обучили DALL-E 3 Сложно назвать это релизом, скорее просто неплохая модель, работающая в связке с GPT-4. Мне лично кажется, что следующий Stable Diffusion будет куда умнее и интереснее эстетической точки зрения. 2021 DALL-E 1 — 12B модель, пейпер / API нет 2021 GLIDE — 2B модель, пейпер + опенсорс 300M модели 2022 DALL-E 2 — 2B модель, пейпер unCLIP + API 2023 DALL-E 3 — Хрен пойми что это, но будет интег

23

4 Aug 2023, 18:09 UTC≈8,870 views26 reactionsread 7 August 2026
Forwarded from @ai_newzPhoto

Релизнулась SOTA библиотека для генерации аудио AudioCraft v1.0.0 Я писал раньше о выходе начальной версии AudioCraft, когда Meta AI опубликовали статью MusicGen для генерации музыки по тексту. Почему новый релиз интересен? Это стабильный релиз и в него добавили код для трениновки моделей, в том числе несколько новых: - EnCodec - по сути квантизованый автоэнкодер (VQGAN), который сжимает аудио в серию дискретных т

26

20 Jun 2023, 18:03 UTC≈7,460 views35 reactionsread 7 August 2026
Forwarded from @tech_priestess

В честь 3000 подписчиков расскажу про наш новый препринт, в котором тексты, сгенерированные ChatGPT, детектируются с помощью анализа их внутренней размерности: https://arxiv.org/abs/2306.04723 Итак, здесь мои коллеги и я продолжили заниматься полюбившейся с 2021 года темой - детекцией сгенерированного контента. Особое внимание, конечно, уделили детекции текста, сгенерированного моделями семейства GPT-3.5 (davinci,

35

15 May 2023, 11:28 UTC≈15,800 views46 reactionsread 7 August 2026
Video

3D с DeepFloyd-IF выглядит неплохо, модель справилась с рендерингом и генерацией текста на кепке 👀 если вдруг кому-то интересно потыкать, то вот [GitHub с реализацией IF и 3D] + в комменты закинул еще несколько 3D анимаций @shonenkovAI

46

3 May 2023, 05:50 UTC≈7,730 views21 reactionsread 7 August 2026
Photo

пока что не понял за счет чего, но выглядит так, будто pyTorch-2.1 на А100 ускорил SD модели x2.5, а IF-I-M x5.0 в имплементации Diffusers 🚀 уже встроили в gradio-demo, вот pull-request; "This PR should speed-up IF stage1 by roughly 30% and stage2 and 3 by roughly 20%" [Demo] | [GitHub] | [DeepFloyd IF]

21

29 Apr 2023, 19:07 UTC≈7,240 views24 reactionsread 7 August 2026
Photo

Photo, posted without a caption

👨‍💻193🕊2

28 Apr 2023, 20:06 UTC≈6,870 views15 reactionsread 7 August 2026

опа, уже обзорчик на ютубе 🍿 https://www.youtube.com/watch?v=4Zkipll5Rjc

👨‍💻15

28 Apr 2023, 17:44 UTC≈5,630 views18 reactionsread 7 August 2026
Photo

Photo, posted without a caption

171

28 Apr 2023, 16:31 UTC≈4,190 views30 reactionsread 7 August 2026
Forwarded from @mishin_learningPhoto

👾 Мы DeepFloyd (Research AI Lab at StabilityAI) зарелизили лучшую Text-to-Image модель DeepFloyd IF DeepFloyd IF это новая каскадная диффузионная модель основанная на идеи Imagen от Google: — Текст кодируется T5 XXL v1.1 — Далее интерпретируется в пиксели через IF-I-XL (4.3B UNet), генерирующий изображения в 64х64 — IF-II-L (1.2B кастомный Optimal UNet) апскелит изображения 64х64 в 256х256, используя T5 — Для фина

17🕊9👨‍💻4

28 Apr 2023, 16:05 UTC≈4,190 views26 reactionsread 7 August 2026

ГО тыкать IF? 👀 https://github.com/deep-floyd/IF

👨‍💻23🕊21

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

Polls

The poll we hold for this entry, as Telegram rendered it when we read the post. A poll’s figures keep moving after that, so each one is dated.

3 Apr 2023, 12:43 UTCAnonymous Poll874 voters

что из мультимодального полезнее развивать [April 2023]?

  1. text-to-image24%
  2. text-to-3D28%
  3. text-to-video35%
  4. text-to-audio14%
  5. multi-task38%

The shares total 139%, above 100: this poll accepts more than one answer per voter. No per-option vote count is published, so the number of voters who chose each option is not derivable and is not shown.

Percentages only — there are no per-option vote counts here, because Telegram publishes none.The public post preview gives each option’s share and a single voter total, and nothing else. Multiplying one by the other would produce a per-option tally that looks measured and is not: the shares are rounded to whole numbers before we ever see them. We print what was published and leave the column that does not exist empty.

The shares need not add up to 100.Rounding alone puts many polls at 99 or 101. A poll that allows more than one answer per voter runs well past 100 by design, and several here do. The bars are drawn against a fixed 100% track at each option’s own percentage rather than normalised to the total, so a poll that exceeds it shows that it does instead of being quietly rescaled.

Read from the 18 most recent posts we hold, published 28 January 2023 to 10 October 2023. Telegram labels each poll by kind — an anonymous poll, a quiz, a closed set of final results — and that label is reproduced rather than paraphrased.

Citation-graph rank

Citation-graph rank — 901,225 of 1,160,990entries 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 1 registered channel — 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.

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.

“shonenkov AI” (@shonenkovAI), 3,345 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/shonenkovAI.

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.