Skip to content

feat: TIDAL play-reporting #148

Open
lullabyX wants to merge 10 commits into
masterfrom
feat/tidal-play-reporting
Open

feat: TIDAL play-reporting #148
lullabyX wants to merge 10 commits into
masterfrom
feat/tidal-play-reporting

Conversation

@lullabyX

Copy link
Copy Markdown
Owner

Summary

Opt-in Report plays to TIDAL toggle (default on). On a full listen, sends a
playback_session event to TIDAL's Event Platform (ec.tidal.com/api/event-batch),
driven by the existing notify_track_* lifecycle with a streamingSessionId threaded
through the stream fetch.

Status: does not work — TIDAL drops the tracking

  • Events are sent and accepted (HTTP 200, no SenderFault)
  • Plays never surface in history. Attribution is gated on a first-party player client_id;
    SONE's community cid can stream but isn't a recognized player, so play_log ignores the events.
  • Legacy et.tidal.com (Option A) wouldn't help — same cid, same downstream gate.

State

Pipeline complete, builds clean (0 warnings), 69 tests pass. Kept open as a correct reference.

@lullabyX lullabyX added help wanted Extra attention is needed not feasible For feature requests that are not possible due to technical or other limitations labels Jun 15, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

help wanted Extra attention is needed not feasible For feature requests that are not possible due to technical or other limitations

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant