Re: @TimidScript:

Ideas can be "borrowed"... Code should not without proper forking here on OUJS... and besides you "borrowed" yours from Mindeye and he borrowed it from Arvid under GPL. So I wouldn't be talking. :P

Re: @TimidScript:

Having more than one homepage, means it is good to have homeURL.

Try not to make up keys that don't exist. The last value is always the primary of any key and are in LIFO order. GM rules applied. This isn't a breaking thing... yet.

Look at my USO scripts and you'll see multiple @homepageURLs.

Re: @TimidScript:

404 when I try to access the meta.js

We don't support that style for the meta routine and is unnecessary unless you want to force it to an external repo like GitHub.

Re: @TimidScript:

if the homepage URL points to one of the supported sites (OUJS, GF or MG).

Then do more than one key... we support multiple ones. @supportURL however is only the last one.

Re: @Marti:

can see rather.

Re: @Computerexpert:

Can't read your code properly dude. Try reposting with back apostrophes e.g code fences like mentioned here.

// @homeurl https://openuserjs.org/scripts/TimidScript/GM_update_Tester

Metadata key might be better suited as:

// @homepageURL             https://openuserjs.org/scripts/TimidScript/GM_update_Tester

You can all the keys we support at https://openuserjs.org/user/add/scripts.

Re: @cuzi:

ahh good point. ;) sup dude! :)

Re: @burn:

what do you mean by "use of superscript"?

I took it as a compliment to you. I think it meant that he "loves using your super script".

Oh, the right word isn't "steal", it's "inspire" :)

Indeed! ;)

Re: @TimidScript:

commercial usage?

Just for additional clarification to you MIT allows commercial usage of the Code not the Content.

Re: @TimidScript:

I thought "Creative Commons BY-NC-SA" was not allowed due to limitations on commercial usage?

*No derivative licenses are not allowed of any kind. CC is a Content license in which arbitration will force MIT as the Code license... therefore one can fork this users code. It's all in the TOS. :)

If you are willing to do this it would be very kewl.

Btw thanks for the screenshot... your next challenge, if you wish to take this on, is to do it for any account. :)

Re: @burn:

Does this Make sense?

The likelihood of using local storage is minimal from the OUJS perspective due to this. It would be very frustrating for those users that did clear it and reports would come in. Also some extensions/add-ons block local storage usage completely. I think it's best to keep this user.js side.

Re: @devnoname120:

I changed the license to Creative Commons BY-NC-SA.

That means you've selected MIT Code License which is okay in tandem with your Content License. :)

Re: @jerone:

see this build-in to the site

We could use client side local storage but will run into a security risk. I've thought many a time about doing something similar to US.o script author helper but usually it ends up needing the data stored client side... which runs into collisions with automatic cleanup routines on the client computer.

Re: @burn:

It would be nice to have a screenshot on your script homepage too. I've installed this a few times and didn't observe much happening... so it would be nice to know exactly where to look.

Re: @TimidScript:

That seems very odd that they are in sync like that.

Not in sync right now and not odd to me if they were. As per a potential bug report please do those on the GitHub Issue Tracker.

Please review the Terms of Service.

Thanks.

Re: @TimidScript:

Does the install counter include automatic updates?

It is the accumulation of all installs.

Re: @pootz:

Relook at your markdown code now and see how it is generated the way you want it with inlineImageSyntax space inlineImageSyntax space inlineImageSyntax and so on.

Would this be better as a Library? Just curious based off your @name.

Re: @pootz:

Probably the same issue as #221.

Re: @TimidScript:

http://opensource.org/faq#commercial. In your case I wouldsuggest GPL Code License and a Content License if images are present. GPL will force changes to be made available to you and everyone else. Anyone can sell a disc containing any open-source... however GPL must make the code freely available to everyone.

Re: @TimidScript:

Can I do a hello world script, it should be perfectly legitimate just 100% useless

See this script. Nobody visits IANA test domains other than for testing.

Re: @Marti:

Your license resembles MIT now with your comment... so @license MIT License; https://github.com/TimidScript/GreasyMonkey/blob/master/LICENSE.mdcould work.

Re: @TimidScript:

Is it ok now?

You must have the OSI approved license name in your source. You can't just link @license to a URL elsewhere.