Tell you what... we've deployed some prelimary bug checking to prevent you from making this specific mistake... I'll be deleting your script and you may reupload at your leisure with the correct OpenUserJS block items.

Leaving the issue open so you may close when it is reuploaded... or I will get around to it at a later date.

OUJS Admin

Re: @Chewbaka69:

This script is not wrotten by me...

Hey if you want the security risk of another user possibly being able to edit your script please feel free to keep that in there. However I would strongly suggest that you change the key in the OpenUserJS metadata block to prevent this. If we get a report that there is abuse of this script, and it is confirmed, by another account editing it... then it is your account that is at risk. i.e. you will be eligible for removal.

so i let the name of the true authors

I'm not recommending changing the UserScript metadata block key since that key has a completely different syntax. However the OpenUserJS one is specific to your account and plays a specific role for collaboration here on OUJS. This is why it is not part of the UserScript metadata block.

Bottom line is you may decide to keep the collaboration this way however you and you alone are allowing a security breach on your own script. Thus you will be responsible for any and all consequences.

OUJS Admin

You should probably correct this since it can be a security issue for your script:

--- /libs/Chewbaka69/OGame_VersionCheck/source@1.4+830cb5c
+++ /libs/Chewbaka69/OGame_VersionCheck/source
@@ -18,7 +18,7 @@
 // @license MIT
 // ==/UserLibrary==
 // ==OpenUserJS==
-// @author Eleria, Francolino & Origin.team
+// @author Chewbaka69
 // ==/OpenUserJS==
 
     // Call oGameVersionCheck(scriptName, testedOgameVersion, scriptUrl) at the beginning of your script - document.readyState must be 'interactive' or 'complete'

Thanks for the attention on this matter,
OUJS Admin

Trailing newline is the the trigger in the online editor I believe vs. your repo which doesn't seem to have it.

So you don't freak out... had to resave this to test out a glitch.

No content (to my knowledge) was changed as you. Perhaps it picked up a UTF change or automatic BOM removal in the editor? The rest of your scripts were unaffected by the resave.

OUJS Admin

Re: @rmpbklyn:

Don't doubt this with an online video transcoder however the Userscript source is currently benign at 5.1+056181e. What the target website does with you is up to them... although always nice to know if someone has encountered injected adware. Provided a recent, and current, browser is doing it's job there shouldn't be a security issue. However this does use a MITM conversion site. e.g. use at your own risk.

OUJS Admin

Re: @lachlanmck:

Please use a code fence and the Preview button here next time so you are being agreeable with the TOS. I've fixed it this time. Tabbed/spaced indenting can be one of the worst features of markdown if you don't do it correctly. Code fences hardly ever go sour. There's also a guide icon right below this comment window to the far left. Look for the M and down arrow e.g. Markdown.

Thank you for your cooperation.
OUJS Admin

Please use the following diff correction to clear your system critical error:

--- /scripts/sytha/xkcd_keyboard_navigation/source@0.1.2+4f77477
+++ /scripts/sytha/xkcd_keyboard_navigation/source
@@ -9,7 +9,7 @@
 // @license      GPL-3.0-or-later
 // @copyright    2019, Sytha (https://openuserjs.org/users/sytha)
 // @downloadURL  https://openuserjs.org/install/sytha/xkcd_keyboard_navigation.user.js
-// @updateURL    https://openuserjs.org/meta/sytha/xkcd_keyboard_navigation.meta.json
+// @updateURL    https://openuserjs.org/meta/sytha/xkcd_keyboard_navigation.meta.js
 // ==/UserScript==

 (function() {

You may also find the correct value in your Source Code tab while logged in.

Thanks for the look,
OUJS Admin

CCleaner browser

Awesome... you got it now. Thank you and your welcome too. :)

e.g. remove the slash on the end...

--- /scripts/Draym/OG-Tracker/source@1.0.1.3+26ed5bd
+++ /scripts/Draym/OG-Tracker/source
@@ -7,7 +7,7 @@
 // @license     MIT
 // @version     1.0.1.3
 // @updateURL https://openuserjs.org/meta/Draym/OG-Tracker.meta.js
-// @downloadURL https://openuserjs.org/install/Draym/OG-Tracker.user.js/
+// @downloadURL https://openuserjs.org/install/Draym/OG-Tracker.user.js
 // @grant          GM_getValue
 // @grant          GM_setValue
 // @grant          GM_addStyle

... https://openuserjs.org/install/Draym/OG-Tracker.user.js/ leads no where on the site.

Don't put the traling slash... that still goes no where.

--- /scripts/Draym/OG-Tracker/source@1.0.1.2+efc2ff0
+++ /scripts/Draym/OG-Tracker/source
@@ -7,7 +7,7 @@
 // @license     MIT
 // @version     1.0.1.2
 // @updateURL https://openuserjs.org/meta/Draym/OG-Tracker.meta.js
-// @downloadURL https://openuserjs.org/install/Draym/OG-Tracker.meta.js/
+// @downloadURL https://openuserjs.org/install/Draym/OG-Tracker.user.js
 // @grant          GM_getValue
 // @grant          GM_setValue
 // @grant          GM_addStyle

... will clear your system notice. Currently no one will get automatic updates using a URL that goes no where on the site as well as if it did work they'd get just the abridged metadata. e.g. @updateURL is where to check to see if there is an update and @downloadURL is what to download and do the update for .user.js engines.

You also have the same issue on the rest of your published scripts.

Thanks for the look,
OUJS Admin

// @updateURL    https://openuserjs.org/meta/gaspar_schot/Supercharged_Local_Directory_File_Browser.js

should be:

// @updateURL    https://openuserjs.org/meta/gaspar_schot/Supercharged_Local_Directory_File_Browser.meta.js

... in order to clear your system critical notice. Notice the .meta.js not .js. While this currently "works" as is it may not in the future and none of your users will get updates after that because it will return a different status code and page instead of script meta source.

Thanks for the look,
OUJS Admin

You must keep your source in the clear and not one long string that get evaluated. If you choose to pack "on the fly" into the DOM that may be acceptable however source must always be readable.

Try again.

OUJS Admin

Re: @ajsnyde:

They use obfuscated and regenerated classes and other bloat to make traditional detection difficult.

Agreed... however there are other CSS selectors for pattern matching. FB isn't all that wise (nothing new here) when it comes to this and the script can be updated to do some more intense matching to curtail the privacy and security invasion if present. Perhaps matching on y_tk, n_tk, l_tk, and/or p_tk will work for the time being depending on where they start in class.

Since I'm not, and never will be, on FB I haven't tracked their tokenization of their ad system (which you really only need to post one set of them)... but this might be a start to improve the .user.js

Re: @ajsnyde:

Please reread this section of the TOS and this FAQ for proper formatting. Additional information on presentation can be found at this FAQ entry if a code change is recommended.

Had you not put in your first comment to clarify this code snippet the default TOS action would have been applied. I've corrected your mistake (and beautified your code block which should have been a code fence) this time.

Thank you for your cooperation.
OUJS Admin

Re: @truongbilico:

Revert matching a script to a group

...

Not featured

Not featured is correct. Dependency has changed as well as limits are set on how many new groups one can create. Unlikely, but not impossible, to happen in the near future.

OUJS Admin

Btw you, and anyone using Chromium backend, are experiencing a rather unusual issue that doesn't exist in other more mature browsers. We've added a partial work-around for the deficiency in the affected browsers atm.

Re: @AltoRetrato:

Feel free to open a request on development or better yet a PR to do what you think it should be and it will be there for peer review including DoS attack vectors. I will continue over there to examine possibilities but the idle detection routine is in place for a reason... which you need to grasp that concept. :)

The script is licensed under MIT but i still have to ask, do you mind that I made it into a chrome extension?

As long as you visibly include in something like an "About" somewhere in your extension with at the very least attributions any FOSS license can be forked technically. If the .user.js fork shows up on OUJS then it must be done with the "Submit Code as Fork" button on this scripts homepage.

e.g. the block items of:

// @license      MIT
// @copyright    2018, Newt300 (https://openuserjs.org/users/Newt300)

It is still always good to get acknowledgment from the Author though like you are asking here. Also many won't install an extension due to possibility of elevated privileges which is one of the many reasons a .user.js exists. Peer review is a bit more challenging when it's an extension (presume .crx for Chrome).

OUJS Admin

Re: @AltoRetrato:

Wouldn't it be much nicer to save the message and either submit it or go back to editing after signing in?

That would entail more cookies on your end and would need session forwarding which we don't do due to the TOS and structure e.g. visitors don't currently have a session as per @sizzle.

Will ponder though if there's any other way on development.

Re: @AltoRetrato:

I love OpenUserJS!

Don't we all?! :)

I sign-in, write you a long reply and the site deletes it and asks me to login again

Idleness is currently detected. If you don't initially navigate somewhere on the site you will be logged out within about five minutes with intendend behavior. So either type faster *eg* or visit another page first. ;)

... Change the 13th line, removing both apostrophes ...

You do know you can click the line number for current published revision and get a link for that revision right?

Interesting feature in GM4.x btw... didn't know that myself.

OUJS Admin

Successful reopen by owner

Can comment?!