Telegram RegisterThe public register of Telegram

Channel

Bondy [ SRT/UDP TS Bonding ]

@bondy_ts

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

53subscribers

+0 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1002775518721
TypeChannel
Username@bondy_ts
CreatedBetween 1 June 2025 and 30 September 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded10 August 2026
Last confirmed live10 August 2026
Measurements held2
On Telegramt.me/bondy_ts

Growth

537 August 2026 — 53 subscribers10 August 2026 — 53 subscribers7 August 202610 August 2026
2 measurements spanning 3 days. 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 52–54 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
10 Aug 2026, 09:3153no change
7 Aug 2026, 03:1653first reading

Engagement

14 posts held, back to 15 June 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
81.8%
avg views ÷ 53 subscribers
Avg views / post
43.3
3 posts measured
Reaction rate
12.3%
reactions ÷ views · ER floor
Posts in window
3
of 14 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 2 August 2026
Posts held14 (15 June 20262 August 2026)
Views total130
Reactions total16
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken10 Aug 2026, 09:31 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
58
Videos
4
Links
11

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

Video runtime
1m 38s
Average length
49s

Measured directly from 2 videos 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

55 reactions across 12 posts, in 11 distinct kinds. The most used accounts for 47.3% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🔥2647.3%
🎉814.5%
👍814.5%
❤‍🔥610.9%
11.82%
11.82%
🍾11.82%
👀11.82%
😁11.82%
🙏11.82%
🤯11.82%

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 13 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 55reactions 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 15 June 2026 to 2 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.

Recent posts

2 Aug 2026, 06:00 UTC35 views6 reactionsread 10 August 2026

На этом этапе удалось решить одну из самых сложных проблем full broadcast bonding: нестабильный тайминг выходного потока: Один и тот же пакет приходит по нескольким каналам с разной задержкой. RX выбирает первую копию, удаляет дубли и восстанавливает порядок. Но если выдавать пакеты по времени их фактического прихода, сетевой джиттер попадает в выходной поток: видео периодически ускоряется, замедляется и получает др

🔥4❤‍🔥2

1 Aug 2026, 21:33 UTC36 views2 reactionsread 10 August 2026
Photo

BondyTX 4.0.0-beta.4 https://disk.yandex.ru/d/FskgV4gc1RU3NA Образы для x86 и raspberry pi 4/5 + прошивальщик (но можно использовать что-нибудь свое) RX один для x86/rpi Первый старт и определение модемов может быть не совсем быстрым, дальше будет всё быстрее Добавлена поддержка модемов Sierra EM7455, переработана логика формирования/сборки данных на мультилинке Проект всё еще следует логике работы full broadca

🔥2

27 Jul 2026, 19:23 UTC59 views8 reactionsread 10 August 2026
Photo

Всем привет! Всякие неприятные жизненные дела типа зарабатывания на кусок хлеба не дают заниматься разработкой столько, сколько хотелось бы. Однако на месте все равно мы не стоим: удалось победить неприятные неприятности и 25 минут на двух LTE модемах (Fibocom L-860 и Sierra EM7455) прошли без дропов. Попутно обнаружилась неточность в реализации отправки ARQ - по задумке ретрансмиты должны уходить как и все DATA пак

🎉8

24 Jun 2026, 17:56 UTC141 views6 reactionsread 10 August 2026
Video

Получилось бесшовное полностью пэрэключение 🤓 Единственное ограничение - потоки должны быть в одинаковом кодеке! Один exe файл, работает в трее, управление через web ui. Да оно требует ключ, прошу понять и простить. Ключ выдается в лс ✌️ https://disk.yandex.ru/d/hcvGb9DhB8m6XA UPD.: перезалил файл, переключение теперь полностью бесшовное без микропаузы на звуке

👍6

24 Jun 2026, 12:57 UTC123 views2 reactionsread 10 August 2026
Video

Осталось поработать над бесшовным переключением, не всегда отрабатывает как хотелось бы. Немного тестов и думаю получится подобрать нужные значения для расчетов момента переключения) А у Bondy всё-таки получилось малой кровью вылечить основной найденный баг (который не баг на самом деле, а просчет в реализации архитектуры). Но до новой сборки доберусь уже только в понедельник в лучшем случае.

👍2

24 Jun 2026, 09:09 UTC98 views5 reactionsread 10 August 2026
Photo

Расскажу про еще одну свою SRT-вундервафлю - KarRelay Это простой релей сервер SRT, с помощью которого можно ретранслировать входящий поток SRT на несколько потребителей. И не один, а в принципе сколько душе угодно (ну или пока сетевой стек винды не скажет "ыы я упал"). Потребители цепляются на один порт, что как бы вполне себе прикольно. Также можно создать канал (ы), набрать туда нужные источники, отправить на пл

🔥41

23 Jun 2026, 12:43 UTC79 views2 reactionsread 10 August 2026

Багов всплыло много и на TX и на RX, до конца недели свободного времени на починку примуса катастрофически мало, запасы жидкого хлеба тоже на исходе, к проекту вернусь, вероятно, не ранее следующего понедельника 🫡

❤‍🔥2

21 Jun 2026, 19:31 UTC82 views5 reactionsread 10 August 2026
Photo

Ну не с первого, но с третьего захода взлетело 😁 Версия для x86 систем Шьёте на любой носитель от 16гб и полетели. Secure boot должен быть выключен. Папку можно получить по ссылке: bondytx_x86_d739b48f8bc4 https://disk.yandex.ru/d/wDwvckXRfwjbJg P.S.: всплыли некоторые баги с RX (с TX никак не связаны), вылезают в основном при плохой связи, но это не точно. Будем решать уже завтра, ну а пока в рамках "потыкать-п

🔥41

21 Jun 2026, 14:02 UTC70 views3 reactionsread 10 August 2026
Photo

Я как-то даже не догадывался насколько это трудно и муторно состряпать x86 образ для распространения. Будем надеяться, что оно заработает с первой попытки 😁

🤯1😁1🙏1

19 Jun 2026, 20:15 UTC78 views3 reactionsread 10 August 2026
Photo

Как бы нам не хотелось иметь абсолютно одинаковый функционал на любой архитектуре, но именно особенности этой самой архитектуры заставляют вводить некоторые "платформенно-ориентированные" фичи (это не баг, это фича!!!) На Raspbery Pi мы заперты в рамках совершенно четкой и унифицированной среды, поэтому на версии для малины у нас модуль WiFi выступает как точка доступа. Это очень удобно для сценария, когда малина у

🔥3

17 Jun 2026, 20:18 UTC82 views3 reactionsread 10 August 2026
Photo

Натянул на x86, завтра погоняем

🔥2👀1

15 Jun 2026, 19:45 UTC104 viewsread 10 August 2026

Небольшая заметка по поводу того, как это все работает: Full broadcast = каждый TS-пакет отправляется по каждому активному линку. Почему правильно: в LTE/5G главная проблема не средняя скорость, а потери, джиттер, флапы и задержки. Дублирование даёт RX шанс получить пакет по любому живому каналу без ожидания ретрансляции. Это резко повышает стабильность видео. Почему скорости не складываются: один и тот же поток коп

Showing the 12 most recent of 14 posts we hold for @bondy_ts. 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 — 740,307 of 1,336,469entries 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.

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

“Bondy [ SRT/UDP TS Bonding ]” (@bondy_ts), 53 subscribers as measured 10 August 2026. Telegram Register, tgregister.com/channel/bondy_ts.

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.