Feature Request: User Track Play Statistics
还没有人认领这个 Issue。
评估
- 难度
- 5/5
- 预计耗时
- 一周以上
- 新手友好度
- 38/100
- Issue 类型
- 功能
- 描述清晰度
- 基本清楚
- 活跃度
- 冷清
调研方向
Review the existing public API patterns for likes, playlists, follows, and OAuth scopes before assessing GET /me/track-stats. Done would require an agreed design for collecting and exposing play counts, listening time, timestamps, completion and replay metrics while enforcing explicit track-stats:read consent.
由索引模型根据 Issue 内容生成。
描述
Summary
Provide per-user listening statistics for tracks, including play counts and listening engagement metrics.
Proposed Endpoint
GET /me/track-stats
Example Response
{
"track_id": 12345,
"play_count": 47,
"total_listening_time_ms": 8923000,
"last_played_at": "2026-06-05T12:34:56Z",
"completion_rate": 0.91
}
Requested Data
- Number of times a user played a track
- Total listening time per track
- Last played timestamp
- Completion rate
- Replay count
Use Cases
Personal Analytics
Users can discover which tracks they actually listen to most, rather than relying on likes as a proxy.
Recommendation Engines
Play frequency often provides a much stronger signal of preference than likes alone.
Music Compatibility Apps
Comparing shared listening behavior becomes much more meaningful when based on actual engagement rather than saved tracks.
DJ & Playlist Tools
Developers can identify tracks that consistently receive high replay rates and engagement.
Why This Matters
Currently, developers can access likes, playlists, and follows, but cannot determine which tracks users truly engage with. A track played 50 times and a track played once appear identical through the current API.
Exposing listening statistics would unlock a richer ecosystem of analytics, recommendation, and discovery applications while remaining compatible with OAuth-based user consent.
Privacy
Access should require explicit OAuth authorization, for example:
track-stats:read
- 主要语言
- JavaScript
- 星标
- 256
- 派生
- 53
- 平均合并
- 1 分钟
- 30 天内合并 PR
- 1
环境准备
这个项目没有提供开发容器、Dockerfile 或贡献指南，环境需要你自己搭建：先看它的 README，通用步骤见我们的新手贡献指南。
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
soundcloud/api 的其他 Issue
-
难度 4/5 半天 新手友好度 8/100
soundcloud/api#598 · 2 条评论 ·
-
enhancement
难度 5/5 一周以上 新手友好度 25/100
soundcloud/api#597 ·
-
enhancement
难度 4/5 3-5 天 新手友好度 40/100
soundcloud/api#596 · 2 条评论 ·
-
question
难度 4/5 3-5 天 新手友好度 45/100
soundcloud/api#595 · 4 条评论 ·
-
documentation
难度 4/5 3-5 天 新手友好度 45/100
soundcloud/api#583 · 1 条评论 · 1 个 reaction ·
相似的 Issue
-
[Bug] Composer can submit an IME confirmation when keyCode is 229 but isComposing is false可能已有人在做 关联的 PR 仍在进行中或已合并。 未关闭
难度 2/5 1-3 小时 新手友好度 72/100
apache/rocketmq-dashboard#6067 ·
维护者通常 4 天内回复
-
severity: low
难度 2/5 1-3 小时 新手友好度 70/100
luainkernel/lunatik#1853 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 62/100
维护者通常 1 天内回复
-
factory-active factory-automatic harness/claude-code task-identify-harness-labels-done task-identify-issue-type-done
难度 2/5 1-3 小时 新手友好度 62/100
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 62/100
维护者通常 1 天内回复