Починил смену пароля на апи
❤109👍32🔥18💩7👀6👾5👏3👎2
Signed mospanoff
Channel
@mospanoff_news
On this record: Topic · Growth · Engagement · Reactions · Posts · Cite this entry
2,606subscribers
-130 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1001409473075 |
|---|---|
| Type | Channel |
| Username | @mospanoff_news |
| Created | Between 1 April 2019 and 30 November 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 11 October 2026 |
| Measurements held | 16 |
| Confirmed unchanged | 1 time, most recently 11 October 2026 |
| On Telegram | t.me/mospanoff_news |
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 15 September 2026 and assigned it the closest of 31 fixed categories, at 66% 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 11 Oct 2026, 07:00 | 2,606 | -9 |
| 4 Oct 2026, 21:18 | 2,615 | -22 |
| 25 Sept 2026, 08:42 | 2,637 | -16 |
| 16 Sept 2026, 15:21 | 2,653 | -12 |
| 12 Sept 2026, 16:38 | 2,665 | -5 |
| 8 Sept 2026, 15:37 | 2,670 | -11 |
| 3 Sept 2026, 15:00 | 2,681 | -8 |
| 31 Aug 2026, 07:27 | 2,689 | -8 |
| 27 Aug 2026, 22:32 | 2,697 | -9 |
| 24 Aug 2026, 12:18 | 2,706 | -3 |
| 20 Aug 2026, 22:54 | 2,709 | -5 |
| 17 Aug 2026, 17:16 | 2,714 | -7 |
| 14 Aug 2026, 14:14 | 2,721 | -6 |
| 11 Aug 2026, 11:52 | 2,727 | -8 |
| 8 Aug 2026, 07:04 | 2,735 | -1 |
| 7 Aug 2026, 10:46 | 2,736 | first reading |
20 posts held, back to 19 August 2023 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 2 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 20 posts for this entry, the most recent from 13 March 2024. An engagement rate over an empty window would be a number about nothing.
685 reactions across 14 posts, in 12 distinct kinds. The most used accounts for 44.8% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 307 | 44.8% | |
| 👍 | 253 | 36.9% | |
| ❤🔥 | 37 | 5.40% | |
| 🔥 | 37 | 5.40% | |
| 👎 | 13 | 1.90% | |
| 💩 | 7 | 1.02% | |
| 🎉 | 6 | 0.876% | |
| 👀 | 6 | 0.876% | |
| 🙏 | 6 | 0.876% | |
| 👌 | 5 | 0.73% | |
| 👾 | 5 | 0.73% | |
| 👏 | 3 | 0.438% |
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 14 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 685 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 19 August 2023 to 13 March 2024, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
Починил смену пароля на апи
❤109👍32🔥18💩7👀6👾5👏3👎2
Signed mospanoff
Починил авторизацию на 275 версии апи
❤55👍26👎2
Signed mospanoff
у кого там еще проблемы с лайками с блоками лайков - пробуем убирать вход по кукам,ставим смену пароля в начале работы и запускаем
👍47❤22
Signed mospanoff
В версии 2.3.0 (x64, x32): - Починил подписки через поиск - Починил чистку кук перед сменой пароля - Исправил ошибку авторизации 404 - Исправил зависания в процессе работы Так же сегодня будут еще доработки по остатку функционала. Напоминаю, в случае любых ошибок\чекпоинтов пишите @mospanoff в ЛС лог(тхт файлом) и аккаунт
👍54❤21👎6👌5
Signed mospanoff
В версии 2.2.9(x64, x32): - Добавил подписки на 275 версии апи - Починил привязку почты на веб версии
👍31🔥17
Signed mospanoff
Перезалив 2.2.8 (x64, x32): - Починил зависание при получении блокировки на действие
Signed mospanoff
В версии 2.2.8(x64, x32): - Добавил версию апи 275.0.0.27.98. (На ней работает еще не весь функционал бота, проходятся не все чекпоинты) В случае возникновения любых ошибок предоставьте @mospanoff лог в txt файле и аккаунт - Добавил подсчет аккаунтов во сне(при submitPhoneNumber) - Добавил возможность выделять аккаунты по статусу выделенного аккаунта - Добавил обновление статистики аккаунтов(Кнопка "Обновить") клавиш…
❤37👍3
Signed mospanoff
Друзья, всех с наступающим Новым Годом! Желаю крепкого здоровья, безмерного счастья и любви. Чтобы все цели достигали без препятствий. И самое главное - мирного неба над головой, чтобы война не застала вас в вашем доме!
❤🔥37❤21👍16🎉6🙏6🔥2
В версии 2.2.7(х64, х32): - Добавил возмжность обрабатывать разные responsible_policy(Сон, замена прокси, переавторизация, замена, остановка аккаунта(Список возможных действий могу дополнить по вашему желанию)) Прежде чем пользоваться функцией, прочтите подсказку
❤37👎3
Версия 2.2.6(х64, х32): - Починил ошибку "Не нашли challengeType"(Получение сломал начиная с версии 2.2.4) - Исправил прогрев перед каждой публикацией(Ранее делался только один раз) (Уже точно починил;))
👍11
Версия 2.2.5 (x64, x32): - Добавил возможность прогревать и заполнять аккаунт на отдельных прокси, с контролем количества аккаунтов на 1 прокси(Настройка осуществляется во вкладке "Заполнение аккаунтов + прогрев") - Исправил проблему, когда была включена авторизация на отдельных прокси, и в случае, если прокси не валидные, замена осуществлялась с общих прокси, а не с прокси для авторизации
👍7
Версия 2.2.4 (x64, x32): - Добавил опцию "Не проверять аккаунт перед работой". Перед включением прочтите подсказку - Добавил возможность работать с одной почтой для получения писем(Когда редирект стоит на одну почту) - Исправил прогрев перед каждой публикацией(Ранее делался только один раз) - Исправил запуск аккаунтов, при включенном одном сервисе "Рекомендации"(Аккаунт просто завершал работу из-за отсутствия оплачив…
❤5👍4
Showing the 12 most recent of 20 posts we hold for @mospanoff_news. 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.
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 11 October 2026 — this entry's latest reading, not the date you are reading this.
“Новости (mospanoff)” (@mospanoff_news), 2,606 subscribers as measured 11 October 2026. Telegram Register, tgregister.com/channel/mospanoff_news.
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.