Channel
@Deeplayer_AI
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
278subscribers
+0 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002625606932 |
|---|---|
| Type | Channel |
| Username | @Deeplayer_AI |
| Description | Deeplayer AI 播放器 |
| Created | Between 1 March 2025 and 21 July 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 8 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/Deeplayer_AI |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 8 Aug 2026, 08:34 | 278 | no change |
| 7 Aug 2026, 20:51 | 278 | first reading |
20 posts held, back to 21 July 2025 — 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 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 20 posts for this entry, the most recent from 31 January 2026. An engagement rate over an empty window would be a number about nothing.
Lifetime counters from Telegram’s own channel header, read 8 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.
42 reactions across 16 posts, in 8 distinct kinds. The most used accounts for 57.1% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 24 | 57.1% | |
| 👏 | 6 | 14.3% | |
| 🤔 | 3 | 7.14% | |
| 🤬 | 3 | 7.14% | |
| 🎉 | 2 | 4.76% | |
| 🔥 | 2 | 4.76% | |
| 👍 | 1 | 2.38% | |
| 😁 | 1 | 2.38% |
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 17 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 42reactions 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 21 July 2025 to 31 January 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.
之前订阅过DP的用户可以凭： Apple ID：(文本) Apple ID截图： (App Store 点击右上角，截图账户需要看到Apple ID) DP订阅购买历史截图： (App Store 点击右上角账户-购买历史 - DP订阅历史) 你的邮箱：(用于接收CP兑换码) 私聊提供给我/或者发送到 feifeiduck2026@gmail.com 确认验证后将发送CP兑换码到您的邮箱
👍1
📢 DP 开发进度与后续规划公告 近期我们将主要精力投入在 CapyPlayer（CP） 的开发与优化上，因此 DP 相关问题暂未能及时处理。 目前 CP 的相关工作预计将在 本月底 完成，感谢大家的理解与耐心等待。 以下为 DP 的后续规划说明： 一、功能调整说明 我们将对 APP 的功能定位进行重新划分。 媒体服用户 将优先推荐使用 CapyPlayer（CP），其在 性能、稳定性及功能支持 方面表现更优。 DP 后续将 移除媒体服相关功能，专注于自身核心定位。 作为补偿，我们将为 2026 年之前订阅 DP 的用户，免费发放 CP 对应的订阅兑换码，以保障您的使用权益。 二、后续开发计划 目前全新的技术框架已在 CapyPlayer（CP） 上完成验证。 该框架将在后续同步应用至 DP，为大家带来： 更强的整体性能 更美观、现代化的 UI 更丰富、更完善的功能体验 我们将持续推进产品优化，…
❤6😁1
DeePlayer pinned «新开发的卡皮巴拉播放器：专为媒体服优化，支持Emby、Plex、Jellyfin、飞牛影视，现支持IOS/安卓平台，大家有兴趣可以下载一个试试。官网： https://capyplayer.feifeiduck.com»
新开发的卡皮巴拉播放器：专为媒体服优化，支持Emby、Plex、Jellyfin、飞牛影视，现支持IOS/安卓平台，大家有兴趣可以下载一个试试。官网： https://capyplayer.feifeiduck.com
❤2
新做的媒体服的播放器客户 APP，已经更新到 iOS TF，使用媒体服务器的朋友可以试试！: https://testflight.apple.com/join/r3b5ZMVH
❤2
📢 关于暂时暂停 TV 端版本开发的公告 尊敬的用户们： 感谢你们一直以来对DeePlayer的支持与关注。 在过去一段时间里，我持续进行 DeePlayer TV端版本 的设计与开发，希望为用户带来更出色的大屏观看体验。 然而，在实际研发过程中，我们遇到了较多技术与兼容性问题，开发进度与预期存在一定差距。同时还有自己的工作需要完成。且还需要投入大量精力维护DeePlayer IOS/安卓应用的功能优化与稳定性。让我每天都十分焦虑，严重影响到了自己生活和工作。为了确保整体产品质量与后续规划的有序推进，经过慎重考虑，决定： 👉 暂时暂停 TV 端版本的开发工作。 这一决定并非终止，而是阶段性调整。后续将继续评估 TV 端的技术方案与用户需求，在条件成熟时再重新启动相关项目。 我们始终致力于为用户提供稳定、流畅的使用体验。非常感谢大家的理解与支持。 此外，如有用户因期待 TV 端版本上线而购买了订阅服务，请您联系我。将…
❤3
1.0.7 最新版本已经更新至TF，更新内容如下 * 支持用户登录 * 支持同账号订阅同步 * 字幕显示问题 * 活动促销展示 * 网盘重新添加文件夹会扫描全部已经添加的目录优化 * 替换logo * 使用指南 * 首页数据加载优化 * 刮削数据合并问题处理 * 媒体库页面优化 * 同一个影片出现媒体文件重复修复 * 首页继续播放和查看全部继续播放不一样问题修复 * 在网盘中删除的文件，同步后还是存在问题处理 * 长按屏幕倍数 如有问题，还请多多反馈 TF体验地址：https://testflight.apple.com/join/dAy9NtxH
❤2
iOS 1.0.7 版本已更新到 TF 测试。本次更新： 支持下载网盘视频 iOS26 进度条拖动崩溃问题 安装地址：https://testflight.apple.com/join/dAy9NtxH
❤1
安卓1.0.6版本已更新，大版本更新需到官网下载安装包更新：https://deeplayer.feifeiduck.com/zh/download 更新内容： * 浅色模式支持 * UI更新 * 对Plex/Emby/Jellyfin的支持优化 * 性能优化 * 多个bug修复 * 更多更新详情请到官网-更新日志中查看
👏1
IOS TF 1.0.6 版本已更新，可通过TF提前体验新功能： * 修复Plex自定义域名证书验证问题 * 修复多次弹出Apple帐号验证问题 * 详情页面增加外部链接 * 优化浅色/深色模式UI细节 * 升级内购框架，优化订阅逻辑 * 优化语言界面选择 * 重新设计首页UI，优化首页性能，支持切换数据来源 * 优化播放器性能 * 修复多处问题 TF安装地址：https://testflight.apple.com/join/dAy9NtxH
❤2
IOS TF 1.0.6 版本已更新，可通过TF提前体验新功能： * Plex 远程访问优化 * SMB 挂载优化 * 支持浅色主题模式 * 修改页面 UI TF安装地址：https://testflight.apple.com/join/dAy9NtxH
👏3
emby 买了影视服的用户，使用其它工具可以连接，DeePlayer 无法连接的情况，需要让你的影视服的客服添加 一下 DeePlayer 的 ua，才能允许 DeePlayer 连接：user-agent: DeePlayer/1.0.5
Showing the 12 most recent of 20 posts we hold for @Deeplayer_AI. 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 — 1,064,436 of 1,160,990entries 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.
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.
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 8 August 2026 — this entry's latest reading, not the date you are reading this.
“DeePlayer” (@Deeplayer_AI), 278 subscribers as measured 8 August 2026. Telegram Register, tgregister.com/channel/Deeplayer_AI.
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.