一周后 XSLT 退场 Chrome 将在11月17日于其稳定版移除对 XSLT 的支持。这代表着频道收集过的 RSS Feed 美化工具将受牵连。其中,RSS.Style 已重写成 JavaScript。Chrome 帖子的 RSS 与 Atom 那一节 给出的替代方案是:首先,建议还是用 RSS Feed 发现工具查找 <link rel="alternate" type="application/rss+xml">, 其次是调用 XSLT polyfill。 🔗 Chrome 的移除说明 💬 HN 讨论贴 📌 #XSLT

Channel
ALL About RSS
@aboutrss
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Posts edited after publishing · Citations · Handles named that no longer answer · Cite this entry
9,465subscribers
-113 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 |
|---|---|
| Type | Channel |
| Username | @aboutrss |
| Description | 关于 #RSS 技术的 #应用 #周边 #介绍 #方法 #教程 #指南 #讨论 #观点 #技巧 RSS = Really Simple Syndication / Rich Site Summary 推特:https://twitter.com/aboutrss 频道 RSS Feed:https://feeds.feedburner.com/ALLAboutRSS 频道 bot:@channelmcbot 群组:@allaboutrss (福利:推特账号的 Retweet 会自动发至群组) |
| Created | Between 1 April 2019 and 30 September 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 8 November 2026 |
| Measurements held | 24 |
| Confirmed unchanged | 1 time, most recently 8 November 2026 |
| On Telegram | t.me/aboutrss |
Topic
Technology — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 11 September 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.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 8 Nov 2026, 21:06 | 9,465 | -10 |
| 5 Nov 2026, 07:49 | 9,475 | +1 |
| 2 Nov 2026, 16:37 | 9,474 | -2 |
| 31 Oct 2026, 02:20 | 9,476 | -4 |
| 28 Oct 2026, 08:36 | 9,480 | -7 |
| 24 Oct 2026, 23:27 | 9,487 | -9 |
| 21 Oct 2026, 22:31 | 9,496 | -5 |
| 18 Oct 2026, 14:36 | 9,501 | -13 |
| 15 Oct 2026, 07:08 | 9,514 | +1 |
| 12 Oct 2026, 14:26 | 9,513 | -2 |
| 6 Oct 2026, 02:19 | 9,515 | -7 |
| 29 Sept 2026, 07:00 | 9,522 | -4 |
| 19 Sept 2026, 16:41 | 9,526 | +2 |
| 15 Sept 2026, 02:18 | 9,524 | +2 |
| 11 Sept 2026, 21:20 | 9,522 | +3 |
| 7 Sept 2026, 18:59 | 9,519 | -1 |
| 2 Sept 2026, 09:03 | 9,520 | -8 |
| 30 Aug 2026, 02:45 | 9,528 | -1 |
| 26 Aug 2026, 17:13 | 9,529 | -14 |
| 20 Aug 2026, 04:53 | 9,543 | first reading |
Engagement
31 posts held, back to 7 April 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 51 pages of Telegram’s post history, 20 posts per page.
- ERR · 30 days
- 14.4%
- avg views ÷ 9,465 subscribers
- Avg views / post
- 1,360
- 5 posts measured
- Reaction rate
- 0.352%
- reactions ÷ views · ER floor
- Posts in window
- 5
- of 31 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.
| Window | Rolling 30 days · latest post in window 11 November 2026 |
|---|---|
| Posts held | 31 (7 April 2025 – 11 November 2026) |
| Views total | 6,809 |
| Reactions total | 24 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 11 Nov 2026, 23:43 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
- ≈931
- Links
- ≈1,470
Lifetime counters from Telegram’s own channel header, read 11 November 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked ≈ was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.
Reaction mix
403 reactions across 29 posts, in 12 distinct kinds. The most used accounts for 38.2% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 154 | 38.2% | |
| ❤ | 129 | 32.0% | |
| 😱 | 31 | 7.69% | |
| 😭 | 27 | 6.70% | |
| 🤮 | 25 | 6.20% | |
| 💩 | 17 | 4.22% | |
| 🤡 | 10 | 2.48% | |
| 🔥 | 5 | 1.24% | |
| 🎉 | 2 | 0.496% | |
| 👎 | 1 | 0.248% | |
| 😁 | 1 | 0.248% | |
| 🤔 | 1 | 0.248% |
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 31 of the 31 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 403 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 31 most recent posts we hold, published 7 April 2025 to 11 November 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
Telegram’s own ‘edited’ marker: 0 of 5 posts held from the last 30 days (0%) 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).
Bridgy Fed: 让你的 RSS 站点在 Fediverse 里拥有一个账号 如果你有一个带 RSS / Atom feed 的独立博客,Bridgy Fed 可以把它变成一个可被关注、可互动的 Fediverse 账号——不用注册 Mastodon,也不用装插件。它的定位是「去中心化社交网络的桥」,连接三张网:Fediverse(#Mastodon 等)、Web(独立站点)、Atmosphere(#Bluesky)。 🌉 双向桥接:不只是把内容推过去,别人在 Fediverse 的回复、点赞、转发也会回流到你的站点 📡 站点即账号:首页有可被发现的 Atom / RSS feed(或 microformats + webmention),即可接入 🔗 自定义域名:可以用自己的域名作为 Fediverse handle,不必顶着 *.brid.gy 🆓 开源非营利:代码以 CC0 发布,2024 年底转为非营利组织 A…
❤2👍2
RSS 与 MCP: 让 Agent 真正接上你的信息流 AI 时代, RSS 作为机器可读的规范协议,继续承载着基底的信息流通功用。一个 XML 文件,天生是给机器看的,但既然机器读得了,为什么还要绕一道 MCP?因为「读得懂」和「办得成」是两回事。 只把一条 feed 拿下来念一遍,agent 用一次 HTTP 请求就够了,确实不需要 MCP。卡住的是另外三件事:agent 不知道有哪些 feed 存在、今天哪些是新的,全量拉一次又太贵;RSS 是只读的,标记已读、加订阅、改过滤这些动作它一个都表达不了;写操作要凭证,每个服务一套 key,agent 自己管不了。MCP 就是 2024 年底 Anthropic 提出的那套接口标准,把这三件事包成「工具」交给 agent:先问有哪些工具、参数是什么,再按需调用,凭证由服务端替你收着。 因此,最近的 PR 里收到了数个将 RSS 和 MCP 联动的服务: 📖 输入端接 …
💩4❤2👍1
The Podcast App: 免费版就带 CarPlay 与 AI 问答的播客播放器 感谢开发者提交 PR #139,分享了一款 iOS / Android 播客播放器 The Podcast App: 🎧 免费版相当完整:自定义 RSS 订阅、队列、无限离线下载、OPML 导入导出,CarPlay 与 Android Auto 也不额外收费,而且不用注册账号就能开始听。 🧠 AI 部分是它的 Podcast Brain,分 Ask / Ideas / Recall / Signals 四项,可以就你听过的、有转录的节目提问,并给出出处。转录与问答有每日额度,$4.99/月的订阅只解除额度上限,不锁任何功能。 ✅ 开发者还顺手做了个免费的播客 RSS 校验器,检查 RSS 2.0 结构以及 Apple Podcasts 与 Spotify 的常见要求,不用登录、也不存储你的 feed 地址。 🔗 App:thepodc…
👍1
I ♥️ RSS: 一个 RSS 爱好者的公开名录 1024 程序员节刚过去,补一句迟到的感谢:谢谢还在写 feed、还在维护阅读器、还在给 RSS 添砖加瓦的每一位开发者和爱好者。 这份名录就是这群人自己攒的。在首页挂上「I ♥️ RSS」文字或图片徽章并提交网址,站方核实徽章确实在、站点也确实发布了可被自动发现的 RSS 2.0 feed,就收进公开列表,同时汇入一份任何支持 OPML 的阅读器都能一键订阅的清单。目前 111 位成员。 只收 RSS 2.0 而不收 Atom,是站方明说的取舍;为此还专门写了份指南,教你在 Jekyll / Eleventy / Zola / Astro 等等博客页面上补一行 <link rel="alternate"> 就能被收录。 🔗iheartrss.com 📌 #聚合 #OPML #徽章
❤12
让 AI 写了一个给 RSSHub 写路由的 Agent Skill 不才不咋会写代码,早先时常想着啥时候能给 RSSHub 写写路由,既能自用,又做了贡献。现在 AI Agent 大行其道,这事儿一下简单了,想给哪个网页加 RSS Feed,只要有 Token 就行。所以,让 Agent 分析了 RSSHub 的 2,727 个路由 PR、18,680 条 bot 或管理员的 review 评论,做成一个 Agent Skill,教 AI 写"能尽快过审"的路由,而不只是"能跑"的路由。欢迎试用。 🔸基于 merged 和 unmerged PR 分析了常出现的 review 问题,附完整数据管线 🔸每条避坑建议、例子、验证脚本都在遵从官方 AGENTS.md、官方开发文档的基础上依据上述分析 🔸设计了反馈回路:使用 Skill 的 Agent 会建议用户结合其 PR 经历可选反馈本 Skill 🔸SKill 由 AI 起…
👍28❤4🔥2
Newsairy: 专为 Apple 生态打造的高定制原生 RSS 阅读器 感谢开发者提交 PR #137,向频道推荐了一款适用于 iOS、iPadOS 与 macOS 平台的 RSS 阅读器—— Newsairy: 应用主打无广告、无追踪与高度自由定制,核心特性包括: 🎨 高度个性化排版:提供自动/浅色/深色及专属 Sepia 复古主题;文章列表支持分组或平铺、舒适或紧凑间距,并可自定义缩略图、Favicon、未读标记及 0–6 行预览; 🔍 智能订阅源 (Smart Feeds):除今日、近 24/48/72 小时等预设时间视图外,支持通过关键词包含与屏蔽规则创建自定义智能信息流; ⏱️ 多维度留存与阅读管理:可针对历史抓取深度、未读留存期、已读留存期分别配置独立保留规则;提供按阅读时间排序的浏览历史,支持滚动自动标为已读(Mark as Read on Scroll); ☁️ iCloud 同步与多格式支持:原生支持 …
❤2👍2
Readfine: 集成网页抓取与 AI 助手的可自建 RSS 阅读器 感谢开发者提交 PR #136,自荐了一款Vibe Coding出来的自托管 Web 端 RSS 阅读器—— Readfine。 项目受 Tiny Tiny RSS 启发,采用 Python + HTMX + Tailwind 构建,具备以下特色: 🕸 网页抓取订阅:除标准 RSS/Atom 外,支持通过 CSS 选择器为没有 Feed 的任意网页生成抓取订阅; 📖 全文抽取与多媒体:内置 Trafilatura 正文提取引擎,支持在阅读器内直接播放 YouTube / Vimeo 视频,支持将任意网页剪藏保存; 🖥 双栏/三栏自适应:桌面端可自由配置 2 栏或 3 栏阅读布局,针对移动端进行了独立的交互适配; ⚙️ 规则过滤引擎:支持基于正则与逻辑条件的自动化过滤规则,支持打标签、标星与历史文章回溯处理; 🤖 AI 深度增强 (BYOK):支持接入 …
FriRSS: FreshRSS 的现代化可自建 Web 前端 感谢开发者提交 PR #135,分享了一款为 FreshRSS 打造的高颜值自托管 Web 前端—— FriRSS: 项目通过 Google Reader API 与 FreshRSS 实例无缝连接,主要特性包括: 🖥 多端阅读体验:桌面端采用经典三栏布局;移动端支持可安装的 PWA,提供滑动手势操作与下拉刷新; 📄 全文与离线支持:内置 Readability 全文提取并支持缓存加速;PWA 支持图文离线阅读与一键离线预加载; 🎨 高度个性化定制:支持完全自定义配色主题、字体字号与列宽,提供可嵌套的多层级标签(Labels)管理系统; 🛡 多用户与多服务器:支持角色权限管理、OIDC 单点登录(SSO)以及在多个 FreshRSS 实例间快速切换; 🐳 极简自建:提供单一 Docker 镜像(支持 amd64 / arm64 架构及树莓派),开箱即用。 🐙 …
❤4
RSStoKindle: 将 RSS 与 Substack 订阅排版推送至 Kindle 感谢开发者提交 PR #130,推荐了一款 RSS2KINDLE 在线服务—— RSStoKindle: 核心特性包括: 📖 全文抽取与排版:支持任意 RSS 源及 Substack 订阅,抓取完整文章并自动排版为结构清晰、带章节目录的电子书; 📬 自动定时推送:通过 Amazon Send-to-Kindle 邮箱机制投递,支持一键即时发送或设定每日早间 Digest 自动投递; 💳 资费方案:免费版支持每日最多 5 篇文章投递;包含插图或更高频次需求可升级为 $60/年的付费计划。 🔗 官网:https://www.rsstokindle.com/ 频道提及过的同类服务还有 WhereMyLife、KindleEar、Reabble、Ktool、SyncReads 等。 📌 #RSS2KINDLE #Kindle #工具
❤3
eilmeldung: 基于 Rust 的终端 (TUI) 开源 RSS 阅读器 感谢开发者提交 PR #127,分享了一款极速轻量的终端 RSS 阅读器—— eilmeldung(德语“快讯”之意): 项目基于 Rust + Ratatui 构建,并依托 news-flash 核心库开发,具备以下特性: ⚡️ 极速无阻塞:毫秒级秒开启动,操作非阻塞流畅; ⌨️ (Neo)Vim 键位:支持全键盘 Vim 风格操作与快捷导航; 🧘 Zen 专注模式:可隐藏一切边栏干扰,专注于文章正文排版; 🔍 高级查询语言:内置强大的搜索与过滤语法,支持灵活条件过滤、分类与批量打标签; 🖥 多平台支持:支持 Linux (AUR/Nix)、macOS (Homebrew)、Windows (Scoop) 及 NetBSD。 🐙 Repo: https://github.com/christo-auer/eilmeldung 频道提及过…
❤5👍2
RSStT Bot 项目招募继任者 RSStT Bot 项目在 GitHub 上获星 2K+,@RSStT_Bot 是 Telegram 上有名的 RSS bot。官方 bot 和自架版我都有在用,一直体验很好。上月,项目开发者开始寻求继任者继续维护该开源项目。希望能有合适人选接力运维。
👍16❤1🔥1
Showing the 12 most recent of 31 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.
Posts edited after publishing
@aboutrss edited 2 posts after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.
An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.
- First edit seen
- 3 November 2026
- Most recent edit
- 3 November 2026
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.
Named by
Channels on the register whose posts name this channel's handle.
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.
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
@aboutrss 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.
named in 4 posts, 8 August 2026 – 13 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 8 November 2026 — this entry's latest reading, not the date you are reading this.
“ALL About RSS” (@aboutrss), 9,465 subscribers as measured 8 November 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.