-
Notifications
You must be signed in to change notification settings - Fork 412
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
Greasy Fork update/download URL changes #1904
Comments
That will work (but only for newly installed and updated scripts). 👍 |
Sorry, not sure what exactly you mean by "updated scripts". If a user installed from URL1, then I change URL1 to start serving out scripts with
|
This is what I meant. |
Great, thanks for clarifying. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Greasy Fork is changing the URLs where user.js and meta.js code is hosted. This change is being done to help handle the load on the server coming from update checks.
New URLs are in the format:
https://update.greasyfork.org/scripts/1/GreasemonkeyTampermonkeyViolentmonkey%20test%20style.user.js
https://update.greasyfork.org/scripts/1/GreasemonkeyTampermonkeyViolentmonkey%20test%20style.meta.js
The
Accept
header is not read - what you get is solely based on the extension.The old URLs in the form
https://greasyfork.org/scripts/1-greasemonkey-tampermonkey-violentmonkey-test-style/code/GreasemonkeyTampermonkeyViolentmonkey%20test%20style.user.js
https://greasyfork.org/scripts/1-greasemonkey-tampermonkey-violentmonkey-test-style/code/GreasemonkeyTampermonkeyViolentmonkey%20test%20style.meta.js
will continue to work indefinitely, but may be updated to just redirect to the new URLs.
If a user has already installed from https://greasyfork.org/scripts/1-greasemonkey-tampermonkey-violentmonkey-test-style/code/GreasemonkeyTampermonkeyViolentmonkey%20test%20style.user.js, and I add the following to the script:
Will that properly start getting updates from the new URLs? Or is there a better way to accomplish this?
The text was updated successfully, but these errors were encountered: