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

Channel

Spring АйО

@spring_aio

On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Stars · Advertising · Posts · Posts edited after publishing · Posts recorded as deleted · Citations · Handles named that no longer answer · Telegram's recommendations · Cite this entry

10,933subscribers

+15 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
DescriptionРусскоязычное сообщество Spring-разработчиков. Habr: bit.ly/433IK46 YouTube: bit.ly/4h3Ci0x VK: bit.ly/4hF0OG8 Rutube: bit.ly/4b4UeX6 Яндекс Музыка: bit.ly/3EIizWy Чат для общения: @spring_aio_chat По вопросам сотрудничества: @befayer
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 live10 November 2026
Measurements held56
Confirmed unchanged1 time, most recently 10 November 2026
On Telegramt.me/spring_aio

Topic

Technology — 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 11 September 2026 and assigned it the closest of 31 fixed categories, at 72% 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 the other topics.

Growth

10,89810,96810,9336 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 subscribers2 September 2026 — 10,912 subscribers3 September 2026 — 10,909 subscribers5 September 2026 — 10,903 subscribers8 September 2026 — 10,904 subscribers11 September 2026 — 10,902 subscribers13 September 2026 — 10,905 subscribers14 September 2026 — 10,901 subscribers16 September 2026 — 10,906 subscribers18 September 2026 — 10,916 subscribers25 September 2026 — 10,901 subscribers3 October 2026 — 10,898 subscribers8 October 2026 — 10,917 subscribers12 October 2026 — 10,938 subscribers15 October 2026 — 10,956 subscribers16 October 2026 — 10,960 subscribers17 October 2026 — 10,966 subscribers18 October 2026 — 10,962 subscribers19 October 2026 — 10,961 subscribers20 October 2026 — 10,964 subscribers21 October 2026 — 10,968 subscribers22 October 2026 — 10,962 subscribers23 October 2026 — 10,966 subscribers24 October 2026 — 10,965 subscribers25 October 2026 — 10,962 subscribers26 October 2026 — 10,960 subscribers27 October 2026 — 10,954 subscribers29 October 2026 — 10,952 subscribers30 October 2026 — 10,949 subscribers31 October 2026 — 10,943 subscribers31 October 2026 — 10,941 subscribers3 November 2026 — 10,942 subscribers4 November 2026 — 10,940 subscribers5 November 2026 — 10,943 subscribers6 November 2026 — 10,941 subscribers7 November 2026 — 10,939 subscribers8 November 2026 — 10,936 subscribers10 November 2026 — 10,933 subscribers6 August 202610 November 2026
56 measurements spanning 96 days, net +15. 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,888–10,979 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 56
Measured (UTC)SubscribersChange
10 Nov 2026, 13:5010,933-3
8 Nov 2026, 22:0610,936-3
7 Nov 2026, 11:3710,939-2
6 Nov 2026, 08:2110,941-2
5 Nov 2026, 05:5610,943+3
4 Nov 2026, 02:2910,940-2
3 Nov 2026, 00:4910,942+1
31 Oct 2026, 22:1010,941-2
31 Oct 2026, 01:3710,943-6
30 Oct 2026, 00:4510,949-3
29 Oct 2026, 02:2710,952-2
27 Oct 2026, 22:1010,954-6
26 Oct 2026, 19:0110,960-2
25 Oct 2026, 19:3710,962-3
24 Oct 2026, 18:5610,965-1
23 Oct 2026, 19:3710,966+4
22 Oct 2026, 22:2610,962-6
21 Oct 2026, 17:4410,968+4
20 Oct 2026, 15:5110,964+3
19 Oct 2026, 13:0110,961first reading

Engagement

64 posts held, back to 13 July 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 60 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
47.8%
avg views ÷ 10,933 subscribers
Avg views / post
5,220
17 posts measured
Reaction rate
0.664%
reactions ÷ views · ER floor
Posts in window
17
of 64 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 11 November 2026
Posts held64 (13 July 2026 – 11 November 2026)
Views total88,810
Reactions total590
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken11 Nov 2026, 21:55 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

Photos
549
Videos
328
Links
729

Lifetime counters from Telegram’s own channel header, read 11 November 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.

Video runtime
11m 01s
Average length
47s

Measured directly from 14 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,835 reactions across 62 posts, in 8 distinct kinds. The most used accounts for 33.3% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍94533.3%
🔥91032.1%
❤58620.7%
😁1304.59%
🤔1184.16%
⚡762.68%
🤯652.29%
🤩50.176%

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

Measured over the 64 most recent posts we hold, published 13 July 2026 to 11 November 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
13
across the posts below
Posts paid on
8
of 64 we hold a reading for · 13%
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 64 most recent posts we hold for this entry, published 13 July 2026 to 11 November 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
3.13%
2 of 64 posts carry an ad marker
Regulatory tokens
2
posts carrying an erid · 1 distinct token
Median views · ads
4,570
over 2 measured posts
Median views · rest
5,790
over 62 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 64 most recent posts we hold, published 13 July 2026 to 11 November 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

Telegram’s own ‘edited’ marker: 2 of 17 posts held from the last 30 days (11.8%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).

11 Nov 2026, 15:34 UTC≈2,080 views14 reactionsread 11 November 2026
Photo

📱 Как обжегся Netflix, урезав память контейнеру Вдвое урезали память контейнеру. Тесты прошли. На реальном трафике тоже все отлично. Две недели всё работало стабильно. Но затем почему-то нагрузка изменилась, и больше 60% запусков пришлось повторять с увеличенными ресурсами. Так ребята из Netflix получили классный урок при разработке системы, которая сама подбирает ресурсы контейнеров. Оставить всё с запасом выходи…

👍5🔥5❤4

10 Nov 2026, 10:50 UTC≈3,080 views39 reactionsread 11 November 2026
Photo

🙅‍♂️ Ваш стриминг ненастоящий. Ловушка загрузки файлов в Spring Boot В контроллере Flux, приложение на WebFlux, всё выглядит реактивно. Но под капотом файл сначала целиком оседает во временном хранилище. Можно подождать порядка десяти загрузок по 2 ГБ и идти выяснять, кто съел диск. А дело было в привычном @RequestPart. Оказывается, одного реактивного типа недостаточно, чтобы байты обрабатывались по мере поступлени…

👍31❤6🔥2

9 Nov 2026, 10:56 UTC≈3,350 views44 reactionsread 11 November 2026
Forwarded from @openide_official

⚡️ CLAUDE CODE + CODEX + CURSOR В ОДНОМ ЧАТЕ Выпустили обновление нашего Meta Harness. Что теперь можно делать прямо в IDE: • Звать второго агента через @. Пишете в чате с Claude @codex проверь проект на..., и Codex отвечает в отдельной ветке справа учитывая историю чата • Кастомные пресеты под задачи. Агент + модель + effort под своим именем, например @reviewer. • Спроси сразу всех. И @opus, @sonnet в одном соо…

🔥25👍10❤4😁4⚡1

5 Nov 2026, 14:19 UTC≈5,170 views29 reactionsread 11 November 2026
Video

🧑‍💻 Релизный цикл Spring в 2026. Как AI всё сломал Релиз уже в плане, тесты зелёные. На шаге SCA сборка краснеет: в зависимости нашли уязвимость. Сейчас поднимем patch и поедем дальше. Для того patch-релизы и существуют. Открываете Maven Central, а следующего номера вашей линии Spring Boot там нет. И уже не будет. Коллега говорит: «Так 3.5 же LTS!». В Java на это слово можно опереться годами. Здесь так не выходит. …

🔥16😁7⚡2🤔2❤1👍1

3 Nov 2026, 12:45 UTC≈5,190 views20 reactionsread 11 November 2026
Photo

🔥️️️️️️ Почему каждая JVM в вашей инфраструктуре прогревается отдельно Каждая новая реплика запускает то же приложение, но JIT снова с нуля ищет горячие методы, собирает профиль и компилирует код. Казалось бы, пусть первая JVM сохранит результат, а остальные его заберут. Но машинный код JIT зависит от состояния конкретного процесса. От иерархии классов, загруженных реализаций и реального трафика. В статье разбирае…

❤9👍6🔥2🤯2⚡1

30 Oct 2026, 12:49 UTC≈6,270 views17 reactionsread 11 November 2026
Photo

Когда генератор нагрузки замирает вместе с сервером Если генератор и тестируемая система работают в одной JVM, пауза GC останавливает обоих. Сервер не отвечает, но и новые запросы никто не планирует. В итоге p99 выглядит лучше, чем его увидели бы реальные клиенты. Они-то сборку мусора не ждут. В экспериментах SPECjbb2015 разница между режимами достигала 34 против 100 мс, а с Serial GC даже 278 против 1750 мс. В ст…

👍7🔥7❤3

29 Oct 2026, 12:32 UTC≈5,790 views34 reactionsread 11 November 2026
Photo

🪨 Прод начинается там, где заканчивается магия Наши эксперты Михаил Поливаха и Евгений Сулейманов выступили с двумя практическими разборами для JVM Dev. • Евгений показал, как Redis сначала спасает latency, а потом незаметно начинает влиять на консистентность, права доступа, релизы и отказоустойчивость. Внутри Spring Boot, PostgreSQL, код, метрики и проблемы, которые обычно приходят уже после фразы «давайте просто …

👍13❤11🔥10

28 Oct 2026, 13:03 UTC≈5,100 views20 reactionsread 11 November 2026
Photo

😶 Java упала до первого лога. Виноват AOT-кэш Docker-образ собрали на процессоре с AVX или SVE. JDK 25 сохранила CPU-специфичные адаптеры в AOT-кэш, а затем попыталась выполнить их на машине без этих инструкций. Результат получился на удивление нативным для Java-приложения — SIGILL. В статье разбираем путь от ~AdapterBlob в крэш-логе до бага в OpenJDK. А ещё показываем, как собрать переносимый multi-arch образ, сох…

👍11🔥5❤4

27 Oct 2026, 10:52 UTC≈5,070 views26 reactionsread 11 November 2026
Video

🍃 Spring обошёл авторизацию, Java ускоряется, интерфейсы не нужны? | Spring АйО Подкаст №77 😉 СМОТРЕТЬ НА YOUTUBE 😄 СМОТРЕТЬ НА VK ВИДЕО 🥰 СМОТРЕТЬ НА RUTUBE 🗯 СЛУШАТЬ НА ЯНДЕКС.МУЗЫКЕ 🤩 СЛУШАТЬ НА SPOTIFY 🤩 СЛУШАТЬ НА APPLE PODCASTS 💬 Аудио версию подкаста можно найти в комментариях

❤12🔥10👍4

26 Oct 2026, 11:22 UTC≈5,240 views38 reactionsread 11 November 2026
Photo

🧑‍💻 Мы вынесли Actuator на отдельный порт и потеряли авторизацию Конфигурация самая обычная: бизнес-API на 8080, Actuator на 8081. Так делают очень многие, и это хорошая практика. Но у наших друзей из Axelix при такой настройке Actuator endpoints принимали запросы без JWT-токена. Фильтр при этом был, проверка подписи работала безупречно, просто запрос тайно проходил IAM. Виноват механизм, который живёт в Spring уж…

🔥22👍9❤4😁3

23 Oct 2026, 13:33 UTC≈5,740 views42 reactionsread 11 November 2026
Photo

🐸 JDK 28 ускорит работу с нативной памятью Arena.ofConfined() получит пулы для небольших сегментов. Вместо постоянных вызовов malloc и free JDK сможет повторно использовать блоки памяти. В микробенчмарках выделение 5–20 байт ускорилось в 6,8–18,9 раза. Код менять не придётся, а прежние гарантии безопасности сохранятся. В новом переводе разбираемся, как устроена оптимизация и кому она принесёт пользу. 🔗 Статья на …

🔥28❤7👍7

22 Oct 2026, 11:51 UTC≈5,740 views40 reactionsread 11 November 2026
Photo

😈 Преждевременная оптимизация не всегда зло Все знают фразу Дональда Кнута: «Преждевременная оптимизация — корень всех зол». Но обычно цитату обрывают слишком рано. Кнут предлагал забыть о небольшом выигрыше в 97% случаев, но не упускать возможности в оставшихся критически важных 3%. Иногда для них не нужны профилировщик и чёрная магия. Достаточно не компилировать регулярку при каждом вызове, не искать постоянно …

❤23👍11🔥3😁3

Showing the 12 most recent of 64 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.

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

Posts recorded as deleted after publishing

We recorded 1 post on @spring_aio as deleted — posts this register held that were missing from the channel’s public page on two separate reads, taken from different network addresses at least an hour apart.

A deletion is not wrongdoing. This register can see that a post it held is no longer on the channel’s public page, and when — not why. Expired ad placements, reposts, rotating links and corrections all look the same. This is a count of recorded detections, not an exact total: it misses deletions we could not see, because only a post we held and later re-read inside the page can be seen to go, and it may include a small number of wrong records. How this is measured.

First seen missing
15 August 2026
Most recent seen missing
15 August 2026
Median time before seen missing
4 days
Seen missing in the last 30 days
0

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.

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.

Appears in Telegram’s recommendations for other channels

The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.

Библиотека джависта | Java, Spring, Maven, Hibernate
@javaproglib · 21,780
Telegram ranks this channel #13 of 88 here — alongside 87 others — read 21 September 2026
Java библиотека
@javalib · 30,300
Telegram ranks this channel #13 of 84 here — alongside 83 others — read 7 September 2026
Senior Java Developer
@seniorjavist · 20,358
Telegram ranks this channel #14 of 89 here — alongside 88 others — read 26 September 2026

This channel appears in 3 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.

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

“Spring АйО” (@spring_aio), 10,933 subscribers as measured 10 November 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.