Telegram RegisterThe public register of Telegram
Telegram profile photo for InfoSecTube

Channel

InfoSecTube

@InfoSecTube

On this record: Growth · Engagement · Reactions · Posts · Cite this entry

1,768subscribers

+18 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of 1,000–3,162.

Register entry

Telegram ID-1001304355949
TypeChannel
Username@InfoSecTube
CreatedBetween 1 March 2018 and 31 July 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live22 August 2026
Measurements held7
Confirmed unchanged1 time, most recently 22 August 2026
On Telegramt.me/InfoSecTube

Growth

1,7491,7681,758.56 August 2026 — 1,750 subscribers7 August 2026 — 1,749 subscribers10 August 2026 — 1,755 subscribers13 August 2026 — 1,751 subscribers16 August 2026 — 1,759 subscribers18 August 2026 — 1,760 subscribers22 August 2026 — 1,768 subscribers6 August 202622 August 2026
7 measurements spanning 16 days, net +18. 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 1,746–1,771 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
22 Aug 2026, 14:121,768+8
18 Aug 2026, 21:551,760+1
16 Aug 2026, 05:171,759+8
13 Aug 2026, 00:261,751-4
10 Aug 2026, 01:281,755+6
7 Aug 2026, 06:561,749-1
6 Aug 2026, 09:331,750first reading

Engagement

22 posts held, back to 28 May 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 2 pagesof Telegram’s post history, 20 posts per page.

ERR · 30 days
8.80%
avg views ÷ 1,768 subscribers
Avg views / post
156
2 posts measured
Reaction rate
this channel exposes no reaction counts
Posts in window
4
of 22 held

ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.

ER is defined industry-wide as (forwards + reactions + comments) ÷ views— note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate.

What these figures were computed from
WindowRolling 30 days · latest post in window 7 August 2026
Posts held22 (28 May 20267 August 2026)
Views total311
Reactions total
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken7 Aug 2026, 17:38 UTC

Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.

Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.

Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.

Reaction mix

9 reactions across 7 posts, in 3 distinct kinds. The most used accounts for 77.8% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
777.8%
🏆111.1%
👍111.1%

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 7 of the 22 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 9reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 22 most recent posts we hold, published 28 May 2026 to 7 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.

Recent posts

7 Aug 2026, 16:37 UTCviews —

InfoSecTube pinned «Android apps are isolated from each other for security. One app cannot simply read another app’s memory or directly access protected services. 🔒 But then how does an app use your camera, fingerprint sensor, Wi-Fi, or Android Keystore? 📷👆📶🔐 That is where…»

7 Aug 2026, 16:37 UTC21 viewsread 7 August 2026

Android apps are isolated from each other for security. One app cannot simply read another app’s memory or directly access protected services. 🔒 But then how does an app use your camera, fingerprint sensor, Wi-Fi, or Android Keystore? 📷👆📶🔐 That is where IPC—and especially Android Binder—comes in. 🔄 In this video, I explain: ✅ What a process is ✅ Why Android isolates apps ✅ How IPC lets isolated processes communic

28 Jul 2026, 04:17 UTCviews —

InfoSecTube pinned «🚨 OpenAI’s AI Escaped Its Sandbox—and Reached Hugging Face! This sounds like science fiction, but it happened during a real cybersecurity evaluation. While solving an exploitation benchmark, advanced AI models discovered an unintended route outside their sandbox…»

27 Jul 2026, 19:48 UTC290 viewsread 7 August 2026

🚨 OpenAI’s AI Escaped Its Sandbox—and Reached Hugging Face! This sounds like science fiction, but it happened during a real cybersecurity evaluation. While solving an exploitation benchmark, advanced AI models discovered an unintended route outside their sandbox, gained internet access, and reached Hugging Face’s production infrastructure. 🤖💥 In this video, we explore: 🔹 How the AI escaped its sandbox 🔹 Why a package

24 Jul 2026, 06:08 UTC313 viewsread 7 August 2026

🛡 How do Android apps communicate without sharing memory? When you unlock a banking app with your fingerprint, multiple isolated processes must communicate with Android system services, the Keystore, and secure hardware—all within milliseconds. But if these processes cannot access each other’s memory, how do they exchange information safely? 🤔 In this new InfoSecTube video, you’ll learn: 🔹 What a process is 🔹 Why

23 Jul 2026, 23:29 UTC549 viewsread 7 August 2026

Kimi kimi is one of the strongest AIs recently introduced. 🤖 It has a feature that allows you to get a premium subscription ranging from 3 days to 1 year. ⏳ All you need to do is sign up with a new email to try your luck. ✉️ ▪️Sign up link 🔗 🎯@InfoSecTube 📌YouTube channel 🎁Boost Us

21 Jul 2026, 19:49 UTC297 views1 reactionsread 7 August 2026

⚔️ Android 17: The Quantum Warrior Awakens Quantum computers could eventually break many of today’s encryption systems. So how is Android preparing for the post-quantum era? In this new video, we explore: 🔐 Android 17’s quantum-resistant security direction 🧬 Post-quantum cryptography and why it matters 📱 How future Android devices may protect your sensitive data ⚠️ The security challenges developers and users should

🏆1

18 Jul 2026, 15:16 UTC222 views2 reactionsread 7 August 2026

🚀 NEW VIDEO — HOW LLMs GENERATE TEXT What happens inside an AI after you submit a prompt? In Lesson 2 of AI Security 101, we explain: 🧩 What tokens are 🧠 How attention and embeddings work ⚙️ What model parameters represent 📊 How an LLM predicts its next token 🎲 Greedy decoding vs sampling 🌡 Temperature and top-p 🔐 Why the generation pipeline matters for AI security This lesson gives you the foundation needed to u

2

16 Jul 2026, 16:56 UTCviews —

InfoSecTube pinned «🚀 New Video: AI Security 101 — Neural Networks & LLMs Before learning how to hack or secure AI systems, you need to understand how they actually work. In this video, you’ll learn: 🧠 How neural networks learn ⚖️ What weights and biases do 🔄 How backpropagation…»

16 Jul 2026, 16:56 UTC322 views1 reactionsread 7 August 2026

🚀 New Video: AI Security 101 — Neural Networks & LLMs Before learning how to hack or secure AI systems, you need to understand how they actually work. In this video, you’ll learn: 🧠 How neural networks learn ⚖️ What weights and biases do 🔄 How backpropagation works 🤖 How large language models predict text 🏗 Encoder, decoder, and encoder-decoder architectures 🔐 Why these concepts matter for AI security This is the

👍1

7 Jul 2026, 20:26 UTC256 viewsread 7 August 2026

🎯 What is a Supply Chain Attack? A Supply Chain Attack compromises a trusted vendor or library to reach the actual target. SolarWinds hit 18,000+ orgs. MOVEit hit 2,500+. Log4Shell hit millions of Java apps. One vendor = thousands of victims. 🔍 How it works: 1. Attacker compromises a trusted vendor 2. Injects malicious code into a legitimate update 3. Victim installs "trusted" software 4. Backdoor deployed → latera

3 Jul 2026, 20:26 UTC269 viewsread 7 August 2026

- Email security gateway — block malicious links - Web proxy / TLS inspection — analyze traffic - DNS sinkholing — block C2 callbacks - Behavioral detection — exploit kit behaviors - HIPS / System call filtering — block shellcode - Memory protections: - MFA on email — prevent account-driven downloads - Backup strategy — 3-2-1 immutable backups - Incident response plan — exploit detected, isolate fast - Honeypot / can

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

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

“InfoSecTube” (@InfoSecTube), 1,768 subscribers as measured 22 August 2026. Telegram Register, tgregister.com/channel/InfoSecTube.

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.