Лапатонія в переможцях!!!! https://t.me/Binance_UA_official/7534 Дякую всім хто за нас голосував та підтримував!!
❤15🔥7⚡1❤🔥1

Channel
@zaduha
On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Cite this entry
1,446subscribers
+59 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1001702896925 |
|---|---|
| Type | Channel |
| Username | @zaduha |
| Created | Between 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 15 September 2026 |
| Measurements held | 13 |
| Confirmed unchanged | 1 time, most recently 15 September 2026 |
| On Telegram | t.me/zaduha |
Other / unclassifiable — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 17 September 2026 and assigned it the closest of 31 fixed categories, at 75% 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 15 Sept 2026, 10:19 | 1,446 | +6 |
| 11 Sept 2026, 20:38 | 1,440 | +8 |
| 7 Sept 2026, 16:15 | 1,432 | +14 |
| 3 Sept 2026, 01:18 | 1,418 | +2 |
| 27 Aug 2026, 20:44 | 1,416 | +5 |
| 24 Aug 2026, 14:29 | 1,411 | +14 |
| 20 Aug 2026, 18:56 | 1,397 | +3 |
| 17 Aug 2026, 10:07 | 1,394 | +5 |
| 13 Aug 2026, 12:07 | 1,389 | -3 |
| 10 Aug 2026, 12:52 | 1,392 | +2 |
| 7 Aug 2026, 09:38 | 1,390 | +3 |
| 6 Aug 2026, 15:46 | 1,387 | no change |
| 6 Aug 2026, 15:37 | 1,387 | first reading |
19 posts held, back to 30 July 2026 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 page of 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 19 posts for this entry, the most recent from 6 August 2026. An engagement rate over an empty window would be a number about nothing.
244 reactions across 18 posts, in 15 distinct kinds. The most used accounts for 33.2% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 81 | 33.2% | |
| 😁 | 66 | 27.0% | |
| 🔥 | 42 | 17.2% | |
| 👍 | 17 | 6.97% | |
| 🤯 | 11 | 4.51% | |
| 💯 | 4 | 1.64% | |
| 😢 | 4 | 1.64% | |
| 🤔 | 4 | 1.64% | |
| ⚡ | 3 | 1.23% | |
| ❤🔥 | 3 | 1.23% | |
| 🌚 | 3 | 1.23% | |
| 👎 | 2 | 0.82% | |
| 🤷 | 2 | 0.82% | |
| 👏 | 1 | 0.41% | |
| 🤡 | 1 | 0.41% |
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 18 of the 19 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 244 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 19 most recent posts we hold, published 30 July 2026 to 6 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.
Лапатонія в переможцях!!!! https://t.me/Binance_UA_official/7534 Дякую всім хто за нас голосував та підтримував!!
❤15🔥7⚡1❤🔥1
Потужно https://t.me/AIHOUSE/1480
❤7💯4👍2
Prime Intellect запускають свого self-improving Prime Agent з орієнтацією на кодінг і довгі автономні здаачі. https://www.primeintellect.ai/blog/prime-agent основні концепції: Recursive Language Model - декомпозує промт, розбиває його на підзадачі та викликає сама себе на цих підзадачах і Continual Harness - я так зрозумів дає можливість перероблювати власний Harness в залежності від поточної траєкторії. (Думаю бага…
❤3👍2🤷2🤡1
Ну нарешті!) https://t.me/f0x_ai/33 А то я його анонсував тут як стрімера, а він все не стрімить і не стрімить) в чт в 20.00
❤5😁3❤🔥1👍1
#RunAndLearn Щє одне відео по RL від Nathan Lambert https://www.youtube.com/watch?v=IwpYxANrpUs
❤1
Метрики є метрики, подобаються вони чи ні, але якийсь орієнтир) https://t.me/f0x_ai/32 в Львівську політехніку подали документи 379 вступників, які отримали 200 балів на НМТ, з цих 379, 215 подали документи на кафедру Систем Штучного Інтелекту і 102 обрали її першим пріорітетом. Навіть якщо виходити з розрахунку що це бенчмаксінг замість загальної генералізації, шанс засемплить з такої виборки генільних людей думаю …
❤6🔥2👏1
Мою статтю про адаптацію байт левел BPE токенізаторів прийняли на Second Tokenization Workshop на конференції COLM 2026 Це буде суто постер сесія, самі вони нічого не публікують, тому закинув препрінт на аріхв. https://arxiv.org/pdf/2608.00582 Можна було б потім ще кудись подати, але так втомився від цієї теми що не хочу за то думати) Дякую Mykola Haltiuk що підсвітив цей вузькоспеціалізований воркшоп, бо не знаю ку…
🔥26❤6⚡2❤🔥1
#RunAndLearn Ще раз дивився про RL) https://www.youtube.com/watch?v=ztdTed5egrM Але це доволі якісна серія відео, тож не без задоволення)
❤1
Vladyslav Melnyk був гостем у випуску dev.ua, де в легкій дружній атмосфері обгворювали різні медійні кейси пов'язані з ШІ. Владислав поділився кумедними випадками які траплялись особливо на початку тестування Лапатонії, коли різні чати комьюніті наповнили приклади меседжів з некоректними відповідями, і доводилось шукати рішення щоб доповнити алаймент моделей додатковими знаннями про український контекст. https://www…
❤9👍6
АРТУУР!
❤8
На який трек на цій конференції піти?)
😁17❤3
Захопливо та хвилюючи усвідомлювати що це відбувається прям зараз https://openai.com/index/ten-advances-in-mathematics/
🤯4👍2
Showing the 12 most recent of 19 posts we hold for @zaduha. 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.
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.
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.
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 15 September 2026 — this entry's latest reading, not the date you are reading this.
“Задуха” (@zaduha), 1,446 subscribers as measured 15 September 2026. Telegram Register, tgregister.com/channel/zaduha.
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.