Telegram RegisterThe public register of Telegram

Channel

Смотри что нашел

@b1tw1se

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

480subscribers

+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-1001291860579
TypeChannel
Username@b1tw1se
DescriptionНе мешай. У нас тут секта Deepseek
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/b1tw1se

Growth

4806 Aug 2026, 08:22 — 480 subscribers6 Aug 2026, 18:49 — 480 subscribers6 Aug 2026, 08:226 Aug 2026, 18:49
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 479–481 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
6 Aug 2026, 18:49480no change
6 Aug 2026, 08:22480first reading

Engagement

20 posts held, back to 3 April 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 pageof Telegram’s post history, 20 posts per page.

ERR · 30 days
83.6%
avg views ÷ 480 subscribers
Avg views / post
402
2 posts measured
Reaction rate
3.32%
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. It is computed over the 1 of 2 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 30 July 2026
Posts held20 (3 April 202630 July 2026)
Views total803
Reactions total11
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken6 Aug 2026, 18:49 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
43
Videos
2
Links
180

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

109 reactions across 12 posts, in 4 distinct kinds. The most used accounts for 45.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍4945.0%
😁3027.5%
🔥1816.5%
🤯1211.0%

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 12 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 109reactions 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 3 April 2026 to 30 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.

Telegram Stars

Stars received
2
across the posts below
Posts paid on
1
of 20 we hold a reading for · 5%
Most on one post
2
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @b1tw1se. 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 3 April 2026 to 30 July 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

30 Jul 2026, 08:37 UTC331 views11 reactionsread 6 August 2026

Земля пухом сервисам Яндекса. https://yandex.ru/company/news/29-07-2026-01 Ну вот почему 75%? Почему не 67%? Просто ради красивой циферки? Многие смеялись над гигачатезацией в одной зеленой компании, а по итогу вон как получилось…

😁10👍1

17 Jul 2026, 16:34 UTC472 viewsread 6 August 2026

Митап «Старый добрый Go в мире AI-агентов» — 24 июля в 18:30 в Санкт-Петербурге, в офисе VK (ТДЦ «У Красного моста», наб. реки Мойки, 73). Совместно с VK канал IT-подкастов «Алло, Ада» проводит Go-митап о том, какую роль язык играет в эпоху AI-агентов и как интегрируется в инженерный контур облаков и инфраструктуры. В программе — три доклада и круглый стол: - как обезопасить доступ ИИ к проду через Go и MCP 💪 - как

2 Jul 2026, 08:15 UTC527 views14 reactionsread 6 August 2026

Привет. Это мой небольшой разбор статьи из прикрепленного файла. Я решил сконцентрироваться на главной идее, но в самой статье есть технические детали реализации, которые не менее интересны. Найдите время почитать. Слышали такой тезис «сеть узкое место, CPU в избытке»? И раньше действительно было так, и оверхед на TCP стек был небольшой. Увы, эти времена прошли :( За 10 лет aws инфраструктура под сетевые нагрузки в

👍10🔥4

18 Jun 2026, 15:33 UTC451 views2 reactionsread 6 August 2026

Я сам еще не смотрел, но Леша фигни не делает :)

👍1😁1

18 Jun 2026, 15:33 UTC497 viewsread 6 August 2026
Forwarded from @atercattus_was_here

Наконец-то выкладываю запись к себе в канал https://www.youtube.com/watch?v=XLLIAXR2M2Q. Презентация тоже по ссылке в описании.

23 May 2026, 08:13 UTC699 views10 reactionsread 6 August 2026

Ну наконец-то приняли https://github.com/golang/go/issues/77273#issue-3845127408 Отрадно, что generic-и в Golang развиваются. Вопрос конечно почему сразу не сделать нормально открытый, как всегда :) tldr; теперь можно будет делать generic методы на обычном не дженерик типе или расширять методы другим дженериком

👍4🤯4🔥2

15 May 2026, 10:15 UTC757 views13 reactionsread 6 August 2026
Photo

Photo, posted without a caption

😁10👍2🔥1

13 May 2026, 05:33 UTC647 viewsread 6 August 2026

Мои знакомые из Центрального Университета устраивают митап по ИИ 21го мая в 18:30, кампус Центрального Университета - Москва, ул. Гашека, 7 (метро Маяковская). Будет три доклада, где ребята поделятся опытом запуска LLM на iPhone, расскажут про Agent Client Protocol и как его использовать при построении своего Cursor, а также затронут тему подготовки проекта к агнетскому программированию. В конце будет круглый стол н

11 May 2026, 19:50 UTC563 views7 reactionsread 6 August 2026
Photo

вот только вчера думал, почему нет хорошего бенчмарка агнетов :) Вообще с выходом (и использованием на постоянку) deepseek v4 еще глубже укоренилась мысль у меня, что на данный момент больше решает агент (или если более широко, то harness), чем модель. Ибо модели уже достаточно хороши для повседневных задач. https://artificialanalysis.ai/agents/coding-agents

🔥4👍3

8 May 2026, 06:43 UTC649 views6 reactionsread 6 August 2026

https://lightfoot.dev/direct-i-o-for-cassandra-compaction-cutting-p99-read-latency-by-5x/ Наткнулся на офигенный разбор про Cassandra и дисковый ввод-вывод. TLDR; чел заставил компакшн работать через direct i/o и получили пятикратный буст по p99. Вся боль в том, что компакшн (да и любые фоновые процессы работающие с диском) по идее должен быть … фоновыми, то есть не сильно на себя забирать ресурсы системы, но по

🤯4🔥2

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

Citation-graph rank

Citation-graph rank — 777,696 of 1,176,251entries 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

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 1 registered channel — 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.

Named by

Channels on the register whose posts name this channel's handle.

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

“Смотри что нашел” (@b1tw1se), 480 subscribers as measured 6 August 2026. Telegram Register, tgregister.com/channel/b1tw1se.

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.