tidal-connect-docker VS node-openid-client

Tidal connect: meh. I have several issues with getting it to work. It simply isn't as good as Spotify Connect. Not sure why you can't control any playing devices from any device, maybe to sell more streamers, or have companies pay for the licensing? Last.fm scrobbling isn't integrated on the backend. There are workarounds and you can install local scrobblers for your android app and scrobbling works when controlling a stream via android, but it doesn't work from the desktop (i.e.: you need an instance of tidal running so a scrobbler can pick up the metadata). There are issues with scrobbling from time to time too, but this happens regardless of platform. There isn't an API that will allow all sorts of third party implementations and tools (i.e.: like a last.fm scrobbler that will scrobble regardless of playback source), or an open source client like Raspotify, that will allow a headless rasberrypi act as client. This isn't strictly true, there is a package for hifiberry, but in my experience it isn't really that stable (https://github.com/TonyTromp/tidal-connect-docker) and once again you run into issue that your tracks are not reliably sent to last.fm You can't drag playlists. This isn't a huge deal, but it is kind of annoying. I've had to resort to numbering them. It would also be really nice if you could add playlist images. It gives them a nice personalised touch, especially when your playlists contains albums. Visually, it is also hard to locate different albums when scrolling a playlist. This could be solved by displaying a tiny thumbnail of the track.

Heads up here - I use an HiFi Berry DSP DAC+, with HiFIBerry OS on a RPi4. It has an open source implementation of Tidal Connect (https://github.com/TonyTromp/tidal-connect-docker) and I'm very pleased with, both for audio quality and ease of use. However, a recent update of Tidal App on Android devices messed up the permissions for Tidal Connect. Similar issues were reported by Volumio users.

There's also a free hack if you don't mind a bit of faffing: https://www.raspberrypi.org/forums/viewtopic.php?t=297771 https://github.com/TonyTromp/tidal-connect-docker

Nearly all of the platforms implement OpenID, so I ended up rolling my own integration using openid-client to do the third party auth, and then on success, just set your own cookie.

There is quite a bit of hidden complexity to doing different flows. One approach to learning these is to use a lower level library (and perhaps review its code) such as the excellent openid-client.

I've successfully used this one in the past, specifically the Passport strategy. Based on a cursory search it seems like the best current option.