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
Distinct scripts should have distinct file names #76
Comments
Other than avoiding that bug, I'm having a hard time thinking of ways having different end parts of the URL is "nice". #73 would likely result in URLs like https://greasyfork.org/scripts/123-script-name/code.user.js which I'm going to guess is not enough to avoid the bug. |
Other ways:
|
It seems a bit odd to me that Greasemonkey uses the end part of the URL for anything. It does updates based on On userstyles.org I do (name).user.js, where the name part actually doesn't matter to the server, so I can probably do similar here. |
Greasemonkey has a URL and wants to save a file. URLs are traditionally organized like file paths, slash delimited, where the last part is the file name. So that's the file name that Greasemonkey uses to save the file. Seems perfectly logical to me. Right click and pick save as, and you'll get the exact same behavior. |
The site will now offer URLs like https://greasyfork.org/scripts/358-video-wipe-ads/code/Video%20wipe%20ADs.user.js The old format will continue to work but will not be linked to. |
See greasemonkey/greasemonkey#1906 . We need to fix thatin Greasemonkey, but it is being triggered by the fact that all scripts hosted on greasyfork have the exact same file name (
code.user.js
). Having distinct file names would be nice.This is probably a dupe of #75 which I can't reopen. I consider it a valid feature request, so I'll continue filing it.
The text was updated successfully, but these errors were encountered: