Telegram RegisterThe public register of Telegram
Telegram profile photo for Мамкін Архітектор

Channel

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

@mamkin_architect

On this record: Topic · Growth · Engagement · Reactions · Stars · Advertising · Posts · Citations · Telegram's recommendations · Cite this entry

3,168subscribers

+88 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-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 live18 September 2026
Measurements held14
Confirmed unchanged1 time, most recently 18 September 2026
On Telegramt.me/mamkin_architect

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 14 September 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.

Growth

3,0793,1743,126.56 August 2026 — 3,080 subscribers6 August 2026 — 3,080 subscribers6 August 2026 — 3,079 subscribers9 August 2026 — 3,083 subscribers13 August 2026 — 3,089 subscribers16 August 2026 — 3,090 subscribers20 August 2026 — 3,092 subscribers23 August 2026 — 3,145 subscribers26 August 2026 — 3,149 subscribers1 September 2026 — 3,152 subscribers6 September 2026 — 3,162 subscribers11 September 2026 — 3,174 subscribers14 September 2026 — 3,172 subscribers18 September 2026 — 3,168 subscribers3,1686 August 202618 September 2026
14 measurements spanning 44 days, net +88. 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,065–3,188 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
18 Sept 2026, 22:183,168-4
14 Sept 2026, 19:363,172-2
11 Sept 2026, 03:193,174+12
6 Sept 2026, 08:583,162+10
1 Sept 2026, 19:263,152+3
26 Aug 2026, 16:023,149+4
23 Aug 2026, 14:443,145+53
20 Aug 2026, 02:243,092+2
16 Aug 2026, 16:443,090+1
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 pages 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 21 posts for this entry, the most recent from 7 August 2026. An engagement rate over an empty window would be a number about nothing.

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 842 reactions 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.

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.

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.

Djinni (/◔ ◡ ◔)/
@djinni_official · 50,095
Telegram ranks this channel #65 of 87 here — alongside 86 others — read 26 August 2026
DOU
@doucommunity · 42,324
Telegram ranks this channel #75 of 83 here — alongside 82 others — read 29 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.

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

“Мамкін Архітектор” (@mamkin_architect), 3,168 subscribers as measured 18 September 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.