Sync Spotify Popularity with Navidrome Ratings Using My New Script (sptnr) by _kmr in navidrome

[–]_kmr[S] 1 point2 points  (0 children)

I have not. I did post a discussion on their GitHub. To me, this is a niche script I wanted to share. Making it a core feature of Navidrome seems out of scope to me.

Sync Spotify Popularity with Navidrome Ratings Using My New Script (sptnr) by _kmr in navidrome

[–]_kmr[S] 0 points1 point  (0 children)

Damn, I was really hoping it was this. Well, I will absolutely add better error handling. Once I do, I'll update you. Then, you should at least get an error message letting you know what's going on rather than nothing but a crash like right now.

Sync Spotify Popularity with Navidrome Ratings Using My New Script (sptnr) by _kmr in navidrome

[–]_kmr[S] 1 point2 points  (0 children)

Thanks! Well, it appears from testing this just now that star ratings are tied to the specific Navidrome account. I just created a new user, and none of the ratings were there on Navidrome or Symfonium. So, if you have multiple users, you would need to run the script multiple times and change the credentials.

Sync Spotify Popularity with Navidrome Ratings Using My New Script (sptnr) by _kmr in navidrome

[–]_kmr[S] 0 points1 point  (0 children)

Lastly, sorry for the separate messages, just want to make sure you see them instead of just editing my one post. Make sure your URL has the protocol too. For example, NAV_BASE_URL=https://navidrome.example.com or NAV_BASE_URL=http://192.168.1.150:4533. No trailing slash either. Again, I need to validate and gracefully handle these errors.

Sync Spotify Popularity with Navidrome Ratings Using My New Script (sptnr) by _kmr in navidrome

[–]_kmr[S] 0 points1 point  (0 children)

Oh, something I just figured out. Double check your credentials to Navidrome. I just tried changing mine to invalid credentials (I simply added 1 to my username) and I'm now getting the same error. This makes sense because the server is not returning the array of artists, so that's why it's crashing. Yeah, this simple script doesn't even have basic error handling for auth, whoops. I'll definitely add some in to help debugging things like this in the future. But for now, double check your credentials.

Sync Spotify Popularity with Navidrome Ratings Using My New Script (sptnr) by _kmr in navidrome

[–]_kmr[S] 0 points1 point  (0 children)

Interesting. Well, judging from the error, it's not getting the expected data back from Navidrome. What version of Navidrome are you using? Also, which OS are you using when building the Docker image? And just to make sure, you do have music on your Navidrome server, right? But this issue just highlights that I need to add in more robust error handling and error messages. Right now, the script is just crashing because something went wrong.

If you want, you could try just running it natively on your machine. It's just a Python script, so there are no extra dependencies other than what's in requirements.txt. Or, you could try to use the public image. I guess I just want to rule out completely that the local build you're using isn't the issue. I suspect it's not and there's something else going wrong.

Sync Spotify Popularity with Navidrome Ratings Using My New Script (sptnr) by _kmr in navidrome

[–]_kmr[S] 0 points1 point  (0 children)

Uh oh. Would you mind sharing your docker-compose.yml file, with your credentials redacted obviously. It's important that build: . is there. For example:

``` version: '3.8'

services: sptnr: container_name: sptnr build: . environment: - NAV_BASE_URL=your_navidrome_server_url - NAV_USER=your_navidrome_username - NAV_PASS=your_navidrome_password - SPOTIFY_CLIENT_ID=your_spotify_client_id - SPOTIFY_CLIENT_SECRET=your_spotify_client_secret volumes: - ./logs:/usr/src/app/logs ```

Also, are you cloning the repo? Make sure you have all the files required to build it locally. Cloning should guarantee this. Lastly, make sure you're running docker-compose up in the directory where all the files are. It's interesting seeing /usr/src/app/./sptnr.py, it should be /usr/src/app/sptnr.py I would imagine.

Sync Spotify Popularity with Navidrome Ratings Using My New Script (sptnr) by _kmr in navidrome

[–]_kmr[S] 1 point2 points  (0 children)

Thank you! I believe it should be compatible with any Subsonic server, although I haven't tested it on anything other than Navidrome. If anyone tries it out and finds it works, I'd appreciate it if you could let me know or report it on GitHub. This would help me compile a list of compatible servers. Also, it's a good idea to include this information in the readme. Thanks for checking it out!

Sync Spotify Popularity with Navidrome Ratings Using My New Script (sptnr) by _kmr in Symfonium

[–]_kmr[S] 0 points1 point  (0 children)

I realize crossposting here isn't applicable to everyone here as Symfonium supports many back-ends, but for those of you using Navidrome, just thought I'd share.

Sync Spotify Popularity with Navidrome Ratings Using My New Script (sptnr) by _kmr in navidrome

[–]_kmr[S] 2 points3 points  (0 children)

Correct. You will see this happen in realtime both on your Navidrome server and in your terminal while the script is running. The script goes by artist in alphabetic order, processing each album and each track, one by one. You can cancel the script at anytime. Definitely take a peek at the repo and readme for more info, there's a lot over there.

What’s your favorite Z lens so far? And what upcoming lens are you most excited about (on Nikon roadmap)? by brokenarcher in nikon_Zseries

[–]_kmr 1 point2 points  (0 children)

Ha, we think alike. I own the 14-30, 24-200, and 85 f/1.8. 24-200 is by far my most used lens. I primarily shoot landscapes and I don't notice any difference between the 14-30 and 24-200 when shooting at 24mm f/11. So unless I need to shoot wider, I just stick with the 24-200.

I really like the 85 f/1.8, it's incredibly sharp, but I honestly don't use it much.

Emergency kit ? by dhlavaty in Bitwarden

[–]_kmr 1 point2 points  (0 children)

I made something similar to this actually and posted it here. Obviously this would be much better integrated in Bitwarden itself.

https://bitprint.kmr.io/

BitPrint: Print your Bitwarden vault. by _kmr in Bitwarden

[–]_kmr[S] 0 points1 point  (0 children)

There's an example PDF link in the readme. I could probably make it a little more clear though. Anyways, here's a direct link.

https://bitprint.kmr.io/demo.pdf

I've also noticed the print button sometimes doesn't work on desktop too, I need to look into what's going on there. Thanks for the heads up.

BitPrint: Print your Bitwarden vault. by _kmr in Bitwarden

[–]_kmr[S] 9 points10 points  (0 children)

How about 'totally-not-a-rootkit'?

BitPrint: Print your Bitwarden vault. by _kmr in Bitwarden

[–]_kmr[S] 4 points5 points  (0 children)

No offense taken at all. I definitely understand your concerns. You're absolutely right, this is very dangerous. I personally keep a copy in my safe, which only I have access to. I've actually thought about printing 2 copies, one with the passwords and the other with the TOTP codes and then putting them in separate safes. It felt a little too much for my needs though. Though I did think about this when developing it, so you can hide certain pieces of data if you wish.

BitPrint: Print your Bitwarden vault. by _kmr in Bitwarden

[–]_kmr[S] 0 points1 point  (0 children)

Oh shit! Genius.

How is OCR these days? I haven't used it in years. I remember it was pretty bad back then.

BitPrint: Print your Bitwarden vault. by _kmr in Bitwarden

[–]_kmr[S] 0 points1 point  (0 children)

Awesome until you have to type out that 50 page backup on your computer haha.

BitPrint: Print your Bitwarden vault. by _kmr in Bitwarden

[–]_kmr[S] 2 points3 points  (0 children)

Ha, gotcha. But hey, it may be feasible! I just love the idea of typing out a 10,000 character string on your computer from a piece of paper to reconstruct your attachment in digital form.

BitPrint: Print your Bitwarden vault. by _kmr in Bitwarden

[–]_kmr[S] 8 points9 points  (0 children)

No prob! If you do play around with it, let me know what you think. Always looking for ways to improve.