Channel
@netquiz
On this record: Topic · Growth · Engagement · Reactions · Posts · Telegram's recommendations · Cite this entry
1,489subscribers
-7 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1001328720557 |
|---|---|
| Type | Channel |
| Username | @netquiz |
| Created | Between 1 March 2018 and 31 August 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 19 September 2026 |
| Measurements held | 15 |
| Confirmed unchanged | 1 time, most recently 19 September 2026 |
| On Telegram | t.me/netquiz |
Education — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 17 September 2026 and assigned it the closest of 31 fixed categories, at 99% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and why it has no browse page of its own yet.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 19 Sept 2026, 16:38 | 1,489 | -2 |
| 15 Sept 2026, 08:19 | 1,491 | -1 |
| 11 Sept 2026, 12:19 | 1,492 | -1 |
| 6 Sept 2026, 11:36 | 1,493 | +1 |
| 2 Sept 2026, 04:08 | 1,492 | -3 |
| 30 Aug 2026, 12:16 | 1,495 | +2 |
| 27 Aug 2026, 19:17 | 1,493 | +2 |
| 24 Aug 2026, 13:38 | 1,491 | -1 |
| 20 Aug 2026, 20:38 | 1,492 | +1 |
| 17 Aug 2026, 18:33 | 1,491 | -2 |
| 14 Aug 2026, 19:23 | 1,493 | -2 |
| 10 Aug 2026, 23:42 | 1,495 | -2 |
| 8 Aug 2026, 02:07 | 1,497 | +1 |
| 7 Aug 2026, 11:01 | 1,496 | no change |
| 7 Aug 2026, 10:59 | 1,496 | first reading |
20 posts held, back to 21 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 2 pages 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 4 August 2026. An engagement rate over an empty window would be a number about nothing.
6 reactions across 3 posts, in 1 kind.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 6 | 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 4 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 6 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 21 June 2026 to 4 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.
Какое ключевое слово C# используется для изменения данных и поведения базового класса путем замены члена базового класса новым производным членом? 👾 — overrides 👍 — protected 🥰 — base ⚡️ — new 🐸Библиотека задач по C#
Покупать новый курс каждый раз, когда меняется рабочая задача, — довольно странная механика. Нашли альтернативу 👇
Разработчику нужен стабильный результат, DevOps — контроль инфраструктуры, техлиду — правила для всей команды. Собрали это в одном посте 👇
Как написать получение диапазона и копирование в массив? Ответ на картинке.
Самый страшный файл в проекте — тот, который «работает, не трогай» 👇
Как сделать «асинхронный lock» вокруг критической секции? 👾 — lock работает через await 👍 — await semaphore.WaitAsync() с SemaphoreSlim(1, 1) и try/finally Release() 🥰 — Monitor.Enter/Exit поддерживает await ⚡️ — Interlocked гарантирует эксклюзивный доступ ко всей секции Библиотека задач по C#
Чем BackgroundService отличается от IHostedService? 👾 — Предназначен только для таймеров 👍 — Это базовый класс с циклом ExecuteAsync; IHostedService — лишь интерфейс Start/Stop без цикла 🥰 — Запускается только в Debug ⚡️ — Не поддерживает отмену CancellationToken Библиотека задач по C#
👍1
Что гарантирует readonly struct? 👾 — Что структура хранится только на стеке 👍 — Все поля readonly; методы не могут изменять this, компилятор предотвращает записи и избегает лишних defensive copies для in 🥰 — Автоматическую реализацию IEquatable ⚡️ — Что экземпляры нельзя боксить Библиотека задач по C#
Что даёт record struct по сравнению с обычным struct? 👾 — Делает тип ссылочным 👍 — Генерирует структурное равенство, with-копирование и Deconstruct, оставаясь значимым типом 🥰 — Запрещает изменяемые поля ⚡️ — Автоматически реализует IDisposable Библиотека задач по C#
Можно ли объявить protected член в интерфейсе? 👾 — Да 🥰 — Нет ⚡️ — Иногда Библиотека задач по C#
Что произойдет, если попытаться присвоить значение переменной readonly вне конструктора? 👾 — Ошибка компиляции 👍 — Ошибка выполнения 🥰 — Переменная будет изменена ⚡️ — Переменная станет null Библиотека задач по C#
Как логировать в Microsoft.Extensions.Logging с минимумом аллокаций на горячем пути? 👾 — Интерполяция строк: $"User {id} logged in" 👍 — LoggerMessage.Define/DefineScope с кэшированными делегатами (структурированное логирование) 🥰 — Console.WriteLine — самый лёгкий вариант ⚡️ — Создавать новый EventSource на каждое сообщение Библиотека задач по C#
Showing the 12 most recent of 20 posts we hold for @netquiz. 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 reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.
This channel appears in 1 seed channel's Telegram-generated recommendation list in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
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 19 September 2026 — this entry's latest reading, not the date you are reading this.
“C# / .NET задачи и вопросы” (@netquiz), 1,489 subscribers as measured 19 September 2026. Telegram Register, tgregister.com/channel/netquiz.
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.