Telegram RegisterThe public register of Telegram
Telegram profile photo for Spring АйО

Channel

Spring АйО

@spring_aio

On this record: Growth · Engagement · What this channel posts · Reactions · Stars · Advertising · Posts · Posts edited after publishing · Citations · Cite this entry

10,911subscribers

-7 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1002069349348
TypeChannel
Username@spring_aio
CreatedBetween 1 November 2023 and 31 May 2024— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live30 August 2026
Measurements held19
Confirmed unchanged1 time, most recently 30 August 2026
On Telegramt.me/spring_aio

Growth

10,90410,92110,912.56 August 2026 — 10,918 subscribers6 August 2026 — 10,921 subscribers8 August 2026 — 10,917 subscribers10 August 2026 — 10,915 subscribers11 August 2026 — 10,914 subscribers13 August 2026 — 10,919 subscribers14 August 2026 — 10,920 subscribers16 August 2026 — 10,917 subscribers17 August 2026 — 10,921 subscribers18 August 2026 — 10,919 subscribers19 August 2026 — 10,918 subscribers21 August 2026 — 10,920 subscribers24 August 2026 — 10,913 subscribers25 August 2026 — 10,909 subscribers26 August 2026 — 10,905 subscribers27 August 2026 — 10,904 subscribers28 August 2026 — 10,905 subscribers28 August 2026 — 10,904 subscribers30 August 2026 — 10,911 subscribers10,9116 August 202630 August 2026
19 measurements spanning 24 days, net -7. 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 10,901–10,924 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
30 Aug 2026, 01:5810,911+7
28 Aug 2026, 23:2810,904-1
28 Aug 2026, 02:1210,905+1
27 Aug 2026, 03:3310,904-1
26 Aug 2026, 05:1310,905-4
25 Aug 2026, 05:5210,909-4
24 Aug 2026, 05:3410,913-7
21 Aug 2026, 03:4610,920+2
19 Aug 2026, 09:0310,918-1
18 Aug 2026, 09:0310,919-2
17 Aug 2026, 11:3310,921+4
16 Aug 2026, 02:0610,917-3
14 Aug 2026, 10:2710,920+1
13 Aug 2026, 02:4510,919+5
11 Aug 2026, 00:5110,914-1
10 Aug 2026, 03:2110,915-2
8 Aug 2026, 00:4110,917-4
6 Aug 2026, 22:0710,921+3
6 Aug 2026, 05:4910,918first reading

Engagement

42 posts held, back to 13 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 40 pagesof Telegram’s post history, 20 posts per page.

ERR · 30 days
47.6%
avg views ÷ 10,911 subscribers
Avg views / post
5,190
25 posts measured
Reaction rate
1.04%
reactions ÷ views · ER floor
Posts in window
25
of 42 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 28 August 2026
Posts held42 (13 July 202628 August 2026)
Views total129,740
Reactions total1,355
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken29 Aug 2026, 12:15 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
5m 14s
Average length
35s

Measured directly from 9 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

2,044 reactions across 40 posts, in 8 distinct kinds. The most used accounts for 34.3% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍70134.3%
🔥62930.8%
36517.9%
🤔1135.53%
😁1024.99%
663.23%
🤯633.08%
🤩50.245%

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

Measured over the 42 most recent posts we hold, published 13 July 2026 to 28 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.

Telegram Stars

Stars received
10
across the posts below
Posts paid on
6
of 42 we hold a reading for · 14%
Most on one post
3
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @spring_aio. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.

Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.

This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.

Counted over the 42 most recent posts we hold for this entry, published 13 July 2026 to 28 August 2026. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.

Advertising

Ad load
4.76%
2 of 42 posts carry an ad marker
Regulatory tokens
2
posts carrying an erid · 1 distinct token
Median views · ads
3,890
over 2 measured posts
Median views · rest
5,820
over 40 measured posts

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.

Advertising tokens recorded on this entry
eridPostsFirst seenLast seen
2Vtzqw8Jxi7220 August 202625 August 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 42 most recent posts we hold, published 13 July 2026 to 28 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.

Recent posts

28 Aug 2026, 07:13 UTC≈2,500 views44 reactionsread 29 August 2026
Photo

Anthropic опубликовали AI-Native SDLC плейбук Его основная мысль: агенты уже способны генерировать код намного быстрее человека, но окружающие процессы почти не изменились. Планирование, согласования, тестирование, проверка безопасности и выпуск по-прежнему работают с человеческой скоростью. Узкое место просто переместилось из написания кода в соседние этапы. Anthropic называет предлагаемую модель AI-native SDLC.

👍247🔥6😁6🤯1

Signed Rustam Kuramshin

27 Aug 2026, 09:13 UTC≈3,180 views35 reactionsread 29 August 2026
Photo

🖥 Ваш JSONB тормозит не из-за базы. Возможно, виноват Hibernate Когда Hibernate начинает проседать по производительности, первым делом обычно ищут лишние SQL-запросы. Тем не менее, с JSON или JSONB проблема может скрываться совсем в другом месте. Hibernate способен незаметно выполнять дорогую работу с JSON-объектами, даже когда вы этого не ожидаете. На небольших объёмах это почти не видно, а под нагрузкой превраща

👍21🔥86

Signed Misha Polivakha

26 Aug 2026, 06:54 UTC≈3,050 views38 reactionsread 29 August 2026
Forwarded from @openide_officialPhoto

Спека вместо кода: OpenSpec vs SpecKit Сколько строк сгенерированного кода вы реально прочитали за последнюю неделю? Вопрос неудобный, и именно из него растёт spec-driven development: описываем намерение явно, до генерации, и агент работает по спеке, а не по вашей интуиции. Новая статья на Хабре — сравнение OpenSpec и SpecKit: два взгляда на один процесс, разные компромиссы между простотой и контролем качества. Н

👍20🔥95🤔31

25 Aug 2026, 16:10 UTC≈3,630 views51 reactionsread 29 August 2026

👩‍💻 В Java хотят дать возможность запретить читать поле до того, как ему присвоили значение Дело в том, что, когда создаётся объект, его поля сначала получают значения по умолчанию (null для ссылок, 0 для чисел, false для boolean) и только затем выполняется код инициализации. По итогу на уровне JVM существует короткий промежуток времени, когда поле уже можно прочитать, хотя ему ещё не присвоили настоящее значение.

🔥29👍1083🤔1

Signed Misha Polivakha

25 Aug 2026, 07:04 UTC≈3,890 views18 reactionsread 29 August 2026
Advertisementerid 2Vtzqw8Jxi7Video

Вам доклады по Go или Java? VK приглашает на митап с двойной начинкой 26 августа VK собирает Go- и Java-инженеров, чтобы прокачать знания. В программе два трека — Go и Java, по три доклада в каждом. Трек Go: • «Компиляция Go в динамическую либу, или как мы ускорили выкатку фичи в два раза, но нам не понравилось», Михаил Кичигин, бэкенд-разработчик, Avito Tech • «Go-платформа VK: как мы построили единую основу для с

🔥86👍4

24 Aug 2026, 14:09 UTC≈3,930 views18 reactionsread 29 August 2026
Video

🍃 ИИ придумал уязвимости, IDE всё ещё нужна, Spring Boot vs Quarkus | Spring АйО Подкаст №71 😉 СМОТРЕТЬ НА YOUTUBE 😄 СМОТРЕТЬ В VK ВИДЕО 🥰 СМОТРЕТЬ НА RUTUBE 🗯 Чуть позже... 🤩 СЛУШАТЬ НА SPOTIFY 🤩 СЛУШАТЬ НА APPLE PODCASTS 💬 Аудио версию подкаста можно найти в комментариях

👍8🔥54😁1

20 Aug 2026, 13:32 UTC≈5,880 views32 reactionsread 29 August 2026
Advertisementerid 2Vtzqw8Jxi7Video

Вам доклады по Go или Java? VK приглашает на митап с двойной начинкой 26 августа VK собирает Go- и Java-инженеров, чтобы прокачать знания. В программе два трека — Go и Java, по три доклада в каждом. Трек Go: • «Компиляция Go в динамическую либу, или как мы ускорили выкатку фичи в два раза, но нам не понравилось», Михаил Кичигин, бэкенд-разработчик, Avito Tech • «Go-платформа VK: как мы построили единую основу для с

12🔥86👍5🤩1

20 Aug 2026, 08:05 UTC≈5,250 views24 reactionsread 29 August 2026
Photo

👩‍💻 One Branch To Rule Them All Модель ветвления git в современных проектах - это отдельная головная боль. Кажется, что что бы ты ни делал - ты всё равно проиграешь. В итоге каждый проект решает данную проблему по-своему. Существуют разные модели ветвления: - GitFlow - GitHub-flow - TBD и так далее И разные модели бранчинга страдают от разных проблем. Кто-то сталкивается с merge hell, а кто-то - с огромными накла

12👍7🔥4🤔1

19 Aug 2026, 14:20 UTC≈4,650 views39 reactionsread 29 August 2026

🤖 ИИ настолько ускорил поиск уязвимостей, что команде Spring пришлось менять процессы безопасности За последний месяц количество сообщений о потенциальных уязвимостях в проектах Spring выросло более чем на 1700% (!). Причина неожиданная: массовое использование AI-инструментов для поиска багов. Команда Spring признаёт, что объём обращений оказался беспрецедентным. Чтобы справиться с нагрузкой, пришлось изменить вну

👍287🔥4

18 Aug 2026, 06:25 UTC≈4,410 views34 reactions2 Starsread 29 August 2026
Photo

🔥 Эксперты Spring АйО покажут крутую IDE 27 августа в 11:00 эксперты Spring АйО Илья Сазонов и Фёдор Сазонов обещают показать актуальное состояние OpenIDE Pro: – Как OpenIDE Pro работает с Java/Spring и другими популярными технологическими стеками; – Встроенный DB-клиент: подключение к базам данных, SQL-консоль, просмотр схем и работа с данными прямо из IDE; – Актуальное состояние AI-агентов в IDE. Особенно полезн

👍2154🔥2🤩1😁1

17 Aug 2026, 07:50 UTC≈5,010 views33 reactionsread 29 August 2026

👩‍💻 Oracle хочет, чтобы ИИ писал не только код, но и плагины В GraalVM 25.2 Oracle представила Graal Script Agent. Это очередная новая либа (пока в статусе Early Access), которая позволяет описывать логику на естественном языке и превращать её в локально выполняемые скрипты и плагины. Интересно получается в целом. Вместо того чтобы каждый раз писать Java-код для простой автоматизации, можно дать ИИ задачу типа: «Н

🤔16👍871🔥1

16 Aug 2026, 09:53 UTC≈5,220 views39 reactionsread 29 August 2026

👩‍💻 AI Agent-ы в Open Source разработке на Java Друзья, всем привет! Недавно вышла запись доклада, где наш эксперт, Михаил Поливаха, выступал на конференции AgenticConf с докладом "Axelix: Scaling Open Source with AI". Если вам интересно, как осознанно, на практике и без лишнего хайпа внедряются AI Agent-ы в процесс разработки (и где они не внедряются) - этот доклад для вас. Важно ещё и то, что исходный код ядра

👍19🔥119

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

Stars beside a post are paid reactions — Telegram Stars, bought with money and spent on that post. They are a different unit from reactions and are never added to them, here or anywhere else on this page.

Posts edited after publishing

@spring_aio edited 2 posts after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.

An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.

First edit seen
9 August 2026
Most recent edit
15 August 2026

Citation-graph rank

Citation-graph rank — 41,584 of 1,626,884entries 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

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 6 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.

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.

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 30 August 2026 — this entry's latest reading, not the date you are reading this.

“Spring АйО” (@spring_aio), 10,911 subscribers as measured 30 August 2026. Telegram Register, tgregister.com/channel/spring_aio.

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.