Telegram RegisterThe public register of Telegram
Telegram profile photo for agent-34

Channel

agent-34

@agent34md

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

45subscribers

+5 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1003868042123
TypeChannel
Username@agent34md
CreatedBetween 1 February 2026 and 28 March 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded10 August 2026
Last confirmed live6 October 2026
Measurements held7
Confirmed unchanged1 time, most recently 6 October 2026
On Telegramt.me/agent34md

Topic

Technology — 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 29 September 2026 and assigned it the closest of 31 fixed categories, at 92% 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.

Growth

4046437 August 2026 — 40 subscribers10 August 2026 — 40 subscribers15 August 2026 — 44 subscribers29 August 2026 — 45 subscribers7 September 2026 — 46 subscribers26 September 2026 — 44 subscribers6 October 2026 — 45 subscribers457 August 20266 October 2026
7 measurements spanning 60 days, net +5. 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 39–47 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
6 Oct 2026, 19:1745+1
26 Sept 2026, 04:3844-2
7 Sept 2026, 09:3746+1
29 Aug 2026, 03:0745+1
15 Aug 2026, 19:2244+4
10 Aug 2026, 19:1640no change
7 Aug 2026, 19:0640first reading

Engagement

15 posts held, back to 28 March 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 15 posts for this entry, the most recent from 15 July 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

20 reactions across 8 posts, in 7 distinct kinds. The most used accounts for 30.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤630.0%
👍420.0%
🔥420.0%
👏210.0%
😁210.0%
💯15.00%
😱15.00%

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

Measured over the 15 most recent posts we hold, published 28 March 2026 to 15 July 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

15 Jul 2026, 20:21 UTC226 views2 reactionsread 10 August 2026

GPT 5.6* имба? - очевидно 😠 Но только модель Sol, Но как её использовать? И почему Соль GOAT - а всё остальное - пыль глаза (Речь про Terra/Luna) 5.6 Sol Это смертоносное оружие в прямых руках, но в кривых руках - лёгкий способ выкопать долговую яму и упасть в неё и собственноручно закопаться в этой яме, подробнее ниже: Данный ответ сформирован после пяти дневной лудки☠️ всех моделей на протяжении 10-12 часов еже…

💯1🔥1

6 Jul 2026, 16:11 UTC252 views3 reactionsread 10 August 2026
Photo

Тут китайцы замутили "алиэкспресс"🤝 для нейронок, шо это и кто это? https://a6api.com (Не поверите, но это рефка🌚) маркейтплейс - для LLM моделей, где берёте закидывайте гроши и получаете на выходе те же самые модели, но заметно дешевле, чем по официальным подпискам от OpenAI / Anthropic / Gemini / xAI? А плюсы будут😈? - Дискаунт на тот же GPT 5.5 достигает того что, 20 баксов по китай апи = GPT Pro x5 (100$ план…

❤3

30 May 2026, 16:24 UTC337 views2 reactionsread 10 August 2026

В начале лета, Халява от OpenAI с x2 квотой на Codex на тарифном плане за 100 баксов заканчивается для Pro Lite плана и придётся делать выбор, быть прогретым на 200 баксов и получить x20 квоту, либо оставить Pro Lite за 100$ и постигать дзен на китайских вендорах И это событие надвинуло меня на мысль, пора бы осваивать навык cost-оптимизатора для LLM моделей, а то деньги венчурного капитала не бесконечные и субсидии…

👍2

25 May 2026, 07:11 UTC249 views3 reactionsread 10 August 2026
File

Протестировал работу фичи /goal в Codex CLI, на довольно тяжёлой задаче (рефакторинг "вайб" код harness агента) Вкратце крайне крутая фича, наконец то нормальная реализация Ralph loop, который довели до ума, можно использовать её, если вам лень самому агента промптить на написание кодов, да и по мимо лени, здесь можно совершить меньше ошибок, связанных с человеческим фактором, для рефакторинга (при наличии тестов), …

👍2😱1

16 May 2026, 10:41 UTC217 views2 reactionsread 10 August 2026
Photo

Рекламы не существует (И ublock origin конечно хорош, но он не настолько эффективен, как ядерный вариант ниже:) Собственно Adguard home или pi-hole - кто это и зачем оно нужно? Способ ликвидировать рекламу причём под корень (с небольшими жертвами в виде небольшого отвала некоторые особ не нужных сервисов) Рецепт: 1. Берём вдску с аптаймом желательно 9.99% 2. Ставим туда докер + Adguard Home в этом докере, настраи…

❤2

26 Apr 2026, 16:59 UTC385 views2 reactionsread 10 August 2026
Photo

Если гототовиться к вайтлистам на проводе, дак основательно, А то КПП Верхний Ларс пока не в планах

🔥2

26 Apr 2026, 12:32 UTC392 viewsread 10 August 2026
File

маскировка под самый лучший аппарат на свете https://www.gsmarena.com/tecno_spark_go_5g-14074.php

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

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

“agent-34” (@agent34md), 45 subscribers as measured 6 October 2026. Telegram Register, tgregister.com/channel/agent34md.

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.