Channel
@network_arch
On this record: Growth · Engagement · Posts · Citations · Cite this entry
1,592subscribers
+0 since we began measuring on 11 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1001096263698 |
|---|---|
| Type | Channel |
| Username | @network_arch |
| Created | Between 1 September 2016 and 30 November 2017— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 11 August 2026 |
| Last confirmed live | 11 August 2026 |
| Measurements held | 2 |
| Confirmed unchanged | 1 time, most recently 11 August 2026 |
| On Telegram | t.me/network_arch |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 11 Aug 2026, 11:53 | 1,592 | no change |
| 11 Aug 2026, 02:46 | 1,592 | first reading |
20 posts held, back to 19 November 2024 — 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 20 posts for this entry, the most recent from 12 April 2026. An engagement rate over an empty window would be a number about nothing.
Как работает TCP-квитирование Рукопожатие, благодаря которому стал возможен интернет. Я говорю о трехэтапном рукопожатии TCP. Каждый раз, когда вы открываете веб-сайт, TCP обеспечивает это рукопожатие и надежное соединение. Как это происходит? Давайте рассмотрим каждый этап: https://newsletter.systemdesigncodex.com/p/how-tcp-handshake-works
Переезд с Nginx на Angie. Пошаговая инструкция https://habr.com/ru/articles/912932/
Как подключить виртуальные сетевые диски к выделенному серверу https://habr.com/ru/companies/selectel/articles/912132/
Побег от WSL или Как превратить старый ноутбук в домашний сервер для хранения данных и удаленной работы https://habr.com/ru/articles/906742/
Что будет, если не использовать TCP или UDP? Однажды мне стало интересно: а что будет, если отправить пакет с несуществующим транспортным протоколом? Не TCP, не UDP, не ICMP — вообще что-то выдуманное. Пропустит ли его ОС? Дойдет ли он хотя бы до сетевого интерфейса? Не зарежет ли его какой-нибудь промежуточный маршрутизатор? А вдруг он еще и быстрее обычного дойдет, потому что никто не знает, что с ним делать? Отв…
Дело всегда в TCP_NODELAY https://habr.com/ru/companies/ruvds/articles/890874/
Что бы произошло, если бы мы не использовали TCP или UDP? https://github.com/Hawzen/hdp
NUT на моем Pi, чтобы мои серверы не умирали https://www.jeffgeerling.com/blog/2025/nut-on-my-pi-so-my-servers-dont-die
Как я отправил 500 миллионов HTTP-запросов на 2,5 миллиона хостов https://www.moczadlo.com/2024/how-i-sent-500-million-http-requests-in-under-24h
Как на самом деле работает Интернет Передача данных по оптоволоконным кабелям; TCP/IP; HTTP, HTTPS и TLS; Сетевая коммуникация; IP-адреса, DNS и доменные имена; Центры обработки данных и инфраструктура; https://www.youtube.com/watch?v=fil3KUxYg3c
15 элементов проектирования систем, которые необходимо знать https://newsletter.systemdesigncodex.com/p/15-must-know-elements-of-system-design
Как настраивать сети: облачные роутеры и публичные IP https://habr.com/ru/companies/selectel/articles/875782/
Showing the 12 most recent of 20 posts we hold for @network_arch. 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 — 1,125,488 of 1,151,006entries 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.
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.
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 11 August 2026 — this entry's latest reading, not the date you are reading this.
“Network architecture and Administration” (@network_arch), 1,592 subscribers as measured 11 August 2026. Telegram Register, tgregister.com/channel/network_arch.
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.