Marti Admin

adding a message box somewhere

It's been in the TOS for years with everyone agreeing to it and it's actually as a help template for new scripts as a placeholder now but I only have so much time... plus you have announcements which you seem to have found. :)

Before I went away from dev station I started working on a drop box similar to the .meta.js one in Script Author Tools on every script homepage... so that everyone will know what is accepted easier than visiting external sites but ran out of time to finish before I need a break.

So please be patient and there is currently a ton of notices, so no excuses ;), in which I'll be adding some more over time. ;)

Thanks.


$ sha256sum jquery-1.8.3.min.js 
61c6caebd23921741fb5ffe6603f16634fca9840c2bf56ac8201e9264d6daccf  jquery-1.8.3.min.js
$ sha256sum sa.js
ba6eda7945ab8d7e57b34cc5a3dd292fa2e4c60a5ced79236ecf1a9e0f0c2d32  sa.js

Can't do that.





It's been discussed with the powers that be.

I added rolling last night and next week I'll work on setting three (3) days maximum before authed session is destroyed. Minimum authed session should still be around four (~4) hours. Could change.


You may want to update your scripts metadata.

Thanks,
OUJS Admin


You may want to update your scripts metadata.

Thanks,
OUJS Admin


You may want to update your scripts metadata.

Thanks,
OUJS Admin


You may want to update your scripts metadata.

Thanks,
OUJS Admin


You may want to update your script metadata.

Thanks,
OUJS Admin


Re: @vanowm:

Firstly I'm running some session tests.

Secondly most of you do not logout... part of the test results already. This slows the server down quite a bit when laziness comes into play.

Thirdly if we give you infinite cookie time then it's two weeks on our end... too lengthy imo.

Fourthly I will continue examining the expiration time until the tests are concluded.

Fifth in line, most sites don't give you "unlimited" session time.

Sixth contemplating doing a Pandora style thing of "Are you still there?" and log you out if you aren't responding.

Public or private is irrelevant and not a good reason. WiFi is quite popular so a portable device would definitely not be on a private network. Some large cable providers allow this even when you are not at home.

Anyhow... look for it on Development if I boost it sometime next week... unless a super duper good reason is given before then. :)


Re: @vanowm:

Is there a way stay logged in for more then one hour?

Current session time is 4 hours. This may be improved after next week but probably won't exceed one day unless a good reason is given.


Re: @jscher2000:

... script metadata blocks on userscripts.org and replacing the script contents ...

If I see that those scripts and accounts will be removed. There is also the Flag option to let us know in advance.

Well you can obviously keep the license header inside your code as is but in order to parse these we need you to utilize the SPDX code. If I may suggest create a document of your license terms as well since we link it... for quicker viewing. I'm going around and fixing the display issues manually in the metadata we collect (which is going to take a while) however this only treats display and not the fact that the server will reject script updates without a proper SPDX. Probably later this week or as early as next week @license will be required.

I did offer you on GH a moderator position for OUJS if you'll have it? Then you can see what kind of stuff gets axed here in the Graveyard. Plus you'll have twice the veto power as a normal Author/User when Flagging. :)


Welcome... further detailed analysis of your BSD and comparison indicates that you are using a BSD-3-Clause. It would seem that your "restriction" is unnecessary, from what I've read, as you can't be held liable for damages in the event that someone "includes" it on those target sites. May want to run that through the firm and OSI for sure though.


Re: @Jim_C:

Next time please use the Flag option on the script homepage. The matter is taken care of for now.


OUJS has made a change recently to require SPDX codes for OSI approved licensing.

In order to improve the appearance of your script homepage it would be appreciated if you could modify this affected script.

Instead of:

// @license        GNU GPL v3 (http://www.gnu.org/copyleft/gpl.html)

... please use this:

// @license        GPL-3.0+; http://www.gnu.org/copyleft/gpl.html

Until this change is made you will be unable to update those affected scripts.

Thanks,
OUJS Staff


OUJS has made a change recently to require SPDX codes for OSI approved licensing.

In order to improve the appearance of your script homepages it would be appreciated if you could modify all of your affected scripts.

The fix for these is to use this:

// @license        MPL-2.0

... instead of plain MPL.

Until this change is made you will be unable to update those affected scripts.

Thanks,
OUJS Staff


Heyo,

So your scripts are a bit more to examine as I'm not all that familiar with BSD licensing... so here goes...

OUJS has made a change recently to require SPDX codes for OSI approved licensing. See the announcement too.

In order to improve the appearance of your script homepages it would be appreciated if you could modify all of your affected scripts.

Some of the OSI SPDX codes are as follows:

Until this change is made you will be unable to update those affected scripts.

Thanks,
OUJS Staff


OUJS has made a change recently to require SPDX codes for OSI approved licensing.

In order to improve the appearance of your script homepages it would be appreciated if you could modify all of your affected scripts. You have two here.

The fix for this is to use this short identifier:

// @license      GPL-2.0

... instead of GPLv2. This is syntactically equivalent.

Until these changes are made you will be unable to update those affected scripts.

Thanks,
OUJS Staff


Currently on Line 864 you have:

IdArray[IdArray.length]=$(this).text().replace(/? /g, '');

Did you mean to have /\? /g or something else?

Thanks for the look.


OUJS has made a change recently to require SPDX codes for OSI approved licensing.

In order to improve the appearance of your script homepage it would be appreciated if you could modify your affected script.

Here is the change needed:

// @license        GPL-3.0+; http://www.gnu.org/copyleft/gpl.html

Until this change is made you will be unable to update those affected scripts.

Thanks,
OUJS Staff


OUJS has made a change recently to require SPDX codes for OSI approved licensing.

In order to improve the appearance of your script homepages it would be appreciated if you could modify all of your affected scripts.

// @license       GNU General Public License v3.0

... to ...

// @license       GPL-3.0

Until this change is made you will be unable to update those affected scripts.

Thanks,
OUJS Staff


OUJS has made a change recently to require SPDX codes for OSI approved licensing.

In order to improve the appearance of your script homepages it would be appreciated if you could modify all of your affected scripts that utilize LGPL to use LGPL-3.0+; http://www.gnu.org/licenses/lgpl-3.0.txt for the licensing instead of LGPL http://www.gnu.org/licenses/lgpl.html.

So your end result will need to look like this in the metadata block:

// @license            LGPL-3.0+; http://www.gnu.org/licenses/lgpl-3.0.txt

Until this change is made you will be unable to update those affected scripts.

Thanks,
OUJS Staff


OUJS has made a change recently to require SPDX codes for OSI approved licensing.

In order to improve the appearance of your script homepages it would be appreciated if you could modify all of your affected scripts that utilize GPL version 3 to use GPL-3.0 (or whichever version of it) instead of GPLv3 for the License Type. These are syntactically equivalent for version 3.

Until this change is made you will be unable to update those affected scripts.

Thanks,
OUJS Staff