То что происходит сейчас во втором канале, который @chempik1234_1, имеет вполне прикладное применение в СА, поэтому пост сюда Рисовать империи микросервисов на бумаге очень интересно. Вы представляете, что вы родили и соединили все элементы на диаграмме (по крайней мере, составили для них требования), и по вашим подсчётам система справится с нагрузкой и сделает, что от неё просят. Но кто и зачем просит? Полезно быв…

Channel
chempik1234
@chempik1234
On this record: Topic · Growth · Engagement · Reactions · Stars · Advertising · Posts · Citations · Cite this entry
41subscribers
+4 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 | -1002395794843 |
|---|---|
| Type | Channel |
| Username | @chempik1234 |
| Created | Between 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 10 August 2026 |
| Last confirmed live | 7 October 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 2 times, most recently 7 October 2026 |
| On Telegram | t.me/chempik1234 |
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
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 28 Sept 2026, 06:59 | 41 | +3 |
| 8 Sept 2026, 04:41 | 38 | +1 |
| 10 Aug 2026, 21:30 | 37 | no change |
| 7 Aug 2026, 17:06 | 37 | first reading |
Engagement
19 posts held, back to 24 December 2025 — 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 29 July 2026. An engagement rate over an empty window would be a number about nothing.
Reaction mix
47 reactions across 15 posts, in 10 distinct kinds. The most used accounts for 29.8% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 14 | 29.8% | |
| 🔥 | 8 | 17.0% | |
| 👍 | 6 | 12.8% | |
| ⚡ | 5 | 10.6% | |
| 🆒 | 3 | 6.38% | |
| 👌 | 3 | 6.38% | |
| 🤮 | 3 | 6.38% | |
| 🥰 | 3 | 6.38% | |
| 💩 | 1 | 2.13% | |
| 😱 | 1 | 2.13% |
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 15 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 47 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 24 December 2025 to 29 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.
Telegram Stars
- Stars received
- 2
- across the posts below
- Posts paid on
- 1
- of 19 we hold a reading for · 5%
- Most on one post
- 2
- single highest reading
A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @chempik1234. 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 19 most recent posts we hold for this entry, published 24 December 2025 to 29 July 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
- 5.26%
- 1 of 19 posts carry an ad marker
- Regulatory tokens
- 1
- posts carrying an erid · 1 distinct token
- Median views · ads
- 245
- over 1 measured post
- Median views · rest
- 191
- over 18 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.
| erid | Posts | First seen | Last seen |
|---|---|---|---|
| IDValueType | 1 | 24 December 2025 | 24 December 2025 |
A token repeated across several posts is one advertising contract placed more than once, which is what the identifier is for. The strings are reproduced exactly as they appeared in the post or in its click-through URL and are not validated against any registry — we record the marker a channel published, and whether it resolves to a real contract is a question for the register that issued it.
Measured over the 19 most recent posts we hold, published 24 December 2025 to 29 July 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
Эти картинки до добра не доведут Через какое-то время после этого проекта мне потребовалось разработать бот, который отправляет вакансии в несколько каналов. Тогда мне показалось, что будет отличным решением скопипастить структуру. Сам проект был большой и амбициозный, не знаю, что с ним сейчас, но мы сейчас говорим про бот, который делает ровно 3 операции 2 раза в день. Итак, по расписанию у нас операция "получит…
❤1
Хорошо, когда есть, где эти картинки показывать
❤3
По поводу сервиса онлайн-комнат — я покушал солёных рыбок и мне идея в голову пришла. Сделать многофазный стриминг. Пояснение картинки Первая картинка — то, как это выглядит сейчас. Вторая картинка — то, как это может выглядеть. I/O — цикл обработки запросов/команд от пользователя по gRPC logic — набор функций для изменения данных, проверяет идемпотентность запроса и делает вызовы в БД Вроде просто, но сразу не…
❤1
Время pdf-бедности кончилось. На бумаге читать удобнее + новее издание. Я искал beginner книгу Fundamentals of Data Engineering, но пока нашёл только в pdf (в магазине всё про sql и DS, это не то)
🔥5❤1
Photo, posted without a caption
🥰3
Партиции Вот статья, которой уже 12 лет или больше: https://highload.guide/blog/scaling-database.html Очень доступно и просто написано, но знайте: в PostgreSQL есть возможность делать партиции гораздо проще. Примерно до 10 версии люди делали всё руками. Сейчас добавилось простоты, но есть свои приколы, поэтому на всякий случай способ с руками никуда не делся. Ликбез: Работая с данными, если их становится много, …
⚡2
У сервиса есть 2 режима: либо запускай self-hosted, либо полагайся на яндекс облако. У версии с облаком (SaaS) есть админ панель и лендинг — они используют Admin API. Также есть рейт лимитер на запросы к своей игре. Админка и лендинг навайбкожены и будут беспощадно вайбкодиться. Прокси-сервис навайбкожен, но я это так не мог оставить. Переписывал и говорил гпт, как писать правильно. Сам сервис комнат написан мной…
🆒3
Ноанс проектирования Взаимодействие предполагает набор подключений либо в виде стримов, либо непрерывных отправок одиночных запросов. Я придумал поддерживать и то, и то, но Stream — основа, поэтому при создании одиночных методов надо держать в голове, что нужна аналогичность стрим-режиму — вместо "метода на операцию" у нас разновидности команд. Но ведь в стриме принимается один тип данных. Как реализовать разновид…
Что я там вообще выкладываю Для начала разберём потребность и ЦА. Есть js-игра, которая работает только локально в браузере. Например, мой друг сделал рисовалку, в которой можно пальцем водить на камеру, чтобы рисовать линии. Что делать? Конечно, попробовать помочь. Несколько месяцев назад решил написать сервис для онлайн-комнат. Я не уверен, насколько это хорошая идея, но: 1) я давно не писал на Go и надо было хот…
Я всё переписал💫 Ну, не всё, но очень много. Railway прекрасная площадка, но у неё есть фатальный недостаток. Это рейт лимит по количеству задеплоенных сервисов. Именно поэтому я пошёл в светлое место во всех смыслах — Яндекс облако. С ним работать в разы сложнее, но ничего невозможного. Я решил сделать так: 1. proxy_main_VM: БД, saas-обертка 2. tenant_1_VM: автодеплой с docker-compose 3. tenant_X_VM на каждый чих…
😱1
🚀 Your SaaS is now live! Такую фразу вы бы хотели услышать, и правильно. Однако вам бы ещё хотелось уметь автоматически спавнить всякие сервисы. Давно я начал делать (и забыл где остановился) сервис который запускает пользовательский docker compose на рандомном DinD. Короче, желание иметь такой сервис было не у меня одного. Помните vercel? Даёшь ему git-репозиторий, и ты в облаке. Я делал так с django и fastAPI пр…
⚡3
Showing the 12 most recent of 19 posts we hold for @chempik1234. 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.
Mentions
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.
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 28 September 2026 — this entry's latest reading, not the date you are reading this.
“chempik1234” (@chempik1234), 41 subscribers as measured 28 September 2026. Telegram Register, tgregister.com/channel/chempik1234.
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.