Telegram RegisterThe public register of Telegram

Channel

Comunidade Cloud®

@bootcampcloud

On this record: Topic · Observations · Also posting the same content · Growth · Engagement · Posts · Cite this entry

3,336subscribers

-8 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1001236522555
TypeChannel
Username@bootcampcloud
CreatedBetween 1 March 2018 and 30 June 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live10 August 2026
Measurements held3
Confirmed unchanged1 time, most recently 10 August 2026
On Telegramt.me/bootcampcloud

Topic

Technology — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-UD-Q6_K_XL, prompt version 1) read this channel’s own recent posts on 11 August 2026 and assigned it the closest of 31 fixed categories, at 100% 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.

Observations

These are measurements, not verdicts. Each one below states something we counted, alongside the evidence it was counted from, so you can check it rather than take it. None of them is graded: every observation this register holds is recorded at severity 0, because the precision of the detectors behind them has not been measured yet, and a rating we cannot support is worse than none. Read each as a fact about the data, not as a judgement about the channel. How we measure.

Content that also appears on other registered channels

Posts published here appear word for word on 1 other registered channel. The matching is on the text itself, not on Telegram’s forward marker, so it finds a copy whether or not it was labelled as one.

Matching posts — open both and compare (6 of the pairs behind the counts below)
Posted firstThenOverlapGap
@osmaisnerds/11542 Jun 2022, 23:25 UTC@bootcampcloud/446 · this entry2 Jun 2022, 23:25 UTC1.00under a minute
@bootcampcloud/447 · this entry4 Jun 2022, 19:24 UTC@osmaisnerds/11554 Jun 2022, 19:27 UTC1.002 minutes
@osmaisnerds/11565 Jun 2022, 22:06 UTC@bootcampcloud/448 · this entry5 Jun 2022, 22:06 UTC1.00under a minute
@osmaisnerds/11624 Jan 2023, 22:20 UTC@bootcampcloud/493 · this entry4 Jan 2023, 22:20 UTC1.00under a minute
@bootcampcloud/495 · this entry10 Jan 2023, 12:14 UTC@osmaisnerds/116410 Jan 2023, 12:15 UTC1.0072 seconds
@bootcampcloud/496 · this entry12 Jan 2023, 12:15 UTC@osmaisnerds/116512 Jan 2023, 12:18 UTC1.003 minutes
Every channel this entry shares post bodies with
ChannelMatching postsText overlapTypical gapPublished first
@osmaisnerds11 (8/8 hand-verifiable sample passed)1.00under a minute@osmaisnerds (65)

Text overlap is the Jaccard coefficient over the set of distinct three-word phrases in the two bodies: 1.00 is identical wording, and the threshold for counting a pair at all is 0.70. Candidates are generated by simhash LSH (4 x 16-bit bands, exact Hamming <= 3) verified against the bodies with Jaccard over the SET of distinct 3-word shingles. Published first counts which side of each matching pair carries the earlier timestamp — in this corpus, which is the limitation directly below.

What this cannot establish

MEASURED, DOMINANT ERROR SOURCE: a post ingested before 2026-08-06 may have carried a forward header that was not recorded. A 45-pair hand-check against live t.me pages found 14 (31%) where the live page shows a forward header naming the other channel and the database has none, plus 4 more (9%) naming a third party. The text match itself was wrong 0 times out of 45. Read attribution_capture.items_in_trusted_window before treating the unattributed count as a claim.

Telegram lets a channel forward a post with a header naming the source, and we only began reliably recording that header on 2026-08-06. None of the 6 matches recorded here fall after that date, so for this entry we cannot say whether any of them carried a credit. The duplication is measured; the absence of attribution is not.

“Published first” means first in this corpus. We hold 18 comparable posts for this entry, running 30 May 2022 to 6 July 2023. A channel we have read one page deep will look younger than a neighbour we have read in full, and the order would flip with no change in the underlying facts.

The detector’s own notes on this observation, as it recorded them. Names in this_style are fields of the underlying evidence record, which the plain-English paragraphs above read out for this entry.

  • Verbatim republication has three causes and the text separates only two: a clone/mirror, unattributed copy-paste, or BOTH channels copying a common third source that neither attributes. The spread filter (content held by at most 8 channels) reduces the third and does not remove it.
  • 'Earliest' means earliest IN THIS CORPUS. A channel ingested one page deep will look younger than a neighbour ingested in full; corpus_coverage above is there to be checked before the direction is believed.
  • shared_verified_est extrapolates the sampled pass rate over the full narrow match count; sampled/passed are the numbers actually measured.
  • Absence of a forward header is not proof of intent: Telegram lets a channel disable forward attribution, and a credit written in the body is not parsed as attribution here (mention_edge_either_way above is the closest available signal).

Across the whole group of 2, the earliest publisher we hold is @osmaisnerds. That is a statement about our reading window, not a claim of authorship.

Recorded under the key clone_mutual, last confirmed 8 August 2026. An observation that a later pass no longer finds is cleared, and a cleared observation is removed from this page rather than being shown struck through — we do not keep publishing a claim we have withdrawn. Dispute an observation.

Also posting the same content

This channel’s posts match, word for word or near enough, posts on 1 other registered channel, found by comparing text fingerprints across every channel on the register. That matching has been checked by hand against the live Telegram pages and found reliable — 0 wrong of 45 pairs re-read.

Which channel, if either, published first is deliberately not shown. The same hand-check found that reading wrong 18 of 45 times — 60%, no better than a coin flip — because it depends on how deep our own crawl happened to reach into each channel’s history, not on when the content was actually first posted. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Word-for-word matching has several ordinary explanations besides copying — a channel mirroring itself, an unattributed repost, or two channels independently repeating the same wire story — and this measurement cannot tell those apart. How this is measured.

Growth

3,3363,3443,3406 August 2026 — 3,344 subscribers7 August 2026 — 3,344 subscribers10 August 2026 — 3,336 subscribers6 August 202610 August 2026
3 measurements spanning 4 days, net -8. 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 3,335–3,345 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
10 Aug 2026, 14:573,336-8
7 Aug 2026, 13:003,344no change
6 Aug 2026, 23:003,344first reading

Engagement

20 posts held, back to 30 May 2022the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 3 pagesof 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 6 July 2023. An engagement rate over an empty window would be a number about nothing.

Recent posts

6 Jul 2023, 08:15 UTCviews —

The owner of this channel has been inactive for the last 5 months. If they remain inactive for the next 27 days, they may lose their account and admin rights in this channel. The contents of the channel will remain accessible for all users.

10 Feb 2023, 19:30 UTC≈4,040 viewsread 7 August 2026

Resumão da Semana Um apanhado dos melhores conteúdos sobre Cloud, AWS, Azure e Devops para Profissionais de Infra e desenvolvimento Opa! Tudo certo? Como está sendo sua sexta-feira? Espero que ótima! E, para ficar ainda melhor, trouxe o seu resumão de conteúdos da semana! Confira tudo que aconteceu nessa última semana e fique atualizado: Nunca Migre um Servidor para AWS Assim...O Que Fazer na AWS https://www.you

28 Jan 2023, 11:00 UTC≈2,740 viewsread 7 August 2026

Opaa, bom dia galera! Chegou o seu resumão de conteúdos da semana! É um apanhado dos melhores conteúdos sobre Cloud, AWS, Azure e Devops para Profissionais de Infra e desenvolvimento! Confira tudo que aconteceu nessa última semana e fique atualizado sobre tudo que está por vir! Quero começar dizendo sobre a Maratona Cloud Upper! Saiba mais abaixo: A MARATONA Cloud Upper foi criada para o seguinte propósito: Pr

21 Jan 2023, 13:00 UTC≈1,820 viewsread 7 August 2026

Falaa galera! Tudo certo? Trouxe o nosso resumão de conteúdos especialmente para vocês! É um apanhado dos melhores conteúdos sobre Cloud, AWS, Azure e Devops para Profissionais de Infra e desenvolvimento! Confira tudo que aconteceu nessa semana e claro, te manter atualizado sobre tudo que está por vir! Ahh, mas antes, quero saber se já te contei uma novidade importante... Não sei se já tá sabendo, mas a Maratona

16 Jan 2023, 03:34 UTCviews —

The account of the user that owns this channel has been inactive for the last 5 months. If it remains inactive in the next 7 days, that account will self-destruct and this channel may no longer have an owner.

12 Jan 2023, 12:15 UTC≈1,560 viewsread 7 August 2026
Photo

🤯 Comece o ano mais bem preparado para conquistar melhores vagas🚨 🔥 No dia 14/01 faremos um treinamento intensivo e prático de Microsoft Azure. Vamos juntar teoria, prática e a experiência de um professor que respira Cloud diariamente dentro de grandes empresas para você aprender tudo o que precisa para começar a trabalhar com Azure. 👉🏻 Aperte no link abaixo e saiba mais detalhes: https://bit.ly/intensivao-azure-t

10 Jan 2023, 12:14 UTC≈1,480 viewsread 7 August 2026

🤯 INTENSIVÃO AZURE - 3 meses de aprendizado em um dia 🚨 🔥 Um Treinamento Intensivo e Hands-on para você começar a trabalhar com Microsoft Azure, uma das 3 plataformas de Cloud mais usadas no mundo. 👉🏻 Aperte no link abaixo e saiba mais detalhes: https://bit.ly/intensivao-azure-t1tg Aproveite o 1o Lote com valor promocional - inscrições por tempo limitado! O preço está indecente de tão baixo… 🚀 Bora começar o ano

9 Jan 2023, 23:14 UTC≈1,410 viewsread 7 August 2026

Intensivão AZURE 🤯 Quer começar 2023 aprendendo Microsoft Azure, na Prática? Azure é a plataforma de CLOUD da Microsoft. É uma das que mais cresce no mundo e que mais tem oportunidades com bons cargos e salários. Se você quer dar seus primeiros passos em Azure de forma prática e do Jeito Certo, Então matricule-se no Intensivão Azure por um preço indecente de tão baixo… Veja todos detalhes no link: https://bit.ly

4 Jan 2023, 22:20 UTC≈1,790 viewsread 7 August 2026

Fique na frente no jogo de armazenamento em nuvem com @Azure Blob Storage and Storage Accounts - a combinação perfeita para um armazenamento seguro e eficiente! Assista aqui, a aula completa: https://www.youtube.com/watch?v=xbfokXF_O6w #Azure #CloudStorage #VocêNaFrente

3 Jan 2023, 19:41 UTCviews —

The account of the user that owns this channel has been inactive for the last 5 months. If it remains inactive in the next 20 days, that account will self-destruct and this channel may no longer have an owner.

27 Dec 2022, 00:25 UTCviews —

The account of the user that owns this channel has been inactive for the last 5 months. If it remains inactive in the next 27 days, that account will self-destruct and this channel may no longer have an owner.

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

“Comunidade Cloud®” (@bootcampcloud), 3,336 subscribers as measured 10 August 2026. Telegram Register, tgregister.com/channel/bootcampcloud.

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.