Channel
@b4ckc0nn3ct
On this record: Topic · Growth · Engagement · Advertising · Posts · Citations · Cite this entry
1,537subscribers
+102 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1001826794105 |
|---|---|
| Type | Channel |
| Username | @b4ckc0nn3ct |
| Created | Between 1 October 2022 and 30 September 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 19 September 2026 |
| Measurements held | 13 |
| Confirmed unchanged | 2 times, most recently 19 September 2026 |
| On Telegram | t.me/b4ckc0nn3ct |
Hacking & security — 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 17 September 2026 and assigned it the closest of 31 fixed categories, at 78% 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 |
|---|---|---|
| 14 Sept 2026, 19:00 | 1,537 | +2 |
| 11 Sept 2026, 04:39 | 1,535 | +18 |
| 6 Sept 2026, 16:15 | 1,517 | +13 |
| 1 Sept 2026, 22:37 | 1,504 | +7 |
| 29 Aug 2026, 15:35 | 1,497 | +12 |
| 26 Aug 2026, 08:48 | 1,485 | +35 |
| 23 Aug 2026, 04:16 | 1,450 | +10 |
| 19 Aug 2026, 14:14 | 1,440 | +4 |
| 16 Aug 2026, 18:38 | 1,436 | -1 |
| 13 Aug 2026, 01:03 | 1,437 | -1 |
| 10 Aug 2026, 01:14 | 1,438 | +2 |
| 6 Aug 2026, 17:20 | 1,436 | +1 |
| 6 Aug 2026, 08:35 | 1,435 | first reading |
20 posts held, back to 29 May 2026 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 page 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 4 August 2026. An engagement rate over an empty window would be a number about nothing.
An ad marker, not a judgement about a post. A post is counted here because it carries one of two explicit markings: an erid token, which Russian law has required on paid placements since 2022 and which is issued against a specific advertising contract, or a #реклама / #ad hashtag in the body, which is the channel declaring it itself. The first is documentary; the second is a self-declaration and is weaker. No classifier reads the text and decides — nothing on this site guesses that a post is an advertisement.
This is a floor, and it can only ever be a floor. A channel that runs paid placements without marking them produces no marker for us to count, and an unmarked ad is indistinguishable from an ordinary post on the public surface. The ad load above therefore means “the share of posts that declared themselves”, never “the share of posts that were paid for”. A low figure is not evidence of a channel that runs few ads.
Both figures are medians, and no ratio between them is published. Each is a view reading that actually occurred on a post, picked by percentile_disc rather than averaged, so one viral post cannot move it and no interpolated value is invented between two readings. The sample on one side is under five posts, which is too thin to compare. The two figures are shown side by side with the count behind each, and deliberately not divided into a headline like “ads get x% fewer views” — an arithmetic that is easy to print and, at this sample size, means nothing.
| erid | Posts | First seen | Last seen |
|---|---|---|---|
| 2Vtzqvar6L9 | 1 | 26 June 2026 | 26 June 2026 |
A token repeated across several posts is one advertising contract placed more than once, which is what the identifier is for. The strings are reproduced exactly as they appeared in the post or in its click-through URL and are not validated against any registry — we record the marker a channel published, and whether it resolves to a real contract is a question for the register that issued it.
Measured over the 20 most recent posts we hold, published 29 May 2026 to 4 August 2026. Views are the latest single reading held for each post, and any reading at or above 1,000 is rounded by Telegram to three significant figures.
5 TOP FIVE - 10 ДОРОГИЕ ПОДПИСЧИКИ! Презентуем вашему вниманию юбилейный (десятый!) выпуск нашего журнала! правила игры те же: лайки, репосты и комменты ❤️ *Результатами психо-теста по одной из ссылок внутри журнала можно делиться в комментариях! ____ 🤖 backconnect
Для расширения кругозора отчеты различных rce с h1 ____ 🦌 backconnect
Для противодействия вербовке украинскими террористами, как ответственный гражданин России, я требую запретить все интернет-сайты и все приложения, через которые один человек может пообщаться с другим.
злободневная ____ 😁 backconnect
Обобщаем: Законопроект формально создает основу для поддержки российских фундаментальных моделей, но большая часть конкретных требований, процедур и мер поддержки вынесена в будущие постановления Правительства. Поэтому реальное содержание регулирования мы увидим не в самом законе, а в подзаконных актах. Главный бизнес риск заключается в концентрации рынка вокруг нескольких крупнейших компаний. Именно у них уже есть…
ИИ Законопроект Общее: 1. Риск усиления олигополии Формально закон поддерживает российских разработчиков. Фактически требования к суверенной модели реализуемы только крупнейшим компаниям (сбер/яндекс). 2. Порог в 1 млрд параметров Количество параметров является технически слабым критерием регулирования. Риск системы определяется не только размером модели, но и сферой применения, автономностью, доступом к инструмен…
Backconnect pinned a file
5 TOP FIVE - 9 Редакция специально для вас фильтрует инфошум и рисует смешных котов, дорогие подписчики ❤️ Рады презентовать вам новую экспериментальную рубрику «ЭйАй Security», в которой мы будем освещать наиболее интересные новости, связанные с искусственным интеллектом. Также обновили блок «Актуальные CVE», где будем описывать угрозы, наиболее актуальные для отечественного зоопарка продуктов, чтобы вы могли как…
«Следствие вели...» в Авито! И это не заголовок пугающей новости, а совсем наоборот ⚡️ Авито пригласил легенду тру-крайма Леонида Каневского, чтобы он разгадал таинственное и запутанное дело о внезапном росте ошибок 404 на endpoint аватарок и нашёл виновных. Звучит как план для просмотра на вечер! Кстати, кейс в основе сюжета довольно реальный... Но это уже совсем другая история 👀 📱 YouTube 📱 Rutube 📱 VK Видео
https://huggingface.co/empero-ai/Qwythos-9B-Claude-Mythos-5-1M yet another ai model, но в этот раз говорят, что натренированная на Claude Mythos и Claude Fable. ____ 💻 backconnect
На задворках Вселенной находился один магазинчик. Вывески на нем давно уже не было - ее когда-то унесло ураганом, а новую хозяин не стал прибивать, потому что каждый местный житель и так знал, что магазин продает желания. Ассортимент магазина был огромен, здесь можно было купить практически всё: огромные яхты, квартиры, замужество, пост вице-президента корпорации, деньги, детей, любимую работу, красивую фигуру, побе…
Photo, posted without a caption
Showing the 12 most recent of 20 posts we hold for @b4ckc0nn3ct. 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.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
Republishes
Channels on the register whose posts this channel has forwarded.
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.
Named by 3 registered channels — every channel on the register whose own posts have named this one, by its current username or any other username it currently holds, merged from two separately captured readings of the same fact so a namer caught by only one of them is not missed and a namer both caught is not counted twice. A username this channel has since dropped is not matched — that handle may belong to someone else now, and crediting today’s namer to yesterday’s owner would misattribute it.
Named by
Channels on the register whose posts name this channel's handle.
Names
Channels on the register whose handles appear in this channel's posts.
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.
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 14 September 2026 — this entry's latest reading, not the date you are reading this.
“Backconnect” (@b4ckc0nn3ct), 1,537 subscribers as measured 14 September 2026. Telegram Register, tgregister.com/channel/b4ckc0nn3ct.
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.