Telegram RegisterThe public register of Telegram

Channel

Official Psalm channel

@psalmphp

On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry

65subscribers

+0 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1002514070980
TypeChannel
Username@psalmphp
DescriptionOfficial news channel for Psalm, a PHP static analysis tool for finding errors and security vulnerabilities in PHP applications!
Created22 March 2025measured — dated from the channel’s first post
First recorded10 August 2026
Last confirmed live10 August 2026
Measurements held2
On Telegramt.me/psalmphp

Growth

657 August 2026 — 65 subscribers10 August 2026 — 65 subscribers7 August 202610 August 2026
2 measurements spanning 2 days. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 64–66 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
10 Aug 2026, 02:3265no change
7 Aug 2026, 15:5365first reading

Engagement

11 posts held, back to 22 March 2025the 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.

Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 11 posts for this entry, the most recent from 10 July 2025. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Links
7

Lifetime counters from Telegram’s own channel header, read 10 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

37 reactions across 9 posts, in 4 distinct kinds. The most used accounts for 56.8% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🔥2156.8%
👍821.6%
718.9%
12.70%

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 9 of the 11 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 37reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 11 most recent posts we hold, published 22 March 2025 to 10 July 2025, 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

10 Jul 2025, 14:25 UTC224 views7 reactionsread 10 August 2026
Forwarded from @danog_blog

Also announcing the public beta of Psalm v7! Psalm v7 brings huge performance improvements to security analysis, up to 10x thanks to a full refactoring of both the internal representation of taints, and optimization of the graph resolution logic. A major new feature was also added: combined analysis! Combined analysis, enabled by default in Psalm v7, allows running normal analysis, security analysis and dead code

5🔥2

Signed Daniil Gentili

10 Jul 2025, 13:44 UTC204 views3 reactionsread 10 August 2026
Forwarded from @danog_blog

Psalm is one of the biggest and most powerful PHP Static analysis tools, featuring exclusive features like security analysis, and in Psalm 6.9, an official, hyperoptimized Docker image was introduced. Psalm’s docker image uses a custom build of PHP built from scratch with a custom deepbind patch and the jemalloc allocator, running Psalm +30% faster on average than normal PHP (+50% faster if comparing to PHP without

🔥3

Signed Daniil Gentili

18 May 2025, 14:52 UTC260 views5 reactionsread 10 August 2026

Small overview of the new psalm-review tool I added in Psalm 6.3: https://blog.daniil.it/2025/05/18/psalm-review-tool-in-psalm-6-3/

👍41

Signed Daniil Gentili

11 May 2025, 13:12 UTC191 views7 reactionsread 10 August 2026
Forwarded from @danog_blog

Psalm v6 Deep Dive: Copy-on-Write + dynamic task dispatching Psalm is one of the biggest and most powerful PHP Static analysis tools, featuring exclusive features like security analysis. In Psalm 6.1, I implemented a major refactoring of multithreaded mode (automatically enabled on Linux/Mac OS) based on amphp/parallel, which greatly reduced analysis speeds! But why was it so effective? To understand, one must fir

🔥7

Signed Daniil Gentili

11 May 2025, 12:16 UTC114 viewsread 10 August 2026
Forwarded from @danog_blog

And then, a long overdue post about my Autonomous System (AS198747), and an over more overdue MadelineProto v9 :D

Signed Daniil Gentili

11 May 2025, 12:16 UTC103 views1 reactionsread 10 August 2026
Forwarded from @danog_blog

Happy to announce I've launched a blog, where I'll be posting news about all my different projects, MadelineProto, Psalm, and much more: blog.daniil.it! I now also have a newsletter, feel free to subscribe to receive all the latest news: blog.daniil.it/newsletter ❤️ All posts posted to my blog and newsletter will also be posted here (replacing the old @daniilgentili blog for technical reasons, as I do not have acce

1

Signed Daniil Gentili

11 May 2025, 12:16 UTC108 views1 reactionsread 10 August 2026
Forwarded from @danog_blog

The first series of posts I'll be adding here will be some technical deep dives into the performance improvements I've made in Psalm v6, can't wait to share them all with you!

🔥1

Signed Daniil Gentili

8 Apr 2025, 14:15 UTC267 views9 reactionsread 10 August 2026

Psalm 7.0.0-beta5 is out! This beta release adds a major new feature to Psalm v7: combined analysis! Combined analysis allows running normal analysis, security analysis and dead code analysis all at the same time, within a single run, greatly reducing overall runtimes! Future beta releases will also enable taint analysis by default, given that now it can be run alongside normal analysis.

🔥81

Signed Daniil Gentili

31 Mar 2025, 10:23 UTC292 views3 reactionsread 10 August 2026

Psalm 6.10.0 is out! This is a smaller release, in preparation for some bigger feature releases, both on the v6 and v7 branches. Features: - Added rank to SARIF report - Added forceJit and noCache configuration keys 7.0.0-beta4 was also released from the v7 branch with the same additions.

👍3

Signed Daniil Gentili

28 Mar 2025, 18:20 UTC246 views1 reactionsread 10 August 2026

Welcome to the official channel for Psalm, a PHP static analysis tool for finding errors and security vulnerabilities in PHP applications! This channel will be used to post news regarding Psalm and other projects maintained by Daniil Gentili. Feel free to also join my other channels as well! - @MadelineProto - Official channel for MadelineProto, an async PHP client API for the telegram MTProto protocol - @daniilge

👍1

Signed Daniil Gentili

Showing the 11 most recent of 11 posts we hold for @psalmphp. 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.

Forward network

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.

Mentions

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.

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 10 August 2026 — this entry's latest reading, not the date you are reading this.

“Official Psalm channel” (@psalmphp), 65 subscribers as measured 10 August 2026. Telegram Register, tgregister.com/channel/psalmphp.

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.