Orion Techs | اُریون تکز🖤 pinned «RsvAPI — Event Ticketing API بالاخره بعد از چند ماه، فکر کنم وقتش رسیده RsvAPI رو باهاتون به اشتراک بذارم. حدود یک سال پیش، یهویی تصمیم بر این شد که خیلی سریع یه API برای رزرو Event بنویسم. نسخه اول پروژه رو تقریباً توی ۳ روز و با کمک ChatGPT بالا آوردم.…»

Channel
Orion Techs | اُریون تکز🖤
@OrionTechz
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Telegram's recommendations · Cite this entry
240subscribers
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1001728899632 |
|---|---|
| Type | Channel |
| Username | @OrionTechz |
| Description | اینجا اُریونه ، کامیونیتی برای تمام دنبال کنندگان آینده. امیر آقایاری هستم برنامه نویس فول استک و به صورت تخصصی مهندسی بک اند رو جلو میبرم یادگیری ها و تجاربی که کسب میکنم رو براتون میزارم راه ارتباطی: @maqhbul |
| Created | Between 1 December 2021 and 30 April 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 16 August 2026 |
| Last confirmed live | 16 August 2026 |
| Measurements held | 1 |
| On Telegram | t.me/OrionTechz |
Growth
Growth history is still building. We hold one measurement for this entry. A trend needs at least two, taken days apart — so this will fill in on its own rather than being estimated. We do not publish numbers we have not measured.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 16 Aug 2026, 09:01 | 240 | first reading |
Engagement
20 posts held, back to 29 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 1 pageof Telegram’s post history, 20 posts per page.
- ERR · 30 days
- 70.3%
- avg views ÷ 240 subscribers
- Avg views / post
- 169
- 19 posts measured
- Reaction rate
- 8.01%
- reactions ÷ views · ER floor
- Posts in window
- 20
- of 20 held
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 15 August 2026 |
|---|---|
| Posts held | 20 (29 July 2026 – 15 August 2026) |
| Views total | 3,207 |
| Reactions total | 257 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 16 Aug 2026, 09:01 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.
What this channel posts
- Photos
- 288
- Videos
- 106
- Links
- 448
Lifetime counters from Telegram’s own channel header, read 16 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
257 reactions across 19 posts, in 11 distinct kinds. The most used accounts for 30.7% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤🔥 | 79 | 30.7% | |
| ❤ | 66 | 25.7% | |
| 👌 | 65 | 25.3% | |
| 👾 | 18 | 7.00% | |
| 🔥 | 10 | 3.89% | |
| ⚡ | 7 | 2.72% | |
| 👏 | 5 | 1.95% | |
| 👍 | 2 | 0.778% | |
| 👨💻 | 2 | 0.778% | |
| 🗿 | 2 | 0.778% | |
| 😡 | 1 | 0.389% |
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 19 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 257reactions 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 29 July 2026 to 15 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.
Recent posts
RsvAPI — Event Ticketing API بالاخره بعد از چند ماه، فکر کنم وقتش رسیده RsvAPI رو باهاتون به اشتراک بذارم. حدود یک سال پیش، یهویی تصمیم بر این شد که خیلی سریع یه API برای رزرو Event بنویسم. نسخه اول پروژه رو تقریباً توی ۳ روز و با کمک ChatGPT بالا آوردم. ولی اون موقع طبیعتاً دانش و تجربهای که امروز دارم رو نداشتم و صرفا میخواستم یه پروژه اکسپرسی در گیتهابم باشه. دیزاین دیتابیس، معماری، ساختار پروژه و حتی بخش زی…
🔥5👌4❤3❤🔥2👾1
Signed realAmir
ISP دپندنسی های غیر ضروری رو حذف میکنه (چون باعث میشه متد های غیر ضروری رو در کانترکتمون نداشته باشیم و اینترفیسمون کوچک تر باشه) از اونور اگه اینترفیسمون بزرگ تر باشه ابستکرشنمون رو بد میکنه از اونور کوهیژن میگه که چیزایی که به هم مرتبط هستند رو کنار هم بزار ISP هم میگه که اینترفیس رو طوری طراحی کن که کانترکت های مرتبط کنار هم باشند و مصرف کننده چیزای غیر مرتبط را نگیرد پس یه ارتباط مستقیم خفن اینحا داریم تو بحث …
👌6❤🔥4❤1
Signed realAmir
خب خب رسیدیم به اصل چهارم ISP interface segregation principle این اصل دقیقا ادامه lsp هستش که درموردش حرف زدیم و به کوهیژن و کانترکت و اینترفیس و ابسترکشن وصل میشه اصل تفکیک اینترفیس : Clients should not be forced to depend on methods they do not use. هیچ مصرف کننده ای نباید مجبور باشد به متد هایی وابسته شود که به انها نیازی ندارد مثال : interface Worker { work(): void; eat(): void; sleep(): void; } class …
❤8👌5❤🔥2
Signed realAmir
بچهها یه تفاوت مهم npm که خیلیها روش کار نمیکنن: npm i با npm ci فرق داره! ✅ npm i (یا npm install) • برای کار روزمره و توسعه خوبه • انعطافپذیره • ممکنه package-lock.json رو تغییر بده • اگه node_modules باشه، فقط تغییرات رو اعمال میکنه ✅ npm ci مخفف clean install هستش • مخصوص CI/CD و Docker و production ساخته شده • اول node_modules رو کامل پاک میکنه • فقط از روی package-lock.json نصب میکنه (هیچ تغییر…
❤🔥6❤5👌4👾1
Signed realAmir
درود بچه ها یه چنل زدم که هر شب، خلاصه و نکتههایی که از کتابهای مهندسی و معماری نرمافزار و موضوعات مرتبط ، مطالعه میکنم رو باهاتون شیر میکنم امیدوارم به دردتون بخوره https://t.me/OriginalAbouei
❤🔥4👾4
Signed realAmir
درود امروز میخوایم ببینیم Liskov Substitution Principle چطور با مفاهیم پایهای و مهم دیگه درارتباطه LSP و Interface / Contract با تعریف اینترفیس در واقع یک قرارداد رفتاری میسازیم. LSP تضمین میکنه که سابتایپ فقط شکل اینترفیس رو کپی نکنه، بلکه کانترکت اون رو هم کامل رعایت کنه. اگر این قرارداد نقض بشه، کلاینتهایی که به اینترفیس وابستهان خراب میشن. LSP و Abstraction ابسترکشن یعنی جزئیات غیرضروری رو پنهان کنیم و ی…
❤🔥6👌6❤3👾1
Signed realAmir
بعد داکرایز کردن پروژه و نوشتن اینتگرشن تست ها خداییش دیگه خسته شدم و یونیت تست هارو گذاشتم برای بعد و اینکه نمیخواستم این تست هارو به ai بسپرم چون این پروژه یه جورایی مسیر یادگیریه منه و کمترین استفاده از ai روتوش داشته حالا امروز رفتم سراغ ci/cd و گیت هاب اکشنز و اینا و قسمت ci رو تقریبا تا یه حدودایی اوکی کردم CI : Continuos Integration در این روش هر بار که تغییر جدید تو کد ایجاد میشه به طور خودکار میاد فرای…
❤8🔥3👨💻2👾1
Signed realAmir
حاجی سلام امروز رسیدیم به اصل سوم SOLID: LSP — Liskov Substitution Principle اگر B زیرنوع A است، باید بتوانیم B را هرجا که A انتظار میرود جایگزین کنیم، بدون اینکه رفتار مورد انتظار سیستم خراب شود (همون رابطه چایلد و پرنت رو میگه). یه مثال معروف 😂 پرنده -> پرواز میکنه پنگوئن -> پرنده است، ولی پرواز نمیکنه پس اگر Bird را طوری طراحی کنیم که همهی پرندهها مجبور به fly() باشند، قراردادمان از اول اشتباه طراحی شده. به…
❤7👌4❤🔥1👾1
Signed realAmir
به زیبایی نوشته بود که اگه احتمال بردت ۱۰۰ درصده پس فدای سرت که سرعت کمه
❤9❤🔥2👾1
Signed realAmir
بزنید پلی بشه گوش کنید هم انگلیسیتون خوب میشه هم اگه انگلیسیتون خوبه نیاز به خوندن ندارید که حوصلتون سر بره.
❤🔥7❤3👾1
Signed 𝐌𝐀𝐓𝐈O
https://www.geeksforgeeks.org/node-js/node-js-event-loop/
❤🔥9❤2👾1
Signed realAmir
Showing the 12 most recent of 20 posts we hold for @OrionTechz. 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.
Appears in Telegram’s recommendations for other channels
The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.
@Bdan_Sazi · 124,329
Telegram ranks this channel #66 of 91 here — alongside 90 others — read 16 August 2026
This channel appears in 1 seed channel's Telegram-generated recommendation list in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
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 16 August 2026 — this entry's latest reading, not the date you are reading this.
“Orion Techs | اُریون تکز🖤” (@OrionTechz), 240 subscribers as measured 16 August 2026. Telegram Register, tgregister.com/channel/OrionTechz.
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.