Channel
@tech0ver
On this record: Growth · Engagement · Reactions · Posts · Polls · Citations · Cite this entry
21subscribers
-1 since we began measuring on 9 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002100419853 |
|---|---|
| Type | Channel |
| Username | @tech0ver |
| Created | Between 1 November 2023 and 31 May 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 11 August 2026 |
| Last confirmed live | 19 September 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 4 times, most recently 19 September 2026 |
| On Telegram | t.me/tech0ver |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 24 Aug 2026, 23:48 | 21 | -1 |
| 11 Aug 2026, 12:34 | 22 | no change |
| 9 Aug 2026, 05:15 | 22 | first reading |
19 posts held, back to 24 August 2025 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 page 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 19 posts for this entry, the most recent from 4 September 2025. An engagement rate over an empty window would be a number about nothing.
19 reactions across 18 posts, in 1 kind.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 19 | 100.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 18 of the 19 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 19 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 19 most recent posts we hold, published 24 August 2025 to 4 September 2025, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
⏰ Wall Clock vs Monotonic Clock — в разных языках #java #python #js #go 🔹 Wall/System Clock: ▪️ Java: System.currentTimeMillis() ▪️ Python: time.time() ▪️ JavaScript: Date.now() ▪️ Go: time.Now() 🔹 Monotonic Clock ▪️ Java: System.nanoTime() ▪️ Python: time.monotonic() ▪️ JavaScript: performance.now() * из perf_hooks ▪️ Go: start := time.Now() elapsed := time.Now().Sub(start) // time.Since(start) // time.Un…
👍1
⏰ Wall Clock vs Monotonic Clock #CS 🔹 RTC (Real-Time Clock) — кварцевые часы на материнской плате, постоянно хранят текущее время за счет собственной батарейки 🔹 System Clock — при загрузке OS получает стартовое значение из RTC как Unix time и продолжает «тикать», при завершении сохраняет текущее значение обратно в RTC, может корректироваться вручную или автоматически через NTP 🔹 NTP (Network Time Protocol) — про…
👍1
⏰ currentTimeMillis vs nanoTime #poll #java © tech0ver
👍1
Какие из двух исключений могут быть выброшены в Java-коде ниже? (только из явно обозначенных в коде)
Shares as published. No per-option vote count is published by Telegram, so none is shown.
⏱️ Leaky Bucket #systemdesign #cheatsheet © tech0ver
👍1
⏱️ Leaky Bucket #systemdesign #java Зеркальная ситуация: вместо наполнения бакета как в Token Bucket, занимается опустошением с заданной скоростью Посмотреть в репозитории 👀 Рассмотренные реализации до этого отменяли запросы (Traffic Policing), но данная реализация показывает преимущество в сглаживании (Traffic Shaping) за счет ожидания в (виртуальной) очереди 🔹 Хранение данных — O(N) ▪️ Интервал между запросами…
👍1
⏱️ Token Bucket #systemdesign #cheatsheet © tech0ver
👍1
⏱️ Token Bucket #systemdesign #java Каждый запрос расходует токен из бакета, который пополняется с заданной скоростью до максимальной емкости, при отсутствии токенов — новые запросы отклоняются до пополнения 🔹 Хранение данных — O(N) ▪️ Емкость: long capacity ▪️ Скорость наполнения в token/ns: double tokensPerNano ▪️ Бакеты ресурсов: Map<String, Bucket> buckets ▪️ В бакете кол-во токенов и время последнего попо…
👍1
⏱️ Сравнение реализаций Rate Limiter на основе временных окон #systemdesign #cheatsheet ▪️ Равномерный поток ▪️ Общий пик в середине ▪️ Зеркальные пики по краям ▪️ Пик в середине Прочитать про другие 🧐 © tech0ver
👍1
⏱️ Sliding Window Counter based on linear interpolation #systemdesign #cheatsheet © tech0ver
👍1
⏱️ Sliding Window Counter based on linear interpolation #systemdesign #java Заменяем бакеты из Sliding Window Counter (based on buckets) на счетчики текущего и предыдущего окон, текущее кол-во запросов вычисляется как сумма текущего окна и доли от предыдущего, пропорциональной оставшемуся времени текущего окна 🔹 Хранение данных — O(N) ▪️ Лимит: long limit ▪️ Размер окна в ns: long windowSizeNanos ▪️ Окна ресурс…
👍1
⏱️ Sliding Window Counter based on buckets #systemdesign #cheatsheet © tech0ver
👍1
Showing the 12 most recent of 19 posts we hold for @tech0ver. 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.
The poll we hold for this entry, as Telegram rendered it when we read the post. A poll’s figures keep moving after that, so each one is dated.
Какие из двух исключений могут быть выброшены в Java-коде ниже? (только из явно обозначенных в коде)
Shares as published. No per-option vote count is published by Telegram, so none is shown.
Percentages only — there are no per-option vote counts here, because Telegram publishes none. The public post preview gives each option’s share and a single voter total, and nothing else. Multiplying one by the other would produce a per-option tally that looks measured and is not: the shares are rounded to whole numbers before we ever see them. We print what was published and leave the column that does not exist empty.
The shares need not add up to 100. Rounding alone puts many polls at 99 or 101. A poll that allows more than one answer per voter runs well past 100 by design, and several here do. The bars are drawn against a fixed 100% track at each option’s own percentage rather than normalised to the total, so a poll that exceeds it shows that it does instead of being quietly rescaled.
Read from the 19 most recent posts we hold, published 24 August 2025 to 4 September 2025. Telegram labels each poll by kind — an anonymous poll, a quiz, a closed set of final results — and that label is reproduced rather than paraphrased.
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.
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 24 August 2026 — this entry's latest reading, not the date you are reading this.
“tech0ver” (@tech0ver), 21 subscribers as measured 24 August 2026. Telegram Register, tgregister.com/channel/tech0ver.
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.