Channel
@moshniyWeb
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
61subscribers
-2 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1003791976397 |
|---|---|
| Type | Channel |
| Username | @moshniyWeb |
| Created | Between 1 February 2026 and 10 June 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 10 August 2026 |
| Last confirmed live | 30 August 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 3 times, most recently 30 August 2026 |
| On Telegram | t.me/moshniyWeb |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 14 Aug 2026, 18:05 | 61 | -2 |
| 10 Aug 2026, 03:31 | 63 | no change |
| 7 Aug 2026, 18:38 | 63 | first reading |
20 posts held, back to 10 June 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 20 posts for this entry, the most recent from 8 August 2026. An engagement rate over an empty window would be a number about nothing.
Measured directly from 1 video with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no ≈ mark.
191 reactions across 20 posts, in 14 distinct kinds. The most used accounts for 36.6% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 70 | 36.6% | |
| ❤ | 44 | 23.0% | |
| 👌 | 31 | 16.2% | |
| ⚡ | 13 | 6.81% | |
| 🤔 | 7 | 3.66% | |
| 🔥 | 6 | 3.14% | |
| 👏 | 4 | 2.09% | |
| 🤯 | 4 | 2.09% | |
| 👀 | 3 | 1.57% | |
| 👾 | 3 | 1.57% | |
| ❤🔥 | 2 | 1.05% | |
| 🤓 | 2 | 1.05% | |
| 🆒 | 1 | 0.524% | |
| 💯 | 1 | 0.524% |
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 191 reactions 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 10 June 2026 to 8 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.
toReversed() — обратный порядок без мутаций В JavaScript есть метод reverse(), который меняет исходный массив. Если тебе нужно сохранить оригинал - используй toReversed(), который появился в ES2023 const arr = [1, 2, 3]; const reversed = arr.toReversed(); // [3, 2, 1] console.log(arr); // [1, 2, 3] Работает как reverse(), но возвращает новый массив, не трогая старый. Отлично подходит для React-состояний и функцион…
❤3👍2💯1🤔1
Posted without readable text
❤4👌3👍2🤯1
Posted without readable text
👍6👾2🤓2
Posted without readable text
👍5❤2👌2👏1
Обратный слеш в PHP: функции vs классы В PHP пространства имён (namespaces) работают по-разному для функций и классов. Это важно понимать, чтобы не ловить ошибки и писать эффективный код. Для функций - fallback есть, но лучше использовать use function. Если ты внутри пространства имён и вызываешь strlen() без слеша или оператора импорта use function, PHP сначала ищет функцию в текущем пространстве. Если не находит …
❤3👌2👍2
Используй css функцию light-dark() для смены темы на сайте. :root { color-scheme: light dark; } body { background: light-dark(white, black); color: light-dark(black, white); } light-dark() реагирует на системные настройки пользователя. Если нужно принудительно включить какую-то тему на части страницы, можно использовать color-scheme: light или color-scheme: dark на отдельном контейнере - тогда light-dark() …
❤3👌2👍2
Posted without readable text
👌2🤯2❤1👍1👾1
StructuredClone() — нативное глубокое копирование в JS Многие знают, что поверхностное копирование (const copy = obj) копирует только ссылку на объект, но не создаёт полноценную копию. Если изменить copy, изменится и исходный объект. Для глубокого копирования раньше использовали JSON.parse(JSON.stringify()). Но у этого способа куча проблем: он не копирует Date, Map, Set, RegExp, undefined, падает на циклических ссы…
👍5👌1🤯1
CoreInfra AI Hub — доступ к топовым AI-агентам без VPN В России доступ к OpenAI Codex, Claude Code и другим западным AI-агентам — это всегда квест: то VPN, то платежи не проходят, то подписки дорогие. CoreInfra AI Hub ,это единая точка входа к популярным AI-агентам: 💪OpenAI Codex 💪Claude Code 💪Claude Sonnet 3.5 / 3.7 🦾И другие модели Всё работает без VPN, с российских IP, стабильно и быстро. Никаких подписок…
👍5⚡2👌2
use Теперь вместо громоздкого кода ,для загрузки данных с использованием useState+useEffect+проверка на наличие загрузки или ошибки, используем новый хук use(); use() - это новый хук, который разворачивает промисы прямо в компоненте. Если данные не загружены - use() приостанавливает рендеринг. Когда данные готовы - use() возвращает их, и компонент рендерится с ними. Родительский компонент оборачивает всё в <Susp…
❤4👏3🤔3
Короткая шпаргалка методов масcивов JS Мутируют: push | pop | unshift | shift Не мутируют (создают новый массив / строку): filter | map | concat | slice | flat | join @moshniyWeb #JavaScript 📺Max
👍6❤3👌2
Майкрософт увольняет 4800 сотрудников ,говорят что ИИ ни при чем . а как считаете вы , оставь своем мнение в комментариях @moshniyWeb #AI 📺Max
❤4👌3👍2
Showing the 12 most recent of 20 posts we hold for @moshniyWeb. 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.
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 14 August 2026 — this entry's latest reading, not the date you are reading this.
“Мощный WEB | Веб-разработка, инструменты и AI” (@moshniyWeb), 61 subscribers as measured 14 August 2026. Telegram Register, tgregister.com/channel/moshniyWeb.
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.