3 measurements spanning 8 days, net -3. 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 775–778 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)
Subscribers
Change
14 Aug 2026, 20:53
775
-2
7 Aug 2026, 13:20
777
-1
6 Aug 2026, 16:35
778
first reading
Engagement
16 posts held, back to 28 January 2024 — 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 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 16 posts for this entry, the most recent from 21 April 2026. An engagement rate over an empty window would be a number about nothing.
Reaction mix
218 reactions across 16 posts, in 20 distinct kinds. The most used accounts for 41.7% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
❤
91
41.7%
👏
31
14.2%
👍
30
13.8%
😢
26
11.9%
😨
8
3.67%
🥰
7
3.21%
🫡
7
3.21%
🔥
3
1.38%
😇
2
0.917%
😭
2
0.917%
🙏
2
0.917%
🎉
1
0.459%
👎
1
0.459%
💔
1
0.459%
💯
1
0.459%
🕊
1
0.459%
🖕
1
0.459%
🙈
1
0.459%
🤬
1
0.459%
🦄
1
0.459%
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 16 of the 16 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 218reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 16 most recent posts we hold, published 28 January 2024 to 21 April 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.
Call for New Maintainers
As the years passed by, my passion for this project faded. I now focus on Linux kernel development and don't have the time or energy to continue maintaining this project.
RSStT is always precious to me as it is to its users, so it's time to turn over a new leaf.
I am looking for new maintainers to continue maintaining RSStT so that it can finally be a community-driven project. Reply to the…
You may have noticed that @RSStT_Bot was deleted by Telegram last week. After appealing, @RSStT_Bot was recovered several hours ago (thanks for the help from Telegram Support Team). It is partially functioning again, with update pushing temporarily disabled. You won't receive any messages for feed updates, but you can still send commands to it. It is scheduled to reenable update pushing after 9 hours. You can now use…
#Release v2.10.0: Container health check, chat-specific #hashtags, and more
Highlights
● Container health check: The official Docker image includes an automatic health check to determine if the container is running properly. The health check status can be checked in docker ps. This feature, combined with autoheal or some other monitoring tool, can restart the container automatically when it is unhealthy.
● Support f…
#Release v2.9.0: Telegraph-related revert, skip cert verification, and more
BREAKING CHANGES
Media (image and video) are no longer uploaded when generating Telegraph posts due to Telegraph disabling media upload. (first introduced in v2.6.0)
Addition
● Disable TLS certificate verification: The environment variable VERIFY_TLS has been added to disable (when set to 0) or enable (when set to 1, default) TLS certificat…
Which subscription-topic relation satisfies your typical use case? (If more than one option satisfies your typical use case, choose the one with the smallest number)
哪种订阅-主题关系满足您的典型用例？(如果多于一个选项满足您的典型用例，选择数字最小的一个)
[1]78%
[2]10%
[3]12%
Shares as published. No per-option vote count is published by Telegram, so none is shown.
（简体中文翻译在下一条消息）
I am adding topic group support to RSStT and would like to know which subscription-topic relation satisfies your typical use case.
[1]
⭕️ Easy to implement.
⭕️ Migrating subscriptions among topics is straightforward.
❌ Unable to copy subscriptions among topics.
❌ Unable to subscribe to the same feed in different topics.
❌ Unable to subscribe to the same feed in the same topic.
[2]
⭕️ Easy to implemen…
#Release v2.8.0: Retain post order, rewritten monitor, and more
Highlights
● Retain post order: Retain the order of posts in a feed when sending them. Previously, all new posts were sent simultaneously, losing their order within the feed. Note: Posts from different feeds are still sent simultaneously, so it is expected to see them interlaced.
● Rewritten monitor: The feed monitor has been rewritten for flexibility a…
#Release v2.7.0: #Hashtags from post, Python 3.12 support, and more
BREAKING CHANGES
● Migrate to aerich 0.7.2: A breaking change introduced in aerich (a dependency of RSStT) 0.7.x has prevented RSStT from upgrading it for a long time. A lot of effort has been made, so the migration is expected to be seamless and shouldn't break anything. However, it is encouraged to make a database backup before upgrading RSStT. If…
Showing the 12 most recent of 16 posts we hold for @RSStT_Channel. 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.
Polls
The poll we hold for this entry, as Telegram rendered it when we read the post. A poll’s figures keep moving after that, so each one is dated.
Which subscription-topic relation satisfies your typical use case? (If more than one option satisfies your typical use case, choose the one with the smallest number)
哪种订阅-主题关系满足您的典型用例？(如果多于一个选项满足您的典型用例，选择数字最小的一个)
[1]78%
[2]10%
[3]12%
Shares as published. No per-option vote count is published by Telegram, so none is shown.
Percentages only — there are no per-option vote counts here, because Telegram publishes none.The public post preview gives each option’s share and a single voter total, and nothing else. Multiplying one by the other would produce a per-option tally that looks measured and is not: the shares are rounded to whole numbers before we ever see them. We print what was published and leave the column that does not exist empty.
The shares need not add up to 100.Rounding alone puts many polls at 99 or 101. A poll that allows more than one answer per voter runs well past 100 by design, and several here do. The bars are drawn against a fixed 100% track at each option’s own percentage rather than normalised to the total, so a poll that exceeds it shows that it does instead of being quietly rescaled.
Read from the 16 most recent posts we hold, published 28 January 2024 to 21 April 2026. Telegram labels each poll by kind — an anonymous poll, a quiz, a closed set of final results — and that label is reproduced rather than paraphrased.
Citation-graph rank
Citation-graph rank — 583,167 of 1,549,376entries 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.
Mentions
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.
Handles this channel named that no longer answer
Dead references
1
handles named in this channel’s posts, vacant today
Evidenced gone
0
we ourselves saw one of these resolve, at some point
Never seen alive
1
vacant every time we have ever looked
@RSStT_Channel named 1 handle that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all.A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
Never seen alive
References a handle that is not a live channel — we have no record it ever was one.
@maooyer named in 1 post, 8 August 2026 – 8 August 2026
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 14 August 2026 — this
entry's latest reading, not the date you are reading this.
“RSStT Bot Channel” (@RSStT_Channel), 775 subscribers as measured 14 August 2026. Telegram Register, tgregister.com/channel/RSStT_Channel.
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.
