Channel
@phpme
On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry
7,784subscribers
-61 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
| Telegram ID | -1001105620290 |
|---|---|
| Type | Channel |
| Username | @phpme |
| Created | Between 1 February 2017 and 31 May 2019— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 25 August 2026 |
| Measurements held | 9 |
| Confirmed unchanged | 1 time, most recently 25 August 2026 |
| On Telegram | t.me/phpme |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 25 Aug 2026, 13:34 | 7,784 | -8 |
| 22 Aug 2026, 23:17 | 7,792 | -10 |
| 19 Aug 2026, 19:25 | 7,802 | -10 |
| 16 Aug 2026, 14:34 | 7,812 | -11 |
| 12 Aug 2026, 12:03 | 7,823 | -11 |
| 9 Aug 2026, 08:51 | 7,834 | -8 |
| 6 Aug 2026, 15:08 | 7,842 | -3 |
| 6 Aug 2026, 03:05 | 7,845 | no change |
| 6 Aug 2026, 02:12 | 7,845 | first reading |
20 posts held, back to 3 June 2021 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 16 pagesof 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 20 posts for this entry, the most recent from 11 September 2023. An engagement rate over an empty window would be a number about nothing.
505 reactions across 18 posts, in 6 distinct kinds. The most used accounts for 69.3% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 350 | 69.3% | |
| ❤ | 106 | 21.0% | |
| 🔥 | 30 | 5.94% | |
| 😁 | 7 | 1.39% | |
| 👎 | 6 | 1.19% | |
| 👏 | 6 | 1.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 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 505reactions 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 3 June 2021 to 11 September 2023, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
An Internet of PHP PHP is big. The trolls can proclaim its all-but-certain “death” until the cows come home, but no amount of heckling changes that the Internet runs on PHP. The evidence is overwhelming. What follows is a loosely organised collection of precisely that evidence.
❤38👍18🔥12👎4
5 Books You Must Read as a Developer In this article, we present a handpicked selection of five books that every developer should read to enrich their professional journey. These literary gems go beyond mere technical instruction manuals, offering profound insights, practical wisdom, and inspiring stories that can shape and elevate your approach to software development. Whether you’re a seasoned programmer looking …
👍36❤17🔥5😁5
Unveiling the secret power of encapsulation In the world of software development, encapsulation is a fundamental concept that plays a crucial role in building robust, maintainable, and scalable applications. Encapsulation is one of the four pillars of object-oriented programming (OOP), along with inheritance, polymorphism, and abstraction. It provides a mechanism to bundle related data and methods into a single uni…
👍41❤12🔥2
Avoiding the pitfalls of abstract and common services In the ever-evolving world of software engineering, creating robust and maintainable applications is a constant challenge. One common mistake that engineers often make is creating overly common or abstract services. While the idea of reusability and abstraction is appealing, it can lead to a host of problems, including violations of the single responsibility pri…
👍33❤5🔥3
Why we should avoid null in software development In software development, null is a term that is often used to represent a lack of value or an unknown state. It’s a concept that has been around for a long time and has been a source of confusion and bugs in software development. In this article, we will explore why we should avoid null in software development and what we can do instead.
👍29❤9🔥5
Stop using setters In this article, I want to focus your attention on the problem with setters. Let’s talk about the problems:
👍23❤4🔥3👎1
Unit testing tips by examples in PHP In these times, the benefits of writing unit tests are huge. I think that most of the recently started projects contain any unit tests. In enterprise applications with a lot of business logic, unit tests are the most important tests, because they are fast and can us instantly assure that our implementation is correct. However, I often see a problem with good tests in projects, tho…
👍30❤4👏3
Do generators really reduce the memory usage? Recently I noticed some controversy regarding memory usage with generators. It looks like that many people genuinely take generators as a tool that somehow can get them "a big performance boost" when working with large datasets. Sort of a magician's hat, where one can put any amount of data without affecting the PHP process' memory.
👍38❤4👏2😁1
6 Algorithms Every Developer Should Know Hello, I am Richard. I am a developer, and you should know that I’m not a big fan of data structures and algorithms. If you can relate to this, don’t worry; after working on many projects (small and large), I discovered the six important algorithms that every developer should know, and these six will almost always solve every problem in your development process.
👍38❤2👏1
Accessing private properties in PHP Private properties can only be accessed by the class that defines the property… right? Actually, PHP has a few ways to circumvent this: reflection, closures and array casting.
👍21❤1👎1
Starting with Microservices in PHP In this article, we will take theory and apply it in practice using PHP. We will use Ecotone Framework and RabbitMQ, to integrate two Services together.
👍16❤4
Modern PHP data Encryption/Decryption with Sodium extension Throughout the years PHP has added support for several extensions, libraries, and algorithms to encrypt and decrypt data. With several libraries and extensions with various levels of maintenance, several algorithms each potentially carrying pros and cons, some even inherently being insecure, it is very difficult to select the appropriate PHP extension, lib…
👍8❤1
Showing the 12 most recent of 20 posts we hold for @phpme. 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,576,166 of 1,602,822entries 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 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 25 August 2026 — this entry's latest reading, not the date you are reading this.
“Amazing PHP” (@phpme), 7,784 subscribers as measured 25 August 2026. Telegram Register, tgregister.com/channel/phpme.
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.