嘿嘿,败家子又可以买新的了(
🎉57

Channel
@saltplayerupdate
On this record: Growth · Engagement · What this channel posts · Reactions · Stars · Posts · Citations · Telegram's recommendations · Cite this entry
17,099subscribers
+79 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
| Telegram ID | -1001404299449 |
|---|---|
| Type | Channel |
| Username | @saltplayerupdate |
| Description | 椒盐音乐(PC/Android/鸿蒙)更新公告,开发者动态,椒盐全家桶 |
| Created | Between 1 April 2019 and 31 October 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 22 August 2026 |
| Measurements held | 16 |
| Confirmed unchanged | 1 time, most recently 22 August 2026 |
| On Telegram | t.me/saltplayerupdate |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 22 Aug 2026, 19:13 | 17,099 | +12 |
| 21 Aug 2026, 11:54 | 17,087 | +2 |
| 20 Aug 2026, 08:36 | 17,085 | +9 |
| 19 Aug 2026, 07:24 | 17,076 | +7 |
| 18 Aug 2026, 09:48 | 17,069 | +1 |
| 17 Aug 2026, 10:55 | 17,068 | -2 |
| 15 Aug 2026, 20:24 | 17,070 | +6 |
| 14 Aug 2026, 09:57 | 17,064 | +3 |
| 13 Aug 2026, 01:16 | 17,061 | +9 |
| 12 Aug 2026, 00:12 | 17,052 | +2 |
| 11 Aug 2026, 03:08 | 17,050 | +4 |
| 10 Aug 2026, 05:21 | 17,046 | +11 |
| 9 Aug 2026, 06:42 | 17,035 | +9 |
| 8 Aug 2026, 03:17 | 17,026 | +6 |
| 7 Aug 2026, 05:30 | 17,020 | no change |
| 7 Aug 2026, 05:29 | 17,020 | first reading |
73 posts held, back to 1 August 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 33 pagesof Telegram’s post history, 20 posts per page.
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.
| Window | Rolling 30 days · latest post in window 22 August 2026 |
|---|---|
| Posts held | 73 (1 August 2026 – 22 August 2026) |
| Views total | 254,430 |
| Reactions total | 3,572 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 22 Aug 2026, 22:48 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.
Lifetime counters from Telegram’s own channel header, read 22 August 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.
3,572 reactions across 70 posts, in 1 kind.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 🎉 | 3,572 | 100.0% |
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 70 of the 73 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 3,572reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 73 most recent posts we hold, published 1 August 2026 to 22 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.
A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @saltplayerupdate. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.
Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.
This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.
Counted over the 73 most recent posts we hold for this entry, published 1 August 2026 to 22 August 2026. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.
嘿嘿,败家子又可以买新的了(
🎉57
估计蓝牙耳机落到滨江一个店里了,啊啊啊啊啊啊我真服了我自己
🎉27
升级了 HyperOS 4 Beta,接着挑挑系统 App 短信的刺 大小眼 O_o 反馈怎么没信息选项呢
🎉50
12.2.2-release-2026082101 优化软件稳定性
🎉43
Photo, posted without a caption
🎉40
SPW 1.17.0 版本微软商店渠道安装在非 C 盘会启动崩溃,正在解决中,涉及的东西有点多多多( 中午已经修复
🎉39
12.3.0-alpha02-2026081901 *对比 12.3.0-alpha01 新增迷你播放条至播放界面的封面过渡动画
🎉51
SPW 1.17.0 2026/8/19 - 新增 Morvanium 智能过渡 - 新增回放增益音量平衡支持(需要重新扫描音乐库) - 新增乌克兰语(Ukrainian)适配 - 新增添加 .spl 格式, 并同步 Android 端 .spl 优先 .lrc 回退的外部歌词读取支持 - 新增添加歌词获取顺序设置,支持拖拽调整歌词获取顺序 - 优化完善迷你播放条弧形进度交互 - 优化手动切歌播放流不终止保持流畅 - 优化适配艺术家 HUNTR/X 不分割 - 优化侧边栏调整拖拽滚动触发边距 - 修复音频流创建取消路径的句柄泄漏的问题 - 修复浮动迷你播放条透明区域阻断点击 - 修复 JUnique message exchange failed for lock 错误
🎉35
支付宝开源了 MYKMP https://github.com/MYKMP
🎉25
SaltVideo-0.1.1-2026081909-x64 架构优化提升稳定性 修复退出全屏卡死的问题
🎉33
我提到过我大一的时候,软件工程老师问我:“你觉得软件工程在用户需求阶段它应该是什么?”我回答说,应该要不断地去满足用户的各种需求来达到完美 她说我的想法不对,告诉我觉得学习的深入,会有不同的感受 这么多年来确实感受非常多,比如说很多用户会把他自己的一个需求放大成好像全世界人都有这个需求一样 我觉得有的时候我的个人意志或者主观性有点太强了。我对这个软件的控制,首先它要符合我自己的喜欢,那么用户的肯定是排在后方的,就当我自己的占比在里面 当然很多时候他有成本的考虑,如果这个小功能就一两个用户用,我为他投入的时间成本我觉得好像回报率太低了,那为什么要做呢 那么当这个流程已经完全搭建起来,而且我觉得单个的小功能点它的 AI 开发费率较低的话,那么完全可以做到 所以如果你对本软件有什么想法或者问题的反馈,都可以在仓库提交 issue。可能明天 AI 就扫描到了这个问题 我就做最后的把关就可以了(比如避免安装包膨胀 http…
🎉38
比如说这 5 个完全是 AI 决策驱动的,都有对应的仓库 issue 反馈 用户有拖拽排序歌曲的需求,以及用户有 ID3 标签头的文件 有的用户需要 SPL 特殊的扩展名支持来区分 LRC 以及最后两个也是用户的需求 通过这种方式,再经过我最后的 AI + 人工 Review 审核,便可以不断地迭代软件更新 “你不要去焦虑这个东西能不能完成,能不能做是 AI 的事情。” AI 这个工具要合理地使用,可以极大地提高开发效率,并且不断地改进可以让整个软件的开发体验越来越好。它并不会造成意外质量下降,而是一个更正向的反馈过程
🎉50
Showing the 12 most recent of 73 posts we hold for @saltplayerupdate. 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.
Stars beside a post are paid reactions — Telegram Stars, bought with money and spent on that post. They are a different unit from reactions and are never added to them, here or anywhere else on this page.
Citation-graph rank — 1,141,601 of 1,584,142entries 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.
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.
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.
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.
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 22 August 2026 — this entry's latest reading, not the date you are reading this.
“不要糖醋放椒盐” (@saltplayerupdate), 17,099 subscribers as measured 22 August 2026. Telegram Register, tgregister.com/channel/saltplayerupdate.
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.