Marti Admin


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.




Re: @Black_Cat:

I published this version of my script on userscripts.org in October 24, 2013

No you published it on USO on Jul 26, 2009 23:31... anyhow you know the routine as I posted above... if you wish to pursue this that is how you do it. Just because your script on gf is now nearly in sync with this one doesn't necessarily mean anything specific to your allegation. I've already examined it and your USO script is a derivative of at the very least Appels which there is also anoter reference to another ScriptWright there. This issue is closed with OUJS admin... if you would like I can message Jason to have your script removed from GF for violation of his terms based off of the available information... but I think you should just accept the credit given in this one. Like I said it's unusual that GF shows your script is newly published compared to this one... our date is correct and verified... so must be an issue over at gf. It's your choice.



Re: @Black_Cat:

I'm original author of this script. It is available here: https://greasyfork.org/fr/scripts/4444-ogame-moon-spy-and-recycler with correct use of @require tag.

It would appear that you are not the original author of this script.

  • The original author is neither one of you from what I can tell... The earliest ScriptWright that I can find is Appels in 2007 at http://userscripts-mirror.org/scripts/show/12318.html in 2007 in which you copied it in 2009.
  • Somehow you published it on gf in August 23, 2014 yet Amynka published July 19, 2014.
  • From this information it is possible to deduce that you have broken the "rules" of gf. Open-source is just that... our licensing terms are available here. If you wish to pursue this on the grounds that it is... it has already been minimally shown as not being your script. You must follow the DMCA to pursue this further.

Imo there is no merit for this allegation.


Re: @TimidScript:

This is totally offtopic but just wanted to let you know we support highlighting in code fences e.g. use ``` javascript

// ==UserScript==
// @name        Mozilla Remove Events
// @namespace   TimidScript
// @include     https://addons.mozilla.org/*
// @version     1
// @grant       none
// ==/UserScript==


(function ()
{
    //var links = document.getElementsByTagName("a");
    var links = document.querySelectorAll("aside a, #addon-description");
    for (var i = 0; i < links.length; i++)
    {
        links[i].addEventListener("click", Stop);
        //links[i].onclick = Stop;
    }


    function Stop(e)
    {
        e.stopImmediatePropagation();
    }
})();

:)


I strongly recommend that you explain to users what you are doing with your external script... you've already been flagged once.

If you explain it you won't be eligible for removal this time. Peace out.


It would be beneficial to others if you actually named your library.

Thanks.


It would be beneficial to others if you actually named your library.

Thanks.


Re: @TimidScript:

in the works like Greasefire for ... OUJS?

Not yet but it is on my long term TODO list... so probably not soon.




Alright give it a whirl now. Tested all methods here okay.


Pushed a fix for the one confirmation... awaiting redeploy.


Re: @ardiman:

write online

Confirmed. When I get back to dev this evening I will look into this. I'll see if sizzle can restart too if he is available. Thanks for the report.




Re: @TimidScript:

Haven't tested this in a long time but you might try how I did it in GM_setStyle.

Not currently for our site but greasemonkey/greasmonkey#2046 may come into play for some by GM (or others) not using the correct origin. The @grant none is "intended" however when Sandboxed e.g. ~`@grant GM_*` should be having expanded principles in effect... so basically there can be an issue with Content Security Policy (CSP) not obeying Expanded Principles.

See related:



Please add the following to your metadata block to be inline with your code license so everyone can see it.

// @license       GPL version 3 or any later version; http://www.gnu.org/copyleft/gpl.html

Thanks.