How can an open source app get full-track playback approval?

[feoh]

Hi, I've written an open source terminal (TUI) TIDAL player: https://github.com/feoh/tidalbar

Right now, in compliance with the developer guidelines, it only plays official previews. I'd like it to be able to play full tracks for the logged-in user's account. What's the process for getting that approved, please?

Thanks!

[tomhandal]

Hi, I've written an open source terminal (TUI) TIDAL player: https://github.com/feoh/tidalbar

Right now, in compliance with the developer guidelines, it only plays official previews. I'd like it to be able to play full tracks for the logged-in user's account. What's the process for getting that approved, please?

Thanks!

I am hitting the same thing. A paying user not being able to playback a song and only having previews is a non-starter.

It seems that this is the position of Tidal and they will not allow the embedded player to play more than preview (so what is the point?).

Spotify and other service allow this. I don't think I will be able to support Tidal in this case. That is going to be to the detriment of Tidal unfortunately - which is too bad, because I like Tidal in general.

If we can get some direction on this, that would be great - but it seems several people have asked on here and there has been no answer. Support has also just redirected me here.

[feoh]

I can't speak to "Embedding" but I know other open source applications have gotten permission.

Witness high-tide, a very impressive TIDAL client for LInux:

https://github.com/Nokse22/high-tide

I get the feeling I posted to the wrong place. I'm going to start crawling LInkedIn to find a human I can, with exceeding politeness, ask about this :)

[tomhandal]

I e-mailed Tidal support and politely asked how to pursue the permission. They redirected me here. So, I am not sure what to do. Let me know if you make any headway. Thanks

[tomhandal]

@feoh - from what AI is saying - The project you referenced is not using the official API and is getting around it by doing this:

"Therefore, High Tide demonstrates that the user’s ordinary OAuth login can technically authorize full playback—but only when combined with TIDAL’s private mobile-client identity and post-paywall endpoint. It does not reveal a supported public OAuth configuration that you is missing. Adopting the same approach in your app would be fragile, expose private-client behavior in a web application, and conflict with TIDAL’s published developer restrictions."

So, sounds like a private workaround that probably isn't condoned by Tidal. I want to follow Tidal's rules, SDK, etc. - this project doesn't look like they are based on what I am reading (unless the AI is not explaining it well).