Please re-read this section.

Provided the fork history is intact it's acceptable... if not flag it and then I'll add it in if necessary.

Thanks,
OUJS Admin

Heh... I should know better than to do anything on 4/20 ... bizarre dependencies... working on it.

And we're back. :)

In about 40 minutes I'm taking the server offline to do a much needed backup... should be approximately 10 minutes.

See you on the other side.

Re: @Marti:

as soon as I get it up and running locally I should be able to reset every ones counts from that date that are way off.

One issue that I see is that some are definitely gaming the install counter now... so I'm not sure this would do any good to reset them. I think I've done everything I can to minimize some of this noise but as @sizzle said the install counts aren't guaranteed to be accurate elsewhere a while back.

Btw it was either a fix or a removal of this script.

This was fixed for you due to lack of response. Chose item 3 as it's closest to the source published. You also had a regular expression issue with checkversion and /\/\/\s+@version\s+(\d+\.\d+\.\d+) is the corrected one.

Quite honestly I don't know why you have this in here other than for super old .user.js engine support. The vast majority of extensions/add-ons do update checking by themselves.

Leaving the issue open.

I wonder whether it might need a caption to explain what it's for?

There is now a question mark and alternately an exclamation mark when we are locked down that points to a document page.

Don't forget to bump your @version from 0.7.5 to something bigger like 0.7.6 please. :)

What you should not currently have...

GM_xmlhttpRequest({
  method:           "GET",
  url:              "https://openuserjs.org/src/scripts/burn/Youtube_Persist_Worldwide.user.js#?sinc="+time,
  headers:          { Accept:"text/javascript; charset=UTF-8" },
  overrideMimeType: "application/javascript; charset=UTF-8",
  onload:           function(response) { checkversion(response); }
});

... what you should have ...

GM_xmlhttpRequest({
  method:           "GET",
  url:              "https://openuserjs.org/meta/burn/Youtube_Persist_Worldwide.meta.js#?sinc="+time,
  overrideMimeType: "application/javascript; charset=UTF-8",
  onload:           function(response) { checkversion(response); }
});

... or ...

GM_xmlhttpRequest({
  method:           "GET",
  url:              "https://openuserjs.org/src/scripts/burn/Youtube_Persist_Worldwide.meta.js#?sinc="+time,
  overrideMimeType: "application/javascript; charset=UTF-8",
  onload:           function(response) { checkversion(response); }
});

... or lastly and possibly the least ...

GM_xmlhttpRequest({
  method:           "GET",
  url:              "https://openuserjs.org/src/scripts/burn/Youtube_Persist_Worldwide.user.js#?sinc="+time,
  headers:          { Accept:"text/x-userscript-meta; charset=UTF-8" },
  overrideMimeType: "application/javascript; charset=UTF-8",
  onload:           function(response) { checkversion(response); }
});

While it is nice that you are using the src/scripts route you are pulling full script source on internal update checks for you and your users.

Thanks for fixing this as soon as possible.

Re: @jscher2000:

How's that? I presume you want lockdown mode to allow publishing of scripts but not serve until added in? Like it is said in the FAQ I'm hoping this isn't needed in the future but I always recommend the @updateURL personally to avoid this modes consequences.

Re: @jscher2000:

Great shared idea. That's what #970 is about... a helper to show the cleaned href to insert. Still working on the brute force attacks though.

If we have to we'll amend the TOS to wrap just like usoCheckup did... but that needs @sizzle approval first and implementing that is a last resort... have to explore all other known avenues first.

Rather than keep letting everyone know manually if the @updateURL restriction is in place I've put it on the About page referenced at the bottom of every page on OUJS. It is also cleaned up in all the Document pages and Userscript upload page.

The server stats today look better and I do appreciate everyone for their feedback.

alter the uploaded script

We usually prefer not to do that. This has been a trying time, lots of chatter, with TM being bugged and taking down servers... I'd rather not have this in place myself due to GH but if it means maintaining the integrity of the site, which is part of the TOS, then it has to be done when needed until a more permanent solution can be achieved. So this has nothing to do with your not liking or disliking it... it's part of the mutual agreement for us to host scripts.

In greasyfork I don't need something like this

As you are well aware his site was taken out too... so don't try to lead others into thinking otherwise... this requirement was necessary and if it's needed again we'll implement it.

Re: @Marti:

Still best to use https://openuserjs.org/meta/username/scriptname.meta.js syntax for @updateURL.

Re: @Marti:

I've now blocked anyone trying to publish a script without an appropriate @updateURL e.g. if it's absent or set to a OUJS .user.js it will be rejected.

I've temporarily lifted this restriction.

I've temporarily lifted this restriction.

Btw we're not the only site being bombarded... so keep that in mind.

Re: @lino10:

After I upload the script, the filename changed.

You can also put in something like @updateURL https://openuserjs.org/meta/xxxx/xxxx.meta.js temporarily and it will upload it... then copy the url from the install button and fix it... however if one of the mods or higher notices a script that hasn't been corrected it... it will be removed.

Re: @lino10:

How to put the url if the script is not even on the site yet?

#970 and what I just said about some new pages probably. I've been up for over 24 hours now so it won't get started until tomorrow unless one of the others pick it up.

Thank you for your patience.

See here, here, here and the FAQ item here.

We're currently in a "lockdown" and a few more pages need to be made. I see you have one script so to use the meta routine... copy the url on the install button and then change it according to the documentation... it's quite simple to change install to meta and the .user.js to .meta.js.

Re: @jscher2000:

Thanks.

I've now blocked anyone trying to publish a script without an appropriate @updateURL e.g. if it's absent or set to a OUJS .user.js it will be rejected.

Update.

1. "Went back to school" for the last 7ish hours.
2. Changed a few things around... you'll be seeing 503's some more everywhere until this subsides.
3. We got a kernel update! ... hopefully this one is better... beginning testing. If you don't have an @updateURL or the url points to .user.js here on OUJS we currently aren't serving the script ... plain and simple as before.
4. I have access to April 3rd, 2016 install counts... as soon as I get it up and running locally I should be able to reset every ones counts from that date that are way off... however... until TamperMonkey v4.0.25 (and better since that packages .meta.js check is broken even in this version) is fully deployed world-wide you are stuck with what you have.

Thank you for your extreme patience... I hope this helps.

I've put in a request to @sizzle to grab a copy of the DB and save it for rollback... what this means is when this is over we'll rollback the pages and their stats to that copy... the scripts on S3 will be whatever you've done in the last period but the MongoDB will be out of sync... this happened once before in a completely different issue but I can fix that when that time comes.

See I'm so exhausted I forgot I put in an option to not serve those without @updateURL. This is in effect now.