[GH-ISSUE #31] Remove songs in history #22

New issue

Closed

opened 2026-02-27 22:07:36 +03:00 by kerem · 2 comments

kerem commented

2026-02-27 22:07:36 +03:00

Owner

Originally created by @allanin on GitHub (Jun 24, 2020).
Original GitHub issue: https://github.com/sigma67/ytmusicapi/issues/31

According to Google songs played change the recommendation:

https://support.google.com/youtubemusic/thread/160722?hl=en

Would it be possible adding a delete_song_history() function?

Originally created by @allanin on GitHub (Jun 24, 2020). Original GitHub issue: https://github.com/sigma67/ytmusicapi/issues/31 According to Google songs played change the recommendation: https://support.google.com/youtubemusic/thread/160722?hl=en Would it be possible adding a delete_song_history() function?

kerem

2026-02-27 22:07:36 +03:00

closed this issue
added the
enhancement
label

kerem commented

2026-02-27 22:07:37 +03:00

Author

Owner

@sigma67 commented on GitHub (Jun 24, 2020):

Good suggestion. I implemented this feature locally (it uses the 'feedback' endpoint and it works fine.

However, I found that removing items from the history does not seem to be persisted. For example, try removing a watched item in your browser on music.youtube.com/history. It will disappear, but after reloading it will reappear again.

@sigma67 commented on GitHub (Jun 24, 2020): Good suggestion. I implemented this feature locally (it uses the 'feedback' endpoint and it works fine. However, I found that removing items from the history does not seem to be persisted. For example, try removing a watched item in your browser on music.youtube.com/history. It will disappear, but after reloading it will reappear again.

kerem commented

2026-02-27 22:07:37 +03:00

Author

Owner

@sigma67 commented on GitHub (Aug 27, 2020):

Regarding my previous comment, the persistence bug still exists. However, I discovered that it only occurs on brand accounts. It works fine on normal accounts.

@sigma67 commented on GitHub (Aug 27, 2020): Regarding my previous comment, the persistence bug still exists. However, I discovered that it only occurs on brand accounts. It works fine on normal accounts.