Telegram RegisterThe public register of Telegram

Channel

Бесконечное ИТ

@neverendingit

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

367subscribers

+0 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-1001298767811
TypeChannel
Username@neverendingit
DescriptionБесконечное ИТ - ИТ новости, интересные ссылки на статьи по разработке и менеджменту. Вопросы, предложения, комментарии @tirex_kz
CreatedBetween 1 March 2018 and 30 June 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live7 August 2026
Measurements held2
On Telegramt.me/neverendingit

Growth

3676 Aug 2026, 09:26 — 367 subscribers6 Aug 2026, 21:01 — 367 subscribers6 Aug 2026, 09:266 Aug 2026, 21:01
2 measurements taken within a single day. 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 366–368 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
6 Aug 2026, 21:01367no change
6 Aug 2026, 09:26367first reading

Engagement

20 posts held, back to 29 May 2025the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 pageof Telegram’s post history, 20 posts per page.

ERR · 30 days
64.2%
avg views ÷ 367 subscribers
Avg views / post
236
2 posts measured
Reaction rate
2.34%
reactions ÷ views · ER floor
Posts in window
2
of 20 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 23 July 2026
Posts held20 (29 May 202523 July 2026)
Views total471
Reactions total11
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken6 Aug 2026, 21:01 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
297
Videos
5
Links
557

Lifetime counters from Telegram’s own channel header, read 6 August 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.

Reaction mix

77 reactions across 18 posts, in 6 distinct kinds. The most used accounts for 46.8% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍3646.8%
2026.0%
🔥1519.5%
❤‍🔥33.90%
🤩22.60%
👏11.30%

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 18 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 77reactions 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 29 May 2025 to 23 July 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

23 Jul 2026, 08:50 UTC111 views7 reactionsread 6 August 2026
Photo

"В конечном счёте, и лидерство, и доверие заслуживаются одинаково - постоянством в том, что ты делаешь." "In the end, leadership and trust are earned the same way: showing up consistently." CTO одной компании каждую неделю пишет письмо команде из 400 инженеров про то, что считает важным. Почему принимаются те или иные решения, какие-то новые идеи, и т.д. Как пишет автор это стало источником интересных разговоров.

6👍1

22 Jul 2026, 03:46 UTC360 views4 reactionsread 6 August 2026

Потрясающая история произошла недавно в мире AI/Security буквально на наших с вами глазах. Часть 1 Взлом 16 Июля Huggingface раскрыли информацию о том, что на них была совершена очень изощренная атака. По скорости, объему и масштабу предложили, что это мог быть какой-то очень узкопрофильный LLM агент/модель. Интересен этап анализа данных. Команда хотела проанализировать все артефакты которые них были(логи, примеры

❤‍🔥2👍2

1 Jul 2026, 04:00 UTC185 views2 reactionsread 6 August 2026
Photo

Как ArchUnit помогает командам Netflix управлять изменениями в коде. Я несколько раз вплотную подбирался к использованию ArcUnit и уже даже писал примеры правил, но как-то так и не добрался до хорошего уровня внедрения. Попалась статья от которой можно оттолкнутся, чтобы понять нужно вам это или нет. Какие предпосылки использования? В Netflix нужен был инструмент который позволит командам которые ответственным за р

👍2

25 Jun 2026, 04:27 UTC207 views2 reactionsread 6 August 2026

Блокировка доступа к моделям Anthropic, OpenAI породила огромный черный рынок в Китае (и в других странах где ограничен доступ тоже) на реселлеров доступа к API AI моделей. Ресселеры продают доступ к API всего за 5%-10% от оригинальной цены! Как это возможно? Реселлеры идут на разные ухищрения: - Перепродают неиспользованные квоты разных аккаунтов - переиспользуют корпоративные аккаунты и аккаунты для образовательн

👍2

23 Jun 2026, 11:52 UTC181 views4 reactionsread 6 August 2026
Photo

Представили новый HTTP метод - QUERY. Призван закрыть пустоту между GET и POST в части работы с запросами на получение данных, запросы, фильтры, запросы с body и прочее похожее. Понятно что пройдет какое-то время пока его имплементация разойдется. https://www.rfc-editor.org/info/rfc10008/

👍2🔥2

19 Jun 2026, 10:58 UTC219 views6 reactionsread 6 August 2026
Photo

Последние тренды

🔥4👍1🤩1

20 May 2026, 06:48 UTC346 viewsread 6 August 2026

Инцидент в github, через VS Code extension, пока по оценке утекло 3800 внутренних репозиториев. "Yesterday we detected and contained a compromise of an employee device involving a poisoned VS Code extension. We removed the malicious extension version, isolated the endpoint, and began incident response immediately. " https://x.com/i/status/2056949168208552080

7 Mar 2026, 06:57 UTC427 views11 reactionsread 6 August 2026
Photo

Kagi добавили в свой переводчик языков, перевод на корпоративный язык! И мне кажется теперь это будет мой любимый сайт) Я считал, что я неплохо пишу на "корпоративном", но результаты тут - мое почтение!

8👍2🤩1

25 Feb 2026, 11:14 UTC417 views4 reactionsread 6 August 2026

Хорошая статья от OpenAI про масштабирование их postgresql базы. Вот как они поэтапно шли к масшибированию своего хранилища. Важно понимать что между каждыми этими этапами есть какие-то интервалы времени, иногда меньше, иногда больше, главным драйвером был пользовательский спрос на продукт. Мне кажется просто хрестоматийный пример неспешного, постепенного улучшения. 1. Долгое время просто масштабировали инстанс, ве

🔥3👍1

25 Feb 2026, 10:55 UTC220 viewsread 6 August 2026

В свете CFP разных конференций задумался о чем рассказать. Закинул такой промпт во все свои AI-компаньоны и в целом даже идеи какие-то появились. Рекомендую: "Исходя из всего знания обо мне напиши какую бы тему я мог бы рассказать на технической конференции" Claude Code единственный кто сказал, я о тебе ничего не знаю, и только уже после напоминания о том, что у него вообще-то есть история чатов, опомнился и предл

23 Jan 2026, 04:28 UTC311 views4 reactionsread 6 August 2026

Очень вдохновляющая статья "Don't fall into the anti-AI hype" от Salvatore Sanfilippo - создателя и основного коммитера проекта Redis. По слогу статья очень напомнила мне статьи Joel Spolsky в его блоге Joel on Software. Такое размышление о программировании как о ремесле в эру развития AI кодинга. Главные тезисы - Написание кода теперь необязательно самая важная часть. Теперь намного интереснее понимать ЧТО сделать

👍4

19 Nov 2025, 03:40 UTC393 views3 reactionsread 6 August 2026
Photo

Вчера половина интернета висело из за сбоя в Cloudflare. Вообще управление инцидентами в распределенной среде это мега сложно, тем более в такой большой. Пост-мортем от команды Cloudflare (меньше чем за 24 часа!) https://blog.cloudflare.com/18-november-2025-outage/

❤‍🔥1👍1👏1

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

Citation-graph rank

Citation-graph rank — 861,406 of 1,169,250entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.

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.

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

“Бесконечное ИТ” (@neverendingit), 367 subscribers as measured 6 August 2026. Telegram Register, tgregister.com/channel/neverendingit.

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.