Waiting on a redeploy with a change... with any luck this should resolve this.

Again thanks for your patience. We all should know more in the next 48 hours or so... so keep trying. :)

Re: @spuds:

Please note https://openuserjs.org/announcements/Server_Restarts which could be affecting this.

I'm not sure why this is happening right now and I've got two separate issue reports sent in one with nodejitsu and one with sizzle.

I will post here again (hopefully) when this gets resolved.

Thanks for your patience.

How about explaining what this script is intended to do.

Point being is if you dual license with MIT then everything will be okay.

Your script started out with MIT at https://github.com/elundmark/tz-aio-userscript/blob/988c6f4663b21e6f717285e4c3934ff78da3b0e5/tzaiov2.user.js#L7

Notified upstream at https://github.com/elundmark/tz-aio-userscript/issues/7

CC Zero isn't OSI approved. Please read the Terms of Service for our site and also you can read it as OSI http://opensource.org/faq#cc-zero

test

Forward reference to https://github.com/KrazyTheFox/FIMFiction-Emote-API/blob/master/emoteAPI.js

Re: @TimidScript:

It seems one of my scripts is now flagged... Do Admin eventually remove the flagging or thus it stay until the flagger removes it?

#134 until then you are stuck with what you have. I will spend a one time around quality evaluation of any flagged scripts when sizzle is finished with his changes and reevaluate in major depth whether or not a existing flag will be kept around.

I jinxed myself.

Anytime you ask questions here that is always a possibility.

User scripts end in .user.js not .js. So for this script you would do a rename of your filename from whatever.js to whatever.user.js. Then you can correctly upload that to OpenUserJS.org.

Re: @Marti:

This could also change when we get a "reason" too.

Re: @srazzano:

#134.

Re: @TimidScript:

explain it usage.
...
it is meant to be used to get attention of admin for one reason or another.

Ideally the voting mechanism for scripts that don't work is preferred. Flagging is to get our attention.

Please don't obfuscate your code even on googledrive. This is currently prohibited.

You and/or your script has become eligible for removal.

Re: @srazzano:

@Marti,
Why was this script flagged?

Maybe someone found that it doesn't work for them. IDK.

Re: @sizzle:

... if you install a script using the short url if updating will work properly ...

<Script basedir="oujs_-_Meta_View"
    checkRemoteUpdates="1"
    dependhash="539ed46e1984fc3993e4000176dda3da5d4c4bd3"
    description="Adds a script navigation link next to `Source Code` titled `Meta` and opens a phantom url to show the detected metadata block"
    enabled="true"
    filename="oujs_-_Meta_View.user.js"
    installTime="1410548947000"
    modified="1410548947000"
    name="oujs - Meta View"
    namespace="https://openuserjs.org/users/Marti"
    runAt="document-end"
    updateMetaStatus="unknown"
    uuid="00000000-0000-0000-0000-000000000000"
    version="2.2.4"
    installurl="http://oujs.org/install/Marti/oujs_-_Meta_View.user.js"
    updateurl="http://oujs.org/install/Marti/oujs_-_Meta_View.user.js"
    icon="7ff58eb098c23feafa72e0b4cd13f396">
  <Grant>none</Grant>
  <Include>/^https?://openuserjs\.org(?::\d{1,5})?/scripts//</Include>
  <Include>/^http://localhost(?::\d{1,5})?/scripts//</Include>
  <Include>https://openuserjs.org/scripts/*/*</Include>
  <Include>http://localhost:8080/scripts/*/*</Include>
</Script>

It would appear that GM doesn't use the finalUrl equivalent after a redirect to store in the config.xml... so probably needs Require Secure Updates unticked if that FQDN is used for installs.

Re: @srazzano:

I believe I got it fixed.

Partially... since I was still at a for your max per page it prompted me... changed it around back and forth a bit just to see if I could crash it (usual testing procedure... tried 0 aka zero tried 12 tried 200 and a few other values) and I managed to get to do 100 by default without actually having it in there... then I went to go take it out and it went into a nice recursive loop always prompting me to change it and then it triggered our protection.... but I finally got it back to 25... so still might need some work to prevent that. :) This url is fun https://openuserjs.org/?orderBy=rating&orderBy=installs&orderDir=desc&limit=0&p=4 ;)

Re: @srazzano:

I would suggest still that you fix direct entry... use something like this url, https://openuserjs.org/?orderBy=installs&orderDir=asc&limit=a, to click when you test to see if you have it correct. If you have one page only of results of every script then it's a DDoS. Your script is currently triggering our protection against this which is why sizzle created this issue. You have to fix it or it will be eligible for removal permanently as per the Terms of Service. I'm trying to help you out here and so is he... you might also use the scroll event in JavaScript to only read one page in advance the further down a user scrolls (e.g. a page look-ahead only)... this will help quite a bit. Both google images and yahoo images employ this sort of JavaScript. I wrote a queue for USO that did this for installWith... e.g. I only scraped/looked ahead when absolutely necessary and always only in the view port plus maybe one or two extra outside...e.g. be more gentle before you get booted.

Re: @srazzano:

please re-test

Still present. Steps to reproduce:

• Force a hack of the max per page to be a string of a
• Save and Reload
• Goto https://openuserjs.org/?p=2
• Click the installs column which brings one to https://openuserjs.org/?orderBy=installs&orderDir=asc&limit=a

Even if I didn't put in an invalid value in your dialog from the "Table View" link... the direct url pasted into the address bar shows 100% of all the scripts in a single page for the pagination (and no table view btw). This is a DDoS in it's current state. I really suggest that you don't do this at all especially this early in our production. I may be able to add a QSP in that will do this for you but it will be a few weeks before I, or another dev, can look into it as I'm busy trying to do some other issues. It probably won't be 100 entries... 50 seems more appropriate especially with when I asked you why you were doing this. Adding 100 table entries is going to generate a lot of scrolling which is what you said you were trying to limit.

Re: @srazzano:

Now that you have added it back in today you still have the bug with https://openuserjs.org/?orderBy=installs&orderDir=desc&limit=a. I clicked on sort by installs and this is the url generated. You might want to check all of the sort by's. Thanks.

Re: @Marti:

Just remember to leave the master license header intact and add your own modification block attributing you and/or your project.

Re: @doomred:

Is this what you mean...

Here is the current highlighted master license header at https://github.com/sizzlemctwizzle/GM_config/blob/master/gm_config.js#L1-L24 plus your header stating that you modified it afterwards... like you stated.

Once I fixed out an issue in gm_config

You might want to let us know upstream with a new issue ticket. I haven't been testing it since May when USO went down but it was working exactly how I was using it. :)

I looks impossible to linking mirrored library on different sites with only web hook set on github.

Fork it on GitHub and just reference your fork/branch in this user.js with the @require. There's no need to web hook it in for that usage. You can see my fork and my branches here. master branch is a mirror of upstream GM_config (GMC) and slave branch is around the last version of version 2ish. Sizzle uses commit hashes over major dot minor dot build versioning so that's why it's "2ish". You can create your own slave branch, or other name, on your own fork of GMC and modify to your hearts content.

Greasemonkey Port 2.2.0.1rc1pre-sm is available. The affected issue with GM_xmlhttpRequest tests okay here. Available on across-stream repo. Please note new minVersion is 2.29 for SeaMonkey.