Telegram RegisterThe public register of Telegram
Telegram profile photo for From A | Все про IT

Channel

From A | Все про IT

@from_artur

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

5,304subscribers

+1 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-1001615255661
TypeChannel
Username@from_artur
CreatedBetween 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live6 September 2026
Measurements held11
Confirmed unchanged1 time, most recently 6 September 2026
On Telegramt.me/from_artur

Growth

5,2865,3045,2956 August 2026 — 5,303 subscribers6 August 2026 — 5,302 subscribers10 August 2026 — 5,300 subscribers12 August 2026 — 5,303 subscribers16 August 2026 — 5,298 subscribers19 August 2026 — 5,297 subscribers23 August 2026 — 5,295 subscribers26 August 2026 — 5,293 subscribers29 August 2026 — 5,292 subscribers1 September 2026 — 5,286 subscribers6 September 2026 — 5,304 subscribers6 August 20266 September 2026
11 measurements spanning 31 days, net +1. 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 5,283–5,307 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
6 Sept 2026, 10:205,304+18
1 Sept 2026, 18:055,286-6
29 Aug 2026, 08:425,292-1
26 Aug 2026, 12:035,293-2
23 Aug 2026, 02:385,295-2
19 Aug 2026, 08:225,297-1
16 Aug 2026, 16:595,298-5
12 Aug 2026, 22:325,303+3
10 Aug 2026, 06:505,300-2
6 Aug 2026, 21:045,302-1
6 Aug 2026, 05:195,303first reading

Engagement

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

What this channel posts

Video runtime
13s
Average length
13s

Measured directly from 1 video 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

685 reactions across 20 posts, in 9 distinct kinds. The most used accounts for 47.3% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
😁32447.3%
👍14320.9%
🔥8712.7%
7410.8%
😱426.13%
🤯81.17%
❤‍🔥30.438%
🎉20.292%
😢20.292%

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

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

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

10 Aug 2026, 08:50 UTC902 views24 reactions1 Starread 12 August 2026
Photo

Простими словами про патерни. Сьогодні про API Gateway. Заходиш у лікарню - не бігаєш сотнею кабінетів, а йдеш до реєстратури, і вона скеровує куди треба. API Gateway - ті самі єдині двері: клієнт стукає раз, а шлюз розкидає запит по сервісах. Різні клієнти без АРІ гейтвею вони будуть викликати десятки дрібних сервісів. Клієнт мусить знати їхні адреси, робити купу мережевих ходів і зшивати відповіді сам. Ставимо п

👍18🔥4😢2

5 Aug 2026, 19:55 UTC≈1,540 views19 reactionsread 12 August 2026

Мені інколи здається шо люди які пишуть спагетті код, без патернів де треба, з купою дублікатів, без думок про розширення просто таким чином виражають якийсь протест. Фізично больно таке читати прям

😁19

4 Aug 2026, 15:05 UTC≈1,580 views16 reactionsread 12 August 2026

У мене часто вживалось слово - компенсаторна подія Уявіть, що банк помилково зняв з вашого рахунку 30 грн: у журналі вже є подія ЗНЯТЬ_БАБЛО(30). У звичайній базі ви б просто виправили число або видалили рядок. В event sourcing так робити не можна - журнал append-only, історію не переписують. Тож помилку виправляють так само, як у бухгалтерії - дописують у кінець журналу нову подію, яка скасовує попередню. Наприклад

👍151

4 Aug 2026, 14:55 UTC≈1,500 views11 reactions1 Starread 12 August 2026

Простими словами про патерни. Сьогодні про Event Sourcing. Інколи хотілось би відмотати час назад та деякі речі відтворити знову. Наприклад купити біткоїни. Event Sourcing - саме про це: сервіс тримає не "як зараз", а весь список подій і щоразу вираховує стан із них. Класичне сховище зберігає лише поточний стан і затирає, як ми до нього дійшли. Історія, аудит, "а що було у минулий вівторок?" - усе втрачено назавжди

🔥8🤯21

3 Aug 2026, 12:15 UTC≈1,640 views66 reactionsread 12 August 2026
Photo

які часи такі і подарунки

😁641👍1

31 Jul 2026, 07:58 UTC≈2,090 views13 reactions1 Starread 12 August 2026
Photo

Простими словами про патерни. Сьогодні про CQRS. На екзамен ти маєш товстий зошит, де все записано ретельно і окрему шпаргалку з готовими відповідями. Шпаргалку не редагуєш напряму. CQRS це приблизно так само: одна модель для запису, окрема швидка модель для читання. Чому? Бо одна модель даних рідко добре служить і записам, і читанням. Запис хоче нормалізації та інваріантів; читання — інколи денормалізованих форм п

🔥13

30 Jul 2026, 06:08 UTC≈1,770 views14 reactionsread 12 August 2026
Photo

Свіже повітря, 7000 айтівців і благодійний пікнік 🧃 5 вересня DOU влаштовує найбільший невимушений нетворкінг в українському ІТ — DOU Day Picnic. 👉 На вас чекають велика сцена з топовими спікерами, фудкорт, зони для чілу, стендап Васі Байдака, концерт, майстерки, барахолка й десятки способів провести день без напрягів, познайомитись з людьми з індустрії та підтримати армію. Приходьте з дітьми — для них буде окрема

🔥122

29 Jul 2026, 13:30 UTC≈1,660 views62 reactionsread 12 August 2026

Як же бісить коли комусь задаєш одне просте питання і очікуєш відповідь у boolean, а тобі висирають string на 50 000 символів.

😁60👍2

28 Jul 2026, 17:15 UTC≈1,840 views55 reactionsread 12 August 2026
Video

Тоже так ?

😁50👍4❤‍🔥1

28 Jul 2026, 07:08 UTC≈1,710 viewsread 12 August 2026
Photo

🟢Цікаві пропозиції від UPSTARS🟢 UPSTARS – продуктова IT-компанія, з якою злітають і люди, і бренди. Команда створює технологічні рішення та B2B-сервіси для міжнародних клієнтів. Ваша наступна роль може починатися з цього допису: 🔹 Senior Security Engineer (SecOps) 🔹 Senior Atlassian Administrator 🔹 Senior Ruby Engineer 🔹 Senior Product Owner 🔹 Middle Business Development Manager Відчуваєш метч? Нумо знайомитися

27 Jul 2026, 06:57 UTC≈1,660 views17 reactions1 Starread 12 August 2026

Простими словами про патерни. Сьогодні про сагу. Уяви: ти зібрав відпустку по кусочках - квиток, готель, авто напрокат. Готель зірвався і ти не летиш "в нікуди", а скасовуєш квиток і повертаєш гроші за авто. Saga - це операція з кроків, де для кожного заздалегідь відомо, як його скасувати, якщо далі щось зламалось. Більш технічно: Нехай бізнес-операція охоплює кілька сервісів- наприклад, оформлення замовленні в яком

👍132❤‍🔥2

24 Jul 2026, 10:08 UTC≈1,790 views7 reactionsread 12 August 2026

https://x.com/unclebobmartin/status/2080257779395154409 ну всьо. дядя боб трошки того.. перегрелся. дідууу, таблетки пий давай!

🤯6😁1

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

рецепти від mil_alexx
@mil_alexx_recipes · 46,142
Telegram ranks this channel #28 of 65 here — alongside 64 others — read 7 September 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 6 September 2026 — this entry's latest reading, not the date you are reading this.

“From A | Все про IT” (@from_artur), 5,304 subscribers as measured 6 September 2026. Telegram Register, tgregister.com/channel/from_artur.

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.