Telegram RegisterThe public register of Telegram
Telegram profile photo for کاپیتان کد | برنامه‌نویسی و هوش مصنوعی

Channel

کاپیتان کد | برنامه‌نویسی و هوش مصنوعی

@captaincode_tech

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

248subscribers

+103 since we began measuring on 8 August 2026

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

Register entry

Telegram ID-1004363029169
TypeChannel
Username@captaincode_tech
CreatedBetween 1 June 2026 and 31 July 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live15 September 2026
Measurements held7
Confirmed unchanged1 time, most recently 15 September 2026
On Telegramt.me/captaincode_tech

Topic

Technology — 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 23 September 2026 and assigned it the closest of 31 fixed categories, at 100% 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.

Growth

1382481938 August 2026 — 145 subscribers8 August 2026 — 145 subscribers16 August 2026 — 143 subscribers22 August 2026 — 142 subscribers30 August 2026 — 138 subscribers8 September 2026 — 207 subscribers15 September 2026 — 248 subscribers8 August 202615 September 2026
7 measurements spanning 39 days, net +103. 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 122–265 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
15 Sept 2026, 19:40248+41
8 Sept 2026, 01:17207+69
30 Aug 2026, 07:47138-4
22 Aug 2026, 15:57142-1
16 Aug 2026, 07:44143-2
8 Aug 2026, 21:16145no change
8 Aug 2026, 03:46145first reading

Engagement

20 posts held, back to 31 July 2026the 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 8 August 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

184 reactions across 20 posts, in 8 distinct kinds. The most used accounts for 55.4% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
10255.4%
👍3016.3%
🔥2413.0%
❤‍🔥168.70%
💯52.72%
💔42.17%
🆒21.09%
😢10.543%

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 20 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 184 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 31 July 2026 to 8 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.

Telegram Stars

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

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @captaincode_tech. 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 31 July 2026 to 8 August 2026. 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

8 Aug 2026, 20:14 UTC21 views5 reactionsread 8 August 2026

اینترنتِ ایران باید به لیستِ شکنجه‌های تاریخ بشریت اضافه بشه. Channel: @captaincode_tech

💔4😢1

8 Aug 2026, 16:38 UTC41 views7 reactionsread 8 August 2026
Photo

🧠 جایگزین دستوری و فوق‌العاده برای man در لینوکس! ⚡️ همه می‌دونیم راهنمای خود لینوکس یعنی دستور man خیلی خشک و طولانی توضیح میده و آدم وسط اون همه متن گیج میشه. ابزار tldr دقیقاً همون چیزیه که نیاز داری. به جای توضیحات اضافه، فقط چند تا مثال واقعی و پرکاربرد از هر دستور رو بهت میده: tldr tar کافیه با مدیریت پکیج سیستم‌عاملت مثل sudo apt install tldr نصبش کنی تا سرعت کارت موقع دستور زدن چند برابر بشه! 🚀 #لینوکس #ترم

7

8 Aug 2026, 06:52 UTC37 views7 reactionsread 8 August 2026
Photo

🔥 یه ترفند ریز ولی روانی‌کننده تو ترمینال! ⚡️ وقتی داری تو ترمینال (Terminal) یه دستور طولانی می‌زنی و وسطش یادت میفته باید یه فولدر بسازی یا یه کار دیگه بکنی، لازم نیست کلشو پاک کنی! کافیه دکمه Ctrl + U رو بزنی تا کل خط پاک بشه و بره تو حافظه. کارتو که انجام دادی، با Ctrl + Y دوباره همون دستور طولانی رو می‌چسبونی (Paste) سر جاش! 🎯 💡 با همین دو تا شورت‌کات ساده، دیگه هیچ‌وقت دستورهای طولانی که تایپ کردی رو از دست

🔥5❤‍🔥2

7 Aug 2026, 09:27 UTC47 views8 reactionsread 8 August 2026
Photo

🔋 باتری گوشیت زود خالی می‌شه؟ قبل از روشن‌کردن Battery Saver، مقصر رو پیدا کن! برو به: ⚙️ تنظیمات 👈 باتری 👈 مصرف باتری اگر اپی که زیاد استفاده نمی‌کنی بالای لیست بود: 1️⃣ فعالیت پس‌زمینه‌ش رو محدود کن 2️⃣ اعلان‌های اضافیش رو ببند 3️⃣ دسترسی موقعیت مکانی رو روی فقط هنگام استفاده بذار لازم نیست کل گوشی رو محدود کنی؛ معمولا یک یا دو اپ دارن یواشکی شارژ می‌خورن 😅 #باتری #موبایل #ترفند Channel: @captaincode_tech

7🔥1

6 Aug 2026, 15:06 UTC82 views11 reactionsread 8 August 2026
Photo

🖥☑️ DevLosso ☑️🖥 جایی برای عاشقان کدنویسی، توسعه و خلاقیت دیجیتال! 🚀 آموزش و ترفندهای برنامه‌نویسی (Python، JS و...) 🛠️ معرفی ابزارها و فریم‌ورک‌های کاربردی 📂 پروژه‌های متن‌باز و اسکریپت‌های آماده 🎯 نکات حرفه‌ای برای توسعه نرم‌افزار و امنیت 🔥 اگر دنبال رشد مهارت‌هات در دنیای کدنویسی هستی، همین الان به DevLosso بپیوند! 📌 کدنویسی، خلاقیت، آینده — همه در یک جا! 🚀 @DevLosso

8🔥3

6 Aug 2026, 15:06 UTC91 views7 reactionsread 8 August 2026
Photo

🔎 گوگل رو این‌طوری سرچ کن تا واقعاً به کارت بیاد: 📄 دنبال یک فایل PDF هستی؟ filetype:pdf 🌐 فقط داخل یک سایت خاص می‌خوای بگردی؟ site:example.com 🔍 یک عبارت دقیق رو می‌خوای پیدا کنی؟ بذار داخل گیومه: "عبارت دقیق" 🚫 از یک کلمه خسته شدی و نمی‌خوای توی نتایج ببینیش؟ قبلش خط تیره بذار: -کلمه مثلاً: site:youtube.com آموزش فتوشاپ filetype:pdf همین چندتا ترفند، سرچ‌کردنت رو از «گشتن الکی» تبدیل می‌کنه به پیدا کردن دقیق

7

6 Aug 2026, 09:52 UTC67 views9 reactions1 Starread 8 August 2026

😵‍💫 هنوز برای هر آپدیت سایت، دستی فایل می‌ریزی روی هاست؟ با GitHub Actions فقط کدت رو "push" می‌کنی و دیپلوی خودش انجام می‌شه. 🚀 توی مقاله جدیدم، کامل و مرحله‌به‌مرحله توضیح دادم چطور راهش بندازی: https://captaincode.tech/blog/github-actions-automated-deployment

9

5 Aug 2026, 14:47 UTC79 views11 reactionsread 8 August 2026
Photo

😩 یه تب مهم رو اشتباهی بستی؟ لازم نیست بری توی History دنبالش بگردی؛ فقط این میانبر رو بزن: Ctrl + Shift + T آخرین تب بسته‌شده برمی‌گرده. اگه چند بار بزنی، تب‌های قبلی هم یکی‌یکی باز می‌شن. 😄 روی مک: Command + Shift + T #ترفند #مرورگر #کامپیوتر Channel: @captaincode_tech Twitter

❤‍🔥83

5 Aug 2026, 10:03 UTC70 views10 reactionsread 8 August 2026
Photo

📱 قبل از اینکه گوشی‌تو بدی دست کسی، این یک کار رو انجام بده: «حالت تعمیر» یا Maintenance Mode رو فعال کن. توی خیلی از گوشی‌های جدید، تعمیرکار فقط به بخش‌های لازم برای تست دسترسی داره و عکس‌ها، چت‌ها و فایل‌هات دیده نمی‌شن. اگه گوشیت این گزینه رو نداره، حداقل قبلش از اطلاعاتت بکاپ بگیر و قفل صفحه رو موقتاً عوض کن. #موبایل #حریم_خصوصی #ترفند Channel: @captaincode_tech

9🆒1

4 Aug 2026, 14:02 UTC98 views8 reactionsread 8 August 2026
Photo

🚀 سایتت موقع اسکرول لگ می‌زنه؟ برای بخش‌های طولانی صفحه، این خط CSS رو امتحان کن: .section { content-visibility: auto; contain-intrinsic-size: 500px; } مرورگر محتوایی که هنوز دیده نشده رو دیرتر رندر می‌کنه؛ نتیجه؟ 🔹 رندر اولیه سریع‌تر 🔹 مصرف کمتر منابع 🔹 اسکرول روان‌تر در صفحات طولانی گاهی برای افزایش سرعت، لازم نیست سراغ کد پیچیده بری؛ یک CSS درست کافی است. #CSS #Frontend #بهینه_سازی Channel: @captaincode

8

4 Aug 2026, 06:03 UTC75 views12 reactionsread 8 August 2026
Photo

📱 گوشیت کند شده؟ اول نرو سراغ نصب اپ‌های Clean و Booster. بیشترشون پر از تبلیغن و بعضی‌هاشون حتی گوشی رو کندتر می‌کنن. یه سر به برنامه‌ها بزن؛ هر چیزی رو که مدت‌هاست باز نکردی پاک کن. بعد هم یک‌بار گوشی رو خاموش روشن کن. خیلی وقتا مشکل همین‌جا حل می‌شه. #موبایل #تکنولوژی Channel: @captaincode_tech

8❤‍🔥2👍2

3 Aug 2026, 15:29 UTC73 views10 reactionsread 8 August 2026
Photo

🤖 جواب هوش مصنوعی همیشه درست نیست! گاهی خیلی مطمئن جواب می‌ده، اما ممکنه اشتباه باشه. ✅ منبع بخواه ✅ اطلاعات مهم رو بررسی کن ✅ برای مسائل مالی و پزشکی بدون بررسی تصمیم نگیر هوش مصنوعی دستیار خوبیه، نه جایگزین فکرکردن. 🔍 #هوش_مصنوعی #تکنولوژی #امنیت Channel: @captaincode_tech

10

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

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

Named by 2 registered channels — 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.

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

“کاپیتان کد | برنامه‌نویسی و هوش مصنوعی” (@captaincode_tech), 248 subscribers as measured 15 September 2026. Telegram Register, tgregister.com/channel/captaincode_tech.

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.