Channel
@OxinCode
On this record: Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry
7,893subscribers
-17 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
| Telegram ID | -1001314453422 |
|---|---|
| Type | Channel |
| Username | @OxinCode |
| Description | جمعی از فعالان حوزه کامپیوتر و علوم محاسباتی👇 @Oxin_Code . ایران 🇮🇷 | استرالیا 🇦🇺 . ادمین👇 @OxinCode_Admin |
| Created | 20 October 2018 — measured — cross-checked against a third-party dataset (TGDataset) |
| First recorded | 6 August 2026 |
| Last confirmed live | 11 August 2026 |
| Measurements held | 5 |
| Confirmed unchanged | 1 time, most recently 11 August 2026 |
| On Telegram | t.me/OxinCode |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 11 Aug 2026, 23:05 | 7,893 | -9 |
| 9 Aug 2026, 08:12 | 7,902 | -9 |
| 6 Aug 2026, 12:21 | 7,911 | +1 |
| 6 Aug 2026, 07:00 | 7,910 | no change |
| 6 Aug 2026, 06:58 | 7,910 | first reading |
27 posts held, back to 18 July 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 11 pagesof Telegram’s post history, 20 posts per page.
ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.
ER is defined industry-wide as (forwards + reactions + comments) ÷ views— note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate.
| Window | Rolling 30 days · latest post in window 12 August 2026 |
|---|---|
| Posts held | 27 (18 July 2026 – 12 August 2026) |
| Views total | 10,360 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 12 Aug 2026, 17:00 UTC |
Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.
Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.
Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.
Lifetime counters from Telegram’s own channel header, read 12 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.
📱 پیدا کردن و حذف کدهای مرده در iOS و اندروید 🔹 نوشتن کد راحت شده، حذفش هم باید راحت باشه! Reaper یه SDK متنبازه که کدهایی که تو اپلیکیشن شما استفاده نمیشن رو پیدا میکنه. 🔹 با آنالیز زمان اجرا، Reaper نشون میده کدهایی که کاربر هیچوقت بهشون دسترسی نداشته، قابل حذف هستن. 🔹 Android 🔹 IOS #برنامهنویسی #اندروید #IOS ---------- 🆔 @OxinCode
💥 آشنایی با Unosend 🔹 امروز میخوایم با Unosend آشنا شویم، یک API ایمیل که ارسال ایمیلهای تراکنشی و مارکتینگ رو با ۹۹.۹٪ تحویلپذیری فراهم میکنه. 🔹 پنجهزار ایمیل رایگان در ماه 🔹 قیمت شفاف و مقیاسپذیر 🔹 زیرساخت قابل اعتماد مثل Resend و SendGrid 🔹 تجربه توسعهدهنده عالی 🔹 برای شروع نیازی به کارت اعتباری نیست. #مارکتینگ #API ---------- 🆔 @OxinCode
نسل جدید طراحی تجربه کاربری (UX 3.0) فراتر از رابطهای سنتی است. 🔹 این عصر، تعامل بین انسان و هوش مصنوعی را محور قرار میدهد. چهار پایه اصلی UX 3.0 را در زیر ببینید. 🔹 اکوسیستم هوشمند: طراحی تجربه یکپارچه بین دستگاهها و سرویسها. 🔹 همزیستی انسان و ماشین: سیستمها نه تنها پاسخ میدهند، بلکه پیشبینی میکنند و همکاری میکنند. 🔹 تعامل انسانی-هوش مصنوعی: تجربهای شفاف، قابل اعتماد و شخصیسازیشده. 🔹 همآفرینی و هوش را…
📚 معرفی کتابِ Just Use Postgres! 🔹 اگه با PostgreSQL کار میکنید یا قصد دارید استفاده کنید، این کتاب عالیه! 🐘 🔹 مفاهیم پایه تا پیشرفته: کوئریها، تراکنش، ایندکسها، JSON، Full-Text Search و … 🔹 بررسی اکوسیستم PostgreSQL و افزونهها مثل pgvector و PostGIS 🔹 نکات عملی برای بهینهسازی عملکرد و طراحی نرمافزارهای حرفهای 🔹 نویسنده: Denis Magda #کتاب #PostgreSQL ---------- 🆔 @OxinCode
🎯 افکار نهایی برای تبدیل شدن به یک برنامهنویس در سطح ۱٪ برتر ✅ از مسیر لذت ببرید ✅ با ذهنیت امروزی و پیشرفته حرکت کنید ✅ مهارتهای حل مسئله را جدی بگیرید ✅ فرصتها را ببینید و غنیمت بشمارید ✅ کیفیت را به کمیت ترجیح دهید ✅ روی مهارتهای خود سرمایهگذاری کنید ✅ کد دیگران را بخوانید و تحلیل کنید ✅ با دیگر برنامهنویسان همکاری و ارتباط برقرار کنید ✅ از بهترینها یاد بگیرید #برنامهنویسی ---------- 🆔 @OxinCode
شما میدونید Istio چیه؟ یک سرویسمش (Service Mesh) قدرتمند برای مدیریت ترافیک، امنیت، مانیتورینگ و کنترل ارتباطات بین سرویسها در محیطهای Kubernetes 🔹 https://istio.io/latest/docs/overview/quickstart #امنیت #مدیریت_ترافیک ---------- 🆔 @OxinCode
شما میدونید DuckDB چیه؟ 🔹 یک پایگاه دادهی فوقسریع و سبک برای تحلیل داده! 🔹 این پایگاه داده شبیه SQLite هست اما برای کارهای تحلیلی و پردازش دادههای بزرگ استفاده میشه. #پایگاه_داده ---------- 🆔 @OxinCode
آشنایی با کتابخانه ReUI 🔹 یه مجموعه اوپنسورس از کامپوننتهای React با افکتهای انیمیشنی فوقالعاده! 🔹 این مجموعه با React, Typescript, Tailwind CSS, and Motion ساخته شده و کاملاً با shadcn/ui سازگار است. 🔹 https://reui.io/docs/installation #وب #طراحی ---------- 🆔 @OxinCode
🛠 آیا میدانید Forgejo چیست؟ 🔹 یک پلتفرم متنباز و خودمیزبان برای مدیریت مخازن Git که شبیه GitHub عمل میکنه اما کاملاً آزاد، سبک و قابلنصب روی سرور خودتون. 🔹 اخیرا نسخه 13ام Forgejo هم منتشر شده! حتما امتحانش کنید. #گیت #گیتهاب #دانستنیها ---------- 🆔 @OxinCode
منبع درآمد متا #دانستنیها #متا ---------- 🆔 @OxinCode
امروز میخوایم خیلی خلاصه درباره یک نکته مهم در طراحی فرمهای وب حرف بزنیم: تقویمهای انتخاب تاریخ! 🔹 واقعیت اینه که در اکثر مواقع اصلاً نیازی به Date Pickerهای پیچیده نیست. 🔹 استفاده از ورودیهای ساده و بومی مرورگر مثل date و time خیلی سریعتر، قابلاعتمادتر و کاربرپسندتره. 🔹 گاهی حتی بهتره تاریخ رو با چند ورودی جدا (روز/ماه/سال) یا حتی یک ورودی ساده با پیشنهادها وارد کنیم. #وب ---------- 🆔 @OxinCode
منبع درآمد گوگل #دانستنیها #گوگل ---------- 🆔 @OxinCode
Showing the 12 most recent of 27 posts we hold for @OxinCode. 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 — 846,064 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.
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.
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.
“Oxin Code” (@OxinCode), 7,893 subscribers as measured 11 August 2026. Telegram Register, tgregister.com/channel/OxinCode.
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.