Open brodin opened 6 years ago
Thanks for the report, I'll look into it
What was the result of your investigation @hughrawlinson ?
Anything new about this? We've got the same issue here with some of spotify's official playlists.
I am also curious/disturbed by this. If you Base64decode you will notice that there are two parts to the SnapshotID separated with a ",". The first part changes continuously, the second part appears stable. Unclear for how long? I hav a feeling that the first part is some measure in seconds.
Hi, can you give some examples of playlists that exhibit this behavior? And can you explain a bit more about the impact this is having on your apps?
@hughrawlinson I am also experiencing the same behaviour. Here are some samples:
https://open.spotify.com/playlist/37i9dQZF1DX2S9rTKTX6JP https://open.spotify.com/playlist/37i9dQZF1DX76Wlfdnj7AP
If you base64 decode snapshot_id, it's a timestamp comma separated with some looks-like md5 value. Timestamp part keeps changing for each request. Both playlists seem to be from Spotify, however, I do not experience the same issue with other Spotify playlists in my account.
Thank you for looking into it and please keep us posted on the issue.
The
snapshot_id
for a playlist has previously been constant if there is no "change" to the playlist between two requests – this is no longer the case for playlists published by Spotify. Is this a bug or intentionally?Running the following request six times gives you different
snapshot_id
every time.Running it for any playlist not published via the
spotify
user gives you the samesnapshot_id
every time.