如何创建一个属于自己的机器人 1. 打开 @BotFather 发送 /newbot 2. 发送机器人的名字(可以是中文) 3. 发送机器人的用户名,(英文且bot结尾) 4. 申请完成会得到一串如123456:xxxxxxxxx 格式的密钥,这就是机器人的Token。 ( 密钥很重要! 请勿轻易向他人展示 ) 不小心泄露了Token,怎么重置 ? 1. 打开 @BotFather 发送 /mybots 2. 选择要重置的机器人 3. 按下 API Token 按钮 4. 然后会出现机器人现在的Token,按下 Revoke current token 按钮,就会重新生成一个新的Token。( 即可重置新的令牌,旧的将会失效) 机器人怎么改名字 ? 1. 给 @BotFather 发送 /setname 2. 小键盘选择要改变的机器人 3. 发送机器人的新名字 机器人怎么改头像 ? 1. 给 @BotFather 发送 …

Channel
Telegram 知识大百科
@liebaobaike
On this record: Growth · Engagement · What this channel posts · Posts · Citations · Handles named that no longer answer · Cite this entry
2,844subscribers
+2,825 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1001873967067 |
|---|---|
| Type | Channel |
| Username | @liebaobaike |
| Created | Between 1 October 2022 and 30 September 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 11 August 2026 |
| Last confirmed live | 15 August 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 1 time, most recently 15 August 2026 |
| On Telegram | t.me/liebaobaike |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 15 Aug 2026, 15:46 | 2,844 | +2,820 |
| 11 Aug 2026, 10:48 | 24 | no change |
| 7 Aug 2026, 18:43 | 24 | +5 |
| 7 Aug 2026, 06:51 | 19 | first reading |
Engagement
15 posts held, back to 3 August 2026 — 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.
- ERR · 30 days
- 1.67%
- avg views ÷ 2,844 subscribers
- Avg views / post
- 47.4
- 15 posts measured
- Reaction rate
- —
- this channel exposes no reaction counts
- Posts in window
- 15
- of 15 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 10 August 2026 |
|---|---|
| Posts held | 15 (3 August 2026 – 10 August 2026) |
| Views total | 711 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 11 Aug 2026, 10:48 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
- Video runtime
- 14s
- Average length
- 14s
Measured directly from 1 video 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
关于TG苹果手机换绑号码教程,一张图告诉你如何快速操作
Telegram 终于解决了中文搜索的问题 为什么以前的搜索那么“残废”? Telegram 长期以来在中文搜索上有一个顽疾:由于缺乏分词机制,必须输入完整句子或特定分词(空格、标点或符号)才能搜到内容。 这个问题的原因其实很简单:英文有空格分词,中文没有。在英文里,单词之间有天然空格,搜索非常精准。但中文是一句话连在一起写的,系统不容易判断一个词从哪里开始、到哪里结束。这个问题在中、日、韩等语言里都存在。 搜索的“进化时刻”: 在最近的版本更新中,Telegram 从服务器端到底层算法做了重构,正式引入了针对中日韩语言的索引机制。简单说,系统现在具备了“子字符串匹配”的能力——即使你只搜某个词组中的一部分,系统也能在长句里精准找到相关内容。 实际体验改善很明显:中文搜索比之前好用了。而且这次更新不需要更新 App,直接搜索就行。之前的历史消息也被重新索引了,同样可以正常搜索。 一个小提示: 目前搜索时可能会…
如何设置机器人转发消息的文字样式 <b>加粗</b> <i>斜体</i> <u>下划线</u> <s>删除线</s> <blockquote>引用</blockquote> <pre>等宽1</pre> <code>等宽2</code> <tg-spoiler>剧透</tg-spoiler> <a href='https://t.me/liebao1>超链接</a>
Telegram 知识大百科 ✳️TG两步验证 ✳️TG隐私设置 ✳️谨防盗号 ✳️谨防盗号 ✳️TG如何联系官方 ✳️TG账号限制 ✳️TG注册和登录 ✳️TG限制私聊 ✳️TG解除双向 ✳️TG 分组/文件夹 ✳️TG注册/登录收不到短信验证码 ✳️TG iOS 客户端无法进入/查看开车群的方法 ✳️TG 官方客户端下载地址 ✳️TG 归档 ✳️TG 主题 ✳️TG限制 ✳️TG 如何建群 ✳️TG 新建频道 ✳️TG 评论功能 ✳️TG 如…
富文本编辑器。 发送富媒体消息”功能已为 Telegram Premium 用户启用;您可以使用**可视化编辑器**创建文章和长篇内容,该编辑器支持数十种格式选项,例如**表格**、列表、**内联媒体**等,并且可以创作超过**32,000个字符**的内容。 该编辑器还允许您使用**注重隐私保护**的AI工具**生成文本**和格式。
解决TG收不到通知的问题 打开小火箭,点底部中间的“配置”,找到你正在用的配置文件,点右边的“i”进去。点右上角加号加一条规则:类型选 DOMAIN-SUFFIX,策略PROXY,域名输入 push.apple.com ,填完点蓝色勾保存。最后回到首页把全局路由改成“配置”模式,再开关一次飞行模式重连网络就行了。 这样TG推送基本就能正常收到了。
【关于近期Telegram登录异常及“短信费用”问题的说明】 由于Telegram自2025年8月大更新后引入了严格的风控机制,针对未绑定邮箱的账号,登录时常会出现以下两种情况: 强制补绑邮箱: 因注册时未关联邮箱,系统要求二次验证。 出现短信费用提示: 这是官方针对非会员账号的新规,与号码质量无关。 💡以下是解决方案 绕过限制: 使用电脑端登录,或下载第三方客户端进行登录。 (下载第三方飞机,下载地址 https://nicegram.app/或是swiftgram) 解除费用: 为该号码开通单月Telegram会员,即可恢复官方原版App正常登录。 风险提示: 官方目前对设备风控严厉,如遇账号冻结属于系统封号,目前暂无解法。
Telegram 更换绑定邮箱接收验证码教程 你是否遇到这种情况: 买来的 Telegram 账号或者自己的号,设置里压根没有“邮箱绑定”按钮? 别急,今天教你 “跳邮箱” 的完整解决方案,让你也能通过邮箱接收验证码,甚至不需要手机号登录 Telegram! 有两种账号类型: ✅ 已经绑定邮箱的账号:可直接更换邮箱,输入新邮箱 → 收验证码 → 成功换绑 ⚠️ 没有绑定邮箱的账号:没有“绑定按钮”,但可以通过“跳邮箱”方式强制激活 ✅ 跳邮箱方法 1️⃣ 方法一:Telegram X 不断登录退出法 使用安卓版本 Telegram X 不断登录 → 退出 → 登录 → 退出,让账号“进入频繁状态” 一般第二天就会触发邮箱验证弹窗 📌 优点:安全、稳定,不会封号 2️⃣ 方法二:安卓 + iPhone 联动法 先用安卓登录账号 然后切换到 iPhone 上重新登录 很大概率直接触发邮箱验证步骤 📌 小贴士…
通行密钥(Passkeys):Telegram 全新安全登录方式 通行密钥(Passkeys)是一种免密码的安全登录技术,它依托公钥私钥加密体系与设备本地验证机制,替代了传统密码形式,能显著提升账户登录的安全性与操作便捷性。 Telegram 已正式上线通行密钥登录功能,该功能可完全取代短信验证码登录。一方面解决了此前国际短信验证码存在的发送成本高、部分地区接收失败等痛点,另一方面也有效规避了短信验证码被劫持的风险,实现了登录安全与便捷性的双重升级。 值得注意的是,通行密钥会存储在用户自主选择的密码管理器中,其安全性与可用性不受 Telegram 平台服务本身的影响,保障了密钥的独立性与稳定性。 核心优势 * 替代短信验证,无接收地域限制、无劫持风险 * 依托公钥加密体系,登录安全等级更高 * 密钥存于个人密码管理器,与平台服务解耦 已支持的客户端: * iOS 官方客户端版本 ≥ v12.2.…
Telegram 客户端 Proxy 代理设置 Telegram.February 15,2020 at 20:10 1. Telegram Desktop 客户端 TelegramDesktop默认并没有勾选"使用系统代理",所以很多人觉 得需要开全局才能用,其实不然,可以手动勾选"使用系统代理"或使 用自定义代理。 步骤: A:末登录账号:界面左下角按钮 B:已登录账号:Telegram Desktop 客户端→左上角三短线→设置→ 高级→网络和代理→代理类型→勾选”使用系统代理"或"使用自定义 代理’ 使用自定义代理添加方法:添加代理(Add proxy)→SOCKS5/HTTP→服务器:127.0.0.1,端口:端口需查看你的代理软件,不需要填写用户名和密码. 代理软件查看本地端口的方法: Mihomo Party:主界面→内核设置→混合端口(默认是:7890) Clash Verge:主界面→设置→Cl…
接收和回复Gmail → @GmailBot 私信机器人 → @ModularBot @NodeForwardBot Telegram Premium订阅 → @PremiumBot 入群审核只能Premium进群 → @PremiumjoinBot 自动封禁群中的Premium用户 → @PremiumXBot 自动删除群中的Premium贴纸 → @AntiPremiumStickerBot 统计 Premium 用户占比 → @PremiumCounterBot 搜索引擎搜索→ @letmebot Telegraph 文章管理 → @telegraph InstantView 生成姬 → @ChnInstantViewBot 智能合租机器人 → @daixiahu_bot 删除加群退群消息→@AntiServiceMessage_Bot 删除命令 → @AntiCommandBot 解除频道消息在群组的置顶 → @arep…
Showing the 12 most recent of 15 posts we hold for @liebaobaike. 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 — 590,338 of 1,480,944entries 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 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.
Names
Channels on the register whose handles appear in this channel's posts.
@creationdatebot · 39,6422 postsGetIDs Bot
@getidsbot · 30,4462 postsBotFather
@BotFather · 8,483,4851 postController Bot
@ControllerBot · 227,3891 post自訂型入群驗證🤖
@Customize_Captcha_Bot · 88,5761 postDiscussBot
@discussbot · 38,4951 post方丈机器人
@fangzhang_bot · 295,0911 postGroup Help
@GHelpBot · 66,2871 postGmail Bot
@GmailBot · 36,5821 postGroup Help
@GroupHelpBot · 1,747,6221 postKinhRoBot
@KinhRoBot · 115,1401 postLikeBot
@like · 648,7081 postManybot
@Manybot · 925,3751 postRose
@MissRose_bot · 2,297,0371 postModularBot
@ModularBot · 187,2501 postnmBot
@nmnmfunbot · 744,1321 postPremium Bot
@PremiumBot · 6,833,8811 postSpam Info Bot
@SpamBot · 32,533,6521 postTemp Mail ✉️ Official Bot
@TempMail_org_bot · 83,7551 postUser Info • Get ID • IDbot
@userinfobot · 525,6161 postIDBot
@username_to_id_bot · 46,0991 post
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
- 6
- 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
- 6
- vacant every time we have ever looked
@liebaobaike named 6 handles 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 1 post, 12 August 2026 – 12 August 2026
named in 1 post, 12 August 2026 – 12 August 2026
named in 1 post, 12 August 2026 – 12 August 2026
named in 1 post, 12 August 2026 – 12 August 2026
named in 1 post, 12 August 2026 – 12 August 2026
named in 1 post, 12 August 2026 – 12 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 15 August 2026 — this entry's latest reading, not the date you are reading this.
“Telegram 知识大百科” (@liebaobaike), 2,844 subscribers as measured 15 August 2026. Telegram Register, tgregister.com/channel/liebaobaike.
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.