Telegram RegisterThe public register of Telegram

Channel

Axiom JDK

@axiomjdkpro

On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry

1,520subscribers

+2 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-1001185402298
TypeChannel
Username@axiomjdkpro
CreatedBetween 1 April 2018 and 31 July 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live13 August 2026
Measurements held3
Confirmed unchanged2 times, most recently 13 August 2026
On Telegramt.me/axiomjdkpro

Growth

1,5181,5201,5196 August 2026 — 1,518 subscribers7 August 2026 — 1,519 subscribers10 August 2026 — 1,520 subscribers6 August 202610 August 2026
3 measurements spanning 3 days, net +2. 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,518–1,520 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
10 Aug 2026, 02:521,520+1
7 Aug 2026, 02:531,519+1
6 Aug 2026, 15:491,518first reading

Engagement

21 posts held, back to 23 June 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
32.1%
avg views ÷ 1,520 subscribers
Avg views / post
488
14 posts measured
Reaction rate
1.19%
reactions ÷ views · ER floor
Posts in window
14
of 21 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. It is computed over the 13 of 14 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 7 August 2026
Posts held21 (23 June 20267 August 2026)
Views total6,837
Reactions total78
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken7 Aug 2026, 18:10 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.

What this channel posts

Video runtime
15s
Average length
8s

Measured directly from 2 videos 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.

Reaction mix

145 reactions across 20 posts, in 13 distinct kinds. The most used accounts for 43.4% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🔥6343.4%
👍3121.4%
1510.3%
106.90%
👀106.90%
🍾42.76%
🐳32.07%
❤‍🔥21.38%
👨‍💻21.38%
🤔21.38%
🎉10.69%
🏆10.69%
👏10.69%

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

Measured over the 21 most recent posts we hold, published 23 June 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, 11:04 UTC181 views4 reactionsread 7 August 2026

#видеозаписи 🌟 Как собрать Java-образ для контейнера так, чтобы он был компактным, быстро стартовал и не сыпался на проверках безопасности? Максим Лебедев, Developer Advocate Axiom JDK, разобрал это на БеКон 2026. В докладе — о безопасном базовом образе, кастомном JRE, настройке JVM в контейнере, ускорении старта через AppCDS и Native Image и верифицируемой цепочке поставки с SBOM, подписями и VEX. А в финале — ч

2🔥2

6 Aug 2026, 09:59 UTC289 views6 reactionsread 7 August 2026
Photo

👨‍💻 54% вайбкодеров проверяют код тем же ИИ, который его написал «Битрикс24» изучил, как российские вайбкодеры создают и проверяют приложения: Среди участников исследования 81% не считают разработку своей основной профессией, а 52% начали практически с нуля. При этом 72% сообщили, что их приложения уже работают почти автономно и обслуживают коллег или клиентов. 😬 Проверка за этим темпом не успевает: 54% респонденто

👨‍💻2🤔21👀1

4 Aug 2026, 08:35 UTC366 views6 reactionsread 7 August 2026
Photo

📦 Gradle всё ещё выглядит как чёрный ящик, где один build.gradle держится на магии и надежде? Наши друзья из PVS-Studio сделали бесплатный курс, который поможет разложить всё по полочкам. На примере реального мультимодульного проекта разберут api и implementation, Version Catalog и BOM, Convention Plugins, build-logic, а также сборку общих отчётов по тестам и покрытию. Хороший вариант, чтобы перестать дублировать н

❤‍🔥2👍2🔥2

3 Aug 2026, 10:45 UTC365 views3 reactionsread 7 August 2026

Большой семейный фестиваль для всех, кто интересуется технологиями — со стендапом и без скучных слайдов В программе наши друзья из 3data подготовили лекции, инженерные челленджи, спортивные активности, живую музыку, мастер-классы и отдельную зону для детей. Отличная возможность обсудить проекты, обменяться опытом и провести насыщенный выходной вместе с семьей.

🔥2👀1

3 Aug 2026, 10:45 UTC367 views7 reactionsread 7 August 2026
Forwarded from @dc3dataVideo

Что ждет гостей Фестиваля 3data «Московские ЦОДы»? 💚 15-го августа Таганский детский парк превратится в самый настоящий город впечатлений с огромным количеством активностей, лекций, развлечений и, конечно, подарков! 📌Главная сцена Яркое шоу иллюзиониста Марка Филини, выступление секретного стендап-хедлайнера, имя которого мы раскроем совсем скоро, а также интерактивные квизы. 📌«Университет» Выступления приглашенны

🔥3🍾2🎉1👏1

31 Jul 2026, 12:59 UTC509 views7 reactionsread 7 August 2026
Photo

⚠️ Код напишет ИИ. Кто проверит, что он не сломает прод? С помощью ИИ уже можно избавиться от значительной части рутины и навайбкодить вполне рабочий прототип — это мы все и так знаем. Но работу инженера это не отменяет — фокус смещается с «написать руками» на «поставить задачу, проверить и встроить результат». В рамках опроса «Авито Работы» 2 тыс. россиян выделили следующие ключевые навыки работы с нейросетями: —

👍4👀21

30 Jul 2026, 10:05 UTC538 views8 reactionsread 7 August 2026
Photo

🚀 JDK будет получать обновления чаще 20 июля Oracle объявила о переходе на ежемесячные релизы обновлений безопасности Java. Теперь к привычным квартальным CPU (Critical Patch Update), которые выходят в январе, апреле, июле и октябре, добавятся промежуточные релизы раз в месяц — CSPU (Critical Security Patch Update). Эти обновления посвящены безопасности и стабильности Java-платформы, а не развитию языка или добавлен

🔥431

29 Jul 2026, 08:29 UTC501 views2 reactionsread 7 August 2026
Photo

#релиз 🔄 Продолжаем обновлять наши продукты в рамках июльского цикла. Вышли новые сборки Axiom Native Image Kit Pro: 23.0.13, 23.1.12 и 25.0.4. Axiom NIK Pro преобразует JVM-приложения в нативные исполняемые файлы. Они запускаются автономно и почти моментально, занимают меньше места и помогают сократить потребление памяти — особенно это заметно в контейнерных и облачных сценариях. ✔️Главное в релизе: • устранено 1

👍1🔥1

28 Jul 2026, 10:01 UTC≈1,040 views7 reactionsread 7 August 2026
Photo

#кейсы 🤝 GitFlic и Axiom JDK подтвердили совместимость своих решений Теперь российскую DevOps-платформу можно использовать вместе с полноценным Java-стеком Axiom Spring — от исходного кода до запуска приложения. В состав Axiom Spring входят Spring Framework и Spring Boot с российской поддержкой, а также: 🔘 Axiom JDK Pro — среда разработки и исполнения Java-приложений, в которой GitFlic может работать на инфраструк

🔥3👀211

27 Jul 2026, 13:59 UTC462 views8 reactionsread 7 August 2026
Photo

#релиз ☕️ Обновили Axiom JDK для шести версий Java Вышел июльский апдейт Axiom JDK — от актуальных Java 26 и 25 до проверенных временем Java 8 и 11. Доступны сборки 26.0.2, 25.0.4, 21.0.12, 17.0.20, 11.0.32 и 8u502. Главное: • устранено 18 CVE в core-libs, security-libs, client-libs и JavaFX; • добавлено 1141 исправление и бэкпорт для шести поддерживаемых веток; • база часовых поясов IANA обновлена до версии 2026b

🔥51👀1👍1

22 Jul 2026, 10:02 UTC601 views4 reactionsread 7 August 2026
Photo

#релиз 🔐 Обновили Libercat и Libercat EE: CVE закрыты, исправления внесены Вышли новые версии Libercat 11.0.23-1, 10.1.56-1 и 9.0.119-1, а также Libercat EE 9.1.3-21 и 8.0.16-38. Обновления доступны и для Libercat 9/10 Embedded. 📌 Главное: • Исправлены 37 уязвимостей, включая CVE в Catalina, ActiveMQ, Bouncy Castle и Neethi; • Внесено 541 исправление и улучшение: 174 — в Libercat 11, по 172 — в Libercat 9 и 10, ещ

🔥3👍1

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

Citation-graph rank

Citation-graph rank — 131,195 of 1,478,351entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.

Forward network

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.

Mentions

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.

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.

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.

“Axiom JDK” (@axiomjdkpro), 1,520 subscribers as measured 10 August 2026. Telegram Register, tgregister.com/channel/axiomjdkpro.

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.