File, posted without a caption
👍1

Channel
@pixel_tailor_cn
On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Cite this entry
199subscribers
+63 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1003837438893 |
|---|---|
| Type | Channel |
| Username | @pixel_tailor_cn |
| Created | Between 1 February 2026 and 28 June 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 9 October 2026 |
| Measurements held | 9 |
| Confirmed unchanged | 1 time, most recently 9 October 2026 |
| On Telegram | t.me/pixel_tailor_cn |
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 25 September 2026 and assigned it the closest of 31 fixed categories, at 94% 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 why it has no browse page of its own yet.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 9 Oct 2026, 07:21 | 199 | +16 |
| 27 Sept 2026, 21:01 | 183 | +12 |
| 13 Sept 2026, 13:16 | 171 | +5 |
| 4 Sept 2026, 16:59 | 166 | +11 |
| 27 Aug 2026, 15:33 | 155 | +9 |
| 21 Aug 2026, 11:23 | 146 | +3 |
| 15 Aug 2026, 10:07 | 143 | +7 |
| 8 Aug 2026, 23:31 | 136 | no change |
| 7 Aug 2026, 22:59 | 136 | first reading |
20 posts held, back to 28 June 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 page of 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 26 July 2026. An engagement rate over an empty window would be a number about nothing.
8 reactions across 5 posts, in 5 distinct kinds. The most used accounts for 25.0% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 2 | 25.0% | |
| 😢 | 2 | 25.0% | |
| 🥰 | 2 | 25.0% | |
| ❤ | 1 | 12.5% | |
| 🤔 | 1 | 12.5% |
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 5 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 8 reactions 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 28 June 2026 to 26 July 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.
File, posted without a caption
👍1
#GitHub 🎉 Pixel Telo v1.3.6 for Pixel-Tailor-CN/PixelTelo Released! 🎉 ## 新增 - 来电归属地悬浮窗新增“固定时长”和“显示至通话结束”两种模式;固定时长支持 3 至 30 秒调节,并可选择卡片或简洁文本样式 - 支持识别中国移动“和多号/一卡多号”的 125831、125832、125833 前缀,自动还原真实号码用于离线库、联网查询、黑白名单和联系人匹配 - 拦截记录新增归属地与联系人姓名展示,详情页面同步显示完整号码和归属地;备份与恢复也会保留归属地信息 ## 优化 - 拦截记录改为分页加载,仅查询当前已加载记录对应的联系人,降低大量历史记录下的内存与联系人查询开销 - 重新整理设置页面分类,将在线查询、归属地悬浮窗等配置拆分到独立区域,查找设置项更清晰 v1.3.6
File, posted without a caption
#GitHub 🎉 PixelSnooze v1.1.1 for Pixel-Tailor-CN/PixelSnooze Released! 🎉 ## 新增 - 新增临时休息模式,可选择仅今天、指定结束日期或直到手动关闭;开启期间只把今天按休息日处理,不会改动原有休息日规则。 - 主页面新增临时休息状态卡,可快速开关模式、查看有效期限并进入时长设置。 - 新增“临时休息”快捷设置磁贴,可从系统快捷设置直接开启或关闭。 - 新增静默状态通知,模式开启时可查看有效期限,并直接关闭或修改时长。 - 新增应用图标长按快捷方式,支持开启今天、关闭模式和管理时长。 ## 优化 - Android Gradle Plugin、Kotlin 和 Compose BOM 更新至较新版本。 v1.1.1
#GitHub 🎉 PixelText v1.2.1 for Pixel-Tailor-CN/PixelText Released! 🎉 ## 修复 - 修复窄屏设备上复制按钮挤占验证码卡片空间,导致较长验证码显示不完整的问题 - 修复收到新短信后首页会话列表可能不更新,且下拉刷新仍无法显示新消息的问题 v1.2.1
PixelTelo用的api被限流的很严重,大概是1分钟只能请求1次的样子,基本上无法使用了。看来要准备准备搞用户自主标记以及自建服务端了
😢2🤔1
File, posted without a caption
#GitHub 🎉 PixelText v1.2.0 for Pixel-Tailor-CN/PixelText Released! 🎉 ## 新增 - 新增“验证码”页面,聚合展示短信验证码,支持一键复制、查看原文、跳转会话,可设置自动删除 - 新增关键词拦截骚扰短信 - 会话按钮新增未读数量红点 - 新增短信通知图标选择 - 新增快捷设置磁贴,一键启动应用 ## 修复 - 修复通知快捷回复短信后会话未标记已读的问题 v1.2.0
File, posted without a caption
#GitHub 🎉 Pixel Telo v1.3.5 for Pixel-Tailor-CN/PixelTelo Released! 🎉 ## 新增 - 新增“重复来电策略”,可选择“不修改”“放行但静音”或“完全放行”,并在拦截记录中明确展示实际处理方式 ## 修复 - 修复“通话结束后提醒反馈”未检查电话状态和通知权限的问题,缺少权限时不再显示为已开启,关闭功能或撤销权限后也不会继续弹出遗留提醒 - 修复 Release 混淆版本中,从通知栏或拦截记录提交识别结果反馈失败的问题 v1.3.5
File, posted without a caption
#GitHub 🎉 Pixel Telo v1.3.4 for Pixel-Tailor-CN/PixelTelo Released! 🎉 ## 新增 - 来电记录支持将识别到的号码保存到本地通讯录,自动填入号码与识别标签 - 新增快捷设置磁贴,下拉快捷设置面板即可一键打开应用 - 新增 Smartspacer 插件:展示在您未察觉时被直接挂断的骚扰来电数量,进入应用后计数清零 v1.3.4
Showing the 12 most recent of 20 posts we hold for @pixel_tailor_cn. 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.
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.
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.
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 9 October 2026 — this entry's latest reading, not the date you are reading this.
“PixelTailorCN” (@pixel_tailor_cn), 199 subscribers as measured 9 October 2026. Telegram Register, tgregister.com/channel/pixel_tailor_cn.
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.