Telegram RegisterThe public register of Telegram
Telegram profile photo for 📝Full bug的日常

Channel

📝Full bug的日常

@fullbugccc

On this record: Previous handles · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Telegram's recommendations · Cite this entry

1,325subscribers

+0 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-1001658816232
TypeChannel
Username@fullbugccc
Description技术分享,此频道主要发布更新日志
CreatedBetween 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live8 September 2026
Measurements held5
On Telegramt.me/fullbugccc

Previous handles

@fullbugccc was previously reachable at this handle, before switching to its current one. This says nothing about who or what answers at the old handle today — only that this channel no longer does.

@fullbugcc
held 7 August 20267 August 2026

Growth

1,3251,3271,3267 August 2026 — 1,325 subscribers7 August 2026 — 1,325 subscribers10 August 2026 — 1,326 subscribers14 August 2026 — 1,327 subscribers1 September 2026 — 1,325 subscribers7 August 20261 September 2026
5 measurements spanning 25 days. 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 1,325–1,327 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
1 Sept 2026, 19:301,325-2
14 Aug 2026, 13:381,327+1
10 Aug 2026, 22:471,326+1
7 Aug 2026, 22:311,325no change
7 Aug 2026, 12:581,325first reading

Engagement

21 posts held, back to 12 December 2025the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 2 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
24.9%
avg views ÷ 1,325 subscribers
Avg views / post
330
3 posts measured
Reaction rate
0%
reactions ÷ views · ER floor
Posts in window
3
of 21 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 1 of 3 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 30 August 2026
Posts held21 (12 December 202530 August 2026)
Views total991
Reactions total0
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken1 Sept 2026, 19:30 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
77
Videos
2
Links
75

Lifetime counters from Telegram’s own channel header, read 1 September 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

71 reactions across 11 posts, in 13 distinct kinds. The most used accounts for 26.8% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍1926.8%
😁1622.5%
🫡811.3%
💩68.45%
57.04%
🔥57.04%
💯34.23%
🤡34.23%
🥰22.82%
❤‍🔥11.41%
👏11.41%
😈11.41%
😱11.41%

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

Measured over the 21 most recent posts we hold, published 12 December 2025 to 30 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

30 Aug 2026, 05:58 UTC230 viewsread 1 September 2026
File

#工具留档 如果还有在用cfw,说一下换代理内核的注意事项。 如果你仅仅通过替换文件并改名的方式进行启动,是无法使用 ”服务模式“的。因为服务模式会让内核以SYSTEM权限运行,cfw的服务模式进程clash-core-service会验证内核(clash-win64.exe)的数据完整性。同目录下有一个clash-win64.exe.sign签名文件,服务进程会读取这个文件进行校验。 具体的算法已经逆向出来了,使用上面编写的clash-key-tool(附源码)即可重新对内核进行签名。 工具的原理是对服务进程的内置签名公钥进行修补,把原来的公钥替换成自己生成的,最后用自己公钥对应的私钥进行签名就可以了。 cfw也就这样了,就在这里划下句号吧。

30 Aug 2026, 05:43 UTC248 views0 reactionsread 1 September 2026
Photo

cfw用了蛮多年,尽管不更新了,但后面以手动换内核的方式还是能勉强支持新功能的。 今天清理磁盘是发现了它,也是时候跟它说再见了,因为现在我找到更好的满足我需求的bettbox🤣

20 Aug 2026, 11:23 UTC513 viewsread 1 September 2026

在30个入群申请的样本中,只有一个通过了入群审核(其他29全部是可疑的)。现在的广告机器人十分泛滥,tg api的滥用官方始终没有一个很好的解决方案,因此大部分简体中文群组启用自动化机器人审核入群也就不足为奇了

8 Aug 2026, 10:09 UTC821 views1 reactionsread 1 September 2026
Photo

https://cloudflare.pay 以防你不知道3位数的名字总共46656条结果,目前还剩 7796 个没被注册,其中三位数的纯字母名字短短几天时间已被全部认领😁

1

22 Jul 2026, 15:41 UTC≈1,250 views19 reactionsread 1 September 2026

我要开团那些要求强制绑定TG账号的机场了 不太能理解这种关联用户画像的行为为什么到现在都没有人出来评价,还是大部分end user都已经连最基本的安全措施都无视了,那你上TG是图啥 机场绑定TG账号以后,机场就知道你对应的TG和IP地址之间的强关联,阴谋论一点方便中国警方取证哈,不过别乱说话看看片没人管你。 问题是这个措施是对用户不利的,没有选择的空间。个人建议要求强制绑定TG账号机场慎用哈,一但接受了到时候会有更无底线的试探😅

👍18🤡1

22 Jul 2026, 12:28 UTC878 viewsread 1 September 2026

谁能告诉我为什么用 gitbook 写的文档页面这么卡,切换页面卡飞了😅

24 Jun 2026, 11:01 UTC≈1,250 viewsread 1 September 2026

以防你不知道高德地图加载飞快是经过优化的: https://zhuanlan.zhihu.com/p/344503272

23 Jun 2026, 13:13 UTC≈1,190 views6 reactionsread 1 September 2026

在 Android 设备上运行 OpenHarmony / HarmonyOS HAP 应用: https://github.com/harmony-on-android/HOA

💩6

12 Jun 2026, 16:53 UTC≈1,140 viewsread 1 September 2026
Forwarded from @koipycPhoto

在压测情况下,我们有幸见到了以VLESS协议为载体的网络下行带宽测试,最高峰值速度突破到了20Gbps 这种极端情况下,影响速度的因素有: 1. 测速的大文件链接对应的服务器带宽是否充足 2. 测速程序(miaospeed)设计瓶颈 3. 协议实现瓶颈 4. Go语言性能瓶颈(但应该还达不到上限)

8 Jun 2026, 14:17 UTC947 viewsread 1 September 2026
Forwarded from @kedaya_888File

必看: 1.注册机让DeepSeek或者破限的gpt-5.4帮你配置安装依赖并运行 2.只需要配置一个动态代理或者自己改一下只需要一个代理 不用动态代理 3.软件取的rt可能二十来个请求就401掉线了 但是可以用功能:python ChatGPT_team.py --check-tokens 进行续签覆盖源文件 4.默认导出cpa格式到运行目录codex_tokens,去这个网站转sub2api格式:https://gtxx3600.github.io/CPA2sub2API 5.示例运行命令:python ChatGPT_team.py --total 10000 --workers 20 6.务必开启动态代理 否则会被cloudflare拦截下来 直接用力蹬 蹬快点

8 Jun 2026, 14:16 UTC692 viewsread 1 September 2026
Forwarded from @kedaya_888Photo

@gpt.edu.sixoner.com 用此后缀去注册ChatGPT 输入任意前缀 然后选择sso登录就自动team号 然后去codex登录授权反代使用即可 重点:注册就是team的bug号 250刀 速蹬月限额

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

Republished by

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

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.

Appears in Telegram’s recommendations for other channels

The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.

海豚机场测评|用户侧体验|测速频道
@haitun_channel · 36,540
Telegram ranks this channel #35 of 39 here — alongside 38 others — read 1 September 2026
翻翻墙 | 机场评测
@ffqchannel · 60,932
Telegram ranks this channel #40 of 45 here — alongside 44 others — read 22 August 2026
科学上网观察与机场测速
@jichangtj · 133,836
Telegram ranks this channel #40 of 54 here — alongside 53 others — read 15 August 2026

This channel appears in 3 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.

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

“📝Full bug的日常” (@fullbugccc), 1,325 subscribers as measured 1 September 2026. Telegram Register, tgregister.com/channel/fullbugccc.

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.