Telegram RegisterThe public register of Telegram
Telegram profile photo for BetterForward

Channel

BetterForward

@BetterForward

On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry

468subscribers

+0 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1002040416279
TypeChannel
Username@BetterForward
DescriptionBetterForward is designed by SideCloud. Designed for better message forwarding in Telegram. 为更好地转发 Telegram 消息而设计。 https://github.com/SideCloudGroup/BetterForward
CreatedBetween 1 November 2023 and 31 May 2024— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live16 August 2026
Measurements held2
On Telegramt.me/BetterForward

Growth

4687 Aug 2026, 15:11 — 468 subscribers8 Aug 2026, 04:46 — 468 subscribers7 Aug 2026, 15:118 Aug 2026, 04:46
2 measurements taken within a single day. 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 467–469 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
8 Aug 2026, 04:46468no change
7 Aug 2026, 15:11468first reading

Engagement

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

What this channel posts

Links
6

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

Reaction mix

35 reactions across 9 posts, in 4 distinct kinds. The most used accounts for 54.3% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍1954.3%
1131.4%
🎉411.4%
👎12.86%

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 11 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 35reactions 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 20 August 2024 to 27 December 2025, 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

27 Dec 2025, 14:12 UTC≈2,260 viewsread 8 August 2026

BetterForward v2.0.5 #Update 新增 - 支持对接 TGuard 以实现在线人机验证(可使用hCaptcha、Turnstile、Cap等) *TGuard由Sidecloud开发,是一个现代化的 Telegram 智能验证机器人,既可以用作群组加群验证,通过人机验证自动管理群组成员申请,也提供了完整的 RESTful API 接口,可供第三方 Telegram 程序调用,实现多用途的人机验证功能,为各种需要人机验证的场景提供安全、可靠的验证服务。

13 Nov 2025, 03:49 UTC≈1,760 views3 reactionsread 8 August 2026

BetterForward v2.0.3 #Update 新增 - 主菜单新增查询部署机器IP信息功能,方便因机器太多需要更新时找不到部署在哪的用户快速查询 - 该功能使用第三方API查询实现 如果偶尔显示查询失败docker记录报429错可能是由于机器出口IP短期内查询过多或共享IP导致。如果是其他报错欢迎提供反馈

👍2👎1

12 Nov 2025, 11:14 UTC≈6,210 views2 reactionsread 8 August 2026

BetterForward v2.0.2 #Update 修复 - 修复时区设置需要重启才能生效的问题,现在修改后立即生效 新增 - 垃圾消息防御系统:基于关键词的智能过滤,支持模糊匹配,自动转发到专属垃圾消息会话 - 可扩展检测器接口:模块化设计,可对接AI模型、外部API等多种检测方法 - 独立黑名单表:删除话题后黑名单依然有效,自动记录用户信息(姓名、用户名) - 拉黑用户自动回复:可设置被拉黑用户发消息时的自动回复内容,支持开关 - 封禁用户管理菜单:分页展示被封禁用户,显示详细信息,支持快速解封 - 一键删除话题:封禁用户后可直接删除其话题 - 消息处理时间统计:日志中显示每条消息的处理耗时,便于性能监控 优化 - 关键词匹配算法优化,时间复杂度 O(n) - 黑名单系统完全重构,不再依赖 topics 表的 ban 字段

👍2

10 Nov 2025, 03:09 UTC≈2,130 views0 reactionsread 8 August 2026

BetterForward 是一个开源项目,致力于提升 Telegram 消息转发体验。 它专为更好地转发 Telegram 消息而设计,利用「话题」功能实现更自然、更高效的私聊机器人(PM Bot)体验。 BetterForward 能将用户的消息自动转发到群组中,每位用户拥有独立的主题,从而实现近乎私聊般的对话体验。 其主要特点包括: 隐私保护:管理员账号不会暴露。 灵活对话:每个用户对应独立主题,体验接近私聊。 团队协作:多个管理员可同时处理消息。 多语言支持:包括中文与英文。 自动回复与正则匹配:支持关键词匹配与定时生效。 验证码防垃圾:防止恶意或自动化消息。 广播功能:支持管理员群发消息。 详细请见 https://github.com/SideCloudGroup/BetterForward

Signed 白衣 | 邮局滞销

10 Nov 2025, 03:08 UTC≈1,730 viewsread 8 August 2026

BetterForward v2.0.1 #Update 我们很高兴地宣布 BetterForward 迎来了一次重要更新: 🧵 多线程支持 程序现已支持多线程处理,大幅提升消息处理与转发效率。 在部署时,可通过环境变量 WORKER 灵活调节线程数量,以适配不同的运行环境与负载需求。 📬 全新消息队列设计 我们重新设计了消息队列机制,确保 单个用户的消息不会因并发处理而出现乱序或冲突,进一步提升了系统稳定性与可靠性。 🧭 新增 GitHub 仓库 我们已在 GitHub 上新增官方仓库,并同步提供官方容器镜像,方便社区用户获取与协作。 镜像地址: ghcr.io/sidecloudgroup/betterforward:latest 同时,原有镜像仓库仍将持续同步推送最新版本,以确保现有部署无需修改即可获得更新。 如果在使用过程中遇到任何问题,或有改进建议,欢迎通过 GitHub Issues 提出,我们会积极跟进并

Signed 白衣 | 邮局滞销

29 Jul 2025, 12:24 UTC≈1,020 views6 reactionsread 8 August 2026

BetterForward v1.2.5 #Update New Features 新功能 · Add permission check and confirmation step for terminate command 为删除会话指令增加权限验证和二步确认

6

19 Apr 2025, 02:26 UTC≈2,460 views8 reactionsread 8 August 2026

BetterForward v1.2.4 #Update New Features 新功能 · Support for rich text messages, preserving original formatting when forwarded. 支持富文本消息,转发时保留原格式。 · Improved message handling under high load to avoid errors from frequent requests. 增强高并发场景下的消息处理能力,避免因请求频繁导致报错。 · Support for custom Telegram API configuration. 支持自定义 Telegram API。

👍8

16 Mar 2025, 19:45 UTC≈1,350 views5 reactionsread 8 August 2026

Earlier released images had an issue that could cause messages to be improperly processed. All users are advised to perform an update after seeing this notice. 早些时候发布的镜像存在问题,可能导致消息无法正常处理。请所有用户在看到此通知后执行一次更新操作。

👍5

16 Mar 2025, 19:44 UTC≈1,160 viewsread 8 August 2026

BetterForward v1.2.3 #Update New Features 新功能 • When users delete messages, administrators can still retain the original messages. 用户删除消息时,对于管理员保留原消息。 • Added compatibility for more types of messages. 新增更多消息种类的兼容。 Fixs 修复 • Fixed an issue where emoji reactions were received asymmetrically. 修复表情回应存在不对称的接收问题。 • Fixed an issue where a topic was mistakenly destroyed when message sending failed. 修复发送消息失败时错误地销毁话题。

12 Mar 2025, 19:26 UTC≈1,090 viewsread 8 August 2026

关注 @SideCloud 了解本公司其他产品。 如果觉得 BetterForward 好用,欢迎推荐给更多用户!

12 Mar 2025, 19:25 UTC≈1,000 views0 reactionsread 8 August 2026
Forwarded from @sidecloud

💡你还没有听说过 @BetterForward 吗? 这可能是你未来一段时间所见到的最给力、最实用的Telegram消息转发机器人。 由 @SideCloud 开发,扎根于实践,发布于2024年4月30日的BetterForward,大浪淘沙后仍然保持初心。 免费、开源、自信满满。 - 使用Docker一键部署、一键维护 - 极限的隐私保护 - 实时更新的对话体验 - Topic形式的对话窗口 - 自定义各种参数的自由体验 - 反垃圾信息的出色AntiSpam效果 现在就到 Github 查看部署指令,并欢迎Star⭐️、Fork🌲、Pull Request🔧。 https://github.com/SideCloudGroup/BetterForward Telegram 频道 @BetterForward 关注SideCloud @SideCloud

9 Mar 2025, 10:49 UTC≈1,000 views1 reactionsread 8 August 2026

BetterForward v1.2.2 #Update New Features 新功能 • Displays error message when failing to send message to user 当发送消息失败时,显示错误信息。

👍1

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

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

“BetterForward” (@BetterForward), 468 subscribers as measured 8 August 2026. Telegram Register, tgregister.com/channel/BetterForward.

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.