userscripts icon indicating copy to clipboard operation
userscripts copied to clipboard

d.ontun.es is down

Open YoGo9 opened this issue 1 year ago • 14 comments

The last few days it seems like the domain expired therefore it does no longer work, is it possible to update the link that it should send to https://magicisrc.kepstin.ca/ instead?

YoGo9 avatar Sep 12 '24 03:09 YoGo9

https://isrchunt.com/spotify/importisrc

ISRC hunt also works great with Spotify links!

If you want to modify the script yourself until an official fix exists: Line 54: elem.href = `https://isrchunt.com/spotify/importisrc?releaseId=${spotifyId}`; image

Lioncat6 avatar Oct 03 '24 05:10 Lioncat6

I'll probably make a pull later to propose this change

Lioncat6 avatar Oct 03 '24 05:10 Lioncat6

https://github.com/atj/userscripts/pull/216

Lioncat6 avatar Oct 03 '24 18:10 Lioncat6

@atj Could you take a look at the PR above please! This would help greatly.

arsinclair avatar Oct 24 '24 04:10 arsinclair

Does anyone know how ISRC Hunt matches MB recordings to Spotify? I don't really like the fact that we just pass a Spotify ID and not a MBID...

atj avatar Oct 24 '24 09:10 atj

As for MBID's, it's preforming a Lookup based on url resource. The MB api has a ton of things you can look up a release by. It works simular to the way I've made SAMBL, though by album and not artist

Lioncat6 avatar Oct 24 '24 15:10 Lioncat6

I want to make an open source api for this that would allow specification of an MBID in case of 2 releases with the same spotify id

Lioncat6 avatar Oct 24 '24 15:10 Lioncat6

@Lioncat6 are you a maintainer of that project?

that would allow specification of an MBID in case of 2 releases with the same spotify id

How such conflict is currently handled? Does it present the user with a choice, or it just rejects the import since it's ambiguous?

arsinclair avatar Oct 25 '24 03:10 arsinclair

@Lioncat6 are you a maintainer of that project?

I am not, just peiced together how it works

that would allow specification of an MBID in case of 2 releases with the same spotify id

How such conflict is currently handled? Does it present the user with a choice, or it just rejects the import since it's ambiguous?

I have no clue, I'll check in a bit

Lioncat6 avatar Oct 25 '24 03:10 Lioncat6

This is the thread of the person who created isrchunt if you want to ask here: https://community.metabrainz.org/t/isrchunt-is-a-songs-isrc-already-in-musicbrainz/656127?page=2

Lioncat6 avatar Oct 25 '24 03:10 Lioncat6

Thank you for the information. The tools appears to be a bit buggy, I just went through 25-30 releases of mine and tried importing, and in 10 cases the tool returned 500 Server Error.

Still, I guess it's better than nothing...

arsinclair avatar Oct 25 '24 03:10 arsinclair

Like I said, I want to make my own version specifically for Spotify importing. May or may not be integrated into SAMBL directly, not sure yet.

Lioncat6 avatar Oct 25 '24 03:10 Lioncat6

Okay, it seems when there's two or more releases it just takes the first one, it doesn't resolve the conflicts 😢

Here's an example where two releases by mistake were linked to a spotify page, and it doesn't do a good job: https://isrchunt.com/spotify/importisrc?releaseId=0GAeZ2HCkJ1GL5LaosklAG

arsinclair avatar Oct 25 '24 03:10 arsinclair

I want to make my own version specifically for Spotify importing. May or may not be integrated into SAMBL directly, not sure yet

I wasn't able to find a repository for https://isrchunt.com, so I guess it's closed source. It would make sense to have an open source one.

arsinclair avatar Oct 25 '24 03:10 arsinclair