Retest mongoose using native Promise construction.

Test for specific mongoose migration.

Re: @rpatterson:

Installing tampermonkey/etc.

https://openuserjs.org/about/Userscript-Beginners-HOWTO under the Tampermonkey linkage.

Finding userscripts

You must be missing "Search Userscripts" form in the Userscripts link and every accounts Script lists. OOPS :)

Installing userscripts

Again https://openuserjs.org/about/Userscript-Beginners-HOWTO

Developing and releasing your userscripts with the community

Again https://openuserjs.org/about/Userscript-Beginners-HOWTO as well as your account name at https://openuserjs.org/users/rpatterson

I'm chewing through those now.

Glad that you took a moment to see what your account can do directly by clicking. HIGH FIVE

Still though, this seems like it should be easily google'able,...

All the "about" pages are definitely SEO'd and when you modify your profile that is too.

... or a pinned discussion, ...

No need to repeat what is already in the https://openuserjs.org/about/Userscript-Beginners-HOWTO and the individual profiles.

... or a footer link,...

Take a few moments before you post a question to examine the footer navigation links and you'll see that there is the About link clear as day.

or a FAQ,

Again https://openuserjs.org/about/Userscript-Beginners-HOWTO

or something more discover'able than that.

Would making a stamp on your hand, or placing a ribbon around one of your appendages, help find the common links on every page? ;)

I see an import from github and instructions fo the github hook, but nothing about what the repo's structure should be?

As we are not GitHub (GH) we don't have their documentation which is also SEO'd (searchable). Use GH however you like as we only import .user.js for Userscripts and .js for libs... which just happens to be mentioned at https://openuserjs.org/about/Userscript-Beginners-HOWTO and on each Add Script and Add Library page. WOW!!!!!! If you need a template checkout an Admin or higher user on the Users link and see if any of them mention utilizing GH... I do and I just mirrored what one of the Founders did as it seems to be proficient in style for how I use git... to each their own though as git is quite versatile on user preference.

So I think your bottom line is to check out the navigation headers fully first.

Thanks and good luck spending some time reading what's been in front of you the whole time. TA DA! :)

Re: @jscher2000:

I use the copy/paste method.

That works too since we are a Presentational Userscript Repository here on OpenUserJS (OUJS)... nice to have a SCM via GH though on occasion to refresh the noggin if a lot of time has passed however as you said not always necessary which is why it's optional. WHOA! COOL! :)

Re: @max30_1:

First off please try to not hijack another unrelated discussion. I moved your comment to an existing, related, discussion.

...use the google translator.

We know how to utilize any translator service. Thank you.

Мой аккаунт забанен.
Это мои авторские скрипты
https://openuserjs.org/users/MAX30

That account is not banned it is related to https://openuserjs.org/announcements/Google_Authentication_Deprecation#comment-15ad82d5f4d

Это моя вторая временная страница и тоже забанена
https://openuserjs.org/users/MAX30PageTwo

This one, however, is banned permanently for a Terms of Service violation of an obfuscated script. There is zero tolerance for posting obfuscation. There will be no warnings. There will be no second chances. Those accounts will be strongly eligible for termination.

Мой профиль разработчика на этом форуме (посмотрите дату и мой IP)
http://smotri.forum2x2.com/t206-topic
http://smotri.forum2x2.com/t69-topic
http://smotri.forum2x2.com/t191-topic

We need information here on the OUJS profile in order for verification but it is absent. In other words the MAX30 account is permanently orphaned.

Восстановите мой профиль

Love translations... this seems more like a command rather than a request...

Спасибо за понимание.

... however this tempers it.

Regardless... as I have already stated above you are out of luck.

Not sure exactly what you are looking for but maybe this script would help with translations?

You have a very short period before the axe falls on your account.

Please remove all affected scripts.

Thanks,
OUJS Admin

Re: @Artex:

Okay so your auth key for the duplicate account should be on the original account and I've merged the two comments here into that account as well. So you should be good to go... ensure that you are logged off with your current session and log back in with your username of Artex which uses the google credentials of the "old one" as you put it.

Just a FYI a "newer one", e.g. new google credentials, will spawn a new account here which is how it's supposed to be... so can't change your email with this sort of authentication... however you can add other auth types (Twitter, etc.) as a secondary as you may have already read above... by going to https://openuserjs.org/user/preferences .

I was working towards asking @lednerg if that user wanted to destroy the google auth key since there was another on that account but never heard from that user again. *shrugs*

Re:

See https://openuserjs.org/announcements/Google_Authentication_Deprecation#comment-15ad82d5f4d

Since you left a trail on the old account leave a twitter message, that is public, requesting that this account username is you and that you want it merged with your old account username, e.g. be specific on the usernames so I know it's really you and address it to me, and when I see it I can merge your account.

I will be back online in about 8 hours to revisit this thread presuming you give me a simple message here saying "done" or the like.

Thanks.

Pro test comment.

Pro test comment.

Re: @NobleReign:

@match chromium/chrome reference

Pro test login and comment.

It's been a little bit over three weeks for this. TOS default action is applied for all affected scripts. Please do not do this for your scripts as it may result in eligibility for account removal as well.

OUJS Admin

Re: @Marti:

Since this hasn't happened yet it is being done as you for you. Please feel free to reupload if you wish. You lose your stats this way.

Re: @Marti:

Since this hasn't happened yet it is being done as you for you. Please feel free to reupload if you wish. You lose your stats this way.

We had a disconnect from AWS and your script homepage is orphaned from the source currently. If you reupload it under the https://openuserjs.org/user/add/scripts and use the Upload Script button it will reinitialize your script homepage so it can be installed.

Thanks,
OUJS Admin

We had a disconnect from AWS and your script homepage is orphaned from the source currently. If you reupload it under the https://openuserjs.org/user/add/scripts and use the Upload Script button it will reinitialize your script homepage so it can be installed.

Thanks,
OUJS Admin

Re: @Sandbird:

... is there a version history ...

No.

... like greasemonkey has ?

GM doesn't have this either.

... so basically i lost my most updated version ...

Probably.

OUJS is currently a presentational repository (Hover over the OpenUserJS in the upper left corner tooltip). If you need diffs and versions I suggest GitHub, SourceForge, or the like. For local edits I can currently recommend using git-scm, or the like, even if you don't push to a remote... then you'll have a history when you commit a change. :)

Reminder and recommendations for new users (and perhaps some older ones):

1. If you flag a script, please be detailed as to why but succinct... one word explanations are not enough to arbitrate a decision and risks your account removal.
2. If you are the source author and you do not have at least a @license key in the UserScript metadata block that states what type it is and where the text is, it also makes it more difficult to arbitrate when a report comes in externally. e.g. Even if your Userscript is proprietary and subsequently required to be offsite only you need to include a license key and point it to that license type and URL. If your offsite Userscript is "hidden" that also makes it more difficult to make any kind of decision.
3. Please do not use flagging as a means to let us know a script is "good"... that is really not meaningful in the context of moderation. Use the up and down vote arrows if you like/dislike it that much. When you visit that scripts homepage you will see it as a darker colored arrow on how you voted for it.

Thank you for your courtesy,
OUJS Staff

Re: @Marti:

And we're back... total offline time ~21 minutes.

Time for another offline backup... should be about 20 minutes later this evening the 15th of April, 2017. This should give you all time to finish your taxes in the US. ;)

Greasemonkey Port 3.10.0.1rc3pre-sm.xpi is available now at the SF file repo.

This turns off the skipping the browser cache so 429's shouldn't happen when OUJS is updated shortly in sequence. Also new em:minVersion is SeaMonkey 2.40 or better.

Re: @j80r59m:

Where did you read that Windows portables could do this?

Okay folks... we're going to try a rc2 here to modify GM to handle some of the status codes we still handle normally e.g. 429's mainly but a few others. This does not address the caching issue that GM upstream enforced back in 2014. That will come after some thorough testing around the web hopefully with some help.

Greasemonkey Port 3.10.0.1rc2pre-sm.xpi is available now at the SF file repo.

If you have any issues on other sites with status codes please let me know and you can reinstall Greasemonkey Port 3.9.0.1rc1pre-sm.xpi if you want to revert.

// @name         New Userscript

... is way too vague. Please delete and upload a new script with what this affects for @name.

Thanks,
OUJS Admin