Hi

So far, there is no news of userscripts.org and no idea if it is going to come back or not.

I was wondering, how would @updateURL & @downloadURL work here?

Does OUJS send the meta data for the update?
Does GM accepts the update from OUJS?

I looked at a few of the script at OUJS but most had their downloadURL pointed elsewhere.

Thank you
:)

how would @updateURL & @downloadURL work here?

Best to omit these if this is your permanent and only home here. If you have an external repository and want it to update from there by all means add it in... I would suggest that you create a .meta.js on that repository though. OUJS doesn't need this since GM 1.15+ sends the request header.

See also:

As Marti mentioned, OUJS doesn't need those metadata keys to send updates and respond to update checks. It uses another method supported by all user script engines with updating capabilities. Also as Marti said, if you want your scripts to update from here, omit those keys from your scripts.

Thank you
The reason I asked was that I was not sure. :)

So far, after testing & checking config.xml, what I understood is that:

  • If there is no updateURL & downloadURL, GM logs the install URL as the downloadURL
    GreasyFork intentionally removes updateURL & downloadURL from all scripts
  • MonkeyGuts seems to have adapted both (ie .meta.js?c & .user.js?c) (although the site is heavily dependant on client site scripting)
  • OUJS doesn't alter the updateURL & downloadURL

To be very honest, I cant make up my mind.
I have seen a few scriptwriters that use github as their permanent private repository. I dont know how practical it is..but I have to find a permanent home

PS. The Comment count in this section includes the original post ie after the first post is made, it says comments 1. Other systems count comments after the initial posts.
PS2. View Source is a dead end..there is no back button or link to get back to the script's main page ie for install (have to use browser's back facility)

Other systems count comments after the initial posts.

Other systems count replies after the initial posts. ;)

  • If there is no updateURL & downloadURL, GM logs the install URL as the downloadURL

Correct however in GM 1.16beta5+ it uses a header so if the server recognizes it it will return just the metadata block. See my announcement here.

  • GreasyFork intentionally removes updateURL & downloadURL from all scripts

That's not all they remove. Changing legally protected scripts can be a sticky issue to deal with so it's best not to do it. If you don't type English posts they'll ban you from the site. I thought that was rather prejudicial when I read it in their terms of use... and there is more like this.

  • MonkeyGuts seems to have adapted both (ie .meta.js?c & .user.js?c) (although the site is heavily dependant on client site scripting)

I did not know that about that sites client side scripting... good to know and thank you for that. I don't particularly have favor for equazcions style of accusations so I haven't had much of a chance to visit his pre-fabricated site yet.

I have seen a few scriptwriters that use github as their permanent private repository. I dont know how practical it is..but I have to find a permanent home

I look at this way currently... I have an external repo where I keep my code and content and have a presentational website, such as OUJS here, where I can work in a more integrated community than just a standard SCM offers.

View Source is a dead end..there is no back button or link to get back to the script's main page ie for install (have to use browser's back facility)

I had to think about the logical human interaction on this one quite a bit and came to a few conclusions:

  • "It's too hard"... to use the back button in the browser... was the first thing that came to mind.
  • "What if someone linked directly to the source page?"... then it could be kind of irritating.

So in conclusion I will support this Request for Enhancement (RFE)... however you need to do it on the upstream issue tracker first. There are a few UI changes that may be coming through at some point so we'll need to patiently wait on polishing finishes such as this.