Re: @chacham:

... cache ...

Good idea to use search engine caching to assist. :)

Some miscellaneous notes here about newer version requests...

• SeaMonkey (SM), to my knowledge, doesn't support e10s yet... nor do I expect them to anytime soon. Timeline wise we're possibly looking at well over a year is a guesstimate... unless notified in a status meeting (archives).
• With all the foobars that the Fx team is doing right now I applaud Anthony for trying to keep things up to date in upstream Greasemonkey (GM).
• I still haven't decided if I want to open an issue tracker myself and the others are just as busy.
• If you are having issues with a GM API function and can provide cross-reference to a working script in Fx I will make an attempt to retest it in SM (preferably reduced test case otherwise I may not have time for it)... no guarantees ... (One known issue is GM_listValues which hasn't worked in newer SMs and would require a major rewrite in non-e10s and a strong veer from the near parallel fork architecture which is beyond the scope of this port at this time)... buzz me on GitHub (GH), for now, under your UserScripts repo and I'll see what I can or can't do. This doesn't mean that I will write your script for you and I most certainly don't care to sign up on a bazillion other sites. :)
• Please remember Greasemonkey Port (GM Port) repo is still Beta and typically comes with all the bugs/features that the corresponding GM version had/has for that upstream version.
• I'm also a developer/admin here for OUJS and that takes a lot of my free time.

Thanks so much for your looooooooooooong term patience with this. e.g. this port is at a frozen state for the time being.

NOTE: Restored from search engine cache and augmented.

Re: @chacham:

Thank yu for the site, the maintenance, and the updates!

You are welcome. :)

Your other answer is on the proper discussion over there.

Re: @chacham:

The about page on one of my scripts (the only one that has one) is an older version. Is there any hope for those?

Nope. As you read on development the data was destroyed with that dependency foobar. I lost some important text myself that I need to recreate if possible at some point.

Re: @desarrolloforos:

Este script es ilegal

You will need to get a lot more specific than this. I have looked into the original authors of both this script and some of yours and it doesn't appear to be either of you. Unless you have concrete evidence, preferably in English would be helpful, I will be Admin closing this issue.

es-ES courtesy of Microsoft Translator:

Usted necesitará obtener mucho más específico que esto. He mirado en los autores de este guión y algunos de los suyos y no parece ser una de ustedes. A menos que tengas pruebas concretas, preferiblemente en inglés sería útil, que voy a ser Admin que cierre este tema.

Thanks,
OUJS Admin

That's all for this migration I think.

A-ha... found a log for the usernames:

• Hello World by @sizzle
• Bypass YouTube age verification / Youtube-Altersverifikation umgehen by @tfr
• Crowd Task Google Search Link by @swole_hamster
• Swearify-hansenED by @chrishansen69
• Charcount by @AIMGamesDaler
• Swearify by @chrishansen69
• Under Research Works by @Jefreesujit

Re: @trespassersW:

Now that we are back to current GH master HEAD here on production you may install the most recent version of this script from OUJS if you wish.

NOTE: If the grammar files are still in your cache you'll need to either wait until the expire time (this was on my TODO list for development to correct but the "intermission" interrupted that), or just clear your cache, and it should resume normal operation... otherwise it will be sitting on this message again. I'll version bump as soon as I can but the cache time for anyone using the older version needs to expire first before I do that and I'll be away from dev station for a few days.

Re: @Marti:

Done with migration... in validation, which comes with this, encountered the following script names that didn't have source on S3:

• Hello World
• Bypass YouTube age verification / Youtube-Altersverifikation umgehen
• Crowd Task Google Search Link
• Swearify-hansenED
• Charcount
• Swearify
• Under Research Works

All the above scripts without source have been deleted as their respective user... except for @sizzle 's "Hello World" since I don't have that access but he has been notified to fix it. If you have a script name of these please re-upload your script source at your earliest convenience. Probably should have nabbed the username too with these in the console... but hind sight is always 20/20.

Provided everything goes well in the next 24 hours or so I'll be remigrating the DB now that I seem to have access.

So Sept 3, 2015 late in the evening there will some scheduled downtime. Did this ~9 days ago once on the original DB with the same code. Approximate time should be about 20 minutes perhaps a little less. I'll try to do this as late as I can (EST) but we really need to get the HEAD here back to current master on GH dev.

Thanks again.

Re: @trespassersW:

Thanks... use this version on GH until we resync OUJS completely... 3.0.0.1 is for the current master not at the HEAD that we are using at the moment... I'll drop in an update notice on this script manually for those to reinstall from here. e.g. watch for it. :)

Re: @jscher2000:

I viewed the source and clicked Submit and now the script information page has the contents of the header.

That works too.

Re: @jscher2000:

If there is no script homepage, e.g. new scripts within the last 21ish days the direct install url should be nabbed for those that said they didn't have backups... this may even work for users that aren't here right now from the restore.

If there is a script homepage the source is still from S3 which should be up-to-date... but MongoDB info from the documents may be out of date... if you look at oujs - Meta View it says that it's 3.0.0.0rc6... but if you install it... it pulls my last webhook of 3.0.0.1. If the source is on GH you can just resend the webhook in their settings and that should resync it I think.

This should self correct itself on DB migration as well when I'm able to do it.

Correction... script sources are intact but not matched with DB meta... Those who updated in the last 21ish days should nab their source immediately.

So @sizzle restored his last backup... which is August 10th, 2015

All comments/disucssions/users/scripts/etc. from then until now are lost. I apologize profusely. I'll work on redoing existing commits including the DB migration ASAP.

More details are at #729

Re: @jscher2000:

So please don't take my note as a criticism of this site!

Sorry that wasn't my intended goal to invoke that sort of response... it was to let you know of a lesser known route if you wanted to use it. I'm actually rather fond of your contributions and questions. :)

Re: @chacham:

Where do you get that URL from?

It is a route (a.k.a. URI path) that @sizzle added in a while back.

I would like to add it to my scripts.

If you want to only count new installs then yes by all means publish with that. :)

Sounds like something that could be added automagically.

It could... however some authors like to control where the updates come from with consolidation to one site or another. I usually suggest leaving it blank and let the .user.js engines handle it from wherever it is installed but some people still run older versions that don't support those metadata keys automagically.

Your UserScript metadata block code at:

// @updateURL   https://openuserjs.org/scripts/Nindel/Ice_Apple_Auto_Eater?c
// @downloadURL https://openuserjs.org/scripts/Nindel/Ice_Apple_Auto_Eater?c

shouldn't be trying to tell the userscript engines to check for updates from a web page and install the script source from a web page. Please correct to use the .user.js and .meta.js, or preferably omit these keys, with:

// @updateURL   https://openuserjs.org/meta/Nindel/Ice_Apple_Auto_Eater.meta.js
// @downloadURL https://openuserjs.org/install/Nindel/Ice_Apple_Auto_Eater.user.js

You appear to have this issue in another of your scripts as well with other hosting sites that don't seem to exist anymore... which is why ideally you should just omit them.

Thanks.

And for the first notice...

Sometime between Thursday the 30th of July, 2015 and the 1st of August, 2015... there may be some scheduled downtime to perform some migration.

Again... thanks for your patience on this. :)

NOTICE

At some points in the future this should be where notifications of usually scheduled server maintenance will be for those not watching Development.

During those announced times the server may be offline. Every effort is currently made to limit downtime.

Thank you for your patience.

Re: @FaizanAnwerAli:

How can I message other user?

Unimplemented yet.

How can I get emails or notifications?

We would have to store your email address which we currently do not so it is more likely an on site messaging system will be done first at some point first. Although there might be atom feeds, or equivalent, at some point as well.

Re: @TimidScript:

But you can see if you have any new discussion posts on your scripts from anywhere on the site but using my Script OUJS-1

Yup... @FaizanAnwerAli this is currently a gap filler.

Re: @Marti:

I'll fix your quote syntax

Fixered.

Re: @TimidScript:

CUSS, CUSS and more CUSSING

/me hands you a case of bar soap ;) I'll fix your quote syntax in that post but you really need to preview before you reply until @sizzle is ready with discussion editing. I won't always be this proactive and I know it's difficult. I'm working hard on the metadata as we speak... hopefully to be done this weekend but may need some longer termed testing. :)

Re: @TimidScript:

doubled posted

Removed newest double post. Interesting... will add it to my watch points.

Jumped to the wrong conclusion.

Big difference here... "appears" is not saying you did for sure. Please remember this... e.g. I didn't say you absolutely closed it. :P Might be a feature recheck/enhancement to add to development.

Re: @FaizanAnwerAli:

how to open this issue?

@TimidScript appears to have closed this issue.

You have a very short amount of time before this script goes away permanently... Please re-read the Terms of Service link at the bottom of every page especially this section.

All scripts on OpenUserJS.org are immediately public and able to be used for distribution by any guest and/or member. If you don't correct this the script will be banned and perhaps more.

Thanks.