mirror of
https://github.com/misiektoja/spotify_profile_monitor.git
synced 2026-04-25 23:15:57 +03:00
[GH-ISSUE #6] Feature Suggestion #5
Labels
No labels
Stale
enhancement
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/spotify_profile_monitor#5
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @tomballgithub on GitHub (Mar 31, 2025).
Original GitHub issue: https://github.com/misiektoja/spotify_profile_monitor/issues/6
I made some edits to this tool to allow it to do a few things:
flag to have -L (list tracks for playlist) output in a format that is directly importable into spotify_monitor so that it can be automated. This could be used to dump a private playlist that would not otherwise show up in the friends' info from spotify. You just have to not print all the header and footer messaging, strip the whitespace, and only use the first column.
flag to dump the 'liked songs' playlist from the user associated with the SP_DC cookie. The intent is to be directly importable into spotify_monitor, but the code below actually does {p_artist} - {p_track} because I made a change to spotify_monitor to support that
My code for #1 isn't clean and there's no way you would leverage it.
Below is what I did for #2
Of course, feel free to delete this entire suggestion since we might be the only two using this tool :-) I added all the features of my Node.js tool into your code base since you are maintaining it, and Python is more straightforward.
@misiektoja commented on GitHub (Mar 31, 2025):
Hey, I like the ideas! Please open pull requests for both of them, so you take credits for it.
Even if the code for number 1 is not clean, please also share as PR, I will try to consolidate it so it fits into the base code.
@tomballgithub commented on GitHub (Mar 31, 2025):
I need to figure out how to use git again but will get around to it this
week.
On Mon, Mar 31, 2025, 6:27 AM Michal Szymanski @.***>
wrote:
@tomballgithub commented on GitHub (Apr 9, 2025):
Question. Would you mind sharing how you are using git with your repository yet not checking in your custom info such as your cookie and smtp information? None of the normal ways I know for doing this seem to apply here. There must be something I'm missing.
@misiektoja commented on GitHub (Apr 9, 2025):
I have prepared a script that replaces all the secrets with some generic ones (just simple sed processing).
Here is the gist.
I have it set up in my Git client (I use Sublime Merge) and it runs before any push.
I also use this script to quickly reverse the changes and input some real data.
@tomballgithub commented on GitHub (Apr 10, 2025):
Thanks for sharing that with me. I will set something up similar
On Wed, Apr 9, 2025 at 8:25 AM Michal Szymanski @.***>
wrote:
@github-actions[bot] commented on GitHub (May 11, 2025):
This issue has been marked as stale because it has been inactive for 30 days. It will be closed in 7 days if no further activity occurs.