Telegram RegisterThe public register of Telegram
Telegram profile photo for this->notes.

Channel

this->notes.

@thisnotes

On this record: Topic · Growth · Engagement · Reactions · Stars · Posts · Citations · Telegram's recommendations · Cite this entry

4,522subscribers

+26 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1001425973717
TypeChannel
Username@thisnotes
CreatedBetween 1 April 2019 and 30 September 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live19 September 2026
Measurements held14
Confirmed unchanged1 time, most recently 19 September 2026
On Telegramt.me/thisnotes

Topic

Literature — 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 13 September 2026 and assigned it the closest of 31 fixed categories, at 74% 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

4,4934,5224,507.56 August 2026 — 4,496 subscribers6 August 2026 — 4,496 subscribers6 August 2026 — 4,493 subscribers9 August 2026 — 4,495 subscribers16 August 2026 — 4,493 subscribers19 August 2026 — 4,505 subscribers23 August 2026 — 4,510 subscribers26 August 2026 — 4,511 subscribers28 August 2026 — 4,508 subscribers1 September 2026 — 4,509 subscribers4 September 2026 — 4,510 subscribers10 September 2026 — 4,505 subscribers14 September 2026 — 4,520 subscribers19 September 2026 — 4,522 subscribers6 August 202619 September 2026
14 measurements spanning 44 days, net +26. 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 4,489–4,526 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
19 Sept 2026, 01:004,522+2
14 Sept 2026, 10:164,520+15
10 Sept 2026, 10:374,505-5
4 Sept 2026, 23:394,510+1
1 Sept 2026, 02:064,509+1
28 Aug 2026, 22:154,508-3
26 Aug 2026, 01:534,511+1
23 Aug 2026, 11:344,510+5
19 Aug 2026, 21:124,505+12
16 Aug 2026, 14:124,493-2
9 Aug 2026, 15:164,495+2
6 Aug 2026, 23:044,493-3
6 Aug 2026, 08:314,496no change
6 Aug 2026, 08:264,496first reading

Engagement

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

Reaction mix

501 reactions across 20 posts, in 16 distinct kinds. The most used accounts for 28.9% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍14528.9%
🔥12224.4%
🥴6412.8%
🤯5210.4%
❤448.78%
👎203.99%
🌚173.39%
🫡112.20%
😁61.20%
🗿50.998%
🤩40.798%
🤪40.798%
🤝30.599%
🤓20.399%
👏10.2%
😱10.2%

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

Measured over the 20 most recent posts we hold, published 8 July 2026 to 6 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
50
across the posts below
Posts paid on
1
of 20 we hold a reading for · 5%
Most on one post
50
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @thisnotes. 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 20 most recent posts we hold for this entry, published 8 July 2026 to 6 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.

Recent posts

6 Aug 2026, 08:03 UTC≈1,050 views25 reactionsread 8 August 2026
Photo

#common МАРТИН ИДЕН ОШИБАЛСЯ. Книге уже больше 100 лет, так что у вас было полно времени её прочитать. Потому выдать спойлер бояться не буду (хотя главные панчи всё-таки придержу). Так где он ошибался? Когда Мартин стал уважаемым известным писателем, его стали активно звать на всякие обеды, встречи, интервью. Хорошо с ним обходились, уважали. Мартина это раздражало. Его основная мысль в это время успеха была прим…

👎14❤5👍5🔥1

29 Jul 2026, 11:03 UTC≈2,390 views18 reactionsread 8 August 2026

СОБИРАЮ ВАШИ ИСТОРИИ. Вас тут относительно много. Вы умные. Вы работаете и занимаетесь интересными вещами. А я почему-то этим не пользуюсь! Я бы хотел про них узнать и может заодно поделиться с подписчиками! Расскажите про самую интересную оптимизацию, которую вы сделали. Это может быть что угодно. Ускорили запрос в БД. Поменяли способ хранения данных (может это буквально vector -> unordered_map). Перепридумали арх…

👍18

27 Jul 2026, 06:37 UTC≈2,180 views19 reactionsread 8 August 2026

#highload Я не очень понял, как это работает. Видосы на самом канале так и не появились, хотя прошло уже больше года с конференции. Плейлист со всеми докладами доступен, и видео выложили год назад. Доступ к ним явно есть. Но просмотров нет. То есть как-то никто и не в курсе, что их можно смотреть. Доклады с Saint HighLoad++ 2025. 0. Эволюция векторного поиска в YDB. Александр Зевайкин. Есть ещё в тексте (правда н…

👍9🔥6❤4

24 Jul 2026, 08:03 UTC≈2,250 views14 reactionsread 8 August 2026

#cpp и не только. НАПОМИНАЮ, что 1ого августа будет Back to Back: в Москве back to back трек + C++ трек, в Ереване только back to back, а в Белграде только C++ one. Программу на плюсовый трек мы собрали сочную. Старались, честное слово. Коллеги по цеху на Back to Back тоже интересного выбрали. Меня, дай бог всё будет хорошо, сможете найти в Белграде. Можем с вами за здоровье Страуструпа выпить ракии (хотя я ещё её…

👍7🤝3🔥2❤1👎1

23 Jul 2026, 08:03 UTC≈2,000 views201 reactions50 Starsread 8 August 2026

#cpp Привет. Сегодня последний day 52 марафона. Я знаю, что кому-то он поднадоел. Не зря от меня отписалось больше полусотни человек. Мне тоже надоело, если честно. Если вдруг вы не узнали/не знали, марафон был основан на C++ Preprocessor Iceberg. Я в целом шёл от начала почти по каждому пункту, скипая что-то, что выглядит совсем мутным и невнятным, что я не смог заставить работать или не смог осознать. Попутно …

🔥105🥴64🤯23🌚8❤1

22 Jul 2026, 08:01 UTC≈1,530 views11 reactionsread 8 August 2026

#cpp Day 51. Есть ещё несколько интересных репозиториев, связанных с препроцессором: • datatype99 (фактически синтаксический сахар для генерации типов, но с дополнительными плюшками вроде паттерн матчинга) • interface99 (Golang/Rust inspired интерфейсы для C99) • boline (integer arithmetics with base 16). У последнего код с вайбом ASCII-art. И есть ещё подгон от подписчика про расширение в clang, позволяющее дела…

👍10👏1

21 Jul 2026, 08:05 UTC≈1,590 views8 reactionsread 8 August 2026

#cpp Day 50. Макросы можно класть на и доставать из (со) стека: #define PRAMGA(...) _Pragma(#__VA_ARGS__) #define POP(m) PRAMGA(pop_macro(#m)) #define X 1 POP(X) #pragma push_macro("X") #define X 2 POP(X) #pragma push_macro("X") #define X 3 POP(X) #pragma push_macro("X") #define X 4 POP(X) X // 4 X // 3 X // 2 X // 1 Не уверен, что понимаю, зачем это нужно. @thisnotes. Patreon, Boosty. Спасибо Artyom Garkavy и…

🤪4👍3🔥1

20 Jul 2026, 08:03 UTC≈1,700 views15 reactionsread 8 August 2026
Photo

#cpp Day 49. Одна из моделей, которую можно реализовать на макросах (хотя мы выяснили, что можно любую видимо) — continuation machine. Фактически это штука, в которой вы можете построить пайплайн работы с данными (но такими словами про неё не говорят, слишком современно). На картинке ниже страшная реализация для простого кейса работы с регистрами (разбирать мы ёе не будем, я хочу просто подышать.....). Кстати репо…

❤11🤯3👍1

19 Jul 2026, 08:02 UTC≈1,800 views9 reactionsread 8 August 2026

#cpp Day 48. Если вам нужна сравнительно мощная, но более современная альтернатива chaos-pp, стоит взглянуть на Metalang99. Это хорошая попытка сделать препроцессор похожим на функциональный язык программирования. Но что более важно, проект хорошо документирован. chaos-pp в этом плане проигрывает (и служит скорее исследовательским артефактом). Так что Metalang99 — ваш второй выбор (после Boost.Preprocessor). @th…

❤5👍4

18 Jul 2026, 08:02 UTC≈1,940 views15 reactionsread 8 August 2026

#cpp Day 47. Я уже упоминал Paul Mensodines, который написал огромное письмо про механизм раскрытия макросов. И упоминал про Boost.Preprocessor. Вот Paul когда-то написал chaos-pp — настоящая глыба в мире препроцессорных библиотек. Там вообще всё что хотите. Рекурсия, высокоуровневые алгоритмы (MAP, FOLD, FILTER, ZIP и др.), лямбды и частичное применение макросов, разные контейнеры (sequence, tuple, list). Правд…

👍13❤2

17 Jul 2026, 08:01 UTC≈1,730 views12 reactionsread 8 August 2026

#cpp Day 46. Шагаем на ступеньку номер 7. Мы бы могли с вами реализовать итерацию по sequence, но иногда лучше вовремя остановиться и заиспользовать что-то готовое: #define PRINT(r, data, elem) elem BOOST_PP_SEQ_FOR_EACH( PRINT, _, (a)(b)(c)(d) ) Получим a b c d Как это реализовано? Ну вот примерно как вчера откусываете по одному токену из начала и применяете к нему «функтор». Чего непонятно-то?…

👍8🗿3👎1

16 Jul 2026, 08:05 UTC≈1,790 views8 reactionsread 8 August 2026

#cpp Day 45. Мы уже обсуждали, как сделать LIST, но есть и более свойственная препроцессору структура данных: sequence. Sequence это просто набор элементов в скобках: (1)(2)(3)(4)(5) Тут 5 элементов. Но конечно мы не ограничиваемся числами: (a)(b)(c) (int)(double)(bool) (1)(2)()((),w,())(awoo())(()) Основные операции иногда реализуются просто: #define SEQ_PUSH_FRONT(x, seq) (x) seq SEQ_PUSH_FRONT(z, (a)(b)(c)…

👍5🤯2🤓1

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

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

Named by 2 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.

Codeforces Official
@codeforces_official · 72,808
Telegram ranks this channel #75 of 78 here — alongside 77 others — read 20 August 2026

This channel appears in 1 seed channel's Telegram-generated recommendation list 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 19 September 2026 — this entry's latest reading, not the date you are reading this.

“this->notes.” (@thisnotes), 4,522 subscribers as measured 19 September 2026. Telegram Register, tgregister.com/channel/thisnotes.

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.