Channel
@MinskCSS_MinskJS
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
208subscribers
+0 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001227288218 |
|---|---|
| Type | Channel |
| Username | @MinskCSS_MinskJS |
| Description | Чат сообщества — @MinskCSS_MinskJS_chat |
| Created | Between 1 April 2018 and 30 June 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 7 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/MinskCSS_MinskJS |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 7 Aug 2026, 03:47 | 208 | no change |
| 6 Aug 2026, 18:01 | 208 | first reading |
20 posts held, back to 30 July 2024 — 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 pageof 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 20 posts for this entry, the most recent from 20 August 2025. An engagement rate over an empty window would be a number about nothing.
Lifetime counters from Telegram’s own channel header, read 7 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.
196 reactions across 19 posts, in 6 distinct kinds. The most used accounts for 56.6% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 🔥 | 111 | 56.6% | |
| ❤ | 75 | 38.3% | |
| 👍 | 4 | 2.04% | |
| ❤🔥 | 3 | 1.53% | |
| 🍾 | 2 | 1.02% | |
| 🎉 | 1 | 0.51% |
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 20 of the 20 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 196reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 20 most recent posts we hold, published 30 July 2024 to 20 August 2025, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
Собрали плейлист с докладами MinskJS Meetup №13, теперь можно делиться отдельными видео с коллегами 🙃 https://www.youtube.com/playlist?list=PL-whh3wS8xsLDvwETZ8Dpr2N-wL7sQcnL Если у вас есть желание выступить на наших митапах MinskCSS и MinskJS — не сдерживайтесь, приходите в Call for Papers. Мы помогаем подготовить хорошие доклады в том числе и начинающим спикерам ;)
🔥10❤1
Начинаем! https://www.youtube.com/watch?v=7JyODKQYRX4
🏁 Завершаем знакомить вас с программой MinskJS Meetup #13. Василий Ванчук знает о собеседованиях очень много. В том числе и о том, что за секция такая для фронтенд-разработчиков — System Design. Готовитесь к собесам? Тогда этот доклад точно вам пригодится. 📌 Ждём вас в уютной онлайн-трансляции на нашем YouTube канале. Никакой регистрации, просто приходите! 👉 https://www.youtube.com/watch?v=7JyODKQYRX4 Описание и п…
🔥5
👋 Продолжаем знакомить вас со спикерами MinskJS Meetup #13. Анна Ширяева научит не холиварить, какой фреймворк самый лучший и правильный, а умело выбирать инструмент под конкретную задачу. 📌 Место проведения: уютная онлайн-трансляция на нашем YouTube канале. Никакой регистрации, просто приходите! 👉 https://www.youtube.com/watch?v=7JyODKQYRX4 Описание и программа 👉 https://minskjs.site/events/minskjs-meetup-13/
🔥7❤1
💡А не провести ли нам внезапный летний митап? Мы нашли классных спикеров с классными докладами и готовы на следующей неделе собраться на MinskJS Meetup. MinskJS Meetup #13 пройдет 19 августа 2025 года в 19:00 (по минскому времени) онлайн! И наш первый спикер — Евгений Дорошкевич. Он расскажет и покажет, как с помощью продуманных анимаций можно сделать интерфейсы понятнее, эффективнее для восприятия и приятнее в исп…
🔥12❤3👍1
Собрали плейлист с докладами с MinskCSS Meetup №13, теперь можно делиться отдельными видео с коллегами 🙃 - Доступная тёмная тема. Взгляд изнутри // Анастасия Ярош - Резиновая типографика: магия clamp() // Татьяна Фокина - Вы не знаете MathML. Почти никто не знает // Вадим Макеев https://www.youtube.com/playlist?list=PL3uk4LxG9ZzmZGqpQmIMbGsiwtB6wU5Dp Если у вас есть желание выступить на наших митапах MinskCSS и Mi…
🔥8❤5
Начинаем! 👉 https://youtube.com/live/x8TuxE05cPA 👈
❤3
✨ Завершаем знакомить вас с программой уже завтрашнего MinskCSS Meetup #13. Наш следующий спикер Вадим Макеев поможет разобраться в основах и особенностях MathML — специального языка разметки для математических формул в веб-платформе. Заводите напоминалки в календарях, зовите коллег, друзей и семьи, прогревайте випиэны. Уже завтра в 19:00 по минскому времени, не пропустите. Место проведения: 👉 https://youtube.com/…
🔥10❤6
✨ Продолжаем знакомить вас с докладами MinskCSS Meetup #13. Наш следующий спикер Татьяна Фокина расскажет про то, как работать с резиновой типографикой, зачем и где это нужно и как современные возможности CSS позволяют это делать удобно. Место проведения: 👉 https://youtube.com/live/x8TuxE05cPA 👈 Описание и программа: https://telegra.ph/MinskCSS-Meetup-13-04-11 Подписывайтесь, чтобы ничего не пропускать: Telegram …
🔥8❤4
✨ Возвращаемся с обещанным анонсом! MinskCSS Meetup #13 состоится 16 апреля 2025 года в 19:00 (по минскому времени)! Онлайн. Да, уже на следующей неделе. Наш первый спикер Анастасия Ярош расскажет и покажет, на что стоит обращать внимание при разработке тёмной темы, если вы заботитесь о доступности. Место проведения: уютная онлайн-трансляция на нашем YouTube канале. Никакой регистрации, просто приходите! 👉 https:/…
❤14👍2
Пока мы активно готовимся к MinskCSS #13, наши хорошие друзья из сообщества TbilisiJS уже готовы провести Tbilisi JS Web Performance Day. Программа митапа: - «Три стадии принятия React Compiler» // Анна Ширяева; - «9 ¹⁄₂ недель до релиза» // Даниил Савицкий; - «Приёмы оптимизации финансовых чартов» // Евгений Коробко; - «Когда оптимизации работают против вас» // Иван Акулов. 11 апреля, 19:30 по времени Тбилиси (18:…
🔥3❤2
Собрали плейлист с докладами с MinskJS Meetup №12, теперь можно делиться отдельными видео с коллегами 🙃 https://www.youtube.com/playlist?list=PL-whh3wS8xsKuQdPIESXp0xR1A7tinzkT Уже скоро порадуем вас анонсами следующего MinskCSS. Если у вас есть желание выступить на наших митапах MinskCSS и MinskJS — не сдерживайтесь, приходите в Call for Papers. Мы помогаем подготовить хорошие доклады в том числе и начинающим спи…
❤12
Showing the 12 most recent of 20 posts we hold for @MinskCSS_MinskJS. 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.
Citation-graph rank — 684,382 of 1,183,361entries 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.
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.
Named by 1 registered channel — 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.
Named by
Channels on the register whose posts name this channel's handle.
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 7 August 2026 — this entry's latest reading, not the date you are reading this.
“MinskCSS/MinskJS” (@MinskCSS_MinskJS), 208 subscribers as measured 7 August 2026. Telegram Register, tgregister.com/channel/MinskCSS_MinskJS.
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.