You don’t have access to https://cdn.jsdelivr.net with your browser, now?
These URL are necessary as long as I stay in greasyfork but I plan to leave both Greasyfork and Openuserjs sooner or later.
If you cannot access these URL, you can (re)install the scripts from GitHub and then replace (in the // @require
lines):
https://cdn.jsdelivr.net/gh/jesus2099/konami-command@
by:
https://github.com/jesus2099/konami-command/raw/
1 Like
a23bed
February 11, 2021, 7:33pm
42
jsdelivr.net is skcetchy for me, sometime works, sometimes not
currently getting “ERR_CONNECTION_REFUSED” on Opera (Chrome)
Thinking my ip might be blocked,I have even tried various vpn across the globe.
Earlier on worked and the scripts installed and are currently working now.
Thanks, sorry for the bother.
1 Like
a23bed
February 11, 2021, 7:49pm
43
I’m very embarrassed to say but it was all my fault!
Not sure why, but I had block on the site in my hosts file, I’ve now comment it out
so now all is good, feel such a fool.
Please accept my sincere apologies.
5 Likes
Just a heads up to say I know this script is currently broken.
opened 09:01PM - 20 Jun 21 UTC
environment change
mb_INLINE-STUFF
major
react-hydrate
We cannot see recording comments since some change [on beta](https://beta.musicb… rainz.org/release/1f1e37cd-88bb-4797-ba9d-5e0bf5887583), that will probably occur [on MBS](https://musicbrainz.org/release/1f1e37cd-88bb-4797-ba9d-5e0bf5887583) to, soon.
Spotted by @Lotheric: https://github.com/jesus2099/konami-command/issues/445#issuecomment-864572633
- [x] Fix recording comments
- [ ] Fix recording tools removed by [react/hydrate nightmare](https://github.com/jesus2099/konami-command/labels/react-hydrate)
## Related to
- [Other MBS-9921](https://github.com/jesus2099/konami-command/issues?q=MBS-9921)
- Convert the release index page to React https://tickets.metabrainz.org/browse/MBS-9921
- NG with release with more than 10 mediums after MBS-3841 #38
- [Bitmap’s hint](https://github.com/jesus2099/konami-command/issues/596#issuecomment-871597608)
And also I intend to stop using cdn.jsdelivr.net
soon.
opened 02:55PM - 30 Mar 18 UTC
ninja
environment change
<ins>**Update 5/2/2019**: I will eventually only keep my github repo as some oth… ers do.</ins>
Prerequisites
========
- [ ] Wait for `author`, `downloadURL`, `namespace` and `version` are all aligned (#510)
- [ ] Build a _rotten_ script that will be the last version of each scripts, telling the user to come to konami-command to reinstall their scripts
- [ ] Remove scripts from GF **except SUPER.js library**
- [ ] Remove scripts from OUJS
- [x] <ins>Change all `@require` URL entries from `//greasyfork.org/scripts/` to _GitHub_ `//cdn.jsdelivr.net/gh/` (allowed by GF)</ins> 1fa7a6e5dbbb97b9ed545a1a181fc94f3ebc1931
- [ ] Replace references to `//cdn.jsdelivr.net/gh/` by direct GitHub raw commit URL?
- [ ] Use eslint to spot bugs #543
- [ ] Remove SUPER.js library from GF
Removals
======
- [ ] Remove the more "destructive" scripts from GF / OUJS #572
---
Some regular work is needed to ensure continuous availability of mirrors.
Sometimes webhooks fail.
---
https://greasyfork.org/users/2206-jesus2099?sort=updated#user-script-list where all scripts now using GitHub libraries are no longer updated.
They have good security reasons for users for that.
---
Recently, https://openuserjs.org/users/jesus2099/scripts?orderBy=updated&orderDir=desc also stopped updating because of a new licence policy. I had to work in order to restore updates…
They have good licence reasons for authors for that (#358).
4 Likes
portik
June 8, 2022, 3:39pm
45
AcoustIDs and ISRCs not working for me. But it is working 2 days ago. Is it related to last server update?
2 Likes
Yes it must be that.
I had a bug report for beta server some days ago, beta version might have been released to production (MBS), now.
I don’t remember exactly but I remember I have a good track of fixing it, thanks to @Bitmap discussion.
Workaround to run this script near the end of my userscript list worked for me (mobile and PC), but it didn’t work for Alfge and redactedscribe.
So I have now added quick workaround in the code, as @ROpdebee suggested, until the real fix , that I have no time to do in the very near time.
opened 09:01PM - 20 Jun 21 UTC
server change
mb_INLINE-STUFF
major
react-hydrate
↖ #38 – NG with release with more than 10 mediums after MBS-3841
**Workaround… is to make this script near or at the end of your userscript list.**
---
We cannot see recording comments since some change [on beta](https://beta.musicbrainz.org/release/1f1e37cd-88bb-4797-ba9d-5e0bf5887583), that will probably occur [on MBS](https://musicbrainz.org/release/1f1e37cd-88bb-4797-ba9d-5e0bf5887583) to, soon.
Spotted by @Lotheric: https://github.com/jesus2099/konami-command/issues/445#issuecomment-864572633
- [ ] Fix recording comments
- [ ] Fix inline ISRC and AcoustID
- [ ] Fix recording tools
- [ ] Fix amounts of tracks and works in 10+ medium releases
- [x] Hide them until they are fixed 0f830d11fd2371b2a011187d3f92d5f12ec226d2
## Related to
- [Other MBS-9921](https://github.com/jesus2099/konami-command/issues?q=MBS-9921)
- Convert the release index page to React https://tickets.metabrainz.org/browse/MBS-9921
- NG with release with more than 10 mediums after MBS-3841 #38
- [Bitmap’s hint](https://github.com/jesus2099/konami-command/issues/596#issuecomment-871597608)
2 Likes
I will work again on this script bug , because the work-arounds are still not enough for some releases like this one , and others too, as seen below:
Since a few days I can’t see the AcoustID’s anymore using the INILINE.STUFF-script from @jesus2099
[image]
Do you see this ID’s in your environment?
Example:
agatzk
June 28, 2023, 3:39pm
48
Did this script stop working recently? Mine hasn’t worked in at least 4-5 days. I understand it could take some time to fix, but wanted to know if it’s broken for others as well.
1 Like
Can you give me a URL and tell me what you expected and what’s not showing up?
It’s quite random until I fix the last linked bug, though…
1 Like
agatzk
June 28, 2023, 7:58pm
50
I primarily rely on the script to easily view/click ISRCs and AcoustIDs from the release page. Here’s an example release where the recordings have ISRCs and AcoustIDs attached, Release “Freddie” by Freddie Gibbs - MusicBrainz . Today it looks like this:
I’m used to the ISRCs and AcoustIDs showing up “in line” underneath track titles. I could only find one old screenshot of a single track on a release depicting this, but I think you know what I’m saying
1 Like
It works for me.
Did you click ISRC and AcoustID show button in the sidebar?
Android Kiwi Browser with Violentmonkey
Did you try the clumsy workaround (move the script at the end of the script list)?
1 Like
agatzk
June 28, 2023, 8:41pm
52
I do not see the object in the sidebar. I’m running Chrome (Version 114.0.5735.135 (Official Build) (64-bit)) with Violentmonkey. Troubleshooting:
Move script to last in violentmonkey > no change
Disable all other scripts (16) running on release page > no change
Uninstall and reinstall script > no change
Try on different PC (Chrome) > works as expected
Try in incognito mode on original browser > works as expected
Clear browser cached files and images > still not working
Close and re-open Chrome > still not working
Unfortunately I think I need to clear my cookies and site data for musicbrainz.org .
agatzk
June 28, 2023, 9:22pm
53
The culprit is the Dark Reader extension (Dark Reader - Chrome Web Store ). Disabling the extension allows the script to function as expected. Unfortunately it’s my primary way to modify the MusicBrainz UI to prevent it from blinding me with brightness. Guess I’ll find workarounds. If anyone has suggestions for another ‘dark mode’ extension please do tell
Thank you @jesus2099 for your kind support and all of your scripting efforts which make us way more productive around here.
I guess the most natural things would be user stylesheet installed in Stylus extension.
I guess it should already exist , somewhere.
2 Likes