5 measurements spanning 28 days, net +2. 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 669–672 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)
Subscribers
Change
5 Sept 2026, 04:59
672
+1
28 Aug 2026, 17:32
671
+2
21 Aug 2026, 04:14
669
-1
8 Aug 2026, 02:33
670
no change
7 Aug 2026, 23:09
670
first reading
Engagement
20 posts held, back to 8 June 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 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 20 posts for this entry, the most recent from 7 August 2026. An engagement rate over an empty window would be a number about nothing.
Reaction mix
60 reactions across 12 posts, in 6 distinct kinds. The most used accounts for 60.0% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
🔥
36
60.0%
👍
8
13.3%
😱
6
10.0%
❤
4
6.67%
🆒
3
5.00%
🕊
3
5.00%
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 60 reactions 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 8 June 2026 to 7 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.
CI/CD (Continuous Integration / Continuous Delivery)
Это подход к разработке ПО, который автоматизирует сборку, тестирование и доставку обновлений приложений.
Процесс CI (непрерывная интеграция) автоматически проверяет и тестирует новый код при каждом изменении в Git, чтобы сразу находить баги.
Процесс CD (непрерывная доставка) берет проверенный код и автоматически выкатывает его на рабочие сервера.
Например, ког…
301 и 302
Ну люблю я вопросы про коды ответа HTTP.
Коды 3xx означают, что ресурс был перемещен. 301 говорит о постоянном переносе адреса, а 302 — о временном. Правильным ответом был второй.
502 и 504
Опытный глаз с первого взгляда различил в этом вопросе коды ответа с проблемами на стороне сервера. Коды начинаются с 5xx.
Коды 5xx означают, что запрос был отправлен, но ответ от сервера либо не пришел, либо с ним были какие-то проблемы.
Осталось понять разницу между 502 Bad Gateway и 504 Gateway Timeout. Код 502 означает, что ответ пришел, но он некорректен. Код 504 означает, что за выделенное время от…
Снова про уровни OSI
Возможно не все работают напрямую с OSI, но я думаю, что это отличный пример темы, когда понимание позволяет писать значительно более качественную документацию. Например, понимание разницы между балансировщиками на уровнях L7 и L4 позволяет лучше описывать взаимодействия по сети.
Оба балансировщика перераспределяют трафик между серверами. В чем же разница?
На транспортном уровне L4 у балансиро…
GraphQL
Я не буду пытаться сейчас объяснить всю сложность реализации GraphQL, да это и не нужно. Я хочу донести основную идею.
Основная идея состоит в том, что в случае RESTful API мы получаем от сервера изначально известные поля с известной структурой, например:
user: Elena,
date: 25.07.2026,
occupation: technical writer
Этих полей может быть слишком много или недостаточно, поэтому в GraphQL есть возможность точ…
Git rebase и git merge
Ни одна из этих команд напрямую не связана с удалением веток или подключением к сети. Так что два последних ответа были совсем не про то.
Основная разница между git merge и git rebase в том, что в результате первой команды в истории основной ветки появляется один мерж коммит, а в результате второй — история ветки, то есть порядок коммитов сохраняются, и новые коммиты добавляются в конец ветки…
👍3❤1🔥1
Signed Ленка
Showing the 12 most recent of 20 posts we hold for @quizzes4fun. 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.
Polls
The 6 most recent of 9 polls we hold for this entry, as Telegram rendered them when we read the post. A poll’s figures keep moving after that, so each one is dated.
Какую основную проблему традиционных REST API решает технология GraphQL?
Избыточность или нехватку данных в ответе сервера за счет точного выбора нужных полей.45%
Ограничение на передачу медиафайлов большого объема через стандартные HTTP-запросы.31%
Обязательное требование к использованию только реляционных баз данных на бэкенде.20%
Необходимость настройки сложных политик безопасности CORS на стороне веб-сервера.4%
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 20 most recent posts we hold, published 8 June 2026 to 7 August 2026. 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.
Forward network
Republishes
Channels on the register whose posts this channel has forwarded.
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
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.
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 5 September 2026 — this
entry's latest reading, not the date you are reading this.
“QFE” (@quizzes4fun), 672 subscribers as measured 5 September 2026. Telegram Register, tgregister.com/channel/quizzes4fun.
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.
