New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Retrieve Current User's play History #20

Closed
sean1rose opened this Issue Mar 31, 2015 · 128 comments

Comments

Projects
None yet
@sean1rose

sean1rose commented Mar 31, 2015

Provide information on a user's recently played tracks, or in the alternative - provide info on recent/current listeners of a song.

@thelinmichael

This comment has been minimized.

Show comment
Hide comment
@thelinmichael

thelinmichael Apr 1, 2015

Contributor

Thanks for your feature request @sean1rose. There's an existing issue (#12) covering what track a user is currently listening to, so I think it'd be good to limit the scope of this issue to retrieving a user's recently played tracks.

Contributor

thelinmichael commented Apr 1, 2015

Thanks for your feature request @sean1rose. There's an existing issue (#12) covering what track a user is currently listening to, so I think it'd be good to limit the scope of this issue to retrieving a user's recently played tracks.

@sean1rose

This comment has been minimized.

Show comment
Hide comment
@sean1rose

sean1rose Apr 1, 2015

Ok Michael - I'm excited to see the feature implemented

On Wed, Apr 1, 2015 at 12:46 AM, Michael Thelin notifications@github.com
wrote:

Thanks for your feature request @sean1rose https://github.com/sean1rose.
There's an existing issue (#12
#12) covering what track a
user is currently listening to, so I think it'd be good to limit the scope
of this issue to retrieving a user's recently played tracks.


Reply to this email directly or view it on GitHub
#20 (comment).

Sean Rose
714.469.1796
sean1rose@gmail.com

sean1rose commented Apr 1, 2015

Ok Michael - I'm excited to see the feature implemented

On Wed, Apr 1, 2015 at 12:46 AM, Michael Thelin notifications@github.com
wrote:

Thanks for your feature request @sean1rose https://github.com/sean1rose.
There's an existing issue (#12
#12) covering what track a
user is currently listening to, so I think it'd be good to limit the scope
of this issue to retrieving a user's recently played tracks.


Reply to this email directly or view it on GitHub
#20 (comment).

Sean Rose
714.469.1796
sean1rose@gmail.com

@omasseau

This comment has been minimized.

Show comment
Hide comment
@omasseau

omasseau Apr 3, 2015

Supporting this.
It would be nice to be able to get play history of current user or followed users (would be a workaround to the useless friend feed of the 1.0.1 version of the desktop app).

omasseau commented Apr 3, 2015

Supporting this.
It would be nice to be able to get play history of current user or followed users (would be a workaround to the useless friend feed of the 1.0.1 version of the desktop app).

@DefV

This comment has been minimized.

Show comment
Hide comment
@DefV

DefV commented Apr 23, 2015

+1

@rjrahul

This comment has been minimized.

Show comment
Hide comment
@rjrahul

rjrahul commented Apr 27, 2015

+1

@ptlola

This comment has been minimized.

Show comment
Hide comment
@ptlola

ptlola commented Apr 27, 2015

+1

@ardixiv

This comment has been minimized.

Show comment
Hide comment
@ardixiv

ardixiv commented May 25, 2015

+1

@ghost

This comment has been minimized.

Show comment
Hide comment
@ghost

ghost commented May 26, 2015

+1

@Foorack

This comment has been minimized.

Show comment
Hide comment
@Foorack

Foorack commented Jun 6, 2015

+1

@thelinmichael thelinmichael changed the title from Play History Management - User's recently played tracks, or a track's current/recent listeners to Play History Management - User's recently played tracks Jun 24, 2015

@thelinmichael thelinmichael changed the title from Play History Management - User's recently played tracks to Play History Management - User's recently played tracks, albums, playlists Jun 24, 2015

@thelinmichael

This comment has been minimized.

Show comment
Hide comment
@thelinmichael

thelinmichael Jun 24, 2015

Contributor

I'm merging the scope of #68 with this issue with the aim of facilitating a discussion around what entity types (e.g. tracks, albums, artists, playlists.) are the most important for you.

Contributor

thelinmichael commented Jun 24, 2015

I'm merging the scope of #68 with this issue with the aim of facilitating a discussion around what entity types (e.g. tracks, albums, artists, playlists.) are the most important for you.

@ghost

This comment has been minimized.

Show comment
Hide comment
@ghost

ghost Jun 24, 2015

Great,

from a priority point of view imho its

  • artists
  • albums
  • tracks
  • playlists

thanks!

ghost commented Jun 24, 2015

Great,

from a priority point of view imho its

  • artists
  • albums
  • tracks
  • playlists

thanks!

@sean1rose

This comment has been minimized.

Show comment
Hide comment
@sean1rose

sean1rose Jun 25, 2015

All of them! But if you do need an order:

  1. Tracks
  2. Artists
  3. Playlists
  4. Albums

sean1rose commented Jun 25, 2015

All of them! But if you do need an order:

  1. Tracks
  2. Artists
  3. Playlists
  4. Albums
@ardixiv

This comment has been minimized.

Show comment
Hide comment
@ardixiv

ardixiv Jun 25, 2015

  1. track (artist + title)
  2. album
  3. playlist

ardixiv commented Jun 25, 2015

  1. track (artist + title)
  2. album
  3. playlist
@omasseau

This comment has been minimized.

Show comment
Hide comment
@omasseau

omasseau Jun 25, 2015

Same as the above:
1.Track (artist - title)
2.Album
3.Playlist

omasseau commented Jun 25, 2015

Same as the above:
1.Track (artist - title)
2.Album
3.Playlist

@marianolatorre

This comment has been minimized.

Show comment
Hide comment
@marianolatorre

marianolatorre commented Jun 30, 2015

+1

@jmilloy

This comment has been minimized.

Show comment
Hide comment
@jmilloy

jmilloy Jul 7, 2015

Also very interested in history or stats. I would like to be able to specify some sort of date range when request play counts.

Track stats are the most important/general, because we could figure out artist and album stats on our own if track stats were available.

jmilloy commented Jul 7, 2015

Also very interested in history or stats. I would like to be able to specify some sort of date range when request play counts.

Track stats are the most important/general, because we could figure out artist and album stats on our own if track stats were available.

@sregg

This comment has been minimized.

Show comment
Hide comment
@sregg

sregg commented Jul 7, 2015

+1

@johnthillaye

This comment has been minimized.

Show comment
Hide comment
@johnthillaye

johnthillaye commented Jul 8, 2015

+1

@mwpastore

This comment has been minimized.

Show comment
Hide comment
@mwpastore

mwpastore commented Jul 14, 2015

+1

@sreid8

This comment has been minimized.

Show comment
Hide comment
@sreid8

sreid8 commented Jul 30, 2015

+1

@sevy11

This comment has been minimized.

Show comment
Hide comment
@sevy11

sevy11 commented Aug 18, 2015

+1

@rakauchuk

This comment has been minimized.

Show comment
Hide comment
@rakauchuk

rakauchuk commented Aug 20, 2015

+1

@serafettin

This comment has been minimized.

Show comment
Hide comment
@serafettin

serafettin commented Sep 4, 2015

+1

@mmounirou

This comment has been minimized.

Show comment
Hide comment
@mmounirou

mmounirou commented Sep 6, 2015

+1

@phillycheeze

This comment has been minimized.

Show comment
Hide comment
@phillycheeze

phillycheeze commented Sep 14, 2015

+1

@airstrike

This comment has been minimized.

Show comment
Hide comment
@airstrike

airstrike Sep 11, 2017

+1 on the "all of my history" train. please let us resurrect LastGraph

airstrike commented Sep 11, 2017

+1 on the "all of my history" train. please let us resurrect LastGraph

@AlexSilR

This comment has been minimized.

Show comment
Hide comment
@AlexSilR

AlexSilR Oct 7, 2017

All history +1!

AlexSilR commented Oct 7, 2017

All history +1!

@newpatriks

This comment has been minimized.

Show comment
Hide comment
@newpatriks

newpatriks Oct 23, 2017

+1 on "all my history". Or at least an increase to 1k or 2k possible results on the recently played end point. 50 It's less than the music someone might listen in one or two days.

newpatriks commented Oct 23, 2017

+1 on "all my history". Or at least an increase to 1k or 2k possible results on the recently played end point. 50 It's less than the music someone might listen in one or two days.

@sr-ix

This comment has been minimized.

Show comment
Hide comment
@sr-ix

sr-ix Nov 30, 2017

give us the full history

sr-ix commented Nov 30, 2017

give us the full history

@aidos

This comment has been minimized.

Show comment
Hide comment
@aidos

aidos Dec 6, 2017

I'm assuming https://2017wrapped.com/ is just using the same api as the rest of us? (Though it looks like it's created by spotify) How come that has access to everything?

aidos commented Dec 6, 2017

I'm assuming https://2017wrapped.com/ is just using the same api as the rest of us? (Though it looks like it's created by spotify) How come that has access to everything?

@jscholes

This comment has been minimized.

Show comment
Hide comment
@jscholes

jscholes Dec 6, 2017

(Though it looks like it's created by spotify) How come that has access to everything?

You've just answered your own question there. The site uses a custom backend which returns the data that it needs, rather than accessing the Web API directly. It has access to everything because that's the access Spotify have given it.

jscholes commented Dec 6, 2017

(Though it looks like it's created by spotify) How come that has access to everything?

You've just answered your own question there. The site uses a custom backend which returns the data that it needs, rather than accessing the Web API directly. It has access to everything because that's the access Spotify have given it.

@seahorsepip

This comment has been minimized.

Show comment
Hide comment
@seahorsepip

seahorsepip Dec 6, 2017

@aidos
Spotify applications use closed source APIs them self that are not open to the public. Those APIs might even be RMI, SOAP, Socket etc instead of REST and not created for public use because of technical, legal, security and privacy reasons.

seahorsepip commented Dec 6, 2017

@aidos
Spotify applications use closed source APIs them self that are not open to the public. Those APIs might even be RMI, SOAP, Socket etc instead of REST and not created for public use because of technical, legal, security and privacy reasons.

@aidos

This comment has been minimized.

Show comment
Hide comment
@aidos

aidos Dec 6, 2017

Looking at the API docs there are now next / cursors returned — do they still not allow you to go beyond the 50 tracks?

"next": "https://api.spotify.com/v1/me/player/recently-played?before=1481661737016&limit=2",
  "cursors": {
    "after": "1481661844589",
    "before": "1481661737016"
  },
  "limit": 2,

aidos commented Dec 6, 2017

Looking at the API docs there are now next / cursors returned — do they still not allow you to go beyond the 50 tracks?

"next": "https://api.spotify.com/v1/me/player/recently-played?before=1481661737016&limit=2",
  "cursors": {
    "after": "1481661844589",
    "before": "1481661737016"
  },
  "limit": 2,
@seahorsepip

This comment has been minimized.

Show comment
Hide comment
@seahorsepip

seahorsepip Dec 6, 2017

@aidos
Last time I checked (~2months ago) those cursors where already there and didn't allow me to go beyond 50 tracks.

seahorsepip commented Dec 6, 2017

@aidos
Last time I checked (~2months ago) those cursors where already there and didn't allow me to go beyond 50 tracks.

@aidos

This comment has been minimized.

Show comment
Hide comment
@aidos

aidos Dec 6, 2017

@seahorsepip Looking a bit closer, it still looks limited.

It's so depressing that there are tracks I want to rediscover from the past year (and I've even noted down the rough dates I listened to them), but I'll never find again without Spotify lifting this pointless restriction.

aidos commented Dec 6, 2017

@seahorsepip Looking a bit closer, it still looks limited.

It's so depressing that there are tracks I want to rediscover from the past year (and I've even noted down the rough dates I listened to them), but I'll never find again without Spotify lifting this pointless restriction.

@jscholes

This comment has been minimized.

Show comment
Hide comment
@jscholes

jscholes Dec 6, 2017

It's so depressing that there are tracks I want to rediscover from the past year (and I've even noted down the rough dates I listened to them), but I'll never find again without Spotify lifting this pointless restriction.

It doesn't help you rediscover those tracks from 2017 and earlier, but this is one of the usecases that Last.fm is perfect for. I have detailed day-by-day listening history going back to 2008, across all applications which scrobble. Maybe set that up going into 2018?

jscholes commented Dec 6, 2017

It's so depressing that there are tracks I want to rediscover from the past year (and I've even noted down the rough dates I listened to them), but I'll never find again without Spotify lifting this pointless restriction.

It doesn't help you rediscover those tracks from 2017 and earlier, but this is one of the usecases that Last.fm is perfect for. I have detailed day-by-day listening history going back to 2008, across all applications which scrobble. Maybe set that up going into 2018?

@ndelnano

This comment has been minimized.

Show comment
Hide comment
@ndelnano

ndelnano commented Dec 8, 2017

+1

@steveculverwell

This comment has been minimized.

Show comment
Hide comment
@steveculverwell

steveculverwell Dec 8, 2017

I can just keep scrolling and scrolling on my youtube history and I dont pay a premium for that.

steveculverwell commented Dec 8, 2017

I can just keep scrolling and scrolling on my youtube history and I dont pay a premium for that.

@seahorsepip

This comment has been minimized.

Show comment
Hide comment
@seahorsepip

seahorsepip Dec 8, 2017

@steveculverwell
As end user you can also see more history then 50 tracks in the official apps, that doesn't mean that the developer API should offer the same data since the developer API is not just about your own account but also the accounts that use your app/service/etc and thus there are more privacy concerns to keep in mind.

seahorsepip commented Dec 8, 2017

@steveculverwell
As end user you can also see more history then 50 tracks in the official apps, that doesn't mean that the developer API should offer the same data since the developer API is not just about your own account but also the accounts that use your app/service/etc and thus there are more privacy concerns to keep in mind.

@DalerAsrorov

This comment has been minimized.

Show comment
Hide comment
@DalerAsrorov

DalerAsrorov Mar 3, 2018

"all of my history" please

DalerAsrorov commented Mar 3, 2018

"all of my history" please

@heharkon

This comment has been minimized.

Show comment
Hide comment
@heharkon

heharkon Mar 6, 2018

Per EU GDPR, as a data subject I want to have access to my complete play history.

And while we are at it, the API should also include the possibility to clear the history (consumer right for data erasure), thus it is necessary to be able to retrieve complete history also for verification purposes.

heharkon commented Mar 6, 2018

Per EU GDPR, as a data subject I want to have access to my complete play history.

And while we are at it, the API should also include the possibility to clear the history (consumer right for data erasure), thus it is necessary to be able to retrieve complete history also for verification purposes.

@seahorsepip

This comment has been minimized.

Show comment
Hide comment
@seahorsepip

seahorsepip Mar 6, 2018

@heharkon
Might sound like a good argument but this is not the correct place to make the argument.
The Web API gives access as developer to not just your account information but also everyone's account who's using your application.

So giving developers so much access to this privacy sensitive information which might be years of listening information with time stamps and everything would be actually a problem in the eye of EU privacy laws and the exact thing that the law should be protecting users from.

If you want full access to your own history in some exportable format (like Google search offers) then you should contact Spotify customers relations directly instead of it's developers and request them to add it to the user portal.

Increasing the limit a bit makes sense since 50 is just too low but full history access for 3rd party apps is just a big privacy issue for end users and might not even be feasible considering the different privacy regulations in countries the Spotify service is offered

seahorsepip commented Mar 6, 2018

@heharkon
Might sound like a good argument but this is not the correct place to make the argument.
The Web API gives access as developer to not just your account information but also everyone's account who's using your application.

So giving developers so much access to this privacy sensitive information which might be years of listening information with time stamps and everything would be actually a problem in the eye of EU privacy laws and the exact thing that the law should be protecting users from.

If you want full access to your own history in some exportable format (like Google search offers) then you should contact Spotify customers relations directly instead of it's developers and request them to add it to the user portal.

Increasing the limit a bit makes sense since 50 is just too low but full history access for 3rd party apps is just a big privacy issue for end users and might not even be feasible considering the different privacy regulations in countries the Spotify service is offered

@heharkon

This comment has been minimized.

Show comment
Hide comment
@heharkon

heharkon Mar 6, 2018

@seahorsepip
So basically you are saying that if the app developer would maliciously misuse the access token while the user has it active? But then I'd be more concerned about the much more immediate privacy related information that the third party could attain. Like email address, birth date, connections etc.

Of course it's all about trust between the client and the third party, and I think the Spotify authorization page doesn't do that good of a job informing the client about which scopes the app is applying the grant for.

heharkon commented Mar 6, 2018

@seahorsepip
So basically you are saying that if the app developer would maliciously misuse the access token while the user has it active? But then I'd be more concerned about the much more immediate privacy related information that the third party could attain. Like email address, birth date, connections etc.

Of course it's all about trust between the client and the third party, and I think the Spotify authorization page doesn't do that good of a job informing the client about which scopes the app is applying the grant for.

@Osherz5

This comment has been minimized.

Show comment
Hide comment
@Osherz5

Osherz5 Mar 22, 2018

+1 To all of my history

Osherz5 commented Mar 22, 2018

+1 To all of my history

@jayachithra

This comment has been minimized.

Show comment
Hide comment
@jayachithra

jayachithra Apr 9, 2018

+1 for all history !

jayachithra commented Apr 9, 2018

+1 for all history !

@grillinmuffins

This comment has been minimized.

Show comment
Hide comment
@grillinmuffins

grillinmuffins May 8, 2018

If you can't give us all playback history, can't we get some analytics?

  • Total Number of tracks listened to all time
  • Total Number of Tracks Listened for given date range
  • Number of tracks per category for given date range
  • Number of tracks listened by artist for given range
    etc. etc. etc.

Seems pretty ridiculous to not even have access to this high level information.

grillinmuffins commented May 8, 2018

If you can't give us all playback history, can't we get some analytics?

  • Total Number of tracks listened to all time
  • Total Number of Tracks Listened for given date range
  • Number of tracks per category for given date range
  • Number of tracks listened by artist for given range
    etc. etc. etc.

Seems pretty ridiculous to not even have access to this high level information.

@ruaanvds

This comment has been minimized.

Show comment
Hide comment
@ruaanvds

ruaanvds May 30, 2018

+1 for all history !

ruaanvds commented May 30, 2018

+1 for all history !

@NijsTom

This comment has been minimized.

Show comment
Hide comment
@NijsTom

NijsTom Jun 27, 2018

+1 for all history

NijsTom commented Jun 27, 2018

+1 for all history

@dandv

This comment has been minimized.

Show comment
Hide comment
@dandv

dandv Sep 19, 2018

The GDPR issue is quite serious. What needs to happen for Spotify to offer complete access to a user's play history? Hopefully not a lawsuit.

dandv commented Sep 19, 2018

The GDPR issue is quite serious. What needs to happen for Spotify to offer complete access to a user's play history? Hopefully not a lawsuit.

@seahorsepip

This comment has been minimized.

Show comment
Hide comment
@seahorsepip

seahorsepip Sep 19, 2018

The GDPR issue is quite serious. What needs to happen for Spotify to offer complete access to a user's play history? Hopefully not a lawsuit.

The Web API is primarily meant to be used to fetch data from other users.
Giving full access to the all data and history of Spotify users to 3rd party developers is not what the GDPR stands for.

As for the actual GDPR compliance in my experience:

  • Users can already access all their own data from the official Spotify apps which include a very long history list in recently played. Full history is indeed not available as far I've seen and a topic of discussion but has nothing to do with a 3rd party developer api.

  • As for deleting history, this is already possible by simply deleting your Spotify account.

I can understand 3rd party developers want more endpoints and more data but commething on every issue with +1 or even mentioning unrelated laws does not really help. Suggestions like @grillinmuffins gave above are atleast a good idea if Spotify decides to not up the 50 limit.

GDPR gives users the rights to control all their own data, it does not give 3rd party developers the right to control all the data of their users.

GDPR discussions should be held at the Spotify community forums or with Spotify Support, not on Github issues of an unrelated Web API for 3rd party developers.

Ideally there should be a history management page on the Spotify website to manage your own history similiar to what Facebook and Google offer in compliance with GDPR. But this is unrelated to this web API, GDPR does not demand that this data is available to 3rd party developers and/or trough a public API.

Feel free to correct me if I'm wrong, I'm just tired of getting unrelated email notifications while following this issue and wanted to clear up some confusion.

seahorsepip commented Sep 19, 2018

The GDPR issue is quite serious. What needs to happen for Spotify to offer complete access to a user's play history? Hopefully not a lawsuit.

The Web API is primarily meant to be used to fetch data from other users.
Giving full access to the all data and history of Spotify users to 3rd party developers is not what the GDPR stands for.

As for the actual GDPR compliance in my experience:

  • Users can already access all their own data from the official Spotify apps which include a very long history list in recently played. Full history is indeed not available as far I've seen and a topic of discussion but has nothing to do with a 3rd party developer api.

  • As for deleting history, this is already possible by simply deleting your Spotify account.

I can understand 3rd party developers want more endpoints and more data but commething on every issue with +1 or even mentioning unrelated laws does not really help. Suggestions like @grillinmuffins gave above are atleast a good idea if Spotify decides to not up the 50 limit.

GDPR gives users the rights to control all their own data, it does not give 3rd party developers the right to control all the data of their users.

GDPR discussions should be held at the Spotify community forums or with Spotify Support, not on Github issues of an unrelated Web API for 3rd party developers.

Ideally there should be a history management page on the Spotify website to manage your own history similiar to what Facebook and Google offer in compliance with GDPR. But this is unrelated to this web API, GDPR does not demand that this data is available to 3rd party developers and/or trough a public API.

Feel free to correct me if I'm wrong, I'm just tired of getting unrelated email notifications while following this issue and wanted to clear up some confusion.

@seahorsepip

This comment has been minimized.

Show comment
Hide comment
@seahorsepip

seahorsepip Sep 19, 2018

Update:

After some looking around I found that Spotify already offers a data export option at Download your data in compliance with GDPR.

So that means that Spotify is already GDPR compliant as far I can see.

seahorsepip commented Sep 19, 2018

Update:

After some looking around I found that Spotify already offers a data export option at Download your data in compliance with GDPR.

So that means that Spotify is already GDPR compliant as far I can see.

@pelmered

This comment has been minimized.

Show comment
Hide comment
@pelmered

pelmered Sep 19, 2018

@seahorsepip I've tried that, but you don't get the data in a good format that allows you gather your own analytics from that, at least not in an easy way.

pelmered commented Sep 19, 2018

@seahorsepip I've tried that, but you don't get the data in a good format that allows you gather your own analytics from that, at least not in an easy way.

@seahorsepip

This comment has been minimized.

Show comment
Hide comment
@seahorsepip

seahorsepip Sep 19, 2018

@pelmered
I haven't made an export yet using the tool, I'll make an export and (hopefully) receive the data soon so I can look into it, maybe I'll write a script that transforms the data into an easier format similar to the format returned by the endpoint related to this issue.

seahorsepip commented Sep 19, 2018

@pelmered
I haven't made an export yet using the tool, I'll make an export and (hopefully) receive the data soon so I can look into it, maybe I'll write a script that transforms the data into an easier format similar to the format returned by the endpoint related to this issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment