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 11 September 2026 and assigned it the closest of 31 fixed categories, at 91% 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
16 measurements spanning 51 days, net +4,855. 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 5,945–12,256 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)
Subscribers
Change
25 Sept 2026, 17:57
11,528
+1,709
16 Sept 2026, 20:59
9,819
+352
12 Sept 2026, 14:17
9,467
+149
8 Sept 2026, 17:01
9,318
+803
3 Sept 2026, 18:18
8,515
+194
31 Aug 2026, 05:13
8,321
+138
27 Aug 2026, 21:38
8,183
+139
25 Aug 2026, 01:37
8,044
+307
21 Aug 2026, 08:45
7,737
+192
18 Aug 2026, 11:15
7,545
+185
15 Aug 2026, 16:42
7,360
+264
12 Aug 2026, 14:15
7,096
+294
9 Aug 2026, 13:01
6,802
+101
6 Aug 2026, 16:28
6,701
+28
6 Aug 2026, 03:18
6,673
no change
6 Aug 2026, 01:47
6,673
first reading
Engagement
158 posts held, back to 2 August 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 18 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 158 posts for this entry, the most recent from 28 August 2026. An engagement rate over an empty window would be a number about nothing.
What this channel posts
Video runtime
6m 57s
Average length
1m 44s
Measured directly from 4 videos with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no ≈ mark.
Reaction mix
6,700 reactions across 152 posts, in 27 distinct kinds. The most used accounts for 70.0% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
❤
4,690
70.0%
👍
732
10.9%
🔥
469
7.00%
😁
190
2.84%
👏
167
2.49%
👌
92
1.37%
👎
90
1.34%
🍓
51
0.761%
🤨
47
0.701%
❤🔥
32
0.478%
😎
23
0.343%
🍾
21
0.313%
🎉
18
0.269%
👻
18
0.269%
🤯
13
0.194%
😭
12
0.179%
🌚
8
0.119%
🆒
5
0.075%
👨💻
5
0.075%
😨
5
0.075%
7 further kinds
12
0.179%
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 157 of the 158 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,872 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 158 most recent posts we hold, published 2 August 2026 to 28 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
22
across the posts below
Posts paid on
15
of 157 we hold a reading for · 10%
Most on one post
3
single highest reading
A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @RepoFA. 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 158 most recent posts we hold for this entry, published 2 August 2026 to 28 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.
اگر نمیخواهید سایت بدون VPN باز شود یا هنگام قطع شدن VPN ارتباط ادامه پیدا کند، VPN Guard میتواند کاربردی باشد.
این افزونه Chrome وضعیت اتصال VPN را بررسی میکند و در صورت نبودن اتصال، دسترسی به سایت را مسدود میکند.
https://github.com/Abolfazl-Mohammadi-06/VPN-Guard
@RepoFA
ایستگاه یک اپلیکیشن موبایل برای دیدن شبکه حملونقل عمومی ایران بر روی نقشه است.
ایستگاههای مترو، BRT و اتوبوس را روی یک نقشه ببینید، جستجو کنید، جزئیات هر ایستگاه را بخوانید، زمان رسیدن اتوبوس را ببینید و از موقعیت فعلیتان تا مقصد انتخابشده مسیریابی دریافت کنید.
در حال حاضر برای ۶ شهر (تهران، اصفهان، مشهد، تبریز، کرج، شیراز) توسعه داده شده است.
سورس کد پروژه:
https://github.com/MohsenDastaran/istgah-rn
«ایست…
دیتابیسمنت یه ابزار self-hosted برای مدیریت backup دیتابیسه که یه web UI تمیز داره. باهاش میتونی فرایند schedule، backup و restore رو برای دیتابیسهایی مثل MySQL، PostgreSQL، MariaDB، SQL Server، MongoDB، SQLite و Redis انجام بدی. فایلها رو هم میتونی روی S3، SFTP، Samba یا local storage ذخیره کنی و از SSH Tunnel هم پشتیبانی میکنه.
https://github.com/David-Crty/databasement
@RepoFA
بزرگترین مشکل تست پروژه اینه که معمولاً بعضی سناریوها از یادت میرن؛ همونهایی که بعداً تبدیل به باگ میشن.
برای حل همین مشکل، یه Prompt متنباز منتشر کردم که سورس پروژه رو تحلیل میکنه و بینهایت سناریوی تست فارسی و انگلیسی در قالب ( عمل + انتظار ) با استایل چک لیست داخل یک فایل HTML تولید میکنه. کافیه مرحلهبهمرحله تستها رو اجرا کنی و ببینی آیا نتیجهی مورد انتظار رخ میده یا نه.
https://github.com/sobhanrajabi…
اگر با Jetpack Compose و سرویسهایی مثل Bluetooth کار میکنید، Easify-Android میتونه توسعه رو سادهتر کنه.
این پکیج برای کاهش کدهای تکراری و پیچیدگی سرویسهای اندروید ساخته شده تا پیادهسازی قابلیتهای مختلف سریعتر و سادهتر انجام بشه.
https://github.com/ahbandegan/Easify-Android
@RepoFA
اگه با Claude Code زیاد کار میکنید، احتمالا پیدا کردن و ادامه دادن Sessionهای قبلی براتون دردسره.
ریپو claude-session-log یک Plugin ساده است که Sessionها، زمان شروع و آخرین تغییراتشان را بهصورت خودکار ذخیره میکند تا هر وقت خواستید راحت پیداشان کنید.
https://github.com/aryakvn/claude-session-log
@RepoFA
اگه دنبال یه راه ساده برای مدیریت آرشیو فیلم و سریال روی سیستم هستید، CineVault یه گزینه جالبه.
یک کتابخانه آفلاین برای مدیریت فیلم و سریاله که اطلاعات آرشیو رو بدون نیاز به سرویس آنلاین در اختیارتون قرار میده.
https://github.com/Nokkix/CineVault
@RepoFA
ابزاری پایتونی برای بررسی واقعی پروکسیهای MTProto تلگرام.
برخلاف پورتچکرها، فقط باز بودن پورت را بررسی نمیکند و یک MTProto Handshake واقعی با دیتاسنتر تلگرام انجام میدهد.
https://github.com/Rainman69/MTPCH
@RepoFA
اگر برای کانال یا گروهتون دنبال یه ربات ساده برای انتشار پست هستید، TeleGlass-Bot میتونه گزینه جالبی باشه.
این ربات برای ارسال پست با دکمه های شیشه ای ساخته شده و روی Cloudflare Workers اجرا میشه؛ بنابراین برای راه اندازی به سرور جدا نیاز نداره و برای تعداد کاربر بالا هم بهینه شده.
https://github.com/kingowow/TeleGlass-Bot
@RepoFA
فریمورک Orca؛ جذاب برای زمانی که میخواید چندین ایجنت AI کدنویسی رو به صورت موازی مدیریت کنید. اجازه میده اشتراکهای خودتون رو به ایجنتها وصل کنید و هم رو دسکتاپ هم موبایل روی عملکردشون نظارت داشته باشید.
https://github.com/stablyai/orca
@RepoFA
اگر با چند Agent به صورت همزمان کار میکنید، QM میتونه جالب باشه.
یه هارنس چندنفره برای اجرا و مدیریت Agentهاست که به چند نفر اجازه میده همزمان روی یک تیم از Agentها کار کنن؛ چیزی شبیه VS Code مولتی پلیر، ولی برای Agentها.
https://github.com/yc-software/qm
@RepoFA
یه منتور برنامه نویسی همیشه همراهت
ریپو Dev Mentor Bot یک بات تلگرامی برای یادگیری برنامه نویسیه که هر روز بر اساس زبان، سطح و هدفی که داری برات چالش میسازه.
برنامه رو بفرست، با هوش مصنوعی بررسیش کن و بازخورد بگیر، پیشرفت و استریک روزانهات رو ببین.
یه پروژه جمع و جور ولی کاربردی برای ساخت عادت برنامه نویسی و یادگیری مداوم.
https://github.com/AmirRezaiyan/dev-mentor-bot-ai
@RepoFA
❤31👏4👨💻4😎2
Showing the 12 most recent of 158 posts we hold for @RepoFA. 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
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
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 11 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.
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.
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 25 September 2026 — this
entry's latest reading, not the date you are reading this.
“Persian GitHub” (@RepoFA), 11,528 subscribers as measured 25 September 2026. Telegram Register, tgregister.com/channel/RepoFA.
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.