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.
Re: @Bloggerpemula:
See https://openuserjs.org/about/Terms-of-Service#reserved-rights at last bullet.
Re: @Bloggerpemula:
Already did starting at https://openuserjs.org/scripts/Bloggerpemula/Bypass_All_Shortlinks_Manual_Captcha/issues/Script_info_issue...#comment-17ebd1cf739
OUJS Admin
Test
Re: @sjehuda:
That's the way the group was created albeit very messy.
After I do some checking in a while, it's on my TODO list to check to help assist publishers from making this sort of foo (whether intentional or not)... however it is not a huge priority.
Btw you seem to be not the creator so you shouldn't really be requesting a name change... but instead use the Development link, at the bottom of every page, and create an issue on GitHub (GH) on why you think it should be changed. I'll consider it over there along with my perpetual thinking on how to improve groups (and the site) when time is available. Your request will get lost here for possible DB changes.
OUJS Admin
Re: @rahulraj80:
Btw just a mention the party that installed your script (if it wasn't you) will not be able to autoupdate their installation of your newer script releases since your path to it changed with the typo correction.
OUJS Admin
Re: @rahulraj80:
Not the same context.
Typos happen... just try slow down and pay more attention as we normally don't do this.
Correct. That's not supported.
Granted since there was a please. This is your one and only change.
This never happens except under extreme cases.
Corrected for you since you didn't do too much on the site and I needed the practice. Yes I had to delete your script as that's not redirectable but did reupload it with the basic publishing stats and matches previously recorded
OpenUserJS.hashofsha512-/piRmIzjuF3iMhMrQv1IwZmf2lwZ9FfkkCOdP5pxnL6kvvMQO+q1DnrbHsmUcNa+BZgdPe45/NKvF3D7FcCB8g==. Installation stats are lost.OUJS Admin
See also:
I think this is what you meant by:
Do this:
--- /scripts/alike03/Youtube_grey_out_watched/source@1.0+63356fa +++ /scripts/alike03/Youtube_grey_out_watched/source @@ -8,7 +8,7 @@ // @icon https://www.youtube.com/favicon.ico // @updateURL https://openuserjs.org/meta/alike03/Youtube_grey_out_watched.meta.js // @supportURL https://openuserjs.org/scripts/alike03/yt_grey_out/issues -// @downloadURL https://openuserjs.org/src/scripts/alike03/yt_grey_out.user.js +// @downloadURL https://openuserjs.org/src/scripts/alike03/Youtube_grey_out_watched.user.js // @copyright 2021, alike03 (https://openuserjs.org/users/alike03) //@license MIT // ==/UserScript==We always read in the current URL in your source that you have. So you need to click the
Regenerate some keys from the current editor sourcebutton to correct your incorrect value. That's a reason why the button exists.OUJS Admin
Re: @alike03:
No it doesn't. I just authed as you and it shows these:
Might want to clear your browser cache in case your browser is doing something funky. Glad you have the correct value from the Author Tools now though.
OUJS Admin
I just noticed you converted to
GPL-3.0-or-lateras well and already changed your Script Info. This closes this issue at this time.I hope this gives you a good start on understanding FOSS from my previous comment.
OUJS Admin
Re: @Bloggerpemula:
Not under FOSS at all.
Correct. That is why we are called "The home of FOSS user scripts.".
If you can't publish under these license base terms then you should delete the script and choose a different hosting site. If you can live with the requirements of requiring attribution on derivatives of the licensing and be a team player then keep the script here... with fixing your Script Info to reflect.
I would suggest that you do a little research on FOSS, starting perhaps with wikipedia to better understand the freedoms granted and more.
OUJS Admin
Re:
FOSS licensing means anyone can upload/modify your script anywhere and potentially even sell provided they meet the terms of the standard licensing (MIT) terms. That includes attribution to you and open source Code which is what what the OS in FOSS stands for.
If you don't remove this requirement from your Script Info, we will remove you for licensing violations under the TOS.
Thank you for your immediate cooperation,
OUJS Admin
Re: @iFelix18:
Because it has never been necessary to declare with the implementation.
@granthas never been required in or out of a sandbox forGM_info.Refs:
Correct the errors and you should be fine. If you check your Syncs nav bar tab you'll see that you have more than just those specific issues.
OUJS Admin
You should probably fix this before it gets removed.
OUJS Admin
Re: @jesus2099:
Nope. The moment you hit the page it increments the count. Although that can be a valid case until TPM usage becomes more prevalent in node. Until then it could happen if someone else is hitting the exact same route in your intranet i.e. you will have bad actors in your company which everyone there is responsible for. The route uses your unique username so it shouldn't do that... unless you have a bad actor in your company.
The feature is working as expected, been thought out for several years, and has been thoroughly tested. It is also how the limiters have worked since at least #944. As I mentioned on development there may be some allowances later on however I (we) don't work, live, breathe 24 hours a day here.
The final questions for you are:
I'm open to questions and suggestions but never assume unless you are sure.
Had you not been one of our seasoned Authors you would have easily been eligible for removal. I am giving you a learned experience instead of applying that. It's not like the history of these changes are hidden from anyone and those changes are continually being manipulated by the bad actors currently and mostly on Chinese, Vietnamese, and Bangladesh server areas (i.e. we know exactly where they are doing their dirty work) however we have to leverage the good with the bad.
There are consequences to adding security, or we can just let it go and you'll lose your free hosting when the site goes offline like USO did. Which do you think is the better choice?
OUJS Admin
I let you in and you don't use Submit Code as Fork from Carrizo's script.
After a while you are eligible for removal for doing this.
OUJS Admin
Impact assessment
The following were the affected scripts rebuilt from the log:
https://openuserjs.org/scripts/acedece14/vk.com_clear_ads_postswalls (Already fixed by Author)
https://openuserjs.org/scripts/Richardsssss/For_management_ADM_Script
https://openuserjs.org/scripts/xsanda/GeoGuessr_Path_Logger
https://openuserjs.org/scripts/Temm/Filled_Youtube_Like_Buttons
https://openuserjs.org/scripts/Temm/YouTube_Revert_Material_Rebrand (Already fixed by Author)
Specifically the DB, which is the metadata for when it was published, when it was updated was impacted. AWS, which is the source code, is still present on AWS. However if your script is missing in your script list (That would be you @Temm ) then it will be orphaned until you upload it again.
OUJS Admin
Had some data loss in the production database. Lost the corrupted data between the hours of ~2021 12 23 03:03 to approximately 2021 12 23 12:00 UTC to be exact.
Major Apologies... at least we had a very recent backup.
Not sure what was wrong... even the core restore didn't work and had to drop the entire DB to restore... which is not normal.
Once again MAJOR APOLOGIES!
Please update your scripts if you did that between that period.
OUJS Admin
All work and no play makes...
Re: @pbpublicvivaldi.net:
He can't do that. Also you completely ignored the caution warning when you signed up, which has been there since July 9, 2014, and made the mistake that you need to live with.
Your attitude is poor and I might have considered editing the DB to your other typed in recently name (Starts with "p") however there are consequences for your ignoring warnings. So the only thing you should be aghast at is your inept action.
Apologies for the interruption @jscher2000
OUJS Admin
Re: @Patabugen:
@sourcehas never been a part of updating and is specific to Tampermonkey (TM). See what it aliases to at TM and equates to an "upmix" of@homepageURL. In your case on your most recent update with the most installs that could be a value ofhttps://openuserjs.org/scripts/Patabugen/Always_Remember_Mei.e. it is the homepage URL of the descriptive side of your presentation repository here on OUJS... but not the actual raw source Code itself. That is reserved for@updateURLand@downloadURLrespectively.@updateURLis where it checks for an update, and@downloadURLis where it grabs the actual source if an update is available.This is also okay (but not real helpful to your users) for
@sourcesince it has nothing to do with the updating system in the engines. It can be a visual display of the source Code but not the raw source Code.This is just plain bugged and the route doesn't exist.
If a Greasemonkey (GM) 3.x compatible engine is in a FAIL state then it is possible. I don't believe TM has the same issue but since he closed the source I'd have to go dig to find out for sure and deconstruct his code. As a safe bet for any .user.js engine always assume the "weakest" link which means possibly.
See my previous reply and link. Not part of the update check and download source system.
The Author Tools, on each of your scripts, has been showing the usage of the updating system for quite some time (years or so) on what is "common" across all of the engines. i.e. you can select which type(s) (if available and mentioned from the FAQ) for both
@updateURLand@downloadURL. Currently@downloadURLis optional but right now in lockdown@updateURLis not.Never been a change even before OUJS existed. @sizzle wrote the first updating back in the day with GM and
@sourcehas never been used. That is, again, reserved for the human side of the equation using HTML not .user.js.So long explanation short... your misinterpretation of
@sourceis possibly one cause (but not the only reason) of why we're in lockdown i.e. hopefully you understand the update check and download source keys better?OUJS Admin
Partially up... at least from here.
OUJS Admin
https://www.githubstatus.com/
Github Twitter
Seems they are offline atm.
OUJS Admin
I have an idea that can be done for Gecko browsers too but can't do it until I get back to dev station to tweak for assisting more users.
Patience is always appreciated.
OUJS Admin
Starting to sound like a mynah bird here but...
I've done a work-around for Chromium based browsers to hopefully properly display their messages... however you might actually want to read the drop-down on the red install button which is normally blue for "make your own decision if it is safe to install". "Red (danger) is bad m'kay".
This script, among some other scripts on the site currently, won't be served when we are in lockdown until the Author makes a required change. You as a user may follow the https://openuserjs.org/about link as well for site status messages as documented.
Thanks for your attention,
OUJS Admin
Re: @micahrichards25gmail.com:
I've done a work-around for Chromium based browsers to hopefully properly display their messages... however you might actually want to read the drop-down on the red install button which is normally blue for "make your own decision if it is safe to install". "Red (danger) is bad m'kay".
This script, among some other scripts on the site currently, won't be served when we are in lockdown until the Author makes a required change. You as a user may follow the https://openuserjs.org/about link as well for site status messages as documented.
Thanks for your attention,
OUJS Admin