Channel
@PHPgx
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
4,727subscribers
-31 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
| Telegram ID | -1002152283102 |
|---|---|
| Type | Channel |
| Username | @PHPgx |
| Created | Between 1 June 2024 and 30 September 2024— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 19 August 2026 |
| Measurements held | 6 |
| Confirmed unchanged | 1 time, most recently 19 August 2026 |
| On Telegram | t.me/PHPgx |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 19 Aug 2026, 21:03 | 4,727 | -5 |
| 16 Aug 2026, 18:54 | 4,732 | -4 |
| 13 Aug 2026, 15:38 | 4,736 | -7 |
| 10 Aug 2026, 21:54 | 4,743 | -12 |
| 7 Aug 2026, 17:22 | 4,755 | -3 |
| 6 Aug 2026, 23:46 | 4,758 | first reading |
20 posts held, back to 15 April 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 9 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 8 August 2026 |
|---|---|
| Posts held | 20 (15 April 2026 – 8 August 2026) |
| Views total | 3,748 |
| Reactions total | 32 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 12 Aug 2026, 06:33 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.
Measured directly from 2 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.
203 reactions across 20 posts, in 6 distinct kinds. The most used accounts for 46.3% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 94 | 46.3% | |
| 👍 | 72 | 35.5% | |
| 🔥 | 33 | 16.3% | |
| 😁 | 2 | 0.985% | |
| 🌚 | 1 | 0.493% | |
| 🤔 | 1 | 0.493% |
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 20 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 203reactions 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 15 April 2026 to 8 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.
Разработчики на Laravel, Image API стал ещё лучше в Laravel 13.24. Теперь доминирующий цвет изображения можно определить с помощью dominantColor(). Также добавлена поддержка HEIC и дополнительных форматов AVIF, что упрощает работу с изображениями с современных устройств. 👉 @PHPgx
❤3
PHP-совет Знали, что дефолтный объект можно создать прямо в параметре конструктора? 👉 @PHPgx
❤6👍4
Совет по PHP Перечисляйте в match() все варианты enum и не добавляйте ветку default. Если позже кто-то добавит новый вариант и забудет обновить match(), PHP выбросит UnhandledMatchError, а не молча пропустит его. Так отсутствующий вариант невозможно будет проигнорировать. 👉 @PHPgx
👍13
Разработчики на Laravel, теперь тесты валидации email:dns больше не должны зависеть от реального DNS. В Laravel 13.22 добавили возможность подменять DNS-запросы во время валидации. Можно точно задать, какие DNS-записи должны возвращаться, и сделать тесты предсказуемыми - без внешних DNS-запросов. 👉 @PHPgx
❤6
В Laravel Cloud появился Secrets Manager 🎉 Теперь можно создавать секреты на уровне организации, подключать их к любому окружению и ротировать централизованно. Для всех окружений, где используются обновлённые секреты, доступен повторный деплой в один клик. Значения шифруются прямо в браузере и после сохранения больше не отображаются. Функция доступна на всех тарифах. Подробнее - в документации → https://cloud.lara…
❤2
PhpStorm 2026.2 уже доступен! В релиз вошло множество обновлений, среди которых: - Постоянные ссылки на файлы с помощью #[FileReference] - Новое окно инструментов Laravel - Улучшения для работы с Git worktree - Встроенный GitHub Copilot Подробности релиза: https://jetbrains.com/phpstorm/whatsnew/ Особенно радует новое окно инструментов Laravel: - общая информация о проекте и быстрый доступ к командам Artisan; - пр…
❤6🔥4
Совет по Laravel Сделайте даты Carbon в приложении неизменяемыми Всего одна строка в AppServiceProvider — и $date->addDay() больше не будет незаметно менять исходный объект, который может использоваться в другом месте. 👉 @PHPgx
👍7❤2
В Laravel 13.19 в хелпер str() добавили метод counted(). Небольшое изменение, но теперь форматировать счётчики в пользовательском интерфейсе стало заметно удобнее и выразительнее. Ещё на одно место меньше, где нужно вручную учитывать единственное и множественное число. 👉 @PHPgx
❤7👍1
Совет по Laravel DB::listen() цепляется за каждый SQL-запрос, который выполняет Laravel, и отдает SQL, биндинги и время выполнения. Достаточно зарегистрировать один listener в service provider, чтобы логировать медленные запросы или разбирать N+1-проблемы по всему приложению 👉 @PHPgx
👍7🔥3❤2
Laravel-совет Знали ли вы, что аксессоры Eloquent могут возвращать небольшие value objects? Пример: вместо того чтобы в каждом Blade-шаблоне, view или сервисе повторять fallback-логику вроде «name или email», можно один раз обернуть связанные колонки и вызывать методы, которые явно отражают намерение. 👉 @PHPgx
👍8❤3🤔1
Нашёл полезный пакет для Laravel! sunchayn/nimbus — встроенный API-клиент для Laravel, работающий прямо в браузере. https://github.com/sunchayn/nimbus Автоматически анализирует ваши маршруты и правила валидации, чтобы генерировать интерактивные схемы запросов и предоставлять нативный интерфейс для тестирования, исследования и отладки API 👉 @PHPgx
❤6
Масштабирование Laravel не обязательно означает переписывание всего приложения. Обычно достаточно найти и устранить узкие места: медленные SQL-запросы, отсутствующие индексы, перегруженные очереди и другие проблемы производительности. В этом руководстве Olamilekan показывает, как подготовить Laravel к работе под высокой нагрузкой в production-среде с помощью Redis, очередей, оптимизации базы данных и инструментов н…
❤5😁2🔥1
Showing the 12 most recent of 20 posts we hold for @PHPgx. 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 — 1,273,040 of 1,584,142entries 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.
Named by 3 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.
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.
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 19 August 2026 — this entry's latest reading, not the date you are reading this.
“PHP Portal | Программирование” (@PHPgx), 4,727 subscribers as measured 19 August 2026. Telegram Register, tgregister.com/channel/PHPgx.
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.