Account Banned, use at your own risk #29

Open
opened 2026-01-06 08:50:51 +00:00 by sliceable · 6 comments

Following the Anna Archive Spotify Backup, Spotify is actively looking against downloader accounts.
Mine has been banned yesterday.
This project should not use anything related to Spotify anymore, and rely only on other platform, or, use at your own risk.

Following the Anna Archive Spotify Backup, Spotify is actively looking against downloader accounts. Mine has been banned yesterday. This project should not use anything related to Spotify anymore, and rely only on other platform, or, use at your own risk.

Were you doing the real time downloading?

Were you doing the real time downloading?
Author

Real Time downloading, x3. I've been trying to fix some bugs on the app, so I was using it quite intensively, hence, maybe doing do much call to the API that could have been flagged. Maybe it's through the Librespot call. I've seen on their github that they had a lot of trouble recently with spotify moving to the new DRM system.

The retry was set to 0, but the app was still trying at least 3 times to fetch the data/trying to download

Real Time downloading, x3. I've been trying to fix some bugs on the app, so I was using it quite intensively, hence, maybe doing do much call to the API that could have been flagged. Maybe it's through the Librespot call. I've seen on their github that they had a lot of trouble recently with spotify moving to the new DRM system. The retry was set to 0, but the app was still trying at least 3 times to fetch the data/trying to download

@sliceable sorry to hear that. thanks for the info, heard about the Anna Archive project but didn't see how much they were cracking down after that. will be on the look out and seeing what updates can be made

i would rec creating a separate free account for the api creds and using that

@sliceable sorry to hear that. thanks for the info, heard about the Anna Archive project but didn't see how much they were cracking down after that. will be on the look out and seeing what updates can be made i would rec creating a separate free account for the api creds and using that

My account is still safe, but it's only a matter of time. AA decision to pirate all of the tracks from a global giant company was something else lol

@spotizerrphoenix I'm not sure how this works, but I've been using uimaxbai/tidal-ui and uimaxbai/hifi-api recently. They work wonders, and most of the independent artists I listen to are on Tidal as well. And interestingly, you don't need an account.

My account is still safe, but it's only a matter of time. AA decision to pirate all of the tracks from a global giant company was something else lol @spotizerrphoenix I'm not sure how this works, but I've been using [uimaxbai/tidal-ui](https://github.com/uimaxbai/tidal-ui) and [uimaxbai/hifi-api](https://github.com/uimaxbai/hifi-api) recently. They work wonders, and most of the independent artists I listen to are on Tidal as well. And interestingly, you don't need an account.

if it's any help, just made a new update to spotizerr-phoenix and spotizerr-auth-phoenix

if it's any help, just made a new update to spotizerr-phoenix and spotizerr-auth-phoenix - new release v0.0.15 of `spotizerr-auth-phoenix` will give you the ability to custom device info/name with preset defaults - includes logging for debugging purposes - full spotizerr-phoenix release notes: https://lavaforge.org/spotizerrphoenix/spotizerr-phoenix/releases/tag/v4.0.16

previously, the entire flow for spotizerr would pass defaults for device info/name which would use identifiers such as librespot and project-related info in names and system info for new download sessions.

latest updates to spotizerr-phoenix (v4.0.17), deezspot-spotizerr-phoenix, and spotizerr-auth-phoenix address this by:

  • https://lavaforge.org/spotizerrphoenix/spotizerr-phoenix/releases
  • allows you to set custom device info/types/name with preset defaults
  • stores that custom device from your auth flow in the /data/creds/blobs/{sp_profile_name}/device.json
    • this is then passed/used when creating new sessions for initiating downloads
  • upgrading to latest spotizerr-phoenix will auto backfill your existing sp profiles with custom default device info to automate this for you.
  • if you wish to use custom device info, recommended to delete your existing spotify auth profiles in the UI then re-authenticate with the latest spotizerr-auth-phoenix tool
  • after setting LOG_LEVEL=DEBUG in spotizerr-phoenix you should see logs in the console during downloads

Example Logs:

2026-01-25 12:00:00 [INFO] Search completed successfully for query: '{NAME_OF_SEARCH_QUERY}'
2026-01-25 12:00:01 [INFO] Using Spotify device info for '{SP_PROFILE_NAME}': name=Computer Speakers type=4 id=vZKjlBUe4OubGDfFbftsEe4fp0ofPDJRgMVl9nHb locale=SE
  • this is passed and happens before connecting with spotify
previously, the entire flow for spotizerr would pass defaults for device info/name which would use identifiers such as librespot and project-related info in names and system info for new download sessions. latest updates to spotizerr-phoenix (`v4.0.17`), deezspot-spotizerr-phoenix, and spotizerr-auth-phoenix address this by: - https://lavaforge.org/spotizerrphoenix/spotizerr-phoenix/releases - allows you to set custom device info/types/name with preset defaults - stores that custom device from your auth flow in the /data/creds/blobs/{sp_profile_name}/device.json - this is then passed/used when creating new sessions for initiating downloads - upgrading to latest spotizerr-phoenix will auto backfill your existing sp profiles with custom default device info to automate this for you. - if you wish to use custom device info, recommended to delete your existing spotify auth profiles in the UI then re-authenticate with the latest spotizerr-auth-phoenix tool - after setting LOG_LEVEL=DEBUG in spotizerr-phoenix you should see logs in the console during downloads Example Logs: ```bash 2026-01-25 12:00:00 [INFO] Search completed successfully for query: '{NAME_OF_SEARCH_QUERY}' 2026-01-25 12:00:01 [INFO] Using Spotify device info for '{SP_PROFILE_NAME}': name=Computer Speakers type=4 id=vZKjlBUe4OubGDfFbftsEe4fp0ofPDJRgMVl9nHb locale=SE ``` - this is passed and happens before connecting with spotify
Sign in to join this conversation.
No milestone
No project
No assignees
4 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
spotizerrphoenix/spotizerr-phoenix#29
No description provided.