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.
WTFPL is not on the OSI list.
Please dual license with a Code License (Usually it's MIT for the least protective) and you'll be able to keep your script here.
Further refs:
Thanks
WTFPL is not on the OSI list.
Please dual license with a Code License (Usually it's MIT for the least protective) and you'll be able to keep your script here.
Further refs:
Thanks
Re: @Limnic:
Provided
@nameis still the same (casing, whitespace and characters) it should be fine. OUJS doesn't have the same issue that numeric indexed sites have. We use your modifiedusername/scriptnameinstead of treating you or your scripts as a number. :) Only issue may be in the .user.js engines with using full source for update checks but that is negligible.btw I'll be moving the comments in this discussion later this evening to the proper discussion announcement to keep things on-topic.(Completed move)Re: @Limnic:
And one response to your comment in the cache here. :)
Re: @Limnic:
And here is the source (from Aug 23, 2015) for that script e.g. just a metadata block pulling from your GH io page.
Re: @Limnic:
Yes it was and even here on production too. You created your account on August 14th, 2015 You are back and you will need to restore what you wanted here. Goo's cache is here :)
I only see one in the cache named
Hugelol keyboard navigatorbut that depends on the cache period visitation.Re: @chacham:
Good idea to use search engine caching to assist. :)
Some miscellaneous notes here about newer version requests...
GM_listValueswhich hasn't worked in newer SMs and would require a major rewrite in non-e10s and a strong veer from the near parallel fork architecture which is beyond the scope of this port at this time)... buzz me on GitHub (GH), for now, under your UserScripts repo and I'll see what I can or can't do. This doesn't mean that I will write your script for you and I most certainly don't care to sign up on a bazillion other sites. :)Thanks so much for your looooooooooooong term patience with this. e.g. this port is at a frozen state for the time being.
NOTE: Restored from search engine cache and augmented.
Re: @chacham:
You are welcome. :)
Your other answer is on the proper discussion over there.
Re: @chacham:
Nope. As you read on development the data was destroyed with that dependency foobar. I lost some important text myself that I need to recreate if possible at some point.
Re: @desarrolloforos:
You will need to get a lot more specific than this. I have looked into the original authors of both this script and some of yours and it doesn't appear to be either of you. Unless you have concrete evidence, preferably in English would be helpful, I will be Admin closing this issue.
es-EScourtesy of Microsoft Translator:Thanks,
OUJS Admin
That's all for this migration I think.
A-ha... found a log for the usernames:
Re: @trespassersW:
Now that we are back to current GH master HEAD here on production you may install the most recent version of this script from OUJS if you wish.
NOTE: If the grammar files are still in your cache you'll need to either wait until the expire time (this was on my TODO list for development to correct but the "intermission" interrupted that), or just clear your cache, and it should resume normal operation... otherwise it will be sitting on this message again. I'll version bump as soon as I can but the cache time for anyone using the older version needs to expire first before I do that and I'll be away from dev station for a few days.
Re: @Marti:
Done with migration... in validation, which comes with this, encountered the following script names that didn't have source on S3:
All the above scripts without source have been deleted as their respective user... except for @sizzle 's "Hello World" since I don't have that access but he has been notified to fix it. If you have a script name of these please re-upload your script source at your earliest convenience. Probably should have nabbed the username too with these in the console... but hind sight is always 20/20.
Provided everything goes well in the next 24 hours or so I'll be remigrating the DB now that I seem to have access.
So Sept 3, 2015 late in the evening there will some scheduled downtime. Did this ~9 days ago once on the original DB with the same code. Approximate time should be about 20 minutes perhaps a little less. I'll try to do this as late as I can (EST) but we really need to get the HEAD here back to current master on GH dev.
Thanks again.
Re: @trespassersW:
Thanks... use this version on GH until we resync OUJS completely... 3.0.0.1 is for the current master not at the HEAD that we are using at the moment... I'll drop in an update notice on this script manually for those to reinstall from here. e.g. watch for it. :)
Re: @jscher2000:
That works too.
Re: @jscher2000:
If there is no script homepage, e.g. new scripts within the last 21ish days the direct install url should be nabbed for those that said they didn't have backups... this may even work for users that aren't here right now from the restore.
If there is a script homepage the source is still from S3 which should be up-to-date... but MongoDB info from the documents may be out of date... if you look at oujs - Meta View it says that it's
3.0.0.0rc6... but if you install it... it pulls my last webhook of3.0.0.1. If the source is on GH you can just resend the webhook in their settings and that should resync it I think.This should self correct itself on DB migration as well when I'm able to do it.
Correction... script sources are intact but not matched with DB meta... Those who updated in the last 21ish days should nab their source immediately.
So @sizzle restored his last backup... which is August 10th, 2015
All comments/disucssions/users/scripts/etc. from then until now are lost. I apologize profusely. I'll work on redoing existing commits including the DB migration ASAP.
More details are at #729
Re: @jscher2000:
Sorry that wasn't my intended goal to invoke that sort of response... it was to let you know of a lesser known route if you wanted to use it. I'm actually rather fond of your contributions and questions. :)
Re: @chacham:
It is a route (a.k.a. URI path) that @sizzle added in a while back.
If you want to only count new installs then yes by all means publish with that. :)
It could... however some authors like to control where the updates come from with consolidation to one site or another. I usually suggest leaving it blank and let the .user.js engines handle it from wherever it is installed but some people still run older versions that don't support those metadata keys automagically.
Your UserScript metadata block code at:
// @updateURL https://openuserjs.org/scripts/Nindel/Ice_Apple_Auto_Eater?c // @downloadURL https://openuserjs.org/scripts/Nindel/Ice_Apple_Auto_Eater?cshouldn't be trying to tell the userscript engines to check for updates from a web page and install the script source from a web page. Please correct to use the .user.js and .meta.js, or preferably omit these keys, with:
// @updateURL https://openuserjs.org/meta/Nindel/Ice_Apple_Auto_Eater.meta.js // @downloadURL https://openuserjs.org/install/Nindel/Ice_Apple_Auto_Eater.user.jsYou appear to have this issue in another of your scripts as well with other hosting sites that don't seem to exist anymore... which is why ideally you should just omit them.
Thanks.