Re: @private_lock:

Why is the editor here...

With the minimal impact it gives just ignore it. JSHint is incorrect on all GM instances.

See also:

• ajaxorg/ace-builds/issues/47.

Re: @TimidScript:

Thanks for closing the scripts

Welcome... it's not a perfect solution but the rest can be left up to sizzle at the next DB migration/refactor. ;)

I assume that won't affect the end user script(?).

What is a Library Script?

Would an "@include *" be ok?

Only if you have the @exclude * in the UserScript metadata block as well on publishing to OUJS.

May I know why I need to add this?

• #418 Follow the issues and notification sent out. :)
• A new one that will definitely be going away without further notification since it was done after the TOS announcement.
• The cross-site compatible UserScript metadata block is a courtesy from me... sizzle initially wanted no metadata blocks but I understand the need for other site compatibility... so it is a grant at the moment... if it continues to be abused by others it could go away.

See also:

• http://userscripts-mirror.org/topics/61672.html Historical chatter

@TimidScript

You are officially unique routed with this double issue. You should be able to open and close either one in the list but beware they both point to the same data store. e.g. currently mirrored.

If anyone else is encountering this issue... speak up soon before I move on. I've fixed two other instances in the DB that I found.

Hmmm think I have to wait on sizzle here for more access to see how this is laid out... I don't do well making educated guesses on this part. The best I can offer right now is a 404 page for it. Someone will try again when we get a little further along.

Re: @Marti:

Yes it is which is a litte weird... however with any luck you can close both issues.

Re: @zwxr:

Is this mirrored?

Retest

Re: @TimidScript:

Can admin please close both issues...

Your turn to try again. ;) Please reread the TOS announcement regarding your libs here too. e.g. sometime just slightly after the holidays things need to change before they get removed... this applies to all libs... and I'd rather keep your contribs here without interruption. :)

Re: @havilson:

The problem seems to be that the script is no longer available on it's repository.

This one has gone up and down multiple times... it finally showed for me. The google drive hosted script is also obfuscated which isn't allowed by the TOS. This script will be going away at some point.

Greasemonkey Port 2.3.0.1rc1pre-sm.xpi is available. Finally had some spare time to do this.

Re: @jerone:

there wasn't a copy-paste solution

Me too but from the reverse angle... "Submit Code as Fork" on the Source Code page allows one to change the @name which is fairly common with some authors... whereas a single fork button would be a direct fork of it current metadata and all.

Re: @Marti:

Retest again

Re: @Marti:

Retest

Please read the TOS before publishing. bye.

Re: @trespassersW:

Patience and eventually. You can still fork on the Source Code tab of some other script or library.

Your license appears to be BSD 3-Clause.

It is highly recommended to set the @license key to that instead of applying the default MIT for your users. The recommended structure for this key can currently be found on this OUJS page in the left column.

I also find it interesting that "All rights reserved" is in BSD licensing. Licensing is there to leverage your copyright and that statement basically says that you aren't leveraging... but that's a BSD issue not yours there.

Anyhow Thanks. :)

Re: @TimidScript:

The issue is fixed however the DB hasn't been corrected yet. Nothing I can do. Sorry.

Have you given any thoughts to Content Security Policy potentially breaking this library? I'm doing what I can at Moz with the expanded principal but until that is addressed there might be some issues on certain sites and potentially more.

See also:

• greasemonkey/greasemonkey#2046.

This is not permitted in the Terms of Service. bye

Re: @jesus2099:

The flaggers name shouldn't be shown... I'd rather not have a flaming war on OUJS... but the reason would be quite helpful... which is part of #262.

@TimidScript it was universal proverbial btw. ;) :)

This is not permitted in the Terms of Service. bye

This is not permitted in the Terms of Service. bye

The Terms of Service has been updated, in particular regarding Library scripts... please review it and make the appropriate changes necessary to applicable Library scripts.

Since it is around the holidays extra time will be given to fix this but soon after some Library scripts may be removed.

Thanks.

And here at http://userscripts-mirror.org/scripts/show/7467.html would be the OgamerNLs original... lots of derivatives since then for sure.

Re: @Marti:

another rather.