Telegram RegisterThe public register of Telegram
Telegram profile photo for Аксёнов вещает

Channel

Аксёнов вещает

@shodanski

On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Cite this entry

359subscribers

+15 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1003753284814
TypeChannel
Username@shodanski
CreatedBetween 1 February 2026 and 4 February 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live12 September 2026
Measurements held6
Confirmed unchanged2 times, most recently 12 September 2026
On Telegramt.me/shodanski

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 22 September 2026 and assigned it the closest of 31 fixed categories, at 88% 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.

Growth

344359351.56 August 2026 — 344 subscribers6 August 2026 — 344 subscribers15 August 2026 — 347 subscribers21 August 2026 — 353 subscribers28 August 2026 — 358 subscribers4 September 2026 — 359 subscribers6 August 20264 September 2026
6 measurements spanning 29 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 342–361 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
4 Sept 2026, 22:16359+1
28 Aug 2026, 13:13358+5
21 Aug 2026, 05:54353+6
15 Aug 2026, 03:28347+3
6 Aug 2026, 21:32344no change
6 Aug 2026, 14:21344first reading

Engagement

19 posts held, back to 4 February 2026the 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 19 posts for this entry, the most recent from 1 August 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

216 reactions across 17 posts, in 7 distinct kinds. The most used accounts for 66.7% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🔥14466.7%
👍3214.8%
2612.0%
👏83.70%
🙈31.39%
👀20.926%
🗿10.463%

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

Measured over the 19 most recent posts we hold, published 4 February 2026 to 1 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

1 Aug 2026, 09:04 UTC278 views5 reactionsread 6 August 2026

Всем привет! Уже скоро мы стартуем Back to Back. 🔤Онлайн-трансляция будет доступна на сайте конференции: https://backtobackconf.ru ⭐️А также на Youtube: 💹Москва | Architecture & Performance 💹Москва | C++ Zero Cost 💹Белград | С++ Zero Cost 💹Ереван | Architecture & Performance Для всех, кто будет с нами офлайн, прикладываем карту площадки, чтобы вам было проще ориентироваться. Такие карты также размещены по всей те

🔥5

23 Jul 2026, 10:00 UTC≈1,820 views13 reactionsread 6 August 2026

Оп, мини-анонс, уже через 9 дней вещаю "про многопоточность от регистра до кластера" на https://backtobackconf.ru/ Сначала эта конференция называлась C++ Zero Cost, но теперь переименовалась Пора доделать слайды! (И как только доделаю, так сразу и постами сюда опять займусь, обещаю!)

🔥9👍4

10 Jul 2026, 17:57 UTC≈1,130 views25 reactionsread 6 August 2026

Оп, видео доклада про векторные базы вдруг уже выложили! https://www.youtube.com/watch?v=pjVFD9D1P3E

🔥19👍6

19 Jun 2026, 12:36 UTC911 views30 reactionsread 6 August 2026

Давно и упорно утверждаю, что даже "сложные" структуры данных это базово запредельно просто, типа как полнотекстовый индекс в одну строку. Недавно сделал доклад "Про базу векторных баз", там утверждал это про векторные индексы, что это тоже одна строка. Неясно, насколько слушатели мне поверили. Поэтому хоп, даешь доказательства моих дерзких тезисов! Итак, вот вам работающий HNSW индекс в 1 (одну) строчку кода. usin

🔥246

14 Jun 2026, 16:06 UTC719 views13 reactionsread 6 August 2026

Закрою тему рандома. Сорян, дальше поинтереснее будет пост (уже готовлю его), но чота нимагумалчать. Вот так в прошлом посте (если его расшифровать) выглядел "ну какой-то" ГСЧ покороче. unsigned int x = 1; unsigned int rnd32() { return x = (x * 9973) ^ 97; } Вот так делается вполне приличный ГСЧ по кличке MWC128. Говорят, с периодом 2^127, проходит примерно все разумные тесты, итп. __uint128_t cx = (((__uint12

👍8🔥5

9 Jun 2026, 18:44 UTC614 views9 reactionsread 6 August 2026
Photo

...а рендерит этот код вот такое вот. Мягкие тени! DOF эффект! Неизменно круто :)

🔥9

9 Jun 2026, 18:44 UTC533 views6 reactionsread 6 August 2026
Photo

А вот было/стало

🙈3👀2👍1

9 Jun 2026, 18:43 UTC≈1,230 views4 reactionsread 6 August 2026

Оптимизируем код под упоротое. Под площадь визитки!!! Опять набрел на мега-рейтрейсер имени Andrew Kensler, и на этот раз залип. Стало интересно, сумею ли уменьшить. Немного сумел, сделал за вечерок из 1317 исходных байт свои 1249 байт, что для code golf вроде неплохо. Особо порадовало, что из 35 строк сумел сделать 33 строки (сохранив исходную ширину 39 символов). Весь код тут, скриншоты кода было/стало пониже. Ос

🔥3🗿1

1 Jun 2026, 19:02 UTC760 views11 reactionsread 6 August 2026

Сколько стоит мьютекc? Вопрос, на который удивительно часто рассказывают, эээ, очень странное. Про мьютекс нас всегда интересует предельный, худший случай. Это когда на нем большой contention, во много потоков. На практике мы просто запустим какие-нибудь хотя бы 8 потоков и померим, что получилось. А перед этим глянем в теорию, сколько должно быть? Взять и отпустить мьютекс это базово всего лишь пара синхронизирова

👍65

15 May 2026, 09:23 UTC733 views20 reactionsread 6 August 2026

Хоп, внезапно (нет) вещаю про всё подряд в рамках АвиТолк! https://www.youtube.com/watch?v=WSq48_EY9g4

11🔥9

3 Apr 2026, 10:29 UTC803 views27 reactionsread 6 August 2026

...Вот, в чем заключается суперхак. Суперхак = кусочная интерполяция + ловкая суперскалярность. Идея-раз! А давайте честно считать деления только 1 раз на 16 пикселов. Оказывается, этого хватает, чтобы текстуры не плавали. Хоп, дорогущих делений теперь кратно меньше. Идея-два! А давайте присядем на суперскалярность. Именно Pentium научился параллельно (!) запускать FPU инструкции и обычные целочисленные инструкции

🔥213👍3

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

Forward network

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

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

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

“Аксёнов вещает” (@shodanski), 359 subscribers as measured 4 September 2026. Telegram Register, tgregister.com/channel/shodanski.

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.