Telegram RegisterThe public register of Telegram

Channel

tempus.build

@tempusbuild

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

43subscribers

+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-1004456992267
TypeChannel
Username@tempusbuild
DescriptionУправляемые раннеры для GitHub Actions. Drop-in замена GitHub-hosted раннерам: скорость bare-metal, колокация кэшей зависимостей, посекундная тарификация. https://tempus.build/
CreatedBetween 1 June 2026 and 17 June 2026— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded10 August 2026
Last confirmed live14 August 2026
Measurements held2
On Telegramt.me/tempusbuild

Growth

436 August 2026 — 43 subscribers10 August 2026 — 43 subscribers6 August 202610 August 2026
2 measurements spanning 4 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 42–44 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
10 Aug 2026, 16:1643no change
6 Aug 2026, 13:0443first reading

Engagement

11 posts held, back to 17 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
1217.2%
avg views ÷ 43 subscribers
Avg views / post
523
8 posts measured
Reaction rate
this channel exposes no reaction counts
Posts in window
8
of 11 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 31 July 2026
Posts held11 (17 June 202631 July 2026)
Views total4,187
Reactions total
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken10 Aug 2026, 16:16 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
14
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.

Reaction mix

13 reactions across 2 posts, in 3 distinct kinds. The most used accounts for 38.5% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
538.5%
👍430.8%
🔥430.8%

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

Measured over the 11 most recent posts we hold, published 17 June 2026 to 31 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

31 Jul 2026, 10:58 UTC44 viewsread 10 August 2026
Photo

Отсутствие доверия по умолчанию, это базовое условие в информационной безопасности. В особенности это применимо к зависимостям, которые мы используем в разработке. В контексте managed-runners основная зависимость, это раннер-образ, в котором будет исполняться ваш код. Разобрали и рассказали как мы выстроить supply-chain доверие: digest-пины вместо тегов, Trivy-гейт на CVE, keyless cosign + Sigstore, SLSA-provenance

29 Jul 2026, 08:55 UTC47 viewsread 10 August 2026
Photo

Self-hosted runners или managed: реальная стоимость "Свои раннеры дешевле" — так выглядит, пока сравниваешь только цену инстанса. Но compute — лишь одна из трёх статей расходов. Ещё две, эксплуатация и риск, в тарифах облака не показаны — и разница уходит именно в них. Разбираем, из чего реально складывается стоимость self-hosted: простой always-on ёмкости, автоскейл (ARC), сборка и патчинг образов, изоляция недов

28 Jul 2026, 12:54 UTC45 viewsread 10 August 2026

Разбираем нововведения Kata Containers 4.0 https://tempus.build/ru/blog/kata-containers-4-runtime-rs/

27 Jul 2026, 09:54 UTC≈1,030 viewsread 10 August 2026

Появился блог и опубликована первая статья https://tempus.build/ru/blog/kata-containers-isolation/ Крайне важная технология и подходы, лежащие в основе изоляции в инфрастуктуре tempus.build

24 Jul 2026, 13:46 UTC59 viewsread 10 August 2026

Добавил на сайте Trust Center - страницу про безопасность. Русская версия https://tempus.build/ru/security/ Английская версия https://tempus.build/en/security/

24 Jul 2026, 10:51 UTC≈1,000 viewsread 10 August 2026

Безопасность как дизайн: изоляция по умолчанию Я сам паранойик и топлю за безопасность. Как правило смотрю на репутацию решения, его известность, комьюнити и доступную документацию. Но у tempus.build пока нет ничего, кроме моих слов и части продукта в OSS, который должен добавить доверия. Но я считаю важным описать исчего складывается безопасность решения сейчас. Изоляция в tempus.build - не настройка, которую мож

24 Jul 2026, 09:24 UTC922 viewsread 10 August 2026
Photo

Немного расскажу про стоимость. tempus.build платное решение, оплата идет за потребление. Кадлый шейп стоит сколько-то денег в секунду. На скриншоте цены. Сейчас реализован наиболее популярный стандартный шейп - 4 vCPU, 16 GB RAM. Это стандартный в Github шейп. И если вы работаете уже с GitHub actions, то скорее всего используете его. Соответсвенно, пробуя tempus.build вы сможете проверить разницу 1к1 по ресурсам

24 Jul 2026, 09:15 UTC≈1,040 viewsread 10 August 2026
Photo

Получилось дольше, чем планировал. Но и сделано больше чем планировал. Есть две новости: 1. Бенчмарки начаты, но не закончены. НО! Смотри новость 2. 2. Релизнул платформу https://app.tempus.build/ Что дает платформа? Это полностью self managment сервис по работе с tempus.build. Приложу скриншоты, чтобы вы понимали тот объем проведенной работы и задачи которые решает платформа. Раннеры • Drop-in замена GitHub-hos

21 Jun 2026, 14:47 UTC283 views7 reactionsread 10 August 2026

Сейчас в tempus.build очень много задач. Закрываю их все я самостоятельно. Главная сейчас задача для меня, до того как ходить и предлагать пробовать продукт среди первых последователей, это подтвердить на числах эффективность моего сервиса. Поэтому последние дни я был сконцентрирован на проработке методики бенчмарков и написании сопутствующего кода, который будет проводить бенчмарки и снимать метрики. И все это буде

3👍2🔥2

17 Jun 2026, 19:56 UTC399 views6 reactionsread 10 August 2026

"У GitHub есть Free tier, зачем мне tempus.build" Я не конкурирую с free tier. На публичных репо раннеры GitHub-hosted бесплатны, приватные на Free дают 2000 минут в месяц, Team 3000. Кто укладывается в эти лимиты и кого устраивает скорость, не мои клиенты. 2000-3000 минут уходят достаточно быстро, хоть и кажется, что это много. И стоит ещё учитывать округление минут вверх. Мой клиент тот, кто квоту пробил, платит

2👍2🔥2

Showing the 11 most recent of 11 posts we hold for @tempusbuild. 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 — 281,573 of 1,480,688entries 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 10 August 2026 — this entry's latest reading, not the date you are reading this.

“tempus.build” (@tempusbuild), 43 subscribers as measured 10 August 2026. Telegram Register, tgregister.com/channel/tempusbuild.

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.