-
Notifications
You must be signed in to change notification settings - Fork 1.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
musixmatch source is broken on lyrics plugin (404) #4585
Comments
Broken on 1.6.1 also. |
It seems like Musixmatch have blocked the
Musixmatch do offer an API but their free tier is for evaluation only and doesn't give full access to lyrics. We may have to just remove Musixmatch as a backend, which is a bit of a shame. |
Man, that is indeed a shame 😞 They had the best lyrics from what I've gathered, I know Spotify uses them and just doing a quick comparison Genius has a lot of straight up garbage on their lyrics that Musixmatch doesn't (Publishers: ©Sony/ATV Music Publishing LLC Popularity : 0 users have visited this page Length: 3:46 Sponsored links, repeating the [artist name] Lyrics header into the actual lyrics, messed up unicode etc) |
Indeed; this is too bad. I think the right solution is probably to leave the code in place, in case something changes in the future, but disable it by default and remove it from the documentation? |
Would it be possible to change the UA identifier like you can in a browser, perhaps at the user's side only if not on the actual beets bundle? Maybe adding some function to slow the requests per second. At some point between those two it wouldn't be any more specific than normal/accepted behaviour of opening up their site from a browser and looking up lyrics. |
Musixmatch are currently blocking all requests with the beets user agent. See beetbox#4585.
It feels a bit dishonest to allow UA spoofing, as we are then actively attempting (or at least offering a way) to circumvent their block. You could edit the code yourself to change the UA, but I don't think it's something we'd want to offer officially. I've opened #4616 to do as @sampsyo has suggested. |
Musixmatch are currently blocking all requests with the beets user agent. See beetbox#4585.
I agree with @jackwilsdon here: it feels a little icky to work around a limitation that MusixMatch is clearly imposing with the intent to block beets. And I also don't think it would be effective: any new UA string we choose would likely also get blocked. I would much rather leave it up to individual users to do themselves if they're very motivated to do so. |
Problem
is giving me no results for any query that I give the plugin. For instance:
Setup
My configuration (output of
beet config
) is:The text was updated successfully, but these errors were encountered: