@cleeds Yes, the streaming protocol has a name - it's called TCP/IP and it ensures 100% packet delivery in order thanks to the use of caches, buffers, CRC error detection and retransmission. If your streaming efforts aren't time-sensitive, TCP can be advantageous for enabling the full bandwidth of a network and ensuring enhanced reliability. Amazon Prime, Qobuz, and Netflix use TCP as the transport layer protocol. YouTube on the other hand use both UDP and TCP protocols.
TIDAL uses TCP/IP to send encapsulated PCM data (as FLAC) from it's servers on the Internet to your PC/Mac. There is no concept of "jitter" while audio data is in this domain - the packets are received and reliably assembled into a PCM stream, buffered by your PC, and then sent to your DAC via the OS-specific audio layers (e.g. Core Audio for a Mac). While packets are sequenced, TCP/IP does NOT contain any temporal information, in that the packets are not associated with a time of arrival and associated re-transmit - it's completely asynchronous.
Until it's being sent to the DAC, timing simply does not matter. And, since just about all DACs receive PCM data via an asynchronous USB input, timing from the PC does not come into play either (i.e. there is no "jitter" here, either).
If you're live streaming - a Zoom call - UDP is considered the preferred protocol. UDP does not guarantee packet he other protocol used for streaming is delivery, but offers slightly greater throughput. User Datagram Protocol (UDP) is specifically chosen for time-sensitive applications like gaming, playing videos, or Domain Name System (DNS) lookups. It is not used for streaming music.