Hey,

I've just come onto OpoenUserJS to update a User script I have here, and I saw that I had to update the @updateURL field.

I've done that, but my installed version of my script doesn't auto-update, presumably because the @source URL no longer works.

Does that mean that the ~1900 people with my script installed won't ever get another update without manually reinstalling?

How can I work around this to push the updated @source URL so they continue to get updates?

Specifically this is the script I'm asking about:

https://openuserjs.org/scripts/Patabugen/Always_Remember_Me

which used to have @source like this:
// @source https://openuserjs.org/Patabugen/Always_Remember_Me.meta/source

And now has @updateURL like this: (as per a change in OpenUserJS I presume?)

// @updateURL https://openuserjs.org/meta/Patabugen/Always_Remember_Me.meta.js

--
Patabugen

Re: @Patabugen:

presumably because the @source URL no longer works

@source has never been a part of updating and is specific to Tampermonkey (TM). See what it aliases to at TM and equates to an "upmix" of @homepageURL. In your case on your most recent update with the most installs that could be a value of https://openuserjs.org/scripts/Patabugen/Always_Remember_Me i.e. it is the homepage URL of the descriptive side of your presentation repository here on OUJS... but not the actual raw source Code itself. That is reserved for @updateURL and @downloadURL respectively. @updateURL is where it checks for an update, and @downloadURL is where it grabs the actual source if an update is available.

https://openuserjs.org/scripts/Patabugen/Always_Remember_Me/source

This is also okay (but not real helpful to your users) for @source since it has nothing to do with the updating system in the engines. It can be a visual display of the source Code but not the raw source Code.

// @source https://openuserjs.org/Patabugen/Always_Remember_Me.meta/source

This is just plain bugged and the route doesn't exist.

Does that mean that the ~1900 people with my script installed won't ever get another update without manually reinstalling?

If a Greasemonkey (GM) 3.x compatible engine is in a FAIL state then it is possible. I don't believe TM has the same issue but since he closed the source I'd have to go dig to find out for sure and deconstruct his code. As a safe bet for any .user.js engine always assume the "weakest" link which means possibly.

How can I work around this to push the updated @source URL so they continue to get updates?

See my previous reply and link. Not part of the update check and download source system.

The Author Tools, on each of your scripts, has been showing the usage of the updating system for quite some time (years or so) on what is "common" across all of the engines. i.e. you can select which type(s) (if available and mentioned from the FAQ) for both @updateURL and @downloadURL. Currently @downloadURL is optional but right now in lockdown @updateURL is not.

(as per a change in OpenUserJS I presume?)

Never been a change even before OUJS existed. @sizzle wrote the first updating back in the day with GM and @source has never been used. That is, again, reserved for the human side of the equation using HTML not .user.js.

So long explanation short... your misinterpretation of @source is possibly one cause (but not the only reason) of why we're in lockdown i.e. hopefully you understand the update check and download source keys better?

OUJS Admin