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

{spotify_profile_monitor-2.8 → spotify_profile_monitor-3.0}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: spotify_profile_monitor
-Version: 2.8
+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
@@ -38,24 +38,25 @@ OSINT tool for real-time monitoring of **Spotify users' activities and profile c
 <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 and Genius Lyrics search URLs printed in the console & included in email notifications
-- 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
+- **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)
 
 <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%"/>
@@ -68,6 +69,7 @@ OSINT tool for real-time monitoring of **Spotify users' activities and profile c
 2. [Installation](#installation)
    * [Install from PyPI](#install-from-pypi)
    * [Manual Installation](#manual-installation)
+   * [Upgrading](#upgrading)
 3. [Quick Start](#quick-start)
 4. [Configuration](#configuration)
    * [Configuration File](#configuration-file)
@@ -140,6 +142,17 @@ Alternatively, from the downloaded *[requirements.txt](https://raw.githubusercon
 pip install -r requirements.txt
 ```
 
+<a id="upgrading"></a>
+### Upgrading
+
+To upgrade to the latest version when installed from PyPI:
+
+```sh
+pip install spotify_profile_monitor -U
+```
+
+If you installed manually, download the newest *[spotify_profile_monitor.py](https://raw.githubusercontent.com/misiektoja/spotify_profile_monitor/refs/heads/main/spotify_profile_monitor.py)* file to replace your existing installation.
+
 <a id="quick-start"></a>
 ## Quick Start
 
@@ -179,22 +192,24 @@ spotify_profile_monitor --generate-config > spotify_profile_monitor.conf
 
 Edit the `spotify_profile_monitor.conf` file and change any desired configuration options (detailed comments are provided for each).
 
+**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>
 ### Spotify access token source
 
 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. 
+It can be configured via the `TOKEN_SOURCE` configuration option or the `--token-source` flag.
 
-**Recommended: `cookie`** 
+**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).
 
-**Alternative: `client`** 
+**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.
 
-**Safe fallback: `oauth_app`** 
+**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:
 - viewing the list of followers/followings
@@ -208,7 +223,7 @@ Relies on the official Spotify Web API (Client Credentials OAuth flow). This met
 
 Dedicated to tracking the authenticated user's own account via the official Spotify Web API (Authorization Code OAuth flow). I personally use this mode to monitor changes to my own account - such as new or lost followers/followings, likes on my playlists or when a collaborator adds a new song. You can also use this mode to track other users.
 
-This method is easy to set up and safe to use, but has several limitations. 
+This method is easy to set up and safe to use, but has several limitations.
 
 The following features are **not** supported when monitoring **your own account**:
 - viewing the list of followers
@@ -294,7 +309,7 @@ The same applies to `--token-source client` flag - you can persist it via `TOKEN
 
 The tool will automatically refresh both the access token and client token using the intercepted refresh token.
 
-If your refresh token expires, the tool will notify you via the console and email. In that case, you'll need to re-export the login request body. 
+If your refresh token expires, the tool will notify you via the console and email. In that case, you'll need to re-export the login request body.
 
 If you re-export the login request body to the same file name, you can send a `SIGHUP` signal to reload the file with the new refresh token without restarting the tool. More info in [Signal Controls (macOS/Linux/Unix)](#signal-controls-macoslinuxunix).
 
@@ -394,7 +409,7 @@ Alternatively you can use the built-in functionality to search for usernames (`-
 spotify_profile_monitor -s "user name"
 ```
 
-It will list all users with such names with their user URI ID. 
+It will list all users with such names with their user URI ID.
 
 Before using this feature make sure you followed the instructions [here](#spotify-sha256-optional).
 
@@ -409,7 +424,7 @@ This step is optional and only required if you want to use the feature that sear
 
 - Look for requests with the `searchUsers` or `searchDesktop` operation name
 
-- Display the details of one of these requests and copy the **sha256Hash** parameter value (string marked as `XXXXXXXXXX` below) 
+- Display the details of one of these requests and copy the **sha256Hash** parameter value (string marked as `XXXXXXXXXX` below)
 
 Example request:
 `https://api-partner.spotify.com/pathfinder/v1/query?operationName=searchUsers&variables={"searchTerm":"spotify_user_uri_id","offset":0,"limit":5,"numberOfTopResults":5,"includeAudiobooks":false}&extensions={"persistedQuery":{"version":1,"sha256Hash":"XXXXXXXXXX"}}`
@@ -439,7 +454,7 @@ python3 -c "import pytz; print('\n'.join(pytz.all_timezones))"
 <a id="smtp-settings"></a>
 ### SMTP Settings
 
-If you want to use email notifications functionality, configure SMTP settings in the `spotify_profile_monitor.conf` file. 
+If you want to use email notifications functionality, configure SMTP settings in the `spotify_profile_monitor.conf` file.
 
 Verify your SMTP settings by using `--send-test-email` flag (the tool will try to send a test email notification):
 
@@ -480,7 +495,7 @@ SP_SHA256="your_spotify_client_sha256"
 SMTP_PASSWORD="your_smtp_password"
 ```
 
-By default the tool will auto-search for dotenv file named `.env` in current directory and then upward from it. 
+By default the tool will auto-search for dotenv file named `.env` in current directory and then upward from it.
 
 You can specify a custom file with `DOTENV_FILE` or `--env-file` flag:
 
@@ -515,9 +530,9 @@ spotify_profile_monitor <spotify_user_uri_id> -u "your_sp_dc_cookie_value"
 ```
 
 By default, the tool looks for a configuration file named `spotify_profile_monitor.conf` in:
- - current directory 
+ - current directory
  - home directory (`~`)
- - script directory 
+ - script directory
 
  If you generated a configuration file as described in [Configuration](#configuration), but saved it under a different name or in a different directory, you can specify its location using the `--config-file` flag:
 
@@ -536,7 +551,7 @@ spotify_profile_monitor <spotify_user_uri_id> -k
 
 It is helpful in the case of playlists created by another user added to another user profile.
 
-Some users don't list all their public playlists on their profile, but if you know a playlist's URI, you can still monitor it. 
+Some users don't list all their public playlists on their profile, but if you know a playlist's URI, you can still monitor it.
 
 To do so, add entries to the `ADD_PLAYLISTS_TO_MONITOR` configuration option. Example:
 
@@ -570,7 +585,7 @@ You can monitor multiple Spotify users by running multiple copies of the script.
 The tool automatically saves its output to `spotify_profile_monitor_<user_uri_id/file_suffix>.log` file. The log file name can be changed via `SP_LOGFILE` configuration option and its suffix via `FILE_SUFFIX` / `-y` flag. Logging can be disabled completely via `DISABLE_LOGGING` / `-d` flag.
 
 The tool also saves the list of followings, followers and playlists to these files:
-- `spotify_profile_<user_uri_id/file_suffix>_followings.json` 
+- `spotify_profile_<user_uri_id/file_suffix>_followings.json`
 - `spotify_profile_<user_uri_id/file_suffix>_followers.json`
 - `spotify_profile_<user_uri_id/file_suffix>_playlists.json`
 
@@ -690,7 +705,7 @@ Make sure you defined your SMTP settings earlier (see [SMTP settings](#smtp-sett
 Example email:
 
 <p align="center">
-   <img src="https://raw.githubusercontent.com/misiektoja/spotify_profile_monitor/refs/heads/main/assets/spotify_profile_monitor_email_notifications.png" alt="spotify_profile_monitor_email_notifications" width="80%"/>
+   <img src="https://raw.githubusercontent.com/misiektoja/spotify_profile_monitor/refs/heads/main/assets/spotify_profile_monitor_email_notifications.png" alt="spotify_profile_monitor_email_notifications" width="90%"/>
 </p>
 
 <a id="csv-export"></a>
@@ -732,7 +747,7 @@ If a change is detected, the old picture is moved to `spotify_profile_<user_uri_
 
 If you have `imgcat` installed, you can enable inline display of profile pictures and playlist artwork directly in your terminal.
 
-To do this, set the path to your `imgcat` binary in the `IMGCAT_PATH` configuration option. 
+To do this, set the path to your `imgcat` binary in the `IMGCAT_PATH` configuration option.
 
 If you specify only the binary name, it will be auto-searched in your PATH.
 
@@ -832,7 +847,7 @@ To help with troubleshooting and development, two debug utilities are available
 <a id="access-token-retrieval-via-sp_dc-cookie-and-totp"></a>
 ### Access Token Retrieval via sp_dc Cookie and TOTP
 
-The [spotify_monitor_totp_test](https://github.com/misiektoja/spotify_monitor/blob/dev/debug/spotify_monitor_totp_test.py) tool retrieves a Spotify access token using a Web Player `sp_dc` cookie and TOTP parameters. 
+The [spotify_monitor_totp_test](https://github.com/misiektoja/spotify_monitor/blob/dev/debug/spotify_monitor_totp_test.py) tool retrieves a Spotify access token using a Web Player `sp_dc` cookie and TOTP parameters.
 
 Download from [here](https://github.com/misiektoja/spotify_monitor/blob/dev/debug/spotify_monitor_totp_test.py) or:
 
@@ -863,7 +878,7 @@ You should get a valid Spotify access token, example output:
 <a id="secret-key-extraction-from-spotify-web-player-bundles"></a>
 ### Secret Key Extraction from Spotify Web Player Bundles
 
-The [spotify_monitor_secret_grabber](https://github.com/misiektoja/spotify_monitor/blob/dev/debug/spotify_monitor_secret_grabber.py) tool automatically extracts secret keys used for TOTP generation in Spotify Web Player JavaScript bundles. 
+The [spotify_monitor_secret_grabber](https://github.com/misiektoja/spotify_monitor/blob/dev/debug/spotify_monitor_secret_grabber.py) tool automatically extracts secret keys used for TOTP generation in Spotify Web Player JavaScript bundles.
 
 > 💡 **Quick tip:** The easiest and recommended way to run this tool is via Docker. Jump directly to the [Docker usage section below](#-secret-key-extraction-via-docker-recommended-easiest-way).
 
@@ -983,7 +998,7 @@ See [RELEASE_NOTES.md](https://github.com/misiektoja/spotify_profile_monitor/blo
 <a id="maintainers"></a>
 ## Maintainers
 
-[![Maintainer: misiektoja](https://img.shields.io/badge/maintainer-misiektoja-blue)](https://github.com/misiektoja)  
+[![Maintainer: misiektoja](https://img.shields.io/badge/maintainer-misiektoja-blue)](https://github.com/misiektoja)
 [![Maintainer: tomballgithub](https://img.shields.io/badge/maintainer-tomballgithub-blue)](https://github.com/tomballgithub)
 
 <a id="license"></a>

{spotify_profile_monitor-2.8 → spotify_profile_monitor-3.0}/README.md

@@ -9,24 +9,25 @@ OSINT tool for real-time monitoring of **Spotify users' activities and profile c
 <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 and Genius Lyrics search URLs printed in the console & included in email notifications
-- 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
+- **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)
 
 <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%"/>
@@ -39,6 +40,7 @@ OSINT tool for real-time monitoring of **Spotify users' activities and profile c
 2. [Installation](#installation)
    * [Install from PyPI](#install-from-pypi)
    * [Manual Installation](#manual-installation)
+   * [Upgrading](#upgrading)
 3. [Quick Start](#quick-start)
 4. [Configuration](#configuration)
    * [Configuration File](#configuration-file)
@@ -111,6 +113,17 @@ Alternatively, from the downloaded *[requirements.txt](https://raw.githubusercon
 pip install -r requirements.txt
 ```
 
+<a id="upgrading"></a>
+### Upgrading
+
+To upgrade to the latest version when installed from PyPI:
+
+```sh
+pip install spotify_profile_monitor -U
+```
+
+If you installed manually, download the newest *[spotify_profile_monitor.py](https://raw.githubusercontent.com/misiektoja/spotify_profile_monitor/refs/heads/main/spotify_profile_monitor.py)* file to replace your existing installation.
+
 <a id="quick-start"></a>
 ## Quick Start
 
@@ -150,22 +163,24 @@ spotify_profile_monitor --generate-config > spotify_profile_monitor.conf
 
 Edit the `spotify_profile_monitor.conf` file and change any desired configuration options (detailed comments are provided for each).
 
+**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>
 ### Spotify access token source
 
 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. 
+It can be configured via the `TOKEN_SOURCE` configuration option or the `--token-source` flag.
 
-**Recommended: `cookie`** 
+**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).
 
-**Alternative: `client`** 
+**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.
 
-**Safe fallback: `oauth_app`** 
+**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:
 - viewing the list of followers/followings
@@ -179,7 +194,7 @@ Relies on the official Spotify Web API (Client Credentials OAuth flow). This met
 
 Dedicated to tracking the authenticated user's own account via the official Spotify Web API (Authorization Code OAuth flow). I personally use this mode to monitor changes to my own account - such as new or lost followers/followings, likes on my playlists or when a collaborator adds a new song. You can also use this mode to track other users.
 
-This method is easy to set up and safe to use, but has several limitations. 
+This method is easy to set up and safe to use, but has several limitations.
 
 The following features are **not** supported when monitoring **your own account**:
 - viewing the list of followers
@@ -265,7 +280,7 @@ The same applies to `--token-source client` flag - you can persist it via `TOKEN
 
 The tool will automatically refresh both the access token and client token using the intercepted refresh token.
 
-If your refresh token expires, the tool will notify you via the console and email. In that case, you'll need to re-export the login request body. 
+If your refresh token expires, the tool will notify you via the console and email. In that case, you'll need to re-export the login request body.
 
 If you re-export the login request body to the same file name, you can send a `SIGHUP` signal to reload the file with the new refresh token without restarting the tool. More info in [Signal Controls (macOS/Linux/Unix)](#signal-controls-macoslinuxunix).
 
@@ -365,7 +380,7 @@ Alternatively you can use the built-in functionality to search for usernames (`-
 spotify_profile_monitor -s "user name"
 ```
 
-It will list all users with such names with their user URI ID. 
+It will list all users with such names with their user URI ID.
 
 Before using this feature make sure you followed the instructions [here](#spotify-sha256-optional).
 
@@ -380,7 +395,7 @@ This step is optional and only required if you want to use the feature that sear
 
 - Look for requests with the `searchUsers` or `searchDesktop` operation name
 
-- Display the details of one of these requests and copy the **sha256Hash** parameter value (string marked as `XXXXXXXXXX` below) 
+- Display the details of one of these requests and copy the **sha256Hash** parameter value (string marked as `XXXXXXXXXX` below)
 
 Example request:
 `https://api-partner.spotify.com/pathfinder/v1/query?operationName=searchUsers&variables={"searchTerm":"spotify_user_uri_id","offset":0,"limit":5,"numberOfTopResults":5,"includeAudiobooks":false}&extensions={"persistedQuery":{"version":1,"sha256Hash":"XXXXXXXXXX"}}`
@@ -410,7 +425,7 @@ python3 -c "import pytz; print('\n'.join(pytz.all_timezones))"
 <a id="smtp-settings"></a>
 ### SMTP Settings
 
-If you want to use email notifications functionality, configure SMTP settings in the `spotify_profile_monitor.conf` file. 
+If you want to use email notifications functionality, configure SMTP settings in the `spotify_profile_monitor.conf` file.
 
 Verify your SMTP settings by using `--send-test-email` flag (the tool will try to send a test email notification):
 
@@ -451,7 +466,7 @@ SP_SHA256="your_spotify_client_sha256"
 SMTP_PASSWORD="your_smtp_password"
 ```
 
-By default the tool will auto-search for dotenv file named `.env` in current directory and then upward from it. 
+By default the tool will auto-search for dotenv file named `.env` in current directory and then upward from it.
 
 You can specify a custom file with `DOTENV_FILE` or `--env-file` flag:
 
@@ -486,9 +501,9 @@ spotify_profile_monitor <spotify_user_uri_id> -u "your_sp_dc_cookie_value"
 ```
 
 By default, the tool looks for a configuration file named `spotify_profile_monitor.conf` in:
- - current directory 
+ - current directory
  - home directory (`~`)
- - script directory 
+ - script directory
 
  If you generated a configuration file as described in [Configuration](#configuration), but saved it under a different name or in a different directory, you can specify its location using the `--config-file` flag:
 
@@ -507,7 +522,7 @@ spotify_profile_monitor <spotify_user_uri_id> -k
 
 It is helpful in the case of playlists created by another user added to another user profile.
 
-Some users don't list all their public playlists on their profile, but if you know a playlist's URI, you can still monitor it. 
+Some users don't list all their public playlists on their profile, but if you know a playlist's URI, you can still monitor it.
 
 To do so, add entries to the `ADD_PLAYLISTS_TO_MONITOR` configuration option. Example:
 
@@ -541,7 +556,7 @@ You can monitor multiple Spotify users by running multiple copies of the script.
 The tool automatically saves its output to `spotify_profile_monitor_<user_uri_id/file_suffix>.log` file. The log file name can be changed via `SP_LOGFILE` configuration option and its suffix via `FILE_SUFFIX` / `-y` flag. Logging can be disabled completely via `DISABLE_LOGGING` / `-d` flag.
 
 The tool also saves the list of followings, followers and playlists to these files:
-- `spotify_profile_<user_uri_id/file_suffix>_followings.json` 
+- `spotify_profile_<user_uri_id/file_suffix>_followings.json`
 - `spotify_profile_<user_uri_id/file_suffix>_followers.json`
 - `spotify_profile_<user_uri_id/file_suffix>_playlists.json`
 
@@ -661,7 +676,7 @@ Make sure you defined your SMTP settings earlier (see [SMTP settings](#smtp-sett
 Example email:
 
 <p align="center">
-   <img src="https://raw.githubusercontent.com/misiektoja/spotify_profile_monitor/refs/heads/main/assets/spotify_profile_monitor_email_notifications.png" alt="spotify_profile_monitor_email_notifications" width="80%"/>
+   <img src="https://raw.githubusercontent.com/misiektoja/spotify_profile_monitor/refs/heads/main/assets/spotify_profile_monitor_email_notifications.png" alt="spotify_profile_monitor_email_notifications" width="90%"/>
 </p>
 
 <a id="csv-export"></a>
@@ -703,7 +718,7 @@ If a change is detected, the old picture is moved to `spotify_profile_<user_uri_
 
 If you have `imgcat` installed, you can enable inline display of profile pictures and playlist artwork directly in your terminal.
 
-To do this, set the path to your `imgcat` binary in the `IMGCAT_PATH` configuration option. 
+To do this, set the path to your `imgcat` binary in the `IMGCAT_PATH` configuration option.
 
 If you specify only the binary name, it will be auto-searched in your PATH.
 
@@ -803,7 +818,7 @@ To help with troubleshooting and development, two debug utilities are available
 <a id="access-token-retrieval-via-sp_dc-cookie-and-totp"></a>
 ### Access Token Retrieval via sp_dc Cookie and TOTP
 
-The [spotify_monitor_totp_test](https://github.com/misiektoja/spotify_monitor/blob/dev/debug/spotify_monitor_totp_test.py) tool retrieves a Spotify access token using a Web Player `sp_dc` cookie and TOTP parameters. 
+The [spotify_monitor_totp_test](https://github.com/misiektoja/spotify_monitor/blob/dev/debug/spotify_monitor_totp_test.py) tool retrieves a Spotify access token using a Web Player `sp_dc` cookie and TOTP parameters.
 
 Download from [here](https://github.com/misiektoja/spotify_monitor/blob/dev/debug/spotify_monitor_totp_test.py) or:
 
@@ -834,7 +849,7 @@ You should get a valid Spotify access token, example output:
 <a id="secret-key-extraction-from-spotify-web-player-bundles"></a>
 ### Secret Key Extraction from Spotify Web Player Bundles
 
-The [spotify_monitor_secret_grabber](https://github.com/misiektoja/spotify_monitor/blob/dev/debug/spotify_monitor_secret_grabber.py) tool automatically extracts secret keys used for TOTP generation in Spotify Web Player JavaScript bundles. 
+The [spotify_monitor_secret_grabber](https://github.com/misiektoja/spotify_monitor/blob/dev/debug/spotify_monitor_secret_grabber.py) tool automatically extracts secret keys used for TOTP generation in Spotify Web Player JavaScript bundles.
 
 > 💡 **Quick tip:** The easiest and recommended way to run this tool is via Docker. Jump directly to the [Docker usage section below](#-secret-key-extraction-via-docker-recommended-easiest-way).
 
@@ -954,7 +969,7 @@ See [RELEASE_NOTES.md](https://github.com/misiektoja/spotify_profile_monitor/blo
 <a id="maintainers"></a>
 ## Maintainers
 
-[![Maintainer: misiektoja](https://img.shields.io/badge/maintainer-misiektoja-blue)](https://github.com/misiektoja)  
+[![Maintainer: misiektoja](https://img.shields.io/badge/maintainer-misiektoja-blue)](https://github.com/misiektoja)
 [![Maintainer: tomballgithub](https://img.shields.io/badge/maintainer-tomballgithub-blue)](https://github.com/tomballgithub)
 
 <a id="license"></a>

{spotify_profile_monitor-2.8 → spotify_profile_monitor-3.0}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "setuptools.build_meta"
 
 [project]
 name = "spotify_profile_monitor"
-version = "2.8"
+version = "3.0"
 description = "Tool implementing real-time tracking of Spotify users activities and profile changes including playlists"
 readme = "README.md"
 license = "GPL-3.0-or-later"