Are you sure you want to go to an external site to donate a monetary value?
WARNING: Some countries laws may supersede the payment processors policy such as the GDPR and PayPal. While it is highly appreciated to donate, please check with your countries privacy and identity laws regarding privacy of information first. Use at your utmost discretion.
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:
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/orp_tk
will work for the time being depending on where they start inclass
.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:
...
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. :)
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:
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:
Don't we all?! :)
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. ;)
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?!
While I can read what you are doing most others aren't going to give it the time and potentially flag it.
This script is removed.
OUJS Admin
Ooops upper right. ;) Late for me.
Re: @Al_Caughey:
Click your user name in the upper left corner then on that page it is usually "Add Script".
MITM to https://server.lutily.fr:8443 with user and pass. Undisclosed security breach. Bye.
OUJS Admin
As with all .user.js there can be a risk. This was evaluated already and is a bit sketchy. Bad
@require
and also a library sitting on GF that "downloads codecs" which is suspect imho... however not enough to merit removal just yet.If anyone feels that this is risky then do not install it. If anyone can reproduce a malware type use case for it then flag it with the succinct steps to reproduce. We have plenty of ways test things out in a more safe environment than production machines.
OUJS Admin
Re: @passepartout39:
...
Doesn't do this portion of your query.
Re: @passepartout39:
Take a look at GM_config library and corresponding The GM_config Unit Test to see if it meets your needs. Ensure that you are using
// @grant GM_setValue
and related in your UserScript metadata block so it should pick the GM storage instead of more public storage.Re: @xedx:
Correct and it's obvious. If I didn't need the DB practice then this would not have happened.
Correct... to maintain the integrity of OUJS this is not a feature. You may however delete your content as you have already stated.
Thank you for that consideration.
It is not and even more so since I get to do this directly in the DB.
Completed
Correct.
Why would we want to open a security nightmare for bad actors who create a bazillion accounts tied to one auth strategy?! (rehtorical question here as we wouldn't!)
I had to spend some quality time with my patience levels here and weigh in whether to grant your request. As I stated... since I need the DB practice it was granted and you did make a good faith effort to read similar requests on how to do it. However it is unlikely that anyone else will get this sort of grant in the future.
OUJS Admin
Re: @kdw2060:
You have been, lengthily, merged and discussion redirected. Please remember you lost all of your scripts stats as I mentioned before. I took the liberty and courtesy of reuploading your scripts and their script meta. Since we treat authors as a name/script in the path, instead of number, your users shouldn't have any disruptions since it's the same path.
OUJS Admin
Re: @Mr_FJ:
It is "clean" but the browsers are arguing again on standards. We've made an exception at #1599. You should be good to go.
Just a note... while I do check here on occasion... it is best to use the Development link below on every page to create an issue if you think it's an actual bug.
Thanks for the report.
OUJS Admin
Re: @Mr_FJ:
Re: @Mr_FJ:
Copied vs. upload is a little different story. I'm in the middle of rebuilding dev station and it will probably be another day before things are even remotely set to look for fixes possibly in our deps... possibly in the browsers sending the incorrect MIME type... idk yet.
Anyhow... confirmed with File upload in a "dirty" profile in this browser.