3 ms·

This is ironic because Spotify's playlist backend ("playlist4") is actually implemented as a distributed version control system with automatic conflict resoluti

This is ironic because Spotify's playlist backend ("playlist4") is actually implemented as a distributed version control system with automatic conflict resolution. This is what lets you edit the same playlist on multiple devices, some of which might be offline, and then have a consistent view once everything is synced. It's also what lets our CS staff revert and restore user playlists if there are any accidental or catastrophic changes. We've just never found the demand or a reasonable UI for exposing the underlying complexity to users.

z1mm32m4n 11y ago
We saw that note about how it's version controlled internally; we were actually planning to tap into it as we planned out the hack but realized it wasn't exposed in the API. We would have really loved a way to list all internal snapshots as wall as revert to one given a snapshot ID. Even if it's not exposed in the UI it'd be pretty cool if it was in the API. Also while we're at it, we would have loved to be able to listen to user-generated events (a la GitHub Webhooks).