Auto liking in a script that is advertising new emoticons is a violation of the TOS.

Your script is now eligible for removal

One other quickie too...

// @downloadURL	https://openuserjs.org/install/yasingedik/Aol_Reader_Optimized.user.js
// @updateURL	  https://openuserjs.org/install/yasingedik/Aol_Reader_Optimized.meta.js

... This is not really necessary anymore especially on OUJS (here) but if you wish to keep it in there one of them needs to be modified so you don't kill updating.

// @downloadURL	https://openuserjs.org/install/yasingedik/Aol_Reader_Optimized.user.js
// @updateURL	  https://openuserjs.org/meta/yasingedik/Aol_Reader_Optimized.meta.js

The user.js engines out there handle updating automatically now by trying to see if the meta routine exists first... in our case here on OUJS we focus on using the header not the .meta.js extension.

Hope some of this helps you out. :)

Been seeing this particular here a lot lately...

Rather than having Greasemonkey (the user.js engine) create dozens if not hundreds of <style> tags with code such as yours, from this snippet:

GM_addStyle(".header-search-wrap { margin-top: 0px !important;}");
GM_addStyle(".dropdown-menu-add .page-container {height: 498px !important;}");
GM_addStyle(".dropdown-menu-add {height: 500px !important; left: -50px !important; max-height: 500px !important;}");

// The rest of your CSS rules in here too e.g. ...

it might run more efficiently in the DOM if you only use GM_addStyle minimally like this:

GM_addStyle(
  [
   ".header-search-wrap { margin-top: 0px !important;}",
   ".dropdown-menu-add .page-container {height: 498px !important;}",
   ".dropdown-menu-add {height: 500px !important; left: -50px !important; max-height: 500px !important;}"
   // The rest of your CSS rules in here too e.g. ...

  ].join("\n")
);

Just a suggestion. :)

Re: @dluciv:

Btw if you get some time you can read up on the Tivo fiasco with GPL v2 versus v3 and you can see why GPL exists. It's on the web.

Re: @dluciv:

Can userscript have multiple licenses?

Yes Mozilla has tri-licensing e.g. 3 that can operate. MIT is the least restrictive but the least protective as well. GPL is the most restrictive but the most protective... and then everything in between of course. I also dual license with GPL and CC. GPL covers Code and CC covers Content. Still keeps the Code free for reuse and adaptation. :)

The problem is that not all courts worldwide recognize every public domain. If someone were to prove that WTFPL is a Content only license then the MIT Code License can be applied with arbitration via our TOS e.g. Creative Commons (except no derivatives) is that.

Very sad that WTFPL is not OSI-approved.

It's a difficult situation for those not wanting attribution but you might try petitioning OSI to get it added.

There have been a few Userscripts.org (USO) clones popping up. The only one that I am somewhat familiar with is from USO at http://userscripts-mirror.org/.

Any others I suggest being very careful especially if they advertise logins.

Re: @decoydoug2:

I don't know how this website works, so I posted this under "issues". (good issues)

That works... also on this scripts homepage:

• Where to rate (image removed)

which finally led me here

Welcome! :)

Re: @studgeek:

where can I find the instructions for sharing a script? Optimally from github?

Click on your Username and then "Add Script" which takes you to https://openuserjs.org/user/add/scripts and explains it in column 2 and 3.

Re: @BitTorrentse:

The @license looks well... but now your @copyright is not stating that it's you. :\ e.g. you aren't advertising yourself with copyright status.

You might want to consider using:

// @copyright     2014+, Bit Torrentse (http://www.absba.org)

in your scripts for that.

You'll need to make any necessary changes on GitHub too since that is the main repo file for one of your other scripts. If you sync GitHub to here it will overwrite these changes on OpenUserJS.org. I don't think that you want that to happen. :)

Re: @BitTorrentse:

I remove it

The least restrictive license is MIT.

So you could change your metadata block from:

// @license    Bit Torrentse , http://www.absba.org

to

// @license    MIT

You already have a reference to your forum site in @copyright although it may need a little improvement.

Re: @BitTorrentse:

I remove it

The least restrictive license is MIT.

So you could change your metadata block from:

// @license    Bit Torrentse , http://www.absba.org

to

// @license    MIT

You already have a reference to your forum site in @copyright although it may need a little improvement.

Please read the Terms of Service (TOS) link below on every page regarding public domain licensing.

Thanks.

Please review the Terms of Service (TOS) link at the bottom of every page regarding acceptable licensing. Pointing it to a forum does not fall withing the TOS.

Thanks.

Please review the Terms of Service (TOS) link at the bottom of every page regarding acceptable licensing. Pointing it to a forum does not fall withing the TOS.

Thanks.

Please review the Terms of Service (TOS) link at the bottom of every page regarding acceptable licensing. Pointing it to a forum does not fall withing the TOS.

Thanks.

No derivative license in here. You have less than 24 hours to comply with the Terms of Service (TOS) here regarding this before your script gets removed.

Re: @marine64:

Slightly incorrect place for this I think... might try the script itself.

Re: @BastianKanaan:

Can anyone here help me how I have to create a click event now?

Did you try just calling a synthetic click event on the node element? e.g. someNode.click();

Re: @TimidScript:

Touche

Coulés are a practiced skill when dueling. ;)

Re: @TimidScript:

I prefer to call it re-branding.

Opening a hole for spammers and malicious scripts is not in the best interest of anyone. You can "rebrand" just fine with the existing methodology by having it create a new script for your brand (that would be you btw). Aggregated statistics can also be gamed with your suggestion... not to mention SEO manipulation.

Re: @TimidScript:

One of the useful things of a site where users often discus technical issues is an Edit feature for comments.

In progress.

pages should have a title.

OpenUserJs/OpenUserJS.org#279. Might try searching before asserting your opinion. :)

Re: @TimidScript:

The inability to change the name of the script without creating a new repository (not sure what the correct terminology is). This is by far the most annoying "feature" on this site.

It's called making a new script because when you change the name that is exactly what you are doing by changing the name. The only annoyance is what your actions do... so don't change your script name. Think first before you publish a work. You make a "mistake" then that is your responsibility not OUJS.

Re: @pootz:

This is one of those later copies that I mentioned. Mirror target is here for this script on OUJS. Notice the bigger scriptid number in the link... which means it absolutely came later than sebaro's mirror target here. Since both are GPL embedded it is considered a fork here on this script. USO didn't have forking capabilities hence why you are seeing double.

Re: @pootz:

I had this script version from July, grabbed it from userscripts, and the author's name is different.

Appears to be a continuation of this script. Seems to be a valid continuation of that script.

This is a re-upload or are you the real author?

Based off later created user.js search results from the USO mirror I would probably say that any version you had before with a different name is probably not the original here.

The remainder you will need to wait for sebaro's reply.

Re: @Marti:

Oh and newer Fx since GM will require it... you can always go back to 28 if you need to at http://ftp.mozilla.org/pub/mozilla.org/firefox/releases/28.0/

Re: @Fironet:

Version value of Youtube Center in the config.xml is '2.1.4'

Do you mean edit config.xml and make YT Center an earlier version in the file?

Since you've confirmed it's an earlier version in the config.xml the redundant test isn't needed.

Try a clean temporary profile with the newest GM release. I don't think there are any real major updating related changes in the code but try with only GM. You can install this script, close Fx, edit the config.xml for this script to an earlier version and try running the update check manually in the Add-ons Manager (AOM)... if it still doesn't do it then it's something outside of Fx... which could still include .io pages... although those work for me with a manual check (version down bump in config.xml). I have checked this sources meta.js and user.js again and everything appears to be in order. shrugs