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
Let server deliver a script which will never be (auto) updated #2836
Comments
|
updateURL and downloadURL are not supported for 4.x. |
In 3.x we just used the standard AOM controls for this. In 4.x we don't have automatic updates at all yet, so we'll just have to include this as a base feature, once we do. |
Would putting |
Oh I've just realized that you're saying you want the server that delivers the script to tell GM that it shouldn't update the script. (Whoops, didn't quite get to the end of the description ...) There's no plans to ever read/use the value of any OTOH if TM supports a none value, there's always compatibility to consider. |
The OP says:
From this, I assume that the query parameters are effectively permalinks to specific user scripts. It is also most likely that any auto-update / check-for-update functionality will use the internally saved |
Yes, exactly.
Greasy Fork stores the scripts in DB and rewrites the source anyway (e.g. generates a meta.js from a user.js). Changing the source is not a problem for me. HTTP headers may be a problem as the scripts may be going through caching software.
In my parlance, the version parameter provides a permalink to a specific version of a specific user script.
Greasy Fork does not use URL parameters for any other purpose than linking to specific versions, but I can't promise it won't in the future, or that other sites don't either. |
Upon further reflection: It would take more effort to be cross-engine compliant (@derjanb, @gera2ld), but: If we're going to let the source control update checking I'm thinking more along the lines of a new entry* such as: // @updates never
// @updates 24h
// @updates 7d Let the script specify how often it should be auto-updated. When I'm in active development I can keep it low, when I get stable I can tune it up (but back down if/when I start updating again). And a script host can (if they're going to be munging the script anyway) overwrite the value as they see fit (based on things like how many users have installed it, server resources, etc.). I'd like a more descriptive name but don't have a specific candidate I like yet. * Though for the never value, |
From the technical aspect, it should be sth. like |
Sounds reasonable.
Maybe |
or simply |
|
@Sxderp So you would support |
I'm not a native speaker, but the value (i.e. 24h) is not really a frequency. It's an interval or a period, right? 🤓 |
|
|
I don't really like lapse, so my next suggestion would therefore be |
@arantius, when will automatic update be scheduled? I can not switch to 3.x in FF60. |
(Also posted at Tampermonkey/tampermonkey#499)
Scripts on Greasy Fork do not have
@updateURL
or@downloadURL
, so when checking for updates, the URL originally installed from is used when checking for updates. This is good.Greasy Fork also allows users to install previous versions of a script. The install URL includes a parameter indicating in the version. In this case, updates still "work", but there will never be any changes. To save some resources on the client and the server side, I would like to indicate to Greasemonkey to not check for updates. Is there something I can put in the script to do this?
The text was updated successfully, but these errors were encountered: