Telegram RegisterThe public register of Telegram

Channel

What is IT?

@whatis_it

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

1,772subscribers

+3 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-1001281121559
TypeChannel
Username@whatis_it
Created19 January 2018measured — cross-checked against a third-party dataset (TGDataset)
First recorded6 August 2026
Last confirmed live10 August 2026
Measurements held4
Confirmed unchanged1 time, most recently 10 August 2026
On Telegramt.me/whatis_it

Growth

1,7691,7721,770.56 August 2026 — 1,769 subscribers6 August 2026 — 1,769 subscribers7 August 2026 — 1,770 subscribers10 August 2026 — 1,772 subscribers6 August 202610 August 2026
4 measurements spanning 4 days, net +3. 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,769–1,772 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
10 Aug 2026, 13:241,772+2
7 Aug 2026, 02:571,770+1
6 Aug 2026, 13:321,769no change
6 Aug 2026, 13:281,769first reading

Engagement

14 posts held, back to 21 April 2023the 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.

Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 14 posts for this entry, the most recent from 26 July 2025. An engagement rate over an empty window would be a number about nothing.

Reaction mix

137 reactions across 10 posts, in 15 distinct kinds. The most used accounts for 33.6% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🔥4633.6%
👍4230.7%
🤔75.11%
😢64.38%
53.65%
😁53.65%
👌42.92%
🤓42.92%
👎32.19%
💩32.19%
😨32.19%
🦄32.19%
👏21.46%
🤡21.46%
🥱21.46%

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

Measured over the 14 most recent posts we hold, published 21 April 2023 to 26 July 2025, 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

26 Jul 2025, 06:25 UTCviews —

The owner of this channel has been inactive for the last 11 months. If they remain inactive for the next 9 days, they may lose their account and admin rights in this channel. The contents of the channel will remain accessible for all users.

16 Jul 2025, 08:25 UTCviews —

The owner of this channel has been inactive for the last 11 months. If they remain inactive for the next 19 days, they may lose their account and admin rights in this channel. The contents of the channel will remain accessible for all users.

18 May 2023, 03:04 UTC≈10,200 views16 reactionsread 7 August 2026

И снова интересно о продажах. Теперь от Rubius. Но если честно, я бы с большим удовольствием почитал более развёрнуто об их кейсе для ПИК.

🔥6👌43👍3

17 May 2023, 05:01 UTC≈8,460 viewsread 7 August 2026

И вот такое нравится — не постеснялись и рассказали о какой-то, казалось бы, банальной херне.

16 May 2023, 03:24 UTC≈7,280 views9 reactionsread 7 August 2026

А вот за такие настроения я люблю небольшие компании. Да, уже есть свои отдельные команды, которым отдельно тусить веселее, но ещё нет такого большого разрыва настроений, как это бывает в корпорациях. Если что, это не противопоставление, а поиск плюсов для каждого формата и периода. Всё-таки нужно понимать, что такие сборища — это не от того, что компания готова выделить миллион-полтора на тамаду и прочие дженги.

👍4👏2🤡21

15 May 2023, 03:05 UTC≈5,430 viewsread 7 August 2026
Photo

По привычке зашёл в блог Новео и даже нашёл там интересное — реально, если бы все аутсорсеры писали такие посты, пользы было больше, чем от их «сейчас мы вам покажем ёбаное ничего» — а потом подумал, стоит ли продолжать о них писать? Решил оставить в рамках того, что я сам же хотел писать чуть больше, чем про Сибирское IT.

12 May 2023, 09:01 UTC≈4,770 views10 reactionsread 7 August 2026

И обратный пример — Труинжиринг считают, что это называется «показать кейс».

🤔4👍3🦄3

12 May 2023, 03:50 UTC≈4,220 views2 reactionsread 7 August 2026

Насколько Чипса преуспела в загадочных шоурилах (сделать видео с летающей иконкой — Нолан отдыхает!), настолько они плохи в начале пути шаринга экспертизы текстом. Сравните с постом от Сибирикса из прошлого сообщения.

🤔2

11 May 2023, 04:49 UTC≈3,700 views6 reactionsread 7 August 2026

О, интересная статья от Сибирикс. О том, в чём они реально разбираются. А то всё про дизайн да про ИИ.

👍6

10 May 2023, 09:59 UTC≈3,500 views3 reactionsread 7 August 2026

А если не хотите на митап — поиграйте в шахматы. Рубиус 13 мая проводит турнир в Томске.

🤓3

10 May 2023, 04:02 UTC≈3,740 views11 reactionsread 7 August 2026

Есть кто про бэкенд? Приходите завтра на митап Контура (19:00, Академпарк) Обещают интересное про масштабирование прав в проекте и переезд в opensource проект Спикеры Константин Аносов, старший инженер-программист, Контур Шлянин Сергей, разработчик, Яндекс.Практикум

👍7💩3😢1

22 Apr 2023, 05:37 UTC≈4,060 views5 reactionsread 7 August 2026

Интересно, продержаться дольше, чем приложение Сбера? Ваши ставки?

😁5

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

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.

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.

“What is IT?” (@whatis_it), 1,772 subscribers as measured 10 August 2026. Telegram Register, tgregister.com/channel/whatis_it.

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.