Telegram RegisterThe public register of Telegram

Channel

极客分享 2.0

@xgeekshare

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

12,995subscribers

+88 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of 10,000–31,623.

Register entry

Telegram ID-1003590648343
TypeChannel
Username@xgeekshare
CreatedBetween 1 December 2025 and 31 May 2026— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live13 August 2026
Measurements held8
Confirmed unchanged1 time, most recently 13 August 2026
On Telegramt.me/xgeekshare

Growth

12,90712,99512,9516 August 2026 — 12,907 subscribers7 August 2026 — 12,907 subscribers8 August 2026 — 12,910 subscribers9 August 2026 — 12,917 subscribers10 August 2026 — 12,943 subscribers11 August 2026 — 12,956 subscribers12 August 2026 — 12,972 subscribers13 August 2026 — 12,995 subscribers6 August 202613 August 2026
8 measurements spanning 7 days, net +88. 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 12,894–13,008 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
13 Aug 2026, 12:0712,995+23
12 Aug 2026, 12:0812,972+16
11 Aug 2026, 09:2312,956+13
10 Aug 2026, 08:2612,943+26
9 Aug 2026, 05:5112,917+7
8 Aug 2026, 08:3512,910+3
7 Aug 2026, 08:3612,907no change
6 Aug 2026, 22:0212,907first reading

Engagement

22 posts held, back to 19 June 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 17 pagesof Telegram’s post history, 20 posts per page.

ERR · 30 days
35.6%
avg views ÷ 12,995 subscribers
Avg views / post
4,630
15 posts measured
Reaction rate
0.217%
reactions ÷ views · ER floor
Posts in window
15
of 22 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. It is computed over the 14 of 15 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 12 August 2026
Posts held22 (19 June 202612 August 2026)
Views total69,470
Reactions total142
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken13 Aug 2026, 02:56 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.

Reaction mix

210 reactions across 21 posts, in 6 distinct kinds. The most used accounts for 39.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🤡8239.0%
👍8038.1%
4421.0%
🏆20.952%
😁10.476%
😱10.476%

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 21 of the 22 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 210reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 22 most recent posts we hold, published 19 June 2026 to 12 August 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

12 Aug 2026, 02:03 UTC≈1,490 views11 reactionsread 13 August 2026
Photo

#agent 🆓 manus 限时免费使用 直达:https://manus.im/app 截至 2026年8月25日 老号被封了,只能注册个新号了,需要注意的是注册新号大概率会弹手机号验证。 📮投稿 📢频道 💬吹水 🌐网站

🤡101

10 Aug 2026, 07:58 UTC≈2,270 views6 reactionsread 13 August 2026
Photo

#skill #写作 ✍️ Human Writing - 一个让 AI 中文少点「模型味」的写作 Skill Human Writing,也叫「活人感写作」,是一套面向 AI Agent 的中文写作 Skill,目标很直接:让生成的文章更像一个具体的人在说话,而不是四平八稳的模型作文。 现在看到「不是…而是…」下意识就会认为是 AI 生成的...你觉得呢? 📮投稿 📢频道 💬吹水 🌐网站

👍42

9 Aug 2026, 04:01 UTC≈2,810 views3 reactionsread 13 August 2026

#频道互推 #群组推荐 电影资源频道(4K、原盘) 爱游戏分享社 老司机之家 折腾实验室频道 白嫖小仓库 丨 抽奖福利之家 小众机场测评 影视软件、TVBox接口分享 不是白嫖,这叫借鉴(备用) 零度资源分享-破解软件/游戏分享 电报频道&群组索引

🤡21

31 Jul 2026, 01:27 UTC≈5,610 views15 reactionsread 13 August 2026
Photo

#chatGPT ⭐ Luna API 价格砍掉 80%,OpenAI 开始卷「每美元性能」 OpenAI 宣布下调 GPT-5.6 系列价格:主打高并发、低成本任务的 Luna 降价 80%,偏日常工作的 Terra 降价 20%。 ChatGPT 和 Codex 的订阅价格、额度预算没有变化,但调用 Terra、Luna 时消耗的额度会更少。简单理解就是:套餐没变,同样额度现在可以多跑一些任务。 👾 假设一次任务消耗 100 万输入 Token + 20 万输出 Token:GPT-5.6 Luna 单次成本为 $0.44、DeepSeek-V4-Pro 单次成本为 $0.609 📮投稿 📢频道 💬吹水 🌐网站

👍141

30 Jul 2026, 03:29 UTC≈5,140 views19 reactionsread 13 August 2026

Codex明天又又又要重置了,今天赶紧瞪完 预言失败

🤡172

29 Jul 2026, 14:30 UTC≈5,270 views3 reactionsread 13 August 2026
Photo

🔥 快上车!新西兰 One 实体电话卡,0 月租长期保号 👋 为什么选择新西兰 One 卡 🔵 高性价比:0 月租,国内免费接收短信,激活后一到两年免费使用,之后仅需充值 10 NZD(¥43左右) 保号,一年一次。 🔵 安全可靠:+64 开头的新西兰实体号码,注册与激活无需实名认证,比 GV、接码平台更好用。 🔵 全球漫游可以在国内接听拨打电话、收发短信,还有中国数据漫游套餐,拥有新西兰纯净 IP。 🔵 使用便捷:支持所有品牌手机,有专属的 Web 后台及官方 App,在国内就可以线上完成充值等服务。 🔵 兼容性好:支持绝大部分主流应用,例如 TikTok、Twitter、Facebook、Instagram、LINE、WhatsApp、Telegram、Gmail、ChatGPT 等等。 🗃 月租与保号 0 月租,激活后有效期为一年;之后每年充值一次即可续期保号,每次 10 NZD,约合人民币 43 元。

3

29 Jul 2026, 04:53 UTC≈4,230 views7 reactionsread 13 August 2026
Photo

#安全 ⭐ OpenAI 推出开源的代码安全扫描工具「Codex Security 」 Codex Security 提供命令行和 TypeScript SDK,可以扫描代码仓库、检查代码变更、记录历史问题,并把安全检查接入 CI。 它不只是根据规则报错,还会结合项目代码生成威胁模型,寻找真实攻击路径,在隔离环境中尝试复现漏洞,再提供可供人工审查的修复补丁,不会直接修改仓库代码。 这一工具的诞生大大提高了 AI 生成代码的安全系数! 📮投稿 📢频道 💬吹水 🌐网站

🤡52

29 Jul 2026, 04:20 UTC≈3,960 views9 reactionsread 13 August 2026

Codex又又又重置了 好消息:限额提升18% 坏消息:明天恢复5小时限额

🤡7🏆2

28 Jul 2026, 01:56 UTC≈4,320 views6 reactionsread 13 August 2026
Photo

#剪辑 ✂️ 不会剪视频?把口播素材丢进去,让 AI 先剪一版 Pireel Studio 是一个专注剪辑口播视频的 AI 工作台。 上传素材后,它会自动识别台词、拆分镜头、调整取景、添加动效花字和设计图形,还能直接用对话修改画面,最后导出 MP4。 需要注意的是,开源版本的时间轴、实时预览、主题和视频导出均在浏览器本地运行,不需要账号和后端;不过 AI 生图、生视频、转录和跨设备同步等能力,需要自行接入服务或通过 MCP 连接 Codex、Claude Code 等 Agent。 📮投稿 📢频道 💬吹水 🌐网站

👍3🤡21

27 Jul 2026, 06:13 UTC≈4,590 views14 reactionsread 13 August 2026
Photo

#agent Open Minis:一个开源的 AI 手机助手 Open Minis 不只是聊天,它可以做类似 Codex 在电脑上的操作。浏览网页、读取日历、访问健康数据、管理提醒、控制智能家居等都不在话下。 支持 iOS、Android、macOS 和 visionOS。 我怀疑苹果智能鸽太久,开发者忍不住才做的 📮投稿 📢频道 💬吹水 🌐网站

👍86

25 Jul 2026, 13:20 UTC≈4,840 views10 reactionsread 13 August 2026
Photo

#codex ⌨️ Codex 默认界面太素?这个开源工具可以换个皮肤 Codex Dream Skin 是一个给 Codex 桌面端换肤的开源工具,通过本机 CDP 注入实现主题化效果,不修改官方安装包 它可以把一张背景图变成 Codex 的视觉主题,同时保留侧栏、输入框、项目选择等原生交互控件,并不是简单贴一张假截图。 对于每天打开 Codex 写代码的人来说,换个顺眼的界面确实能增加一点使用乐趣... 📮投稿 📢频道 💬吹水 🌐网站

🤡91

Showing the 12 most recent of 22 posts we hold for @xgeekshare. 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 — 447,730 of 1,169,250entries 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 3 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.

“极客分享 2.0” (@xgeekshare), 12,995 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/xgeekshare.

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.