Channel
@zh_rust
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
207subscribers
+0 since we began measuring on 8 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1003326123552 |
|---|---|
| Type | Channel |
| Username | @zh_rust |
| Description | Тяжела и неказиста жизнь Южно-Голландского Rust-иста. Авторский канал @ovrweb про жизнь в Нидерландах, системную/веб разработку, Rust и всеми любимый JavaScript |
| Created | Between 1 November 2025 and 7 January 2026— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 8 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/zh_rust |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 8 Aug 2026, 11:16 | 207 | no change |
| 8 Aug 2026, 08:30 | 207 | first reading |
15 posts held, back to 7 January 2026 — 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 pageof 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 15 posts for this entry, the most recent from 1 July 2026. An engagement rate over an empty window would be a number about nothing.
Lifetime counters from Telegram’s own channel header, read 8 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.
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.
110 reactions across 12 posts, in 15 distinct kinds. The most used accounts for 30.0% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 😁 | 33 | 30.0% | |
| 🔥 | 23 | 20.9% | |
| ❤ | 20 | 18.2% | |
| 👍 | 11 | 10.0% | |
| 🍓 | 6 | 5.45% | |
| ☃ | 3 | 2.73% | |
| 💅 | 2 | 1.82% | |
| 💯 | 2 | 1.82% | |
| 🤗 | 2 | 1.82% | |
| 🤡 | 2 | 1.82% | |
| 🤯 | 2 | 1.82% | |
| 🌚 | 1 | 0.909% | |
| 🙈 | 1 | 0.909% | |
| 🙏 | 1 | 0.909% | |
| 🫡 | 1 | 0.909% |
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 15 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 110reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 15 most recent posts we hold, published 7 January 2026 to 1 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.
Как и обещал, выкатываю фулл лист моего ПК под телек в сравнении со Steam Machine Для начала цены Steam Machine в Европе: 512GB w/controller - 1 039/1 108 евро 2TB w/controller - 1 359/1 428 евро Моя сборка: CPU - AMD 7500x3d - 219 евро MOTHERBOARD - Gigabyte B650I AX - 146,34 евро MEMORY - Corsair DDR5 Vengeance 2x8GB 6000 CMK16GX5M2E6000Z36 - 237,9 евро CASE - Jonsbo NV10 - 89,90 евро GPU - Gigabyte GeForce RTX 5…
👍7
Video message, posted without a caption
🔥2
Video message, posted without a caption
Video message, posted without a caption
Video message, posted without a caption
❤4
Video message, posted without a caption
❤4
Сервис GitHub собщил о выявлении неавторизированного доступа к своим внутренним репозиториям Оригинальный тред в X Причиной стала компрометация рабочей станции одного из сотрудников, установившего новую версию одного из расширений к редактору кода VS Code, в которую был интегрирован вредоносный код. Какое именно дополнение к VS Code было установлено не уточняется. Скорее всего речь идет о расширении Nx Console (вч…
Продукт, который поможет не терять продуктивность https://github.com/ovr/vibecoder-connector (поддержите лайками! ваша поддержка бесценна) Проблема: разработчик запускает Claude Code, переключается на другую вкладку/телефон/кофе, и пропускает момент, когда агент закончил или ждёт ввод. Внимание фрагментировано. Контекст теряется. Продуктивность падает. Существующие решения — звуковые уведомления — не работают в на…
😁10🔥7
Сегодня будет крайне интересный день в Anthropic, но еще больше интересно то, насколько огромное влияние это окажет на другие агенты. По сути, кодовая база Claude Code - это кладезь интересных приемов и архитектурных решений, которые помогают им быть намного лучше другие (личная оценка, любители других агентов простите). Ранее, кто задавался вопросом, уже знали, что исходников Claude нет на GitHub, а в NPM там обфус…
🍓6❤3
Исходный код Claude был слит в сеть через source map в их npm пакете. Вайб есть - приватности нет. Ребята запушили source map файл в npm пакет @anthropic-ai/claude-code (заметил Chaofan Shou). 59,8 мб файл. С помощью него можно восстановить исходники в оригинальном состоянии, уже есть на GitHub: • Репо 1 • Репо 2 Голландский Rust-ист - канал о веб разработке
😁7🤯2🫡1
Cursor выпустили новую модель Composer 2, но Звучит крайне интересно. Новая модель которая показывает внушающие результаты на бенчмарке Cursor Bench. Что простите? Каком бенчмарке? Да, ребята тестировали свою модель на своем же бенчмарке, лол. Фаундер курсора рассказал, что там такая нереальная команда, что прям вау (an exceptionally talent-dense team of ~40 people with some of the best researchers and engineers fr…
😁13🤡2
Финтех-компания Block решила уволить 40% сотрудников из-за ИИ Вчера Джек Дорси, публично в твиттере написал, что они сокращают штат с 10к до менее чем 6к человек. Читаешь и кажется достаточно логичным на первый взгляд, но вызывает фрустрацию на тему "Кожаные мешки больше не нужны, AI заменит всех, это конец". Сейчас пацаны завайб-мерджат весь этот вайб-код в мастер, а работягам придется идти на минус вайбе на завод…
👍4😁3💯2❤1🙏1
Showing the 12 most recent of 15 posts we hold for @zh_rust. 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 — 682,013 of 1,160,990entries 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.
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.
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.
Names
Channels on the register whose handles appear in this channel's posts.
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.
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 8 August 2026 — this entry's latest reading, not the date you are reading this.
“Голландский Rust-ист” (@zh_rust), 207 subscribers as measured 8 August 2026. Telegram Register, tgregister.com/channel/zh_rust.
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.