Piracy: ꜱᴀɪʟ ᴛʜᴇ ʜɪɢʜ ꜱᴇᴀꜱ

54369 readers

420 users here now

⚓ Dedicated to the discussion of digital piracy, including ethical problems and legal advancements.

Rules • Full Version

1. Posts must be related to the discussion of digital piracy

2. Don't request invites, trade, sell, or self-promote

3. Don't request or link to specific pirated titles, including DMs

4. Don't submit low-quality posts, be entitled, or harass others

Loot, Pillage, & Plunder

📜 c/Piracy Wiki (Community Edition):

💰 Please help cover server costs.


Ko-fi	Liberapay

founded 1 year ago

MODERATORS

[email protected]

Anyone having trouble with Zotify and the like? (lemm.ee)

submitted 4 weeks ago* (last edited 4 weeks ago) by [email protected] to c/[email protected]

4 comments fedilink hide all child comments

I know that recently Spotify requires a credentials.json file and not just a user name and password. I can’t seem to find a method though that works in creating that file. I’ve tried librespot and librespot-auth, both of which should expose themselves as a speaker on my network for Spotify to cast too but it doesn’t show up. I’ve tried them both in a WSL instance and compiled directly for Windows with no luck.

Is there another way I’m missing to generate those credentials? I have a valid account, so I know there’s not an issue there.

all 5 comments

sorted by: hot top controversial new old

[–] [email protected] 3 points 4 weeks ago* (last edited 4 weeks ago)

Imma share the format of my credentials.json later so wait for my update.

[–] [email protected] 2 points 4 weeks ago

I don't know either, and I haven't been able to use spotify_player in a while, either in my Linux or Windows machines because of that. Already ended up accidentally resetting my Spotify password 2-3 times trying to solve that.

[–] [email protected] 0 points 4 weeks ago (1 children)

Try this to generate the credentials.json:

https://github.com/dspearson/librespot-auth

[–] chepdamona 1 points 4 weeks ago

OP mentions librespot-auth not working. I have the same issue actually, can't seem to get it to appear in any client on the home network