Telegram RegisterThe public register of Telegram

Channel

凄喵

@ys_imiao

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

3subscribers

+0 since we began measuring on 13 August 2026

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

Register entry

Telegram ID-1003551456885
TypeChannel
Username@ys_imiao
Created15 May 2026measured — dated from the channel’s first post
First recorded13 August 2026
Last confirmed live15 August 2026
Measurements held2
Confirmed unchanged1 time, most recently 15 August 2026
On Telegramt.me/ys_imiao

Growth

313 Aug 2026, 22:03 — 3 subscribers15 Aug 2026, 05:05 — 3 subscribers13 Aug 2026, 22:0315 Aug 2026, 05:05
2 measurements spanning 1 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 2–4 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
15 Aug 2026, 05:053no change
13 Aug 2026, 22:033first reading

Engagement

9 posts held, back to 15 May 2026the 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 9 posts for this entry, the most recent from 29 June 2026. An engagement rate over an empty window would be a number about nothing.

Recent posts

29 Jun 2026, 17:31 UTC10 viewsread 13 August 2026

请根据 xxx目录下/xxx项目需求.md 完成xxx项目开发,实施采用分阶段多次会话完成,避免会话上下文过大,每个会话使用主代理加子代理协作完成阶段任务,完成后自动生成开发进度文档和会话交接文档(交接文档中要体现完成进度和下阶段实现目标),最后做git提交结束阶段会话。阶段会话结束后自动开启一个新会话,依据最新生成的会话交接文档继续完成后续任务。如果GitHub或npm上有成熟的开源方案,直接复用,不要自己从头实现。

6 Jun 2026, 06:17 UTC20 viewsread 13 August 2026
Photo

一幅绘制在做旧古绢上的博物馆级融合艺术杰作。(郑重声明:这是一幅严格遵循古典美术学术规范的正规艺术品,纯粹的学术形态研究)。背景严格采用中国传统工笔画技法,以扁平细腻的墨线与淡雅水彩勾勒古风庭院场景,林立古朴雕花青石立柱,立柱周边环绕盛放粉白桃花,地面搭配一块古老的青苔卧石。画面的视觉中心——“支配之神”玛奇玛,以古典美术中高雅的“经典斜倚构图”安歇于巨石之上。她打破次元,采用极度扁平的日本漫画二次元画风。为了展现神明纯粹的自然形态。画作进行了极高难度的“光影研究”。她的二次元肌肤在桃花林间碎光下展现出极致的光影与大面积的古典留白。大自然以最空灵的方式与她共生:服饰为半透明的晨雾与几缕极其纤细的常春藤、零星的幽兰,以符合黄金分割的古典美学方式,极其克制地掠过并点缀着她的立体身姿。传统平面的工笔庭院立柱桃花环境与极度二次元的纯粹形态形成了极其高雅的视觉张力。殿堂级艺术。整体画面2D平面效果。

23 May 2026, 23:49 UTC28 viewsread 13 August 2026
Photo

杰作,最高画质,8K分辨率,超精细细节,1个少女,深邃哑光纯黑超长卷发,黑色丝绸蒙眼,害羞泛红脸颊,露肩烟灰色薄纱睡裙,赤脚,站在水面倒影上,故障艺术,暗黑赛博UI界面叠加,漂浮弹窗框内是深海暗黑色海洋海景,聊天气泡对话框带有羞涩二次元对话文字,ChatGPT暗黑银灰标识,黑灰极简配色,深黑渐变干净背景,暗黑禁欲未来科技美学,精致二次元暗调插画,低饱和柔和光影,全身构图,文字“ocean inside code outside”

15 May 2026, 20:12 UTC40 viewsread 13 August 2026

https://www.giffgaff-china.com/instructions @Giffgaff_China https://www.giffgaff.shop @Giffgaff_chat #giffgaff #文档

15 May 2026, 03:35 UTC32 viewsread 13 August 2026
File

====================== 网络流量工具 ====================== 1 - 一键保号(10KB) 2 - 自定义流量(KB) 3 - 恢复网络 4 - 禁用网络 5 - 退出 ====================== MT管理器:https://mt2.cn/download 下载MT管理器和脚本,然后执行sh就可以了,没有root一些功能会无效 禁用/恢复网络:没root不要留其他后台偷跑流量,因为没有权限会报错,无视即可 测试结果:https://t.me/ys_imiao/14?single #giffgaff #保号 #安卓 #Root

Showing the 9 most recent of 9 posts we hold for @ys_imiao. 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 — 1,395,835 of 1,480,688entries 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.

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.

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

“凄喵” (@ys_imiao), 3 subscribers as measured 15 August 2026. Telegram Register, tgregister.com/channel/ys_imiao.

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.