Telegram RegisterThe public register of Telegram

Channel

InfoHub | Новости

@INF0HUB

On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry

139subscribers

+0 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-1002096691695
TypeChannel
Username@INF0HUB
DescriptionIdlnet.online | ⚡️ 🇷🇺 🤍 #политика #технологии #новости
CreatedBetween 1 November 2023 and 31 May 2024— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live8 August 2026
Measurements held2
On Telegramt.me/INF0HUB

Growth

1397 Aug 2026, 16:32 — 139 subscribers8 Aug 2026, 22:46 — 139 subscribers7 Aug 2026, 16:328 Aug 2026, 22:46
2 measurements spanning 1 day. 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 138–140 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
8 Aug 2026, 22:46139no change
7 Aug 2026, 16:32139first reading

Engagement

19 posts held, back to 16 July 2025the 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 19 posts for this entry, the most recent from 6 May 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Photos
2,060
Videos
1,520
Links
3,740

Lifetime counters from Telegram’s own channel header, read 8 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.

Video runtime
36s
Average length
12s

Measured directly from 3 videos 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.

Reaction mix

13 reactions across 3 posts, in 5 distinct kinds. The most used accounts for 38.5% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🤔538.5%
🔥323.1%
215.4%
🤯215.4%
❤‍🔥17.69%

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 3 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 13reactions 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 16 July 2025 to 6 May 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.

Recent posts

6 May 2026, 13:38 UTC54 viewsread 8 August 2026

Тут интернет эксперт выступил с успокоительной речью, что введение платы за зарубежный трафик (мера против VPN) - бессмысленна, потому что ВПНы научились маскироваться под российский. «Оператор видит только ближайший узел маршрута, а дальнейшее соединение проходит через промежуточные серверы вне его контроля — часто в российских дата-центрах. Поэтому технически отследить «зарубежный» трафик будет сложно» Если вас к

7 Apr 2026, 15:51 UTC64 viewsread 8 August 2026
Forwarded from @overbafer1Photo

😏 Популярные в РФ VPN-клиенты работают на товарища майора. Выяснилось, что многие хваленые VPN, через которые работяги спасаются от блокировок РКН, оказались дырявым куском говна. 🕵🏻‍♂️ Энтузиаст с Хабра выкатил разгромное расследование, где выяснил, что VPN на базе Xray и sing-box (всякие v2rayNG, Hiddify и NekoBox) сливают ваш реальный IP-адрес. Проблема в локальном прокси, из-за чего любой сторонний софт на тел

18 Mar 2026, 17:43 UTC78 viewsread 8 August 2026
Forwarded from @WhiteNewsNDAPhoto

⚡️ Telegram наносит ответный удар Прокси-сервер мессенджера атакует фильтры ТСПУ РКН (ответственные за замедление работы приложения), отправляя миллиарды запросов и перегружая оборудование. В результате в некоторых регионах России временно заработал WhatsApp* и возникли проблемы с «белыми списками». * — принадлежит Meta, признанной экстремистской в РФ. ⚪️ W — значит White.

13 Mar 2026, 23:14 UTC80 viewsread 8 August 2026
Forwarded from @media1337Photo

Telegram можно заблокировать только полным отключением от глобального интернета — так считает IT-эксперт Александр Исавнин. По его словам, даже при попытках ограничить доступ мессенджер продолжит работать: борьба Роскомнадзора с VPN может идти бесконечно — на новые блокировки будут появляться новые способы обхода. Даже при введении «белых списков» доступ сохранится, если остаётся хоть какое-то соединение с сетью. Е

6 Mar 2026, 09:31 UTC106 viewsread 8 August 2026
Forwarded from @SecLabNews

🤖MAX снова под огнём: личные фото в мессенджере оказались уязвимы? Вокруг мессенджера MAX разгорелся неожиданный спор о приватности файлов. Пользователь Pikabu под ником 5time заявил, что изображение из личной переписки в веб-версии сервиса можно открыть по прямой ссылке без авторизации. Более того, по его словам, ссылка продолжает работать даже после удаления картинки из чата. Хабр сообщил, что проверка редакции по

5 Mar 2026, 04:26 UTC86 viewsread 8 August 2026

🗣Иран уничтожает мировой интернет — уже несколько дней подряд он целенаправленно разносит дата-центры Amazon ▪️Удары Ирана по Ближнему Востоку выполняют план аятоллы Али Хаменеи, разработанный незадолго до его смерти. Цель — вызвать потрясения на мировых рынках и повысить ставки, чтобы оказать давление на США и Израиль, в частности через атаки на энергетические объекты региона. ▪️1 марта Иран наносит удар по дата-це

24 Feb 2026, 00:23 UTC87 viewsread 8 August 2026
Photo

I keep repeating one thing to myself: prevention is cheaper than recovery. 💸🔒 One “quick login from a link” can turn into hours of IT work, password resets, session kills, finance verification, downtime, and stress. 😬 So my rule is simple: protection should show up BEFORE I type a password/OTP or approve a payment — at the decision moment, not in a report after. 👀⚠️ That’s why I built GhostGuard 👻: privacy-first,

17 Feb 2026, 01:46 UTC92 viewsread 8 August 2026
Photo

Risky page signals 🚩🔒 7 signals a page is risky: 1) 🌀 Extra step / unexpected redirect 2) ❓ Unexpected request (re-login, OTP, “verify identity”, billing update) 3) 🌐 Strange domain (typos, extra words, weird ending) 4) 🧾 Form asks for too much (password + OTP + card, etc.) 5) ⏰ Urgency/pressure (“act now”, “final notice”) 6) 📵 Weird permissions (notifications, downloads, “install update”) 7) 🧐 “Almost right” but sl

11 Feb 2026, 13:34 UTC115 views4 reactionsread 8 August 2026
Video

🧠 This video clearly shows how our brain works When we see a familiar interface, logo, or login form, the brain doesn’t analyze — it recognizes. What’s happening here is important: unused neural connections weaken and fade over time, while new ones are constantly being formed based on repeated patterns. Neural pathways fire automatically: — “I’ve seen this before” — “I’ve been here” — “This is safe” Modern phishin

2❤‍🔥1🤯1

10 Feb 2026, 18:46 UTC98 viewsread 8 August 2026
Video

Наш впн ловит даже в Антарктиде:) Купить: @idlnetbuy_bot

31 Jan 2026, 20:28 UTC153 viewsread 8 August 2026
Forwarded from @Idlnet_group

⚠️ СКАМ-БОТ @pswallet — крадёт initData и запускает цепочку атак на Telegram-аккаунты Описание схемы (на основе реального инцидента 31.01.2026): 1. Пользователь запускает бота @pswallet и Mini App (ссылка: t.me/pswallet или через сайт pswallet.org). 2. Mini App получает полный initData: user.id, first_name, username, номер телефона, language_code, is_premium и т.д. 3. Данные уходят на сервер мошенников (вероятно, Ю

Showing the 12 most recent of 19 posts we hold for @INF0HUB. 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.

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

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

“InfoHub | Новости” (@INF0HUB), 139 subscribers as measured 8 August 2026. Telegram Register, tgregister.com/channel/INF0HUB.

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.