[refactor: 更新浅色和深色主题切换] [refactor: 优化性能]
👍27❤4

Channel
@gyc_123
On this record: Topic · Growth · Engagement · Reactions · Posts · Handles named that no longer answer · Cite this entry
3,579subscribers
-51 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
| Telegram ID | -1002437384363 |
|---|---|
| Type | Channel |
| Username | @gyc_123 |
| Created | Between 1 September 2024 and 28 September 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 12 October 2026 |
| Measurements held | 17 |
| Confirmed unchanged | 1 time, most recently 12 October 2026 |
| On Telegram | t.me/gyc_123 |
Music — 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 14 September 2026 and assigned it the closest of 31 fixed categories, at 95% 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 |
|---|---|---|
| 12 Oct 2026, 19:07 | 3,579 | -5 |
| 6 Oct 2026, 02:39 | 3,584 | -4 |
| 28 Sept 2026, 19:38 | 3,588 | -14 |
| 19 Sept 2026, 02:38 | 3,602 | -7 |
| 15 Sept 2026, 01:20 | 3,609 | -8 |
| 11 Sept 2026, 09:56 | 3,617 | -2 |
| 6 Sept 2026, 09:21 | 3,619 | -5 |
| 2 Sept 2026, 11:34 | 3,624 | -4 |
| 30 Aug 2026, 17:24 | 3,628 | +1 |
| 27 Aug 2026, 22:44 | 3,627 | -4 |
| 25 Aug 2026, 04:24 | 3,631 | -2 |
| 21 Aug 2026, 13:49 | 3,633 | +4 |
| 18 Aug 2026, 07:22 | 3,629 | +2 |
| 15 Aug 2026, 12:28 | 3,627 | -1 |
| 11 Aug 2026, 14:43 | 3,628 | -2 |
| 8 Aug 2026, 11:46 | 3,630 | no change |
| 7 Aug 2026, 15:01 | 3,630 | first reading |
18 posts held, back to 28 September 2024 — the 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.
Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 18 posts for this entry, the most recent from 6 March 2026. An engagement rate over an empty window would be a number about nothing.
518 reactions across 16 posts, in 6 distinct kinds. The most used accounts for 53.7% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 278 | 53.7% | |
| 👍 | 227 | 43.8% | |
| 🥰 | 7 | 1.35% | |
| 🍾 | 3 | 0.579% | |
| 💔 | 2 | 0.386% | |
| 😁 | 1 | 0.193% |
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 16 of the 18 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 518 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 18 most recent posts we hold, published 28 September 2024 to 6 March 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.
[refactor: 更新浅色和深色主题切换] [refactor: 优化性能]
👍27❤4
[feat: 支持分享音源文件导入,支持 url和脚本导入] [feat: 添加歌词延迟控制功能,支持调整和重置歌词显示延迟]
❤1
[feat: 支持导入洛雪音源] [feat: 添加音源测试功能,优化音源状态管理]
❤22👍8
[feat: 搜索歌手和歌曲分開] [fix: APP启动图片不适配不同屏幕的机子] [fix:导入歌单输入栏被键盘遮挡] [fix:音源文件导入更新逻辑,如果第一次导入,则自动选择] 有什么建议或bug可以提issues。点点star🌟支持开发
❤63🥰6
来自 https://github.com/gyc-12/Cymusic/issues/104 https://github.com/gyc-12/Cymusic/issues/103
❤28🥰1
更新地址
❤52👍27
[feat: 遇到无高音质的音乐自动尝试切换低一级音质播放] [feat: 支持创建自定义歌单] [feat: 设置首页播放歌曲数量] [feat: 首页分页加载300 首] [fix: 部分国际化拼写错误] [fix:手动下载缓存路径错误导致读取不到本地缓存缓存歌曲后提示 #78 #81 ] 有什么建议或bug可以提issues。点点star🌟支持开发
❤41👍9
来自 ikun 佬的分享,频道:@ikunshare_channel
👍12❤6
[feat: 设置增加是否显示缓存图标] [feat: 增加已缓存歌曲标识issue: #70 ] [feat:部分弹窗提示改为Toast 提示] [fix: 搜索音乐会点不到第一首歌曲,issue: #60 ] 有什么建议或bug可以提issues。点点star🌟支持开发
👍22❤7
出处(文件里面也写了),https://apii.lolimi.cn/ 可以支持大佬的收费 api
❤18👍4🍾3
[chore: 电台-->广播] [fix: app位于后台时避免频繁Alert] [chore:doc] [feat: 点击正在播放曲目弹出播放界面] [fix: 部分机型搜索页面第一条不显示] 最近比较忙,更新慢,见谅。有什么建议或bug可以提issues。欢迎star🌟https://github.com/gyc-12/Cymusic
👍21❤5
[fix: 一些List性能优化] [feat: 搜索页支持下滑翻页] [feat: 支持状态栏进度条拖动快进] [feat: 支持多语言(英语+中文)选择] [fix:下载按钮逻辑] [doc: readme] 注:1、新加了一个carplay支持分支,在xcode模拟器上测试能正常运行,但是打包出来手机上用不了,大概需要🍎付费开发者证书?暂时放弃了。2、欢迎star、pr
👍26❤3
Showing the 12 most recent of 18 posts we hold for @gyc_123. 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.
@gyc_123 named 1 handle 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.
References a handle that is not a live channel — we have no record it ever was one.
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 12 October 2026 — this entry's latest reading, not the date you are reading this.
“cymusic” (@gyc_123), 3,579 subscribers as measured 12 October 2026. Telegram Register, tgregister.com/channel/gyc_123.
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.