May be a joke, Yes!
But to get the current veryVeryFragile Spotify shuffle to play right and stop those infuriating repeats-- my friends tell me I should think of all of the Spotify misinformation in this discussion thread and similar work areas as OracleAtDelphi riddles-- lots of incredible life-saving wisdom written in riddles that don't make sense unless you put accurate measuring instruments-- such as last.fm-- on what the shuffle actually does as 1) repeats and 2) whether each and every track in a playlist is played before there is any repeat-- but those Spotify oracular clues like "in large playlists (over 150 songs)" and "we'd recommend to split playlists up" can be easily misunderstood-- You have to actually measure what triggers the onset of 1) repeats and 2) Spotify ignoring whole thousands of tracks in a 9000 track playlist that you try to shuffle. Let's take a look.
Here is the falsifiable hypothesis that my friends used to get me the perfect Spotify shuffle for Holiday Music that I ran on my desktop from November 01, 2022 to January 01, 2023 with never an undetected repeat as I ran the standard Spotify desktop shuffle as it shuffled the contents of a folder within which I had sub-folders of 1) Holiday music that repeated but randomly and 2) [pop, classical, blues, country, ... ] of which never a track repeated-- and I had a last.fm report that alerted me whenever the Spotify shuffle broke-- which was sometimes several times a day and sometimes several days without a glitch in the Spotify shuffle.
Falsfiable hypothesis: The Spotify shuffle works perfectly in 1) never a repeat until 2) every track has played-- if you force the Spotify shuffle to always [load the queue] with tracks that you have not played in the last 90 days.
So the way my friends advised me for the above falsifiable hypothesis-- as a ProofOfConcept for a NewIdea to actually fix the SpotifyShuffle-- was to break up the normal 90 day feed to my AllOfSpotify_Queue into small playlists as the Spotify oracle suggested-- remembering Yes!-- that oracle may be joking but apparently speaks incredible wisdom-- because when I implemented this breakup into small playlists in a manner that forced the Spotify shuffle to load the queue always with only tracks that I had not played in the last 90 days-- I got 1) zero repeats and 2) played each and every track in every playlist-- as long as I was successful in keeping both 1) me and 2) the partnership of [Microsoft & Apple & Firefox & Spotify] from doing something that broke irretrievably the current shuffle.
You can witness the current operation of the many small playlists revealed at the top of my public playlists as [ 01_SeriesOfSmallPlaylists, 02_, 03_1, 03_2, etc. ]-- a total of 14 small playlists that range in size from 1800 tracks to 6000 tracks-- So that-- whenever the veryVeryFragile_Spotify shuffle breaks irretrievably-- as detected by the last.fm report for the [most repeated tracks in the date range]-- I just instantiate a whole new Spotify shuffle that loads only the next "small" playlist in the cycle-- no track of which I have played in the last 90 days-- Of course, the [90 days] could be a setting under the SpotifyPlayer Settings-- Right?-- Are you with me? By construction then, the next small playlist in the cycle will contain only tracks that I have not played in the last 90 days-- so conseqently, the Spotify Shuffle will play perfectly until it breaks, right?
And ultimately, this ProofOfConcept should be programmed into the Spotify [LoadOfShuffledTracks to the queue]-- Specifically, the [LoadOfShuffledTracks to the queue] should put onto the queue only those tracks that, for example, are not displayed under the iPhone SpotifyHomeScreen, ClockInTheUpperRight, [RecentlyPlayed] tracks for the last [90 days] such that you could set the [AllowedRepeatTimeForShuffle] to [0] and get the Spotify Shuffle to load the queue the way it does now and keep repeating alreadyPlayed tracks when the veryVeryFragile_Spotify shuffle breaks the way that it does now.
Thus, we would be taking advantage of the current iPhone [RecentlyPlayed] display that collects the tracks that are played under, for example, the rednblu id on all devices-- DeskTop, iPhone, ChromeBrowser, FireFoxBrowser, EdgeBrowser, . . . . Is this true? What do you think?
