Telegram RegisterThe public register of Telegram
Telegram profile photo for Daniil Gentili

Channel

Daniil Gentili

@danog_blog

On this record: Topic · Channels linked by matching posts · Growth · Engagement · Reactions · Stars · Posts · Citations · Cite this entry

413subscribers

+6 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1002528672534
TypeChannel
Username@danog_blog
CreatedBetween 1 March 2025 and 31 July 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live12 November 2026
Measurements held13
Confirmed unchanged1 time, most recently 12 November 2026
On Telegramt.me/danog_blog

Topic

Technology — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-UD-Q6_K_XL, prompt version 1) read this channel’s own recent posts on 11 August 2026 and assigned it the closest of 31 fixed categories, at 99% 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 the other topics.

Channels linked by matching posts

This channel is in a group of 2 registered channels linked by matching posts. Links are found by comparing text fingerprints across every channel on the register.

Which channel, if either, published first is deliberately not shown in this list. “First” could only mean first in our own crawl, which depends on how deep we happened to reach into each channel’s history, not on when the content was actually first posted. Our one hand-check read 45 of the highest-confidence flagged pairs against the live Telegram pages. In 18 of them the live page showed a “Forwarded from” credit that our database had no record of, so reading that pair as an unattributed copy was wrong; the check did not measure who published first. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Near-verbatim matching has several ordinary explanations besides copying — a channel mirroring itself, an unattributed repost, or two channels independently repeating the same wire story — and this measurement cannot tell those apart. How this is measured.

Growth

4044384216 August 2026 — 407 subscribers6 August 2026 — 407 subscribers14 August 2026 — 404 subscribers21 August 2026 — 413 subscribers28 August 2026 — 419 subscribers5 September 2026 — 425 subscribers13 September 2026 — 429 subscribers1 October 2026 — 437 subscribers12 October 2026 — 438 subscribers20 October 2026 — 423 subscribers26 October 2026 — 420 subscribers3 November 2026 — 415 subscribers12 November 2026 — 413 subscribers4136 August 202612 November 2026
13 measurements spanning 98 days, net +6. 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 399–443 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
12 Nov 2026, 13:14413-2
3 Nov 2026, 11:55415-5
26 Oct 2026, 21:28420-3
20 Oct 2026, 03:47423-15
12 Oct 2026, 14:07438+1
1 Oct 2026, 09:19437+8
13 Sept 2026, 03:19429+4
5 Sept 2026, 20:59425+6
28 Aug 2026, 12:23419+6
21 Aug 2026, 00:28413+9
14 Aug 2026, 04:56404-3
6 Aug 2026, 19:33407no change
6 Aug 2026, 03:20407first reading

Engagement

20 posts held, back to 2 August 2025 — 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 page 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 20 posts for this entry, the most recent from 26 July 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

157 reactions across 18 posts, in 13 distinct kinds. The most used accounts for 42.7% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤6742.7%
🔥3421.7%
👍2214.0%
🫡117.01%
🎉85.10%
💋42.55%
🕊31.91%
👌21.27%
🤗21.27%
💩10.637%
💯10.637%
🙏10.637%
🤡10.637%

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 157 reactions 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 2 August 2025 to 26 July 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.

Telegram Stars

Stars received
52
across the posts below
Posts paid on
2
of 20 we hold a reading for · 10%
Most on one post
50
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @danog_blog. 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 20 most recent posts we hold for this entry, published 2 August 2025 to 26 July 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.

Recent posts

26 Jul 2026, 21:05 UTC166 views11 reactionsread 6 August 2026
Forwarded from @MadelineProto

Native, pure-PHP (no FFI, no shell, 💯 webhost support) group and video calls are working and coming in the next MadelineProto version!

🔥10💯1

16 Jun 2026, 17:54 UTC≈4,010 views2 reactionsread 6 August 2026

MadelineProto may also be affected if your upstreams aren't filtering invalid routes via RPKI, i.e. if connection fails and https://rpkitest.nlnetlabs.net/ isn't passing for you, ask your upstreams to enable RPKI validation :)

👍2

16 Jun 2026, 17:51 UTC≈3,990 views2 reactionsread 6 August 2026

Indeed, looking at the announced routes i.e. in https://bgp.he.net/AS18101#_prefixes + https://bgp.he.net/AS18101#_prefixes6, they're hijacking both v4 and v6 prefixes

👍2

16 Jun 2026, 17:50 UTC525 views1 reactionsread 6 August 2026

⚠️ Indian telecom Reliance is sabotaging access to Telegram for millions of users OUTSIDE India (including the UAE) via a rogue method called BGP hijacking. 🧨 The sabotage seems intentional, as Reliance has ignored multiple reports. 😞 This may be part of a competitive war, as Reliance is partially owned by Meta — the company behind WhatsApp. 🌐 Network operators are advised to reject unauthorized BGP announcements …

👍1

14 Mar 2026, 20:16 UTC≈1,620 views28 reactionsread 6 August 2026

The RFC was published! https://externals.io/message/130313

❤11🎉8🔥4🫡3🕊2

12 Mar 2026, 22:16 UTC≈1,530 views10 reactionsread 6 August 2026

Btw, I'm now part of the True Async committee! I decided to not present the RFC as linked to true async, to explicitly prevent an interpretation where it is something that will allow us to "sneak in" True Async into PHP. True Async is one of, but not the only nor the main reason why I created this RFC. I truly believe that PHP could really benefit from a more agile RFC process, that can transform it from just a de…

🔥7🫡2🕊1

12 Mar 2026, 22:08 UTC994 views7 reactionsread 6 August 2026

Previewing my upcoming php-community RFC: https://github.com/danog/php-community-rfc Feel free to submit feedback in the comments, it will be posted to the PHP internals mailing list either this weekend or next week.

🔥4🫡3

1 Mar 2026, 13:19 UTC709 views3 reactionsread 6 August 2026
Forwarded from @MadelineProto

MadelineProto was updated (8.6.3)! Features: - Update to layer 222 (the server is currently returning unreleased Message constructors for layer 223 and above, so delaying those for now) Fixes: - DC fix New Methods: - messages.getEmojiGameInfo - messages.summarizeText - channels.getFutureCreatorAfterLeave - payments.getCraftStarGifts - payments.craftStarGift Changed Methods: - Added share_phone_number param to mes…

❤1👍1🙏1

31 Dec 2025, 23:04 UTC≈10,300 views22 reactionsread 6 August 2026

Happy new year, let this be a year of peace and joy!

❤18👍4

25 Dec 2025, 11:07 UTC≈11,000 views25 reactionsread 6 August 2026

Merry Christmas everyone! 🎄🎉❤️

❤20🔥3🤗2

25 Nov 2025, 13:07 UTC≈14,100 views11 reactionsread 6 August 2026

Let's fight for the future of async PHP, upvote my take on the PHP Async proposal: https://github.com/true-async/php-true-async-rfc/discussions/8#discussioncomment-15074303

👍5🫡3👌2❤1

16 Nov 2025, 20:22 UTC≈1,620 views5 reactionsread 6 August 2026
Forwarded from @MadelineProto

Changed Constructors: - Added note param to inputPhoneContact - Added bot_forum_view param to user - Added schedule_repeat_period param to message - Added days param to messageActionGiftPremium - Removed months param from messageActionGiftPremium - Added title_missing param to messageActionTopicCreate - Added days param to messageActionGiftCode - Removed months param from messageActionGiftCode - Added auction_acquire…

❤2👍2💩1

Showing the 12 most recent of 20 posts we hold for @danog_blog. 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

Named by 4 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.

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.

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

“Daniil Gentili” (@danog_blog), 413 subscribers as measured 12 November 2026. Telegram Register, tgregister.com/channel/danog_blog.

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.