Telegram RegisterThe public register of Telegram
Telegram profile photo for 403

Channel

403

@DevopsNotFound

On this record: Growth · Engagement · Reactions · Stars · Posts · Citations · Cite this entry

174subscribers

+0 since we began measuring on 12 August 2026

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

Register entry

Telegram ID-1001747371703
TypeChannel
Username@DevopsNotFound
Created11 December 2022measured — dated from the channel’s first post
First recorded12 August 2026
Last confirmed live12 August 2026
Measurements held2
Confirmed unchanged1 time, most recently 12 August 2026
On Telegramt.me/DevopsNotFound

Growth

17412 Aug 2026, 12:03 — 174 subscribers12 Aug 2026, 22:04 — 174 subscribers12 Aug 2026, 12:0312 Aug 2026, 22:04
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 173–175 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
12 Aug 2026, 22:04174no change
12 Aug 2026, 12:03174first reading

Engagement

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

Reaction mix

95 reactions across 17 posts, in 11 distinct kinds. The most used accounts for 53.7% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍5153.7%
1414.7%
🔥1414.7%
😁44.21%
🤯44.21%
👎22.11%
👏22.11%
❤‍🔥11.05%
😍11.05%
😱11.05%
🙏11.05%

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

Telegram Stars

Stars received
2
across the posts below
Posts paid on
2
of 19 we hold a reading for · 11%
Most on one post
1
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @DevopsNotFound. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.

Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.

This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.

Counted over the 20 most recent posts we hold for this entry, published 11 December 2022 to 18 November 2025. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.

Recent posts

18 Nov 2025, 17:48 UTC509 views12 reactions1 Starread 12 August 2026

bind: Address already in use این ارور یه دروغه میدونستین 2 تا Process میتونن همزمان روی یک پورت Listen کنن؟ توی TCP یه فلگی هست که اجازه میده پروسه بعدی که میخواد روی یه پورت لیسن کنه بتونه همزمان اینکارو انجام بده و این فلگ SO_REUSEPORT هست. وقتی از این فلگ استفاده میکنیم کرنل خودش بین این 2 تا پروسه فرایند LoadBalancing انجام میده. اینکه با چه الگوریتمی لودبلنس میکنه و یا از چه ورژن کرنل به بعد قابل دسترس هست رو م

👍5🤯4🔥2😱1

11 Nov 2025, 18:21 UTC371 views4 reactions1 Starread 12 August 2026

گاهی اوقات بیشتر از یک پروسه بکند داریم که ممکنه روی سرور های مختلفی باشن و میخوایم درخواست ها به همه اینا برسه. تو اینطور شرایط از چیزی به اسم LoadBalancer استفاده میکنیم. کارش اینه که روی یک پورت لیسن میکنه و هرچی درخواست میاد رو میفرسته به آدرس یا آدرس هایی که بهش میگیم. نمونه: Haproxy و Nginx (چند ده محصول معروف دیگه هستن که اسمشون رو نمیگم) سوالی که پیش میاد اینه که چطور میفهمه به کدوم بکند بفرسته؟ الگوریتم های

🔥21👍1

5 Nov 2025, 18:42 UTC363 views8 reactionsread 12 August 2026

یه ایرادی که خیلی بین تازه کار ها رایجه، متمایز نبودن کلمات Encoding ،Encryption و Hashing تو ذهنشونه. حتی تو افراد باتجربه هم دیدم که بصورت فعال اینارو متمایز نمیبینن. سعی میکنم خیلی ساده توضیح بدم چون در پست های بعد حتما ازشون استفاده میشه. 1️⃣ ‏Encoding: در واقع یک رشته (مجموعه ای از کاراکتر ها) تبدیل به رشته جدیدی کنیم، بصورتی که صرفا با دونستن الگوریتم Encoding استفاده شده بشه بازگردانیش کرد. یکی از Encodingها

4👍3👏1

27 Jul 2025, 20:20 UTC578 views7 reactionsread 12 August 2026

سلام (احتمالا) همه اسم Redis رو شنیدیم. دیتابیس از نوع Key-Value هست که کاری ندارم و میتونید جزئیاتش رو مطالعه کنید. یه نکته ای که هست، ردیس بطور کلی دیتارو تو رم نگهداری میکنه و این یعنی وقتی ریستارت بشه تمامی دیتا از بین میره چون همش روی مموری ذخیره شده. خیلی وقتا (به طرز عجیبی) نیازه که دیتایی که ذخیره میکنیم پاک نشه و بمونه، اون موقع ردیس 2 تا راهکار ارائه میکنه: 1. AOF: تو این حالت ردیس بصورت مستقیم تمامی دستور

5🔥1🙏1

17 Mar 2025, 21:10 UTC882 views6 reactionsread 12 August 2026

این سایت کار با Git بصورت Interactive یاد میده و نقطه شروع خیلی خوبیه: https://learngitbranching.js.org/ #Git

3👍2👎1

11 Mar 2025, 15:19 UTC936 views4 reactionsread 12 August 2026

مدیریت لاگ در Docker: تاحالا مسیر زیر رو دیدید؟ /var/lib/docker/containers توی این مسیر به ازای هر کانتینر یک دیرکتوری وجود داره که توش یه سری فایل هست ولی تمرکز من تو این پست روی فایل زیر هست: container-id-json.log *اسم فایل به آی دی کانتینر بستگی داره اگر کانتینرتون لاگ زیادی تولید میکنه، ممکنه باعث پر شدن دیسک و در نتیجه خطا گرفتن از سرویسا بشه. راه محدود کردن این لاگ به 3 شیوه زیره: موقع ساخت کانتینر: docker ru

👍31

4 Mar 2025, 21:10 UTC712 views3 reactionsread 12 August 2026

شاید تو خیلی از بازرسی ها امنیتی دیده باشید به ورژن اپلیکیشن گیر میدن، و عموما هم بدون توجه به این خطا ها رد میشیم. ولی چرا از نظر امنیتی مشکل داره که ورژن پکیج/سرویس/اپلیکیشن ها قدیمی باشه؟ 1. آشنایی با CVEsها: اول با مبحث CVE آشناتون میکنم، هر باگ امنیتی ای که توسط Community یا صاحب اپلیکیشن پیدا میشه، به اون اپلیکیشن/سرویس گزارش میشه و طی بازه زمانی کوتاهی Patch میشه (اگر دلشون بخواد!) و نسخه جدیدی رو بیرون میدن.

🔥2👍1

3 Mar 2025, 07:58 UTC593 views7 reactionsread 12 August 2026

اگه براتون سواله که از چه دیتابیسی استفاده کنید، میتونید به لینک زیر مراجعه کنید😁. https://choosedb.com/

😁4🔥2👎1

1 Mar 2025, 19:13 UTC586 views4 reactionsread 12 August 2026

میدونستید اگه دیسک یه کامپیوتر/سرور رو ازش جدا کنید، بازم میتونید دیتاشو بخونید؟ بطور کلی سیستم عامل برای نشون دادن هر فایل، باید اول اون رو توی رم بریزه. حالا هر فایلی که خونده میشه با توجه به یه سری پارامتر قابل کنترل، میتونه بعد از اینکه خونده شد توی رم بمونه تا سری بعد مجددا از دیسک فراخوانی نشه، چون IO بصورت کلی خیلی هزینه و زمان بره. اگر میخواید تاثیر این cache رو ببینید میتونید از کامند زیر یک بار با کش و یک ب

👍3❤‍🔥1

26 Feb 2025, 21:56 UTC956 views5 reactionsread 12 August 2026

سلام. با سید مهدی (@seyedmahdidiary) میخوایم پادکست بزاریم، بخش آخر پادکست سوالاتی که کامنت میکنید رو (تا حد توان و سوادمون) جواب میدیم. بصورت کلی هر سوالی که مربوط به Devops SRE Linux و یا Python میشه رو میتونید بپرسید.

🔥5

17 Jan 2025, 12:22 UTC831 views2 reactionsread 12 August 2026

چرا کوبرنتیز از Etcd استفاده میکنه: آیا واقعا فقط از Etcd استفاده میشه؟ (بخش اول: Kubernetes Distributions) ✍️ نصب و بالا آوردن یک کلاستر کوبر چندتا مشکل داره: 1. منابع مورد نیاز 2. پیچیدگی نصب برای همین تعداد زیادی سولوشن برای حل این دو مشکل به وجود اومدن، دسته ای از این سولوشنا فرایند نصب رو ساده تر میکنن (مثل KubeADM KinD Kubespray) ولی بعضیاشون کلا باینری هایی که مدیریت کلاستر رو به عهده دارن رو تغییر دادن و برای

👍2

15 Jan 2025, 08:54 UTC719 views3 reactionsread 12 August 2026

چرا کوبرنتیز از Etcd استفاده میکنه؟ ✍️ تازگیا برام این سوال ایجاد شد و راجع به این موضوع یک سری تحقیقات انجام دادم، نتایج رو در قالب چند پست تو کانال قراره بگذارم: 1. تا چه حد این جمله درسته؟ آیا واقعا فقط از Etcd استفاده میشه؟ 2. (دقیقا) چرا از دیتابیس های SQL استفاده نکردن؟ 3. (دقیقا) چرا از دیتابیس های KV دیگه استفاده نکردن؟ #Kubernetes #Etcd

👍3

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

Stars beside a post are paid reactions — Telegram Stars, bought with money and spent on that post. They are a different unit from reactions and are never added to them, here or anywhere else on this page.

Citation-graph rank

Citation-graph rank — 1,056,490 of 1,481,217entries 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.

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

“403” (@DevopsNotFound), 174 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/DevopsNotFound.

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.