😊 Что будет через 100 дней? В одном месте снова соберутся разработчики, эксперты по защите ПО и те, кто умеет превращать технологии в бизнес. 12 ноября — GuardConf. Регистрация — скоро. Сообщество конференции GuardConf
🔥8🎉4⚡1👏1

Channel
@guardconf
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry
135subscribers
+5 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002721252083 |
|---|---|
| Type | Channel |
| Username | @guardconf |
| Created | Between 1 June 2025 and 30 September 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 9 August 2026 |
| Last confirmed live | 8 September 2026 |
| Measurements held | 5 |
| Confirmed unchanged | 2 times, most recently 8 September 2026 |
| On Telegram | t.me/guardconf |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 29 Aug 2026, 03:06 | 135 | +1 |
| 22 Aug 2026, 22:06 | 134 | +1 |
| 15 Aug 2026, 11:04 | 133 | +3 |
| 9 Aug 2026, 01:15 | 130 | no change |
| 7 Aug 2026, 17:24 | 130 | first reading |
8 posts held, back to 3 October 2025 — 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 8 posts for this entry, the most recent from 4 August 2026. An engagement rate over an empty window would be a number about nothing.
Measured directly from 1 video 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.
77 reactions across 6 posts, in 12 distinct kinds. The most used accounts for 27.3% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 🔥 | 21 | 27.3% | |
| custom 5449759615346548186 | 12 | 15.6% | |
| ⚡ | 11 | 14.3% | |
| 👍 | 7 | 9.09% | |
| custom 5359495603401294031 | 4 | 5.19% | |
| custom 5359705017416711659 | 4 | 5.19% | |
| ❤ | 4 | 5.19% | |
| 🎉 | 4 | 5.19% | |
| 👏 | 4 | 5.19% | |
| custom 5359407268808916487 | 2 | 2.60% | |
| custom 5359733299776356691 | 2 | 2.60% | |
| 🤩 | 2 | 2.60% |
Custom emoji. 5 of the rows above are Telegram custom emoji, which the public preview renders as an element carrying only a numeric id — no character, and no image we can reach. The id is printed as-is rather than substituted with a look-alike glyph, because a stand-in would be our invention showing where a measurement should be. The counts beside them are Telegram’s.
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 6 of the 8 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 77 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 8 most recent posts we hold, published 3 October 2025 to 4 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.
😊 Что будет через 100 дней? В одном месте снова соберутся разработчики, эксперты по защите ПО и те, кто умеет превращать технологии в бизнес. 12 ноября — GuardConf. Регистрация — скоро. Сообщество конференции GuardConf
🔥8🎉4⚡1👏1
Channel name was changed to «GuardConf 2026»
💬 Вы приглашены на Offline Guardant Meetup На GuardConf мы много говорили про лицензирование и способы монетизации софта с помощью решений Guardant — он же защита, он же доверие, он же прибыль, он же спокойствие разработчика! 🙂 📣 Тема получит развитие, ведь общий сбор сообщества Guardant запланирован в северной столице уже 14 ноября на Offline Guardant Meetup. Зарегистрироваться! ⭐️ Что будет? Эксперты поделятся о…
👍7🔥4👏3❤2
📊Экспертная плотность этого саммари зашкаливает Если вы не смогли присутствовать на GuardConf 2025 или хотите вспомнить, о чём шла речь – обязательно прочитайте. 🎯 В этом году мы собрали на площадке более 200 представителей ИТ-рынка, разрабатывающих и продвигающих собственные программные продукты. 🎯 Пригласили более 30 экспертов в области разработки, управления и маркетинга ПО. 🎯 Провели 4 дискуссии и 14 докладов. …
⚡5custom 54497596153465481864🤩2
📣 А вот и фотоотчёт Ещё раз окунаемся в атмосферу GuardConf 2025: https://disk.yandex.ru/d/B9yzMvfQuNDcXw 📩 Презентации спикеров уже разосланы участникам по почте, загляните во «Входящие». Теперь слово за вами!😉 Напомним, что мы подготовили форму обратной связи, чтобы узнать, как конференция прошла глазами участников. Сообщество конференции GuardConf
⚡5custom 54497596153465481864custom 53594072688089164872custom 53597332997763566912
😅 Итоги GuardConf 2025 В итоге конфа - done, впечатления переварил раньше, но решил поделиться мыслями только сейчас. Напомню, что описывал основное, что будет тут. Сами впечатления во время конференции описывал вот тут. Контент, который мы обсудили с коллегами остаётся с вами, кто успел послушать и получить технические кейсы с уязвимостями для разработки, самих процессов и концепта восприятия людей из ИБ. На диск…
🔥9❤1
👍 Выводами дискуссии про разработку безопасного ПО поделился ее модератор, Илья Шмаков, AppSec Teamlead Ланит
GuardConf 2025 — done. Но контент остаётся с вами🔥 В ближайшее время в канале появятся: 🔵фотографии с площадки, 🔵итоги в цифрах и фактах, 🔵информация о том, где можно найти презентации. Спасибо всем, кто уже прошёл опрос выше. Если ещё не отметились — сейчас отличный момент⬆️ 📣 А для тех, кто готов дать более развернутую обратную связь (можно анонимно), мы подготовили форму по ссылке. Сообщество конференции Gu…
custom 53594956034012940314custom 53597050174167116594custom 54497596153465481864❤1
Showing the 8 most recent of 8 posts we hold for @guardconf. 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.
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.
@guardconf named 1 handle that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all. A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
References a handle that is not a live channel — we have no record it ever was one.
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.
“GuardConf 2026” (@guardconf), 135 subscribers as measured 29 August 2026. Telegram Register, tgregister.com/channel/guardconf.
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.