Telegram RegisterThe public register of Telegram

Channel

Мамкін Архітектор

@mamkin_architect

On this record: Growth · Engagement · Reactions · Stars · Advertising · Posts · Citations · Cite this entry

3,089subscribers

+9 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1001692384930
TypeChannel
Username@mamkin_architect
CreatedBetween 1 December 2021 and 30 April 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live13 August 2026
Measurements held5
Confirmed unchanged1 time, most recently 13 August 2026
On Telegramt.me/mamkin_architect

Growth

3,0793,0893,0846 August 2026 — 3,080 subscribers6 August 2026 — 3,080 subscribers6 August 2026 — 3,079 subscribers9 August 2026 — 3,083 subscribers13 August 2026 — 3,089 subscribers6 August 202613 August 2026
5 measurements spanning 7 days, net +9. 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,078–3,091 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
13 Aug 2026, 07:343,089+6
9 Aug 2026, 20:533,083+4
6 Aug 2026, 21:373,079-1
6 Aug 2026, 04:513,080no change
6 Aug 2026, 04:363,080first reading

Engagement

21 posts held, back to 23 June 2026the 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.

ERR · 30 days
61.9%
avg views ÷ 3,089 subscribers
Avg views / post
1,910
8 posts measured
Reaction rate
2.01%
reactions ÷ views · ER floor
Posts in window
8
of 21 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 7 August 2026
Posts held21 (23 June 20267 August 2026)
Views total15,307
Reactions total307
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken7 Aug 2026, 23:59 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

842 reactions across 21 posts, in 19 distinct kinds. The most used accounts for 28.4% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍23928.4%
🔥21024.9%
20524.3%
😁8710.3%
👏202.38%
💊182.14%
❤‍🔥161.90%
🤮111.31%
🥱70.831%
💯50.594%
🤣50.594%
👀40.475%
🤔40.475%
💩30.356%
🤝20.238%
🤡20.238%
🦄20.238%
🌚10.119%
😢10.119%

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

Measured over the 21 most recent posts we hold, published 23 June 2026 to 7 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.

Telegram Stars

Stars received
3
across the posts below
Posts paid on
3
of 21 we hold a reading for · 14%
Most on one post
1
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @mamkin_architect. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.

Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.

This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.

Counted over the 21 most recent posts we hold for this entry, published 23 June 2026 to 7 August 2026. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.

Advertising

Ad load
4.76%
1 of 21 posts carry an ad marker
Regulatory tokens
0
none — marked by hashtag only
Median views · ads
2,030
over 1 measured post
Median views · rest
2,630
over 20 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 21 most recent posts we hold, published 23 June 2026 to 7 August 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

7 Aug 2026, 18:01 UTC897 views14 reactions1 Starread 7 August 2026

Сидів собі думскролив стрічку і знайшов три статті, якими різко захотілось поділитись, від дірки в корпоративному софті до Маріо Карта. Я завжди трохи упереджено ставився до систем Atlassian, і оце якраз той випадок, коли підозра виявилась не параноєю. PromptArmor знайшли, що їхній AI-асистент Rovo може зливати дані в обхід контролів доступу, а вразливість цю знайшли ще в кінці травня і досі не пофіксили. Adform (ц

12👍2

4 Aug 2026, 15:22 UTC≈1,720 views26 reactionsread 7 August 2026

tmux сказав, що я не термінал Я працюю здебільшого в терміналі і використовую tmux для керування сесіями. Сесій декілька, в них запущені важливі речі (агенти пишуть код), і працює це тижнями. Аж тут випадково випав із tmux, пробую підключитись взад tmux attach-session, а воно мені open terminal failed: not a terminal. WTF?! Починаю розбиратись (запускаю claude і копіпащу туди-сюди команди і відповіді), проходимо де

👏20🔥32💯1

3 Aug 2026, 13:42 UTC≈1,790 views35 reactionsread 7 August 2026

Новина, де в назві є Redis і Python, не могла пройти повз цей канал. А тут ще й FastAPI Redis SDK від самого Redis: https://github.com/redis/fastapi-redis-sdk/ Це не просто “ось вам клієнт, далі самі”, а middleware з кешуванням GET endpointʼів, інвалідацією, ETag/304, Cache-Control, rate limiting і підключенням через FastAPI lifespan. Тобто приблизно той набір нудних речей, які всі знають, що треба зробити, але поті

21👍14

31 Jul 2026, 07:03 UTC≈2,030 views19 reactionsread 7 August 2026
AdvertisementPhoto

#реклама від партнерів Як виглядає AI-розробка в компанії, де агенти вже в щоденному процесі. Кирило Сулімовський - Head of Engineering, керує 6 інженерними командами на highload, 200+ мікро сервісів, 10k+ RPS. На воркшопі показує не «як має бути в теорії», а свій щоденний production-процес. Практичний воркшоп Agentic Engineering Workflow, дві частини: 📅 6 серпня, четвер, 19:00 - теорія: контекст, CLAUDE.md, суба

🤮9👍6❤‍🔥2👀1😁1

30 Jul 2026, 16:14 UTC≈1,930 views30 reactionsread 7 August 2026

Я поставив monitoring і воно одразу показало, що мій домашній прод знову не зовсім живий. Минулого разу я писав про прекрасну схему observability, побудовану на фізичних явищах, типу відсутності води в крані. І подумав, шо хотілось би зробити більш приземлений моніторинг, бо не всі сервіси підвʼязані до фізичних речей, а дізнаватись про те, що щось лежить, краще раніше. Давно чув про Uptime Kuma, і тут настав її час

🔥255

28 Jul 2026, 13:06 UTC≈2,060 views69 reactionsread 7 August 2026

У нас в будинку частина автоматизації крутиться на маленькій Lenovo-коробці: Home Assistant, Docker, всякі штуки, які мають просто тихо працювати і не нагадувати про себе. Нагадали через воду. Почались скарги від мешканців, що немає нормального напору, а виявилось, що десь блимнуло світло, відімкнувся smart switch, який керує насосом, і Home Assistant чомусь не увімкнув його назад, хоча мав би. Яжайтішнік, лізу диви

34🔥23👍12

27 Jul 2026, 14:23 UTC≈2,370 views73 reactions1 Starread 7 August 2026

Найсмішніша історія про автоматизацію в моїй родині була про Excel. Ще в студентські роки моя дружина прийшла на практику в державну контору, їй дали компʼютер з Excel-табличкою, колонку цифр і завдання просумувати її. На це виділили день, олівець і калькулятор. Вона не зрозуміла приколу, натиснула кнопку "автосума", і отримала результат менш ніж за секунду. Начальниця дуже здивувалась, сказала, шо це якась хрінь і

🔥28💊18👍125💯4🤔3😁2🌚1

24 Jul 2026, 10:12 UTC≈2,510 views41 reactionsread 7 August 2026

Неочевидний tailscale Я довго використовував Tailscale як зручний ssh до домашніх (і деколи диких) хостів. А потім виявилось, що не кожен корисний сценарій починається з "додай цей хост у tailnet". Бо, наприклад, можна зайти на машину, якої немає в Tailscale, через хост, доданий до Tailscale. Для цього достатньо ssh jump host: ssh -J user@tailscale-host user@internal-host. Якщо таких машин багато, є subnet router.

🔥296👍6

14 Jul 2026, 15:56 UTC≈2,960 views35 reactionsread 7 August 2026

Побачив на каналі Devs Hive пост про запуск stack overflow для AI агентів. З однієї сторони добре, що бізнес не зупиняється і шукає варіанти, а з іншого — шо їм ще робити? По факту AI знищило Stack Overflow, принаймні точно змусило скинути жирок, і тепер вони хочуть щось отримати взамін. Я свого часу на Stack Overflow непогано розкачався, назбирав щось близько дванадцяти тисяч репутації. Спочатку просив команду і з

17👍14🤝2❤‍🔥1😢1

13 Jul 2026, 11:49 UTC≈2,800 views28 reactionsread 7 August 2026

В твітері минулого тижня палала хаскель-драма через те, що якийсь проект почав міграцію Haskell --> Python. Засновник проекту, як я зрозумів, помітна постать у Haskell-спільноті, тож це піддає жару до загального палання дуп. Причина в тому, що дуже повільний цикл зворотного звʼязку через компіляцію критично не підходить для AI driven development. Я про це вже писав ось тут. І виходить, що повільний динамічний інтерп

❤‍🔥12👍54💩3🤡2🔥1🤔1

11 Jul 2026, 09:26 UTC≈2,680 views26 reactionsread 7 August 2026
Photo

Ось така смішна картинка викликала ланцюжок думок. Чого pyhon так працює? Хоча насправді я знаю, і всі пітоністи знають. Це прикол із серії "тупого" javascript, у якого 2+2=22, де насправді абьюзиться якась фіча мови, і нормальна робота виставляється, як якась дічь. А от цікаво, скільки часу і ментального ресурсу спалили схожі питання на інтервью? Вони ж нічого не показують, крім того, що людина вже бачила цей прико

👍223❤‍🔥1

10 Jul 2026, 14:52 UTC≈2,270 views39 reactionsread 7 August 2026

Disaster recovery це просто, особливо для тих, хто його ніколи не робив. Впав сервак, в тебе є другий. Впав дата-центр або availability zone, ти запускаєш резервний. Впав регіон, що буває дуже рідко, але provider має декілька регіонів, тому ми робимо мульти регіон. Ну а якщо впав вже провайдер, що майже ніколи не стається, тоді додаємо іншого провайдера. І такий сетап здається абсолютно bulletproof. Різні варіанти,

25👍10😁4

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

Stars beside a post are paid reactions — Telegram Stars, bought with money and spent on that post. They are a different unit from reactions and are never added to them, here or anywhere else on this page.

Citation-graph rank

Citation-graph rank — 145,371 of 1,478,351entries 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 3 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.

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.

“Мамкін Архітектор” (@mamkin_architect), 3,089 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/mamkin_architect.

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.