Telegram RegisterThe public register of Telegram
Telegram profile photo for Cybersécurité, IA & Tech

Channel

Cybersécurité, IA & Tech

@ledecodeur

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

878subscribers

+25 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-1001939481202
TypeChannel
Username@ledecodeur
CreatedBetween 1 April 2023 and 31 October 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live29 August 2026
Measurements held5
Confirmed unchanged1 time, most recently 29 August 2026
On Telegramt.me/ledecodeur

Growth

853878865.57 August 2026 — 853 subscribers8 August 2026 — 853 subscribers16 August 2026 — 868 subscribers22 August 2026 — 872 subscribers29 August 2026 — 878 subscribers7 August 202629 August 2026
5 measurements spanning 22 days, net +25. 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 849–882 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
29 Aug 2026, 13:28878+6
22 Aug 2026, 18:53872+4
16 Aug 2026, 08:07868+15
8 Aug 2026, 01:18853no change
7 Aug 2026, 21:49853first reading

Engagement

20 posts held, back to 30 July 2026the 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.

ERR · 30 days
8.05%
avg views ÷ 878 subscribers
Avg views / post
70.6
17 posts measured
Reaction rate
this channel exposes no reaction counts
Posts in window
17
of 20 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 held20 (30 July 20267 August 2026)
Views total1,201
Reactions total
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken8 Aug 2026, 01:18 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.

Recent posts

7 Aug 2026, 11:31 UTC37 viewsread 8 August 2026
Photo

📡 Contrôles aux frontières : comment sécuriser ses données Face aux outils d'analyse douaniers, l'EFF préconise le chiffrement intégral, la suppression des fichiers et l'extinction complète des terminaux.

7 Aug 2026, 06:01 UTC43 viewsread 8 August 2026
Photo

📡 Coups de filet & sanctions : 7 opérations contre la cybercriminalité du 7 août 2026 (dont Telegram) Arrestations, démantèlements de réseaux et sanctions : le bilan des 7 actions menées contre la cybercriminalité la semaine du 7 août 2026.

6 Aug 2026, 15:01 UTC49 viewsread 8 August 2026
Photo

📡 FINMA : la majorité des banques manque de plan post-quantique Le régulateur suisse FINMA exige des banques un inventaire cryptographique et une stratégie rapide face à la menace de déchiffrement futur.

6 Aug 2026, 11:30 UTC53 viewsread 8 August 2026
Photo

📡 DEF CON bannit les lunettes connectées à caméra pour sa 34e édition Face aux dérives d'enregistrement sans consentement, l'événement DEF CON bannit les lunettes connectées à caméra pour garantir le respect de la vie privée.

6 Aug 2026, 06:10 UTC52 viewsread 8 August 2026
Photo

📡 Data leaks : 15 fuites de données majeures du 6 août 2026 (dont DEF CON) Bases exposées, vols et compromissions : le bilan des 15 fuites de données marquantes de la semaine du 6 août 2026.

5 Aug 2026, 15:01 UTC60 viewsread 8 August 2026
Photo

📡 Project Perception : Microsoft déploie la défense par IA Microsoft lance Project Perception, une architecture d'agents IA autonomes capables de repérer, évaluer et corriger les vulnérabilités informatiques.

5 Aug 2026, 11:31 UTC60 viewsread 8 August 2026
Photo

📡 Bus électriques Yutong : Zurich relance les questions de cybersécurité La commande de bus électriques Yutong par la ville de Zurich posent des questions à propos des vulnérabilités de prise de contrôle à distance et de protection des données.

5 Aug 2026, 06:02 UTC67 viewsread 8 August 2026
Photo

📡 Menaces & IA : 13 dérives et avancées clés du 5 août 2026 (dont Microsoft) Détournement de modèles, nouveaux malwares génératifs et sécurité des agents : le récapitulatif des 13 actualités IA de la semaine du 5 août 2026.

4 Aug 2026, 15:01 UTC71 viewsread 8 August 2026
Photo

📡 GrapheneOS : la justice américaine poursuit un utilisateur Un citoyen risque cinq ans de prison pour avoir réinitialisé son smartphone GrapheneOS lors d'un contrôle douanier à l'aéroport d'Atlanta.

4 Aug 2026, 11:31 UTC75 viewsread 8 August 2026
Photo

📡 Google Chrome corrige plus de 1 000 vulnérabilités grâce à l'IA Grâce à l'intégration de l'IA, Google Chrome colmate 1 072 vulnérabilités en un mois, surpassant le total de ses correctifs des deux dernières années.

4 Aug 2026, 06:01 UTC78 viewsread 8 August 2026
Photo

📡 Ransomwares & piratages : 13 cyberattaques d’ampleur du 4 août 2026 (dont CyberAv3ngers) Infiltrations, demandes de rançon et paralysies de réseaux : retour sur les 14 attaques majeures de la semaine du 4 août 2026.

3 Aug 2026, 11:31 UTC87 viewsread 8 August 2026
Photo

📡 iMessage confond un chien avec du contenu sensible Alors que l'UE relance Chat Control, les filtres d'Apple montrent leurs limites en floutant par erreur des animaux dans les conversations.

Showing the 12 most recent of 20 posts we hold for @ledecodeur. 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 29 August 2026 — this entry's latest reading, not the date you are reading this.

“Cybersécurité, IA & Tech” (@ledecodeur), 878 subscribers as measured 29 August 2026. Telegram Register, tgregister.com/channel/ledecodeur.

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.