Channel
@laravel_it
On this record: Topic · Growth · Engagement · Reactions · Stars · Posts · Citations · Telegram's recommendations · Cite this entry
7,932subscribers
-77 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
| Telegram ID | -1001276220555 |
|---|---|
| Type | Channel |
| Username | @laravel_it |
| Created | Between 1 April 2018 and 31 July 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 29 September 2026 |
| Measurements held | 14 |
| Confirmed unchanged | 1 time, most recently 29 September 2026 |
| On Telegram | t.me/laravel_it |
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 12 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 29 Sept 2026, 08:17 | 7,932 | -15 |
| 19 Sept 2026, 16:20 | 7,947 | -12 |
| 15 Sept 2026, 02:58 | 7,959 | -8 |
| 11 Sept 2026, 02:01 | 7,967 | -4 |
| 6 Sept 2026, 13:37 | 7,971 | -3 |
| 30 Aug 2026, 05:09 | 7,974 | -4 |
| 26 Aug 2026, 19:55 | 7,978 | -10 |
| 23 Aug 2026, 23:59 | 7,988 | -6 |
| 20 Aug 2026, 05:17 | 7,994 | -1 |
| 17 Aug 2026, 11:18 | 7,995 | -12 |
| 13 Aug 2026, 12:46 | 8,007 | +5 |
| 10 Aug 2026, 03:40 | 8,002 | -6 |
| 7 Aug 2026, 07:25 | 8,008 | -1 |
| 6 Aug 2026, 12:15 | 8,009 | first reading |
27 posts held, back to 28 May 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 19 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 27 posts for this entry, the most recent from 24 August 2026. An engagement rate over an empty window would be a number about nothing.
928 reactions across 27 posts, in 1 kind.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 928 | 100.0% |
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 27 of the 27 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 928 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 27 most recent posts we hold, published 28 May 2026 to 24 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.
A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @laravel_it. 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 27 most recent posts we hold for this entry, published 28 May 2026 to 24 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.
Как работают Eloquent-отношения Пошаговое описание того, как Eloquent формирует запросы к связям, загружает и сопоставляет связанные модели, а также позволяет избежать проблемы N+1 запросов. https://christoskoumpis.com/posts/how-eloquent-relationships-work-behind-the-scenes
❤23
SQID в Laravel: практическое руководство по обфускации идентификаторов Подход к коротким публичным ID вместо обычных автоинкрементных, при этом в базе остаются быстрые integer-ключи и связи. В статье показано, как встроить Sqids в route model binding, API Resources и входящие запросы, чтобы не светить внутренние ID и не переходить на громоздкие UUID/ULID. https://spec.tacul.ar/articles/sqids-in-laravel-short-public-i…
❤24
Зачем неофициальный php-клиент к Manticore, если есть официальный Manticore Search — быстрый поисковый движок с полнотекстовым поиском, фасетами и векторным KNN. У него есть официальный клиент, который поддерживает вендор и который идёт в ногу с релизами сервера. Тем не менее я написал свой. Ниже — три конкретные вещи, из-за которых это произошло, и то, чем за них пришлось заплатить. https://laravel.su/p/zacem-neofic…
❤19
Почему e2e тесты это круто, но никто их не пишет. На примере Laravel Dusk Это автоматизированный мануал-тестировщик, как правило, с использованием Selenium-сервера. При запуске теста он открывает браузер и эмулирует действия пользователя - вводит данные в формы, нажимает кнопки, скроллит страницу. https://habr.com/ru/articles/1070340/
❤16
Laravel Rulebook Пакет для организации версионируемых бизнес-правил, которые меняются со временем: тарифов, комиссий, условий доступности, региональных политик и т. п. Он позволяет определить, какое правило должно применяться на конкретную дату, объяснить причину выбора и сохранить snapshot решения для последующего аудита. https://mathiasonea.com/en/insights/versioned-business-rules-in-laravel
❤27
Laravel MPP Пакет позволяет принимать оплату от AI-агентов за доступ к отдельным маршрутам Laravel-приложения через Machine Payments Protocol. Разработчик задаёт цену доступа, а при обращении без оплаты сервер отвечает 402 Payment Required: агент оплачивает запрос через Stripe или Tempo и повторяет его уже с подтверждением платежа https://github.com/square1-io/laravel-mpp
❤18
Значительные улучшения производительности и обновления безопасности для Filament v4.12 и v5.7! https://filamentphp.com/insights/alexandersix-major-performance-improvements-and-security-patches-for-filament-v4-12-and-v5-7
❤23
Что нового в PHP 8.6 https://stitcher.io/blog/new-in-php-86
❤31
https://x.com/taylorotwell/status/2084323143510880591
❤31
Релиз Pest 5 Кратное ускорение тестов с новым движком. https://pestphp.com/docs/pest5-now-available
❤31
Анонсирован Laravel LSP Официальный language server, который индексирует Laravel-проект и добавляет в редактор автодополнение, проверку ошибок и переходы по маршрутам, конфигам, Blade-шаблонам, переводам, Eloquent и другим сущностям фреймворка. Пакет laravel/lsp устанавливается глобально через Composer и работает с любым редактором, поддерживающим LSP, включая VS Code, Cursor, Sublime Text, Zed и Neovim. https://gith…
❤49
Атрибуты PHP: что, почему, как и когда https://wendelladriel.com/blog/php-attributes-what-why-how-and-when
❤16
Showing the 12 most recent of 27 posts we hold for @laravel_it. 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.
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.
Names
Channels on the register whose handles appear in this channel's posts.
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.
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.
This channel appears in 4 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
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 29 September 2026 — this entry's latest reading, not the date you are reading this.
“Laravel World” (@laravel_it), 7,932 subscribers as measured 29 September 2026. Telegram Register, tgregister.com/channel/laravel_it.
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.