Channel
@DevelopixLaravel
On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry
1,553subscribers
-1 since we began measuring on 12 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1001874556095 |
|---|---|
| Type | Channel |
| Username | @DevelopixLaravel |
| Created | Between 1 October 2022 and 30 September 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 12 August 2026 |
| Last confirmed live | 13 August 2026 |
| Measurements held | 2 |
| Confirmed unchanged | 1 time, most recently 13 August 2026 |
| On Telegram | t.me/DevelopixLaravel |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 13 Aug 2026, 11:34 | 1,553 | -1 |
| 12 Aug 2026, 16:31 | 1,554 | first reading |
17 posts held, back to 6 February 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 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 11 August 2026 |
|---|---|
| Posts held | 17 (6 February 2026 – 11 August 2026) |
| Views total | 1,590 |
| Reactions total | 18 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 12 Aug 2026, 16:31 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.
77 reactions across 14 posts, in 4 distinct kinds. The most used accounts for 58.4% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 45 | 58.4% | |
| ❤ | 22 | 28.6% | |
| 🔥 | 6 | 7.79% | |
| 👎 | 4 | 5.19% |
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 15 of the 17 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 77reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 17 most recent posts we hold, published 6 February 2026 to 11 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.
سوال چالشبرانگیز لاراول (خروجی Collection): خروجی اجرای این کد در لاراول چیست؟ جواب را دقیقا همانطور که در خروجی نهایی چاپ میشود بنویسید (شامل ساختار آرایه/JSON). 🔖 #Laravel #PHP #لاراول 👤 Developix 💎 Channel: @DevelopixLaravel
👍3👎1
خروجی این کد Laravel چیست؟ در نظر بگیرید روی یک پروژه Laravel دارید کار میکنید و از Collection برای دستکاری دادهها استفاده کردهاید. در کد زیر از ترکیب pluck، collapse و values استفاده شده است. بهدقت به نوع دادهای که هر مرحله برمیگرداند توجه کنید و بگویید در انتها چه چیزی روی صفحه چاپ میشود. سؤال: خروجی نهایی اجرای این اسکریپت PHP چیست؟ (دقیقاً همان رشتهای که echo چاپ میکند را بنویسید) 🔖 #Laravel #PHP #لا…
👍2
با Migration Boost هاستایران، برای مهاجرت به سرور ابری دوباره هزینه ترافیک نده! 🚀 با خرید اولین سرور ابری غیرساعتی از **هاستایران**، بسته ترافیک هدیه مهاجرت بهصورت خودکار برای سرویس شما فعال میشود: ✅ حداقل ۱۰۰ گیگابایت ترافیک هدیه مهاجرت ✅ افزایش حجم هدیه متناسب با ظرفیت دیسک اولیه ✅ ترافیک آپلود رایگان ✅ بدون محدودیت زمانی سرور ابری هاستایران را راهاندازی کنید و بکاپها، فایلها و پایگاه داده خود را بدون دغ…
❤2
🧩 ورژن 4 فریمورک LaraGram منتشر شد. یکی از مهمترین قابلیتهای LaraGram 4، معرفی پکیج MTProto است؛ پکیجی که با هدف سادهسازی توسعه پروژههای مبتنی بر Telegram MTProto API طراحی شده است. توسعه با MTProto معمولاً با چالشهایی مانند مدیریت Session، احراز هویت، نگهداری اتصال، دریافت Updateها، مدیریت Flood Wait و پیکربندیهای پیچیده همراه است. در LaraGram تلاش شده تمام این پیچیدگیها از مسیر توسعهدهنده حذف شود تا تجرب…
👍10
Repository Pattern در پروژههای لاراول 🧱 یکی از چیزهایی که پروژههای لاراول بزرگ را قابلنگهداریتر میکند، جدا کردن منطق دسترسی به دیتابیس از باقی لایههاست. اینجاست که Repository Pattern خیلی کمک میکند. ایده ساده است: بهجای اینکه کنترلر مستقیم با Model و کوئریها درگیر شود، با یک اینترفیس صحبت میکند. پشت این اینترفیس هر وقت خواستیم میتوانیم Eloquent را عوض کنیم، کش اضافه کنیم یا منبع داده را تغییر بدهیم، ب…
❤8👍3👎1
💠 نسخه جدید فریمورک لاراول (Laravel) منتشر شده است 🔸 ارتقا از نسخه 13.15.0 به 13.16.1 🔹 لیست تغییرات این نسخه: - رفع مشکل ثبتنشدن برخی Dev Commandها - بهبود پایدارسازی رجیستر شدن DevCommands - سایر اصلاحات جزئی مرتبط با DevCommands و غیره 🔖 #laravel, #php, #laravel, #web, #release 💎 @DevelopixLaravel
🔥5
💠 نسخه جدید فریمورک لاراول (Laravel) منتشر شده است 🔸 ارتقا از نسخه 13.14.0 به 13.15.0 💎 @DevelopixLaravel
👍5
پکیج امروز: spatie/laravel-permission برای مدیریت حرفهای نقشها و سطح دسترسی در Laravel 🔐 وقتی پروژه بزرگ میشود، ifهای تودرتو برای role و permission کد را بههم میریزد. این پکیج یک سیستم تمیز RBAC روی Eloquent میآورد و با Gate / Policy کاملاً سازگار است. ویژگیها: • تعریف role و permission داینامیک از دیتابیس 🧩 • attach شدن به User model با relationهای تمیز • middleware آماده مثل role و permission • پشتیبانی…
👍6❤2
تمیز کردن کنترلرهای Laravel با Service Layer 🧼 خیلی وقتها کنترلرهای Laravel کمکم تبدیل میشوند به محل تجمع همهچیز: validation، منطق بیزنسی، queryهای Eloquent، ارسال notification و… این یعنی: • سختی در تست کردن 🧪 • کدهای تکراری در چند کنترلر • سختی در تغییر منطق بیزنسی بدون شکستن endpointها یکی از الگوهای ساده و کاربردی برای حل این مشکل در Laravel، استفاده از Service Layer است. ایده اصلی ✨ هر action در کنترل…
👍4❤3
⚡️ Eager Loading برای جلوگیری از N+1 در لاراول خیلی وقتها کندی عجیب در صفحههایی دیده میشود که لیستها را با روابط Eloquent نمایش میدهند؛ ریشهاش معمولاً مشکل معروف N+1 Query است. خوشبختانه با یک تغییر کوچک در کوئری میشود کلی بهبود گرفت. 🚀 فرض کن هر Post یک User دارد و موقع لیست پستها، نام نویسنده را هم نمایش میدهی. اگر ساده بنویسی: $posts = Post::all(); foreach ($posts as $post) { echo $post->user->nam…
👍4❤2👎1
در کد زیر داخل یک Controller تلاش شده روی مدل User فیلتر اعمال و نتیجه را paginate کند، اما از یک Anti Pattern جدی استفاده شده که میتواند باعث بروز باگ و رفتار غیرمنتظره شود: use App\Models\User; use Illuminate\Support\Facades\DB; class UserController extends Controller { public function index() { $users = User::all(); $users = DB::table('users') ->where('is_active', true) …
در نمونهکد بالا، در حالت اول تمام رکوردها از دیتابیس خوانده میشوند و بعد با استفاده از Collection فیلتر میگردند که باعث افزایش شدید مصرف مموری و کاهش کارایی در جدولهای بزرگ میشود. در حالت دوم با تعریف یک Query Scope، منطق فیلتر مستقیماً روی کوئری SQL اعمال میشود و فقط دادههای لازم از دیتابیس لود میگردند. شما در پروژههای Laravel خود به جای فیلتر کردن روی Collection بعد از get() یا all()، میتوانید با استفاده…
👍1
Showing the 12 most recent of 17 posts we hold for @DevelopixLaravel. 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 — 628,187 of 1,189,255entries 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.
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.
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 13 August 2026 — this entry's latest reading, not the date you are reading this.
“| کانال توسعهدهندگان لاراول |” (@DevelopixLaravel), 1,553 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/DevelopixLaravel.
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.