Telegram RegisterThe public register of Telegram

Channel

ALL About RSS

@aboutrss

On this record: Growth · Engagement · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry

9,569subscribers

-9 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-1001489753190
TypeChannel
Username@aboutrss
CreatedBetween 1 April 2019 and 31 August 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live13 August 2026
Measurements held3
Confirmed unchanged1 time, most recently 13 August 2026
On Telegramt.me/aboutrss

Growth

9,5699,5789,573.56 August 2026 — 9,578 subscribers6 August 2026 — 9,578 subscribers13 August 2026 — 9,569 subscribers6 August 202613 August 2026
3 measurements spanning 6 days, net -9. 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 9,568–9,579 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
13 Aug 2026, 01:349,569-9
6 Aug 2026, 16:339,578no change
6 Aug 2026, 16:279,578first reading

Engagement

20 posts held, back to 7 April 2025the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 14 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 2 May 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

325 reactions across 20 posts, in 12 distinct kinds. The most used accounts for 36.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍11736.0%
9529.2%
😱309.23%
😭278.31%
🤮257.69%
💩134.00%
🤡103.08%
🔥30.923%
🎉20.615%
👎10.308%
😁10.308%
🤔10.308%

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 20 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 325reactions 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 7 April 2025 to 2 May 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.

Recent posts

2 May 2026, 01:18 UTC≈3,330 views18 reactionsread 12 August 2026
Photo

RSStT Bot 项目招募继任者 RSStT Bot 项目在 GitHub 上获星 2K+,@RSStT_Bot 是 Telegram 上有名的 RSS bot。官方 bot 和自架版我都有在用,一直体验很好。上月,项目开发者开始寻求继任者继续维护该开源项目。希望能有合适人选接力运维。

👍161🔥1

15 Mar 2026, 08:31 UTC≈5,080 views5 reactionsread 12 August 2026
Photo

Dashboard: 无后端需自架的多栏 RSS 订阅器 感谢开发者提交 PR #126,分享了一个无需后端服务器的多栏 RSS 订阅器 Dashboard,纯本地信息存储或可部署于 GitHub Pages: Repository: https://github.com/Rozhovetskyi/Dashboard/ Demo: https://rozhovetskyi.github.io/Dashboard/demo

5

5 Mar 2026, 09:33 UTC≈5,200 views4 reactionsread 12 August 2026
Photo

NebulaPicker: 可自部署的 RSS 生成工具 感谢开发者提交 PR #125,分享了一个可自架的 RSS 生成工具—— NebulaPicker,支持与 Wallabag 集成以实现全文获取: 🐙https://github.com/djsilva99/nebulapicker

4

27 Feb 2026, 02:31 UTC≈5,320 views10 reactionsread 12 August 2026
Photo

Awesome RSSHub Routes 感谢开发者提交 PR #124,分享了 Awesome #RSSHub Routes,包含官网 RSS Feeds 和 RSSHub 的路由,并输出了 #OPML 供一次性导入,且支持及时检测 Feed 可用性。 🔗https://jackyst0.github.io/awesome-rsshub-routes/ 🐙https://github.com/JackyST0/awesome-rsshub-routes/blob/main/readme-zh.md

👍73

23 Feb 2026, 10:01 UTC≈4,970 views2 reactionsread 12 August 2026
Photo

Sponder: 一个 RSS 的中间套件 感谢 PR #123,分享了一款 RSS 中间件工具,支持 #合并 、#过滤 等功能,需付费: https://sponder.app/ 同类工具还包括 feedless \ RSS-lambda \ RSS-Brew 等。

2

2 Jan 2026, 11:04 UTC≈6,590 views17 reactionsread 12 August 2026
Photo

MrRSS: 一个 AI 加持下的多平台 #开源 RSS 阅读器 感谢群友投稿,介绍了一款目前在 GitHub 上 1K+ ⭐️ 的 RSS 阅读器软件: 官网:https://mrrss.ch3nyang.top/ Repo:https://github.com/WCY-dt/MrRSS 「小众软件」的介绍:https://www.appinn.com/mrrss/

16👍1

21 Dec 2025, 08:05 UTC≈6,560 views8 reactionsread 12 August 2026
Photo

ANI-RSS: 基于 RSS 自动追番、订阅、下载、刮削 该项目 #开源,GitHub 上 2K+ ⭐️,支持 Docker/Win/NAS 部署。 网站: https://docs.wushuo.top/ Repo: https://github.com/wushuo894/ani-rss 频道: https://t.me/ani_rss_666

8

13 Oct 2025, 15:00 UTC≈8,540 views63 reactionsread 12 August 2026
Photo

Tiny Tiny RSS 作者将停止维护该项目 项目作者在 #TTRSS 官方论坛发布:The end of tt-rss.org,宣布11月1日终止该项目。目前已有项目贡献者 fork 源码、插件、文档等并转载至 GitHub ,且愿意接棒项目开发和运维: https://github.com/tt-rss/tt-rss 发现于 https://x.com/JeffreyCalm/status/1977632807418745277

😱30😭27👍41😁1

2 Aug 2025, 04:14 UTC≈8,800 views14 reactionsread 12 August 2026
Photo

rssrssrssrss: 一个 feed 合并工具 感谢投稿,向我们推荐了由 Buttondown 开发并 #开源 的一个 RSS feed 合并工具: https://www.rssrssrssrss.com/ 📌#combine-multiple-feeds-into-one

14

15 Jul 2025, 07:31 UTC≈8,110 views10 reactionsread 12 August 2026
Photo

FeedMe: 一款集成 AI 摘要生成的 RSS 阅读工具 项目 #开源,需自部署至 GitHub Pages / Vercel / Docker;已有 500+ ⭐️ Repo: https://github.com/Seanium/feedme Demo: https://feedme.icu/ 发现于 https://t.me/fakeye/1645

6🔥2🤔1🤡1

5 Jul 2025, 02:02 UTC≈7,360 views10 reactionsread 12 August 2026
Photo

ArtFeed: 面向摄影、图像艺术的 RSS 阅读器 该项目 #开源,和 folo 的看图模式一样,也是专为图片型内容 Feed 进行了优化。 https://artfeed.org/ 发现于作者嘟文: https://mamot.fr/@atlza/114614139934160756

10

2 Jul 2025, 12:01 UTC≈6,220 views3 reactionsread 12 August 2026
Photo

RSS Gizmos 作者最近的 3 个 RSS 玩法 RSS Gizmos 是频道介绍过的一个 RSS 工具箱,其作者 Tara Calishain 最近又有新的 RSS 花式用法: 🔸No Kings TV:一个利用 RSS 的当地新闻展示页 根据作者日志,其主要拿该工具追踪美国当地抗议活动、对抗谣言,方法是自选可靠信源,并将文字新闻和视频新闻各用一列展示。 🔸RSStodon:为 #Mastodon 上的标签生成 RSS Feed RSStodon 是作者 Mastodon 工具箱 MastoGizmos 中的一个工具。 🔸The Temporary Obsessions Feed Reader:面向时效信息的 RSS 订阅玩法 Calishain 巧妙利用 Google Sheet 和 Gmail 给 RSS 订阅加了一个定时开关,让基于 RSS 的信息获取仅在设定的日期范围内执行,特别适合追踪一些有时效的事件型

2👍1

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

Citation-graph rank — 482,189 of 1,176,251entries 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.

Forward network

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

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

“ALL About RSS” (@aboutrss), 9,569 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/aboutrss.

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.