Telegram RegisterThe public register of Telegram
Telegram profile photo for MadelineProto | Official Channel

Channel

MadelineProto | Official Channel

@MadelineProto

On this record: Topic · Observations · Also posting the same content · Growth · Engagement · What this channel posts · Posts · Citations · Telegram's recommendations · Cite this entry

6,272subscribers

-263 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of 3,162–10,000.

Register entry

Telegram ID-1001115554076
TypeChannel
Username@MadelineProto
DescriptionOfficial MadelineProto channel. Italian Channel: @MadelineProtoIta Group: @pwrtelegramgroup
Created20 March 2017 — measured — cross-checked against a third-party dataset (ext.tg_channel)
First recorded6 August 2026
Last confirmed live4 November 2026
Measurements held25
Confirmed unchanged1 time, most recently 4 November 2026
On Telegramt.me/MadelineProto

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.

Observations

These are measurements, not verdicts. Each one below states something we counted, alongside the evidence it was counted from, so you can check it rather than take it. None of them is graded: every observation this register holds is recorded at severity 0, because the precision of the detectors behind them has not been measured yet, and a rating we cannot support is worse than none. Read each as a fact about the data, not as a judgement about the channel. How we measure.

Content that also appears on other registered channels

Posts published here appear word for word on 1 other registered channel. The matching is on the text itself, not on Telegram’s forward marker, so it finds a copy whether or not it was labelled as one.

Matching posts — open both and compare (1 of the pairs behind the counts below)
Posted firstThenOverlapGap
@danog_blog/4116 Jun 2026, 17:50 UTC@MadelineProto/752 · this entry16 Jun 2026, 17:55 UTC1.005 minutes
Every channel this entry shares post bodies with
ChannelMatching postsText overlapTypical gapPublished first
@danog_blog12 (8/8 hand-verifiable sample passed)1.005 minutesthis entry (8–4)

Text overlap is the Jaccard coefficient over the set of distinct three-word phrases in the two bodies: 1.00 is identical wording, and the threshold for counting a pair at all is 0.70. Candidates are generated by simhash LSH (4 x 16-bit bands, exact Hamming <= 3) verified against the bodies with Jaccard over the SET of distinct 3-word shingles. Published first counts which side of each matching pair carries the earlier timestamp — in this corpus, which is the limitation directly below.

What this cannot establish

MEASURED, DOMINANT ERROR SOURCE: a post ingested before 2026-08-06 may have carried a forward header that was not recorded. A 45-pair hand-check against live t.me pages found 14 (31%) where the live page shows a forward header naming the other channel and the database has none, plus 4 more (9%) naming a third party. The text match itself was wrong 0 times out of 45. Read attribution_capture.items_in_trusted_window before treating the unattributed count as a claim.

Telegram lets a channel forward a post with a header naming the source, and we only began reliably recording that header on 2026-08-06. None of the 1 matches recorded here fall after that date, so for this entry we cannot say whether any of them carried a credit. The duplication is measured; the absence of attribution is not.

“Published first” means first in this corpus. We hold 16 comparable posts for this entry, running 25 June 2025 to 26 July 2026. A channel we have read one page deep will look younger than a neighbour we have read in full, and the order would flip with no change in the underlying facts.

The detector’s own notes on this observation, as it recorded them. Names in this_style are fields of the underlying evidence record, which the plain-English paragraphs above read out for this entry.

  • Verbatim republication has three causes and the text separates only two: a clone/mirror, unattributed copy-paste, or BOTH channels copying a common third source that neither attributes. The spread filter (content held by at most 8 channels) reduces the third and does not remove it.
  • 'Earliest' means earliest IN THIS CORPUS. A channel ingested one page deep will look younger than a neighbour ingested in full; corpus_coverage above is there to be checked before the direction is believed.
  • shared_verified_est extrapolates the sampled pass rate over the full narrow match count; sampled/passed are the numbers actually measured.
  • Absence of a forward header is not proof of intent: Telegram lets a channel disable forward attribution, and a credit written in the body is not parsed as attribution here (mention_edge_either_way above is the closest available signal).

Across the whole group of 2, the earliest publisher we hold is @MadelineProto — which is this entry. That is a statement about our reading window, not a claim of authorship.

Recorded under the key clone_mutual, last confirmed 7 August 2026. An observation that a later pass no longer finds is cleared, and a cleared observation is removed from this page rather than being shown struck through — we do not keep publishing a claim we have withdrawn. Dispute an observation.

Also posting the same content

This channel’s posts match, word for word or near enough, posts on 1 other registered channel, found by comparing text fingerprints across every channel on the register. That matching has been checked by hand against the live Telegram pages and found reliable — 0 wrong of 45 pairs re-read.

Which channel, if either, published first is deliberately not shown. The same hand-check found that reading wrong 18 of 45 times — 60%, no better than a coin flip — because it depends on how deep our own crawl happened to reach into each channel’s history, not on when the content was actually first posted. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Word-for-word 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

6,2656,5426,403.56 August 2026 — 6,535 subscribers6 August 2026 — 6,535 subscribers6 August 2026 — 6,536 subscribers9 August 2026 — 6,542 subscribers12 August 2026 — 6,534 subscribers15 August 2026 — 6,538 subscribers18 August 2026 — 6,536 subscribers21 August 2026 — 6,541 subscribers25 August 2026 — 6,542 subscribers28 August 2026 — 6,527 subscribers31 August 2026 — 6,523 subscribers3 September 2026 — 6,522 subscribers8 September 2026 — 6,513 subscribers13 September 2026 — 6,499 subscribers17 September 2026 — 6,488 subscribers25 September 2026 — 6,481 subscribers5 October 2026 — 6,467 subscribers10 October 2026 — 6,453 subscribers14 October 2026 — 6,444 subscribers17 October 2026 — 6,433 subscribers20 October 2026 — 6,373 subscribers23 October 2026 — 6,311 subscribers26 October 2026 — 6,300 subscribers29 October 2026 — 6,265 subscribers4 November 2026 — 6,272 subscribers6,2726 August 20264 November 2026
25 measurements spanning 91 days, net -263. 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 6,223–6,584 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 25
Measured (UTC)SubscribersChange
4 Nov 2026, 16:266,272+7
29 Oct 2026, 16:596,265-35
26 Oct 2026, 11:586,300-11
23 Oct 2026, 15:566,311-62
20 Oct 2026, 11:196,373-60
17 Oct 2026, 16:316,433-11
14 Oct 2026, 13:006,444-9
10 Oct 2026, 23:016,453-14
5 Oct 2026, 01:176,467-14
25 Sept 2026, 20:596,481-7
17 Sept 2026, 11:006,488-11
13 Sept 2026, 04:216,499-14
8 Sept 2026, 20:216,513-9
3 Sept 2026, 02:546,522-1
31 Aug 2026, 06:556,523-4
28 Aug 2026, 12:126,527-15
25 Aug 2026, 01:326,542+1
21 Aug 2026, 04:066,541+5
18 Aug 2026, 10:046,536-2
15 Aug 2026, 20:386,538first reading

Engagement

39 posts held, back to 25 June 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 13 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
15.6%
avg views ÷ 6,272 subscribers
Avg views / post
980
17 posts measured
Reaction rate
—
this channel exposes no reaction counts
Posts in window
19
of 39 held

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.

What these figures were computed from
WindowRolling 30 days · latest post in window 28 October 2026
Posts held39 (25 June 2025 – 28 October 2026)
Views total16,654
Reactions total—
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken5 Nov 2026, 13:08 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.

What this channel posts

Photos
41
Videos
6
Links
283

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

Video runtime
1m 20s
Average length
40s

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.

Recent posts

Telegram’s own ‘edited’ marker: 4 of 19 posts held from the last 30 days (21.1%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).

28 Oct 2026, 18:20 UTC841 viewsread 5 November 2026

Moved MadelineProto release announcements to @madelineprotophar, to avoid cluttering this channel, which will only be used for the more important feature and bugfix announcements :)

Signed Daniil Gentili

27 Oct 2026, 21:17 UTC≈1,070 viewsread 5 November 2026
Video

Video, posted without a caption

Signed Daniil Gentili

27 Oct 2026, 09:11 UTC942 viewsread 5 November 2026

MadelineProto 8.13.3 https://github.com/danog/MadelineProto/releases/tag/8.13.3 Phar: https://t.me/madelineprotophar/300 What's Changed Fixes • startLive('me'): the live story has our ID as its poster by @danog in https://github.com/danog/MadelineProto/pull/1908 • Stream mode: follow RTMP streams in real time behind the edge, take chunks cut short as they are by @danog in https://github.com/danog/MadelineProto/pull/…

Signed MadelineProto security

21 Oct 2026, 09:27 UTC≈1,290 viewsread 5 November 2026

Btw MadelineProto's PHP docker image is autoupdated and already has a fix for at least some of the recent PHP vulns :))

Signed Daniil Gentili

21 Oct 2026, 08:37 UTC≈1,190 viewsread 5 November 2026
Forwarded from @danog_blogVideo

This pure PHP webradio bot is capable of streaming any YouTube video/livestream to any telegram channel livestream or group call! Use the official magnaluna instance @magicalcrazypony! Or upload the source code to your favorite free PHP webhost to host your own magnaluna (100% PHP webhost support, no ffmpeg/python needed!): https://t.me/MadelineProto/779 Powered by @MadelineProto!

Signed Daniil Gentili

20 Oct 2026, 19:06 UTC≈1,260 viewsread 5 November 2026
File

This webradio bot is capable of streaming any YouTube video/livestream to any telegram channel livestream or group call, with 100% webhost support, no ffmpeg needed! Upload this to your favorite free PHP webhost to host your own magnaluna, or use the official magnaluna instance @magicalcrazypony! Source code: https://GitHub.com/danog/magnaluna Powered by @MadelineProto!

Signed Daniil Gentili

20 Oct 2026, 19:02 UTC957 viewsread 5 November 2026

Try it out now: https://GitHub.com/danog/magnaluna In Telegram: @magicalcrazypony

Signed Daniil Gentili

19 Oct 2026, 20:45 UTC≈1,070 viewsread 5 November 2026

MadelineProto 8.11.1 https://github.com/danog/MadelineProto/releases/tag/8.11.1 Phar: https://t.me/madelineprotophar/283 What's Changed Fixes • Ship the web UI templates and assets in the phar by @danog in https://github.com/danog/MadelineProto/pull/1840

Signed MadelineProto security

19 Oct 2026, 19:39 UTC≈1,020 viewsread 5 November 2026

MadelineProto 8.11.0 https://github.com/danog/MadelineProto/releases/tag/8.11.0 Phar: https://t.me/madelineprotophar/282 What's Changed Features • Autostart the IPC server on Windows by @danog in https://github.com/danog/MadelineProto/pull/1820 • Support fake TLS MTProxy secrets (ee) (#1723) by @danog in https://github.com/danog/MadelineProto/pull/1804 Fixes • Don't block RPC errors on their report, announce our vid…

Signed MadelineProto security

19 Oct 2026, 10:09 UTC675 viewsread 5 November 2026

MadelineProto Layer 231 https://github.com/danog/MadelineProto/releases/tag/8.10.0 What's Changed Layer • Automatic build (layer 231) by @madelineproto-autobuild[bot] in https://github.com/danog/MadelineProto/pull/1809 Features • Web UI v3: liquid glass (includes #1761) by @danog in https://github.com/danog/MadelineProto/pull/1767 • Expose location, live location and venue messages (#1593) by @danog in https://githu…

Signed Daniil Gentili

18 Oct 2026, 16:09 UTC674 viewsread 5 November 2026

• The properties removed since a session was saved are dropped when loading it, instead of being kept forever as dynamic properties (deprecated since PHP 8.2): every private call carried the state of the old libtgvoip engine. Private calls restored as running from those versions are ended. • Copying the authorization to another DC exports it again when the import fails with AUTH_BYTES_INVALID (another process of the …

Signed Daniil Gentili

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

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.

Appears in Telegram’s recommendations for other channels

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.

YukNgaji Official
@yukngajiofficial · 19,823
Telegram ranks this channel #28 of 50 here — alongside 49 others — read 28 September 2026
BotNews
@BotNews · 132,834
Telegram ranks this channel #47 of 65 here — alongside 64 others — read 20 August 2026

This channel appears in 2 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.

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

“MadelineProto | Official Channel” (@MadelineProto), 6,272 subscribers as measured 4 November 2026. Telegram Register, tgregister.com/channel/MadelineProto.

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.