Telegram RegisterThe public register of Telegram

Channel

cat mindflow.txt > /dev/null

@devnull42

On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry

175subscribers

+0 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1001144306324
TypeChannel
Username@devnull42
DescriptionПоток сознания о программировании, технологиях, жизни и вообще
CreatedBetween 1 June 2017 and 31 August 2020— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live8 August 2026
Measurements held2
On Telegramt.me/devnull42

Growth

1757 Aug 2026, 20:53 — 175 subscribers8 Aug 2026, 14:02 — 175 subscribers7 Aug 2026, 20:538 Aug 2026, 14:02
2 measurements taken within a single day. 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 174–176 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
8 Aug 2026, 14:02175no change
7 Aug 2026, 20:53175first reading

Engagement

20 posts held, back to 19 November 2021the 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 7 December 2022. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Photos
14
Links
87

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.

Reaction mix

61 reactions across 8 posts, in 10 distinct kinds. The most used accounts for 52.5% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🔥3252.5%
👍1829.5%
👏34.92%
❤‍🔥23.28%
11.64%
🎉11.64%
😁11.64%
🤔11.64%
🤣11.64%
🤩11.64%

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 9 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 61reactions 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 19 November 2021 to 7 December 2022, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.

Recent posts

7 Dec 2022, 06:46 UTC929 views6 reactionsread 8 August 2026
Forwarded from @k8securityPhoto

"Forensic container checkpointing in Kubernetes" - еще одна замечательная блоговая запись о новой фичи Kubernetes в официальном блоге. О данной фичи мы уже писали [1,2,3], но на всякий случай напомню, что она: - Базируется на Checkpoint/Restore In Userspace (CRIU) - Появилась в alpha статусе в Kubernetes v1.25 - Требуется включение ContainerCheckpoint gate на API server - Требуется поддержка на стороне Container Runt

🔥51

5 Nov 2022, 13:35 UTC785 views10 reactionsread 8 August 2026

К сожалению, редко получается писать в этот канал. Поэтому я завел другой! Решив не дожидаться пока Илон сломает мою любимую платформу, объявляю неделю диверсификации способов доставки ~полезного~ контента в мозг читателей открытой! https://t.me/iximiuz_hub

👍9🤔1

20 Aug 2022, 11:37 UTC952 views20 reactionsread 8 August 2026

У меня тут интервью взяли, первый раз в жизни, вдруг кому интересно будет 🙂 https://www.slim.ai/blog/clarifying-the-complex-meet-ivan-velichko-container-dude-at-slim.ai.html

🔥16👍3🎉1

6 Jul 2022, 06:58 UTC876 views16 reactionsread 8 August 2026
Forwarded from @k8security

Большинство людей (до 85% населения Земли) являются визуалами (главным типом восприятия является именно зрительный контакт) и изучать таким людям что-то новое или сложное проще на картинках. У Ивана Величко есть замечательный блог с разделом Learning Series, где можно узнать много всего о containers и Kubernetes именно в такой форме. Сейчас есть серии на темы: - Debunking Container Myths - Mastering Container Network

🔥9👏3❤‍🔥2👍1🤩1

15 Jun 2022, 20:49 UTC708 views3 reactionsread 8 August 2026
Forwarded from @deemarique

Совершенно неожиданно разродился статьей про то, как в Си навертеть что-то похожее на ООП. Из серии про "буханку хлеба можно превратить в троллейбус", конечно же, зато с работающим кодом! Статья практически "в стол", потому что в приличном обществе такого показывать ни в коем случае нельзя. Надеюсь, среди вас найдутся ценители 🙂 https://doroshev.com/blog/c-inheritance/

👍3

15 Jun 2022, 20:49 UTC569 viewsread 8 August 2026

С пылу с жару - про ООП и Си! Прям аж молодость вспомнилась!

4 Feb 2022, 09:06 UTC805 viewsread 8 August 2026

Никогда не задумывался о смысле выражения "Исключение подтверждает правило." И, похоже, частенько неправильно его использовал! Или же оказывался тем, на ком его использовали не по назначению в пылу очередного спора какой язык программирования лучше. Но сегодня, читая про истинных шотландцев, узнал, что существует вполне себе логичная интерпретация. Оказывается, на самом деле выражение должно было нам сказать, что сущ

1 Feb 2022, 20:41 UTC756 viewsread 8 August 2026

Я надеюсь, все здесь уже видели вот этот шедевр? Товарищ заморочился и сделал интерактивный плейграунд с systemd в браузере! Работает это естесственно на контейнерах, и у меня большие вопросы к безопасности этого решения, но с образовательной точки зрения ресурс получился просто огненный! Там еще и с картинками! - systemd by example Part 1: Minimization - systemd by example Part 2: Dependencies

26 Jan 2022, 20:36 UTC696 views3 reactionsread 8 August 2026

Если вдруг кому-то интересно, как я выгляжу :) https://twitter.com/iximiuz/status/1486406653335506951?s=21

👍2🤣1

25 Jan 2022, 12:11 UTC502 viewsread 8 August 2026
Photo

Good one! И KodeKloud тоже норм место, хоть и с двумя K пишется.

Showing the 12 most recent of 20 posts we hold for @devnull42. 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.

Forward network

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 8 August 2026 — this entry's latest reading, not the date you are reading this.

“cat mindflow.txt > /dev/null” (@devnull42), 175 subscribers as measured 8 August 2026. Telegram Register, tgregister.com/channel/devnull42.

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.