If you use the "add urls" feature as a way to enable monitoring on a bunch of things already in the DB, the code still re-scrapes data from Tidal even if it already has the information for those in the DB. For example. enabling monitoring on a handful of albums.
Once that change is made; just updating monitoring if something is in the DB to enable monitoring only without hitting the API... then it additionally makes sense to not do "tidalrrStart" as it logs into Tidal in that case even though it isn't needed.
These changes are useful primarily to prevent logging into the Tidal API or hitting portions of it when unneeded.
If you use the "add urls" feature as a way to enable monitoring on a bunch of things already in the DB, the code still re-scrapes data from Tidal even if it already has the information for those in the DB. For example. enabling monitoring on a handful of albums.
Once that change is made; just updating monitoring if something is in the DB to enable monitoring only without hitting the API... then it additionally makes sense to not do "tidalrrStart" as it logs into Tidal in that case even though it isn't needed.
These changes are useful primarily to prevent logging into the Tidal API or hitting portions of it when unneeded.