PyPI - spotify-profile-monitor - Versions diffs - 3.0__tar.gz → 3.2__tar.gz - Mend

spotify-profile-monitor 3.0tar.gz → 3.2tar.gz

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.

Files changed (12) hide show

{spotify_profile_monitor-3.0/spotify_profile_monitor.egg-info → spotify_profile_monitor-3.2}/PKG-INFO RENAMED Viewed

@@ -1,7 +1,7 @@
 Metadata-Version: 2.4
 Name: spotify_profile_monitor
-Version: 3.0
-Summary: Tool implementing real-time tracking of Spotify users activities and profile changes including playlists
+Version: 3.2
+Summary: Track Spotify profile, follower and playlist changes in real time
 Author-email: Michal Szymanski <misiektoja-pypi@rm-rf.ninja>
 License-Expression: GPL-3.0-or-later
 Project-URL: Homepage, https://github.com/misiektoja/spotify_profile_monitor
@@ -9,6 +9,15 @@ Project-URL: Source, https://github.com/misiektoja/spotify_profile_monitor
 Project-URL: Changelog, https://github.com/misiektoja/spotify_profile_monitor/blob/main/RELEASE_NOTES.md
 Keywords: spotify,monitoring,tracking,real-time,playlists,osint
 Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3.6
+Classifier: Programming Language :: Python :: 3.7
+Classifier: Programming Language :: Python :: 3.8
+Classifier: Programming Language :: Python :: 3.9
+Classifier: Programming Language :: Python :: 3.10
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Programming Language :: Python :: 3.13
+Classifier: Programming Language :: Python :: 3.14
 Classifier: Operating System :: OS Independent
 Classifier: Operating System :: Microsoft :: Windows
 Classifier: Operating System :: POSIX :: Linux
@@ -29,38 +38,61 @@ Dynamic: license-file
 # spotify_profile_monitor
-OSINT tool for real-time monitoring of **Spotify users' activities and profile changes including playlists**.
+<p align="left">
+  <img src="https://img.shields.io/github/v/release/misiektoja/spotify_profile_monitor?style=flat-square&color=blue" alt="GitHub Release" />
+  <img src="https://img.shields.io/pypi/v/spotify_profile_monitor?style=flat-square&color=teal" alt="PyPI Version" />
+  <img src="https://img.shields.io/github/stars/misiektoja/spotify_profile_monitor?style=flat-square&color=magenta" alt="GitHub Stars" />
+  <img src="https://img.shields.io/badge/python-3.6+-blueviolet?style=flat-square" alt="Python Versions" />
+  <img src="https://img.shields.io/github/license/misiektoja/spotify_profile_monitor?style=flat-square&color=blue" alt="License" />
+  <img src="https://img.shields.io/github/last-commit/misiektoja/spotify_profile_monitor?style=flat-square&color=green" alt="Last Commit" />
+  <img src="https://img.shields.io/badge/maintenance-active-brightgreen?style=flat-square" alt="Maintenance" />
+</p>
-✨ If you want to track Spotify friends' music activity, check out another tool I developed: [spotify_monitor](https://github.com/misiektoja/spotify_monitor).
+Powerful Spotify tool for real-time tracking of profile changes, playlist updates, follower growth, collaborators and more - delivered straight to your terminal or inbox.
-🛠️ If you're looking for debug tools to get Spotify Web Player access tokens and extract secret keys: [click here](#debugging-tools)
+### 🚀 Quick Install
+```sh
+pip install spotify_profile_monitor
+```
+<p align="center">
+   <img src="https://raw.githubusercontent.com/misiektoja/spotify_profile_monitor/refs/heads/main/assets/spotify_profile_monitor.png" alt="spotify_profile_monitor_screenshot" width="90%"/>
+</p>
 <a id="features"></a>
 ## Features
-- **Real-time tracking** of Spotify user activities and profile changes:
-   - addition/removal of **followings and followers**
-   - addition/removal of **playlists**
-   - addition/removal of **tracks in playlists** (including collaborator info for newly added tracks)
-   - **playlists name and description** changes
-   - **number of likes** for playlists
-   - **number of collaborators** for playlists
-   - **profile picture** changes
-   - **username** changes
-- **Email notifications** for various events (as listed above)
-- **Attaching changed profile pictures** directly to email notifications
-- **Displaying the profile picture** right in your terminal (if you have `imgcat` installed)
-- Additional functionalities on top of the monitoring mode allowing to display **detailed info about the user**, **list of followers & followings**, **recently played artists** and possibility to **search for users** in Spotify catalog with specific names
-- Ability to **display and export** the list of tracks for a specific playlist (including **Liked Songs** for the user who owns the Spotify access token)
-- **Saving all profile changes** (including playlists) with timestamps to the **CSV file**
-- **Clickable** **Spotify**, **Apple Music**, **YouTube Music**, **Amazon Music**, **Deezer**, **Tidal**, **Genius Lyrics**, **AZLyrics**, **Tekstowo.pl**, **Musixmatch** and **Lyrics.com** search URLs printed in the console and included in email notifications (configurable per service)
-- Support for **four different methods to get a Spotify access token** (`sp_dc cookie`, `desktop client`, `OAuth app`, `OAuth user`)
-- Possibility to **control the running copy** of the script via signals
-- **Functional, procedural Python** (minimal OOP)
+### 👤 Profile Monitoring
+- **Real-time tracking**: Monitor Spotify user activities and profile changes.
+- **Social Network**: Detect addition/removal of **followings** and **followers**.
+- **Identity Changes**: Track **profile picture** and **username** changes.
+### 📜 Playlist Tracking
+- **Content Updates**: Monitor addition/removal of **tracks in playlists**.
+- **Collaborator Info**: Identify who added which track in **collaborative playlists**.
+- **Social Proof**: Monitor **likes** and **collaborators** count for playlists.
+- **Metadata**: Track **name** and **description** changes.
+### 📊 Advanced Tools
+- **Deep Insights**: Display detailed info about users, followers and followings.
+- **Historical Data**: View **recently played artists** and **search for users** by name.
+- **Export Power**: Display and export tracks from any playlist (including **Liked Songs**).
+- **Global Search**: Instant links to **Spotify, YouTube Music, Apple Music, Tidal, lyrics** and more.
+### 🔔 Smart Interactions
+- **Instant Alerts**: Detailed **Email notifications** for all profile and playlist changes.
+- **Visual Reports**: Attach changed profile pictures directly to emails.
+- **Terminal Graphics**: Display profile pictures right in your terminal (via `imgcat`).
+### ⚙️ Power Features
+- **Auth Flexibility**: Hybrid support for `sp_dc` cookie, Desktop Client and OAuth.
+- **CSV Logging**: Save all changes with full timestamps to a CSV file.
+- **Flexible Config**: Support for files, dotenv and environment variables.
+- **Signal Control**: Manage the running script via system signals (`SIGHUP`, `USR1`, etc.).
-<p align="center">
-   <img src="https://raw.githubusercontent.com/misiektoja/spotify_profile_monitor/refs/heads/main/assets/spotify_profile_monitor.png" alt="spotify_profile_monitor_screenshot" width="100%"/>
-</p>
+✨ If you want to track Spotify friends' music activity, check out another tool I developed: [spotify_monitor](https://github.com/misiektoja/spotify_monitor).
+🛠️ If you're looking for debug tools to get Spotify Web Player access tokens and extract secret keys: [click here](#debugging-tools)
 <a id="table-of-contents"></a>
 ## Table of Contents
@@ -156,17 +188,16 @@ If you installed manually, download the newest *[spotify_profile_monitor.py](htt
 <a id="quick-start"></a>
 ## Quick Start
-- Grab your [Spotify sp_dc cookie](#spotify-sp_dc-cookie) and track the `spotify_user_uri_id` profile changes (including playlists):
+- Grab your [Spotify sp_dc cookie](#spotify-sp_dc-cookie), set up [OAuth app credentials](#spotify-oauth-app) and track the `spotify_user_uri_id` profile changes (including playlists):
 ```sh
-spotify_profile_monitor <spotify_user_uri_id> -u "your_sp_dc_cookie_value"
+spotify_profile_monitor <spotify_user_uri_id> -u "your_sp_dc_cookie_value" -r "your_spotify_app_client_id:your_spotify_app_client_secret"
 ```
 Or if you installed [manually](#manual-installation):
 ```sh
-python3 spotify_profile_monitor.py <spotify_user_uri_id> -u "your_sp_dc_cookie_value"
+python3 spotify_profile_monitor.py <spotify_user_uri_id> -u "your_sp_dc_cookie_value" -r "your_spotify_app_client_id:your_spotify_app_client_secret"
 ```
 To get the list of all supported command-line arguments / flags:
@@ -186,12 +217,19 @@ Most settings can be configured via command-line arguments.
 If you want to have it stored persistently, generate a default config template and save it to a file named `spotify_profile_monitor.conf`:
 ```sh
+# On macOS, Linux or Windows Command Prompt (cmd.exe)
 spotify_profile_monitor --generate-config > spotify_profile_monitor.conf
+# On Windows PowerShell (recommended to avoid encoding issues)
+spotify_profile_monitor --generate-config spotify_profile_monitor.conf
 ```
+> **IMPORTANT**: On **Windows PowerShell**, using redirection (`>`) can cause the file to be encoded in UTF-16, which will lead to "null bytes" errors when running the tool. It is highly recommended to provide the filename directly as an argument to `--generate-config` to ensure UTF-8 encoding.
 Edit the `spotify_profile_monitor.conf` file and change any desired configuration options (detailed comments are provided for each).
+**New in v3.1:** The tool now uses a hybrid authentication approach. OAuth app credentials (`SP_APP_CLIENT_ID`, `SP_APP_CLIENT_SECRET`) are required for playlist and user information retrieval when using either `cookie` or `client` token source methods. See [Spotify OAuth App](#spotify-oauth-app) section for setup instructions.
 **New in v2.9:** The configuration file includes options to enable/disable music service URLs (Apple Music, YouTube Music, Amazon Music, Deezer, Tidal) and lyrics service URLs (Genius, AZLyrics, Tekstowo.pl, Musixmatch, Lyrics.com) in console and email outputs.
 <a id="spotify-access-token-source"></a>
@@ -199,16 +237,23 @@ Edit the `spotify_profile_monitor.conf` file and change any desired configuratio
 The tool supports four methods for obtaining a Spotify access token.
-It can be configured via the `TOKEN_SOURCE` configuration option or the `--token-source` flag.
+When you decide to use the `cookie` or `client` token source method, the tool uses a **hybrid authentication approach** and you also need to configure **OAuth app credentials** (`SP_APP_CLIENT_ID`, `SP_APP_CLIENT_SECRET`) for playlist and user information retrieval as described in [Spotify OAuth App](#spotify-oauth-app).
+The token source method can be configured via the `TOKEN_SOURCE` configuration option or the `--token-source` flag.
 **Recommended: `cookie`**
 Uses the `sp_dc` cookie to retrieve a token from the Spotify web endpoint. This method is easy to set up and supports all features except fetching the list of liked tracks for the account that owns the access token (due to recent Spotify token's scope restrictions).
+Since version 3.1, due to Spotify restrictions introduced on December 22, 2025, it no longer shows other users' playlists added to a user's profile unless the user is a collaborator on a playlist owned by another user.
 **Alternative: `client`**
 Uses captured credentials from the Spotify desktop client and a Protobuf-based login flow. It's more complex to set up, but supports all features. This method is intended for advanced users who want a long-lasting token with the broadest possible access.
+Since version 3.1, due to Spotify restrictions introduced on December 22, 2025, it no longer shows other users' playlists added to a user's profile unless the user is a collaborator on a playlist owned by another user.
 **Safe fallback: `oauth_app`**
 Relies on the official Spotify Web API (Client Credentials OAuth flow). This method is easy to set up and safe to use, but has several limitations. The following features are **not** supported:
@@ -263,7 +308,7 @@ If your `sp_dc` cookie expires, the tool will notify you via the console and ema
 If you store the `SP_DC_COOKIE` in a dotenv file you can update its value and send a `SIGHUP` signal to reload the file with the new `sp_dc` cookie without restarting the tool. More info in [Storing Secrets](#storing-secrets) and [Signal Controls (macOS/Linux/Unix)](#signal-controls-macoslinuxunix).
-> **NOTE:** secrets used for TOTP generation (`SECRET_CIPHER_DICT`) expire every two days, that's why since v2.7 the tool fetches it from remote URL (see `SECRET_CIPHER_DICT_URL`); you can also run the [spotify_monitor_secret_grabber](https://github.com/misiektoja/spotify_monitor/blob/dev/debug/spotify_monitor_secret_grabber.py) and extract it by yourself (see [Secret Key Extraction from Spotify Web Player Bundles](#secret-key-extraction-from-spotify-web-player-bundles) for more info).
+> **NOTE:** secrets used for TOTP generation (`SECRET_CIPHER_DICT`) expire every few days, that's why since v2.7 the tool fetches it from remote URL (see `SECRET_CIPHER_DICT_URL`); you can also run the [spotify_monitor_secret_grabber](https://github.com/misiektoja/spotify_monitor/blob/dev/debug/spotify_monitor_secret_grabber.py) and extract it by yourself (see [Secret Key Extraction from Spotify Web Player Bundles](#secret-key-extraction-from-spotify-web-player-bundles) for more info).
 <a id="spotify-desktop-client"></a>
 #### Spotify Desktop Client
@@ -318,39 +363,42 @@ Advanced options are available for further customization - refer to the configur
 <a id="spotify-oauth-app"></a>
 #### Spotify OAuth App
+Can be used as a standalone mode, but also as a secondary mode to either a `cookie` or `client` token source method to retrieve playlist and user information (required due to restrictions introduced by Spotify on December 22, 2025).
 This method uses an official Spotify Web API (Client Credentials OAuth flow).
-- Log in to Spotify Developer dashboard: https://developer.spotify.com/dashboard
+To obtain the credentials:
+- Log in to [Spotify Developer dashboard](https://developer.spotify.com/dashboard)
 - Create a new app
-- For **Redirect URL**, use: http://127.0.0.1:1234
-   - The URL must match exactly as shown, including not having a / at the end
-   - When copying the link via right-click, some browsers may add an extra / to the URL
+- For **Redirect URL**, use: `http://127.0.0.1:1234`
+   - The URL must match exactly as shown, including not having a `/` at the end
+   - When copying the link via right-click, some browsers may add an extra `/` to the URL
 - Select **Web API** as the intended API
 - Copy the **Client ID** and **Client Secret**
 - Provide the `SP_APP_CLIENT_ID` and `SP_APP_CLIENT_SECRET` secrets using one of the following methods:
-   - Pass it at runtime with `-r` / `--oauth-app-creds`
-      - Use `SP_APP_CLIENT_ID`:`SP_APP_CLIENT_SECRET` format - note the colon separator
+   - Pass it at runtime with `-r` / `--oauth-app-creds` (use `SP_APP_CLIENT_ID:SP_APP_CLIENT_SECRET` format - note the colon separator)
    - Set it as an [environment variable](#storing-secrets) (e.g. `export SP_APP_CLIENT_ID=...; export SP_APP_CLIENT_SECRET=...`)
    - Add it to [.env file](#storing-secrets) (`SP_APP_CLIENT_ID=...` and `SP_APP_CLIENT_SECRET=...`) for persistent use
    - Fallback: hard-code it in the code or config file
-You can use the same client ID and secret values as those used for the [Spotify OAuth User](#spotify-oauth-user).
 Example:
 ```sh
 spotify_profile_monitor --token-source oauth_app -r "your_spotify_app_client_id:your_spotify_app_client_secret" <spotify_user_uri_id>
 ```
-The tool takes care of refreshing the access token so it should remain valid indefinitely.
+The tool automatically refreshes the OAuth app access token, so it remains valid indefinitely. Tokens are cached in the file specified by `SP_APP_TOKENS_FILE` configuration option (default: `.spotify-profile-monitor-oauth-app.json`).
 If you store the `SP_APP_CLIENT_ID` and `SP_APP_CLIENT_SECRET` in a dotenv file you can update their values and send a `SIGHUP` signal to reload the file with the new secret values without restarting the tool. More info in [Storing Secrets](#storing-secrets) and [Signal Controls (macOS/Linux/Unix)](#signal-controls-macoslinuxunix).
+You can also use this method as a standalone token source (without `cookie` or `client`) by setting `TOKEN_SOURCE` to `oauth_app`, but this has several limitations as described in the [Spotify access token source](#spotify-access-token-source) section.
 <a id="spotify-oauth-user"></a>
 #### Spotify OAuth User
@@ -529,6 +577,14 @@ If you use the default method to obtain a Spotify access token (`cookie`) and ha
 spotify_profile_monitor <spotify_user_uri_id> -u "your_sp_dc_cookie_value"
 ```
+**Note:** OAuth app credentials are now required for playlist and user information retrieval. If you haven't set `SP_APP_CLIENT_ID` and `SP_APP_CLIENT_SECRET` via environment variables or `.env` file, you can use the `-r` flag:
+```sh
+spotify_profile_monitor <spotify_user_uri_id> -u "your_sp_dc_cookie_value" -r "your_spotify_app_client_id:your_spotify_app_client_secret"
+```
+See [Spotify OAuth App](#spotify-oauth-app) for detailed setup instructions.
 By default, the tool looks for a configuration file named `spotify_profile_monitor.conf` in:
  - current directory
  - home directory (`~`)
@@ -661,12 +717,6 @@ If you want to display a list of recently played artists (this feature only work
 spotify_profile_monitor <spotify_user_uri_id> -a
 ```
-To get basic information about the Spotify access token owner (`-v` flag):
-```sh
-spotify_profile_monitor -v
-```
 If you want to search the Spotify catalog for users with a specific name to obtain their Spotify user URI ID (`-s` flag):
 ```sh
@@ -873,7 +923,7 @@ You should get a valid Spotify access token, example output:
    <img src="https://raw.githubusercontent.com/misiektoja/spotify_monitor/refs/heads/main/assets/spotify_monitor_totp_test.png" alt="spotify_monitor_totp_test" width="100%"/>
 </p>
-> **NOTE:** secrets used for TOTP generation (`SECRET_CIPHER_DICT`) expire every two days; you can either run the [spotify_monitor_secret_grabber](https://github.com/misiektoja/spotify_monitor/blob/dev/debug/spotify_monitor_secret_grabber.py) and extract it by yourself (see [here](#secret-key-extraction-from-spotify-web-player-bundles) for more info) or you can pass `--fetch-secrets` flag in `spotify_monitor_totp_test` (available since v1.6). There is also a [xyloflake/spot-secrets-go/](https://github.com/xyloflake/spot-secrets-go/) repo which offers JSON files that are automatically updated with current secrets (you can pass `--download-secrets` flag in `spotify_monitor_totp_test` to get it automatically from remote URL, available since v1.8).
+> **NOTE:** secrets used for TOTP generation (`SECRET_CIPHER_DICT`) expire every few days; you can either run the [spotify_monitor_secret_grabber](https://github.com/misiektoja/spotify_monitor/blob/dev/debug/spotify_monitor_secret_grabber.py) and extract it by yourself (see [here](#secret-key-extraction-from-spotify-web-player-bundles) for more info) or you can pass `--fetch-secrets` flag in `spotify_monitor_totp_test` (available since v1.6). There is also a [xyloflake/spot-secrets-go/](https://github.com/xyloflake/spot-secrets-go/) repo which offers JSON files that are automatically updated with current secrets (you can pass `--download-secrets` flag in `spotify_monitor_totp_test` to get it automatically from remote URL, available since v1.8).
 <a id="secret-key-extraction-from-spotify-web-player-bundles"></a>
 ### Secret Key Extraction from Spotify Web Player Bundles

spotify_profile_monitor-3.0/PKG-INFO → spotify_profile_monitor-3.2/README.md RENAMED Viewed

@@ -1,66 +1,60 @@
-Metadata-Version: 2.4
-Name: spotify_profile_monitor
-Version: 3.0
-Summary: Tool implementing real-time tracking of Spotify users activities and profile changes including playlists
-Author-email: Michal Szymanski <misiektoja-pypi@rm-rf.ninja>
-License-Expression: GPL-3.0-or-later
-Project-URL: Homepage, https://github.com/misiektoja/spotify_profile_monitor
-Project-URL: Source, https://github.com/misiektoja/spotify_profile_monitor
-Project-URL: Changelog, https://github.com/misiektoja/spotify_profile_monitor/blob/main/RELEASE_NOTES.md
-Keywords: spotify,monitoring,tracking,real-time,playlists,osint
-Classifier: Programming Language :: Python :: 3
-Classifier: Operating System :: OS Independent
-Classifier: Operating System :: Microsoft :: Windows
-Classifier: Operating System :: POSIX :: Linux
-Classifier: Operating System :: MacOS :: MacOS X
-Requires-Python: >=3.6
-Description-Content-Type: text/markdown
-License-File: LICENSE
-Requires-Dist: requests>=2.0
-Requires-Dist: python-dateutil>=2.8
-Requires-Dist: urllib3>=2.0.7
-Requires-Dist: pyotp>=2.9.0
-Requires-Dist: pytz>=2020.1
-Requires-Dist: tzlocal>=4.0
-Requires-Dist: python-dotenv>=0.19
-Requires-Dist: spotipy>=2.24.0
-Requires-Dist: wcwidth>=0.2.7
-Dynamic: license-file
 # spotify_profile_monitor
-OSINT tool for real-time monitoring of **Spotify users' activities and profile changes including playlists**.
+<p align="left">
+  <img src="https://img.shields.io/github/v/release/misiektoja/spotify_profile_monitor?style=flat-square&color=blue" alt="GitHub Release" />
+  <img src="https://img.shields.io/pypi/v/spotify_profile_monitor?style=flat-square&color=teal" alt="PyPI Version" />
+  <img src="https://img.shields.io/github/stars/misiektoja/spotify_profile_monitor?style=flat-square&color=magenta" alt="GitHub Stars" />
+  <img src="https://img.shields.io/badge/python-3.6+-blueviolet?style=flat-square" alt="Python Versions" />
+  <img src="https://img.shields.io/github/license/misiektoja/spotify_profile_monitor?style=flat-square&color=blue" alt="License" />
+  <img src="https://img.shields.io/github/last-commit/misiektoja/spotify_profile_monitor?style=flat-square&color=green" alt="Last Commit" />
+  <img src="https://img.shields.io/badge/maintenance-active-brightgreen?style=flat-square" alt="Maintenance" />
+</p>
-✨ If you want to track Spotify friends' music activity, check out another tool I developed: [spotify_monitor](https://github.com/misiektoja/spotify_monitor).
+Powerful Spotify tool for real-time tracking of profile changes, playlist updates, follower growth, collaborators and more - delivered straight to your terminal or inbox.
-🛠️ If you're looking for debug tools to get Spotify Web Player access tokens and extract secret keys: [click here](#debugging-tools)
+### 🚀 Quick Install
+```sh
+pip install spotify_profile_monitor
+```
+<p align="center">
+   <img src="https://raw.githubusercontent.com/misiektoja/spotify_profile_monitor/refs/heads/main/assets/spotify_profile_monitor.png" alt="spotify_profile_monitor_screenshot" width="90%"/>
+</p>
 <a id="features"></a>
 ## Features
-- **Real-time tracking** of Spotify user activities and profile changes:
-   - addition/removal of **followings and followers**
-   - addition/removal of **playlists**
-   - addition/removal of **tracks in playlists** (including collaborator info for newly added tracks)
-   - **playlists name and description** changes
-   - **number of likes** for playlists
-   - **number of collaborators** for playlists
-   - **profile picture** changes
-   - **username** changes
-- **Email notifications** for various events (as listed above)
-- **Attaching changed profile pictures** directly to email notifications
-- **Displaying the profile picture** right in your terminal (if you have `imgcat` installed)
-- Additional functionalities on top of the monitoring mode allowing to display **detailed info about the user**, **list of followers & followings**, **recently played artists** and possibility to **search for users** in Spotify catalog with specific names
-- Ability to **display and export** the list of tracks for a specific playlist (including **Liked Songs** for the user who owns the Spotify access token)
-- **Saving all profile changes** (including playlists) with timestamps to the **CSV file**
-- **Clickable** **Spotify**, **Apple Music**, **YouTube Music**, **Amazon Music**, **Deezer**, **Tidal**, **Genius Lyrics**, **AZLyrics**, **Tekstowo.pl**, **Musixmatch** and **Lyrics.com** search URLs printed in the console and included in email notifications (configurable per service)
-- Support for **four different methods to get a Spotify access token** (`sp_dc cookie`, `desktop client`, `OAuth app`, `OAuth user`)
-- Possibility to **control the running copy** of the script via signals
-- **Functional, procedural Python** (minimal OOP)
+### 👤 Profile Monitoring
+- **Real-time tracking**: Monitor Spotify user activities and profile changes.
+- **Social Network**: Detect addition/removal of **followings** and **followers**.
+- **Identity Changes**: Track **profile picture** and **username** changes.
+### 📜 Playlist Tracking
+- **Content Updates**: Monitor addition/removal of **tracks in playlists**.
+- **Collaborator Info**: Identify who added which track in **collaborative playlists**.
+- **Social Proof**: Monitor **likes** and **collaborators** count for playlists.
+- **Metadata**: Track **name** and **description** changes.
+### 📊 Advanced Tools
+- **Deep Insights**: Display detailed info about users, followers and followings.
+- **Historical Data**: View **recently played artists** and **search for users** by name.
+- **Export Power**: Display and export tracks from any playlist (including **Liked Songs**).
+- **Global Search**: Instant links to **Spotify, YouTube Music, Apple Music, Tidal, lyrics** and more.
+### 🔔 Smart Interactions
+- **Instant Alerts**: Detailed **Email notifications** for all profile and playlist changes.
+- **Visual Reports**: Attach changed profile pictures directly to emails.
+- **Terminal Graphics**: Display profile pictures right in your terminal (via `imgcat`).
+### ⚙️ Power Features
+- **Auth Flexibility**: Hybrid support for `sp_dc` cookie, Desktop Client and OAuth.
+- **CSV Logging**: Save all changes with full timestamps to a CSV file.
+- **Flexible Config**: Support for files, dotenv and environment variables.
+- **Signal Control**: Manage the running script via system signals (`SIGHUP`, `USR1`, etc.).
-<p align="center">
-   <img src="https://raw.githubusercontent.com/misiektoja/spotify_profile_monitor/refs/heads/main/assets/spotify_profile_monitor.png" alt="spotify_profile_monitor_screenshot" width="100%"/>
-</p>
+✨ If you want to track Spotify friends' music activity, check out another tool I developed: [spotify_monitor](https://github.com/misiektoja/spotify_monitor).
+🛠️ If you're looking for debug tools to get Spotify Web Player access tokens and extract secret keys: [click here](#debugging-tools)
 <a id="table-of-contents"></a>
 ## Table of Contents
@@ -156,17 +150,16 @@ If you installed manually, download the newest *[spotify_profile_monitor.py](htt
 <a id="quick-start"></a>
 ## Quick Start
-- Grab your [Spotify sp_dc cookie](#spotify-sp_dc-cookie) and track the `spotify_user_uri_id` profile changes (including playlists):
+- Grab your [Spotify sp_dc cookie](#spotify-sp_dc-cookie), set up [OAuth app credentials](#spotify-oauth-app) and track the `spotify_user_uri_id` profile changes (including playlists):
 ```sh
-spotify_profile_monitor <spotify_user_uri_id> -u "your_sp_dc_cookie_value"
+spotify_profile_monitor <spotify_user_uri_id> -u "your_sp_dc_cookie_value" -r "your_spotify_app_client_id:your_spotify_app_client_secret"
 ```
 Or if you installed [manually](#manual-installation):
 ```sh
-python3 spotify_profile_monitor.py <spotify_user_uri_id> -u "your_sp_dc_cookie_value"
+python3 spotify_profile_monitor.py <spotify_user_uri_id> -u "your_sp_dc_cookie_value" -r "your_spotify_app_client_id:your_spotify_app_client_secret"
 ```
 To get the list of all supported command-line arguments / flags:
@@ -186,12 +179,19 @@ Most settings can be configured via command-line arguments.
 If you want to have it stored persistently, generate a default config template and save it to a file named `spotify_profile_monitor.conf`:
 ```sh
+# On macOS, Linux or Windows Command Prompt (cmd.exe)
 spotify_profile_monitor --generate-config > spotify_profile_monitor.conf
+# On Windows PowerShell (recommended to avoid encoding issues)
+spotify_profile_monitor --generate-config spotify_profile_monitor.conf
 ```
+> **IMPORTANT**: On **Windows PowerShell**, using redirection (`>`) can cause the file to be encoded in UTF-16, which will lead to "null bytes" errors when running the tool. It is highly recommended to provide the filename directly as an argument to `--generate-config` to ensure UTF-8 encoding.
 Edit the `spotify_profile_monitor.conf` file and change any desired configuration options (detailed comments are provided for each).
+**New in v3.1:** The tool now uses a hybrid authentication approach. OAuth app credentials (`SP_APP_CLIENT_ID`, `SP_APP_CLIENT_SECRET`) are required for playlist and user information retrieval when using either `cookie` or `client` token source methods. See [Spotify OAuth App](#spotify-oauth-app) section for setup instructions.
 **New in v2.9:** The configuration file includes options to enable/disable music service URLs (Apple Music, YouTube Music, Amazon Music, Deezer, Tidal) and lyrics service URLs (Genius, AZLyrics, Tekstowo.pl, Musixmatch, Lyrics.com) in console and email outputs.
 <a id="spotify-access-token-source"></a>
@@ -199,16 +199,23 @@ Edit the `spotify_profile_monitor.conf` file and change any desired configuratio
 The tool supports four methods for obtaining a Spotify access token.
-It can be configured via the `TOKEN_SOURCE` configuration option or the `--token-source` flag.
+When you decide to use the `cookie` or `client` token source method, the tool uses a **hybrid authentication approach** and you also need to configure **OAuth app credentials** (`SP_APP_CLIENT_ID`, `SP_APP_CLIENT_SECRET`) for playlist and user information retrieval as described in [Spotify OAuth App](#spotify-oauth-app).
+The token source method can be configured via the `TOKEN_SOURCE` configuration option or the `--token-source` flag.
 **Recommended: `cookie`**
 Uses the `sp_dc` cookie to retrieve a token from the Spotify web endpoint. This method is easy to set up and supports all features except fetching the list of liked tracks for the account that owns the access token (due to recent Spotify token's scope restrictions).
+Since version 3.1, due to Spotify restrictions introduced on December 22, 2025, it no longer shows other users' playlists added to a user's profile unless the user is a collaborator on a playlist owned by another user.
 **Alternative: `client`**
 Uses captured credentials from the Spotify desktop client and a Protobuf-based login flow. It's more complex to set up, but supports all features. This method is intended for advanced users who want a long-lasting token with the broadest possible access.
+Since version 3.1, due to Spotify restrictions introduced on December 22, 2025, it no longer shows other users' playlists added to a user's profile unless the user is a collaborator on a playlist owned by another user.
 **Safe fallback: `oauth_app`**
 Relies on the official Spotify Web API (Client Credentials OAuth flow). This method is easy to set up and safe to use, but has several limitations. The following features are **not** supported:
@@ -263,7 +270,7 @@ If your `sp_dc` cookie expires, the tool will notify you via the console and ema
 If you store the `SP_DC_COOKIE` in a dotenv file you can update its value and send a `SIGHUP` signal to reload the file with the new `sp_dc` cookie without restarting the tool. More info in [Storing Secrets](#storing-secrets) and [Signal Controls (macOS/Linux/Unix)](#signal-controls-macoslinuxunix).
-> **NOTE:** secrets used for TOTP generation (`SECRET_CIPHER_DICT`) expire every two days, that's why since v2.7 the tool fetches it from remote URL (see `SECRET_CIPHER_DICT_URL`); you can also run the [spotify_monitor_secret_grabber](https://github.com/misiektoja/spotify_monitor/blob/dev/debug/spotify_monitor_secret_grabber.py) and extract it by yourself (see [Secret Key Extraction from Spotify Web Player Bundles](#secret-key-extraction-from-spotify-web-player-bundles) for more info).
+> **NOTE:** secrets used for TOTP generation (`SECRET_CIPHER_DICT`) expire every few days, that's why since v2.7 the tool fetches it from remote URL (see `SECRET_CIPHER_DICT_URL`); you can also run the [spotify_monitor_secret_grabber](https://github.com/misiektoja/spotify_monitor/blob/dev/debug/spotify_monitor_secret_grabber.py) and extract it by yourself (see [Secret Key Extraction from Spotify Web Player Bundles](#secret-key-extraction-from-spotify-web-player-bundles) for more info).
 <a id="spotify-desktop-client"></a>
 #### Spotify Desktop Client
@@ -318,39 +325,42 @@ Advanced options are available for further customization - refer to the configur
 <a id="spotify-oauth-app"></a>
 #### Spotify OAuth App
+Can be used as a standalone mode, but also as a secondary mode to either a `cookie` or `client` token source method to retrieve playlist and user information (required due to restrictions introduced by Spotify on December 22, 2025).
 This method uses an official Spotify Web API (Client Credentials OAuth flow).
-- Log in to Spotify Developer dashboard: https://developer.spotify.com/dashboard
+To obtain the credentials:
+- Log in to [Spotify Developer dashboard](https://developer.spotify.com/dashboard)
 - Create a new app
-- For **Redirect URL**, use: http://127.0.0.1:1234
-   - The URL must match exactly as shown, including not having a / at the end
-   - When copying the link via right-click, some browsers may add an extra / to the URL
+- For **Redirect URL**, use: `http://127.0.0.1:1234`
+   - The URL must match exactly as shown, including not having a `/` at the end
+   - When copying the link via right-click, some browsers may add an extra `/` to the URL
 - Select **Web API** as the intended API
 - Copy the **Client ID** and **Client Secret**
 - Provide the `SP_APP_CLIENT_ID` and `SP_APP_CLIENT_SECRET` secrets using one of the following methods:
-   - Pass it at runtime with `-r` / `--oauth-app-creds`
-      - Use `SP_APP_CLIENT_ID`:`SP_APP_CLIENT_SECRET` format - note the colon separator
+   - Pass it at runtime with `-r` / `--oauth-app-creds` (use `SP_APP_CLIENT_ID:SP_APP_CLIENT_SECRET` format - note the colon separator)
    - Set it as an [environment variable](#storing-secrets) (e.g. `export SP_APP_CLIENT_ID=...; export SP_APP_CLIENT_SECRET=...`)
    - Add it to [.env file](#storing-secrets) (`SP_APP_CLIENT_ID=...` and `SP_APP_CLIENT_SECRET=...`) for persistent use
    - Fallback: hard-code it in the code or config file
-You can use the same client ID and secret values as those used for the [Spotify OAuth User](#spotify-oauth-user).
 Example:
 ```sh
 spotify_profile_monitor --token-source oauth_app -r "your_spotify_app_client_id:your_spotify_app_client_secret" <spotify_user_uri_id>
 ```
-The tool takes care of refreshing the access token so it should remain valid indefinitely.
+The tool automatically refreshes the OAuth app access token, so it remains valid indefinitely. Tokens are cached in the file specified by `SP_APP_TOKENS_FILE` configuration option (default: `.spotify-profile-monitor-oauth-app.json`).
 If you store the `SP_APP_CLIENT_ID` and `SP_APP_CLIENT_SECRET` in a dotenv file you can update their values and send a `SIGHUP` signal to reload the file with the new secret values without restarting the tool. More info in [Storing Secrets](#storing-secrets) and [Signal Controls (macOS/Linux/Unix)](#signal-controls-macoslinuxunix).
+You can also use this method as a standalone token source (without `cookie` or `client`) by setting `TOKEN_SOURCE` to `oauth_app`, but this has several limitations as described in the [Spotify access token source](#spotify-access-token-source) section.
 <a id="spotify-oauth-user"></a>
 #### Spotify OAuth User
@@ -529,6 +539,14 @@ If you use the default method to obtain a Spotify access token (`cookie`) and ha
 spotify_profile_monitor <spotify_user_uri_id> -u "your_sp_dc_cookie_value"
 ```
+**Note:** OAuth app credentials are now required for playlist and user information retrieval. If you haven't set `SP_APP_CLIENT_ID` and `SP_APP_CLIENT_SECRET` via environment variables or `.env` file, you can use the `-r` flag:
+```sh
+spotify_profile_monitor <spotify_user_uri_id> -u "your_sp_dc_cookie_value" -r "your_spotify_app_client_id:your_spotify_app_client_secret"
+```
+See [Spotify OAuth App](#spotify-oauth-app) for detailed setup instructions.
 By default, the tool looks for a configuration file named `spotify_profile_monitor.conf` in:
  - current directory
  - home directory (`~`)
@@ -661,12 +679,6 @@ If you want to display a list of recently played artists (this feature only work
 spotify_profile_monitor <spotify_user_uri_id> -a
 ```
-To get basic information about the Spotify access token owner (`-v` flag):
-```sh
-spotify_profile_monitor -v
-```
 If you want to search the Spotify catalog for users with a specific name to obtain their Spotify user URI ID (`-s` flag):
 ```sh
@@ -873,7 +885,7 @@ You should get a valid Spotify access token, example output:
    <img src="https://raw.githubusercontent.com/misiektoja/spotify_monitor/refs/heads/main/assets/spotify_monitor_totp_test.png" alt="spotify_monitor_totp_test" width="100%"/>
 </p>
-> **NOTE:** secrets used for TOTP generation (`SECRET_CIPHER_DICT`) expire every two days; you can either run the [spotify_monitor_secret_grabber](https://github.com/misiektoja/spotify_monitor/blob/dev/debug/spotify_monitor_secret_grabber.py) and extract it by yourself (see [here](#secret-key-extraction-from-spotify-web-player-bundles) for more info) or you can pass `--fetch-secrets` flag in `spotify_monitor_totp_test` (available since v1.6). There is also a [xyloflake/spot-secrets-go/](https://github.com/xyloflake/spot-secrets-go/) repo which offers JSON files that are automatically updated with current secrets (you can pass `--download-secrets` flag in `spotify_monitor_totp_test` to get it automatically from remote URL, available since v1.8).
+> **NOTE:** secrets used for TOTP generation (`SECRET_CIPHER_DICT`) expire every few days; you can either run the [spotify_monitor_secret_grabber](https://github.com/misiektoja/spotify_monitor/blob/dev/debug/spotify_monitor_secret_grabber.py) and extract it by yourself (see [here](#secret-key-extraction-from-spotify-web-player-bundles) for more info) or you can pass `--fetch-secrets` flag in `spotify_monitor_totp_test` (available since v1.6). There is also a [xyloflake/spot-secrets-go/](https://github.com/xyloflake/spot-secrets-go/) repo which offers JSON files that are automatically updated with current secrets (you can pass `--download-secrets` flag in `spotify_monitor_totp_test` to get it automatically from remote URL, available since v1.8).
 <a id="secret-key-extraction-from-spotify-web-player-bundles"></a>
 ### Secret Key Extraction from Spotify Web Player Bundles

{spotify_profile_monitor-3.0 → spotify_profile_monitor-3.2}/pyproject.toml RENAMED Viewed

@@ -4,8 +4,8 @@ build-backend = "setuptools.build_meta"
 [project]
 name = "spotify_profile_monitor"
-version = "3.0"
-description = "Tool implementing real-time tracking of Spotify users activities and profile changes including playlists"
+version = "3.2"
+description = "Track Spotify profile, follower and playlist changes in real time"
 readme = "README.md"
 license = "GPL-3.0-or-later"
 license-files = ["LICEN[CS]E*"]
@@ -24,6 +24,15 @@ dependencies = [
 ]
 classifiers = [
   "Programming Language :: Python :: 3",
+  "Programming Language :: Python :: 3.6",
+  "Programming Language :: Python :: 3.7",
+  "Programming Language :: Python :: 3.8",
+  "Programming Language :: Python :: 3.9",
+  "Programming Language :: Python :: 3.10",
+  "Programming Language :: Python :: 3.11",
+  "Programming Language :: Python :: 3.12",
+  "Programming Language :: Python :: 3.13",
+  "Programming Language :: Python :: 3.14",
   "Operating System :: OS Independent",
   "Operating System :: Microsoft :: Windows",
   "Operating System :: POSIX :: Linux",

spotify-profile-monitor 3.0__tar.gz → 3.2__tar.gz

spotify-profile-monitor 3.0tar.gz → 3.2tar.gz