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: @Fironet:
Hmm perhaps GH is having some growing pains too.
Getting this on a differently hosted script of mine. :\
Re: @Fironet:
That is peculiar. What GM version are you running? Are you Add-ons (Extensions) updating? Did you try in a clean profile to make sure it's not profile corruption? Do you have the version value in your config.xml for that particular script? Once you find this in your config.xml you can shutdown Fx, edit and save that value to an earlier version number, restart Fx and do a manual check to see if the Greasemonkey Updater (GMU) via the Add-on Updater (AOU) is working for any script. Is secure updates on or off in GM? Since it's an .io page on GH it may be misconfigured... although seems to be okay here. Are you running a proxy or a piece of software that might be filtering the checks out?
Re: @mrsweety:
If it was on USO you can possibly nab it from the mirror backup.
Related commits:
75372b2
Still non-functional. If I need to I'll create a slavestep2 branch without these. Still pondering.
Re: @Fironet:
Check about:config?filter=extensions.update.interval for your setting. The default is once a day with
86400
seconds. You can always do a manual check in about:addons too and see if it appears or updates. Occasionally GM needs a browser restart for an intermittent bug that comes and goes over Fx versions to show the version number correctly.Welcome. :)
Re: @Fironet:
The current metadata block contains these keys:
// @updateURL https://yeppha.github.io/downloads/YouTubeCenter.meta.js // @downloadURL https://yeppha.github.io/downloads/YouTubeCenter.user.js
... which is not OpenUserJS (OUJS)... assuming you are using a user.js engine that is capable of updating with these keys. The automatic meta routine here on OUJS is routinely tested just about daily. It is currently working for me with Fx + GM... so look to your user.js engine or the referenced site for downtime/bugs. :)
Re: @kukuhaku:
Should be right below the caption under the video. Says "Auto-Buffer Options" for me.
Re: @Sebastian_Pohl:
Not implemented yet. See OpenUserJs/OpenUserJS.org#108.
Re: @trespassersW:
That's enough trespassersW.
Welcome. Wish I had better news for you. :)
Re: @TimidScript:
Probably not... see v2.0 requirements at goo translate api
Please don't obfuscate your code. This is currently prohibited.
You and/or your script has become eligible for removal.
Please don't obfuscate your code. This is currently prohibited.
You and/or your script has become eligible for removal.
Please don't obfuscate your code. This is currently prohibited.
You and/or your script has become eligible for removal.
Please don't obfuscate your code. This is currently prohibited.
You and/or your script has become eligible for removal.
Re: @trespassersW:
Sure there is... it's called the rating.
More query options will be available at a future date.
Re: @trespassersW:
Can be. The Categories column also has a dependency issue about being modified for sorting so not sure what will be done which is why I said "One of many" because I know there will probably be more. Btw what is "next css" ??
Re: @trespassersW:
Thanks for the report. We do have a few issues open now here and here for this. In the middle of a refactor that is delaying things until they get finished. You can try out the rule set in the pr at this user.js script for the time being.
Re: @Marti:
Btw when I'm goo this is what I use currently.
Re: @jscher2000:
One feature at a time... watching/favoriting/liking or whatever terminology will be used will come eventually. Patience Sir Jefferson. :)
Re: @jscher2000:
This was already answered by me a while back. People might try it out... might not work for them for whatever reason without reporting it or liking it. IDK... may be referenced offsite somewhere too. You will never get 100% accurate stats. I test the meta routine daily with install counts as it's part of my Admin responsibilities. Older GMs don't support the request header. Shared IPs in (proxies) in foreign lands... dynamic IPs... short urls... the list goes on and on and on and on. :)
Target url with obfuscated code:
http://goo.gl/ey9wq7
Please don't obfuscate your code. This is currently prohibited.
You and/or your script has become eligible for removal.
This is your only warning.
Please don't obfuscate your code. This is currently prohibited.
You and/or your script has become eligible for removal.
SeaMonkey (SM) users heads up for Greasemonkey Port (GM Port)
I had to cherry pick up to the current greasemonkey/greasemonkey@
4ea165f
and omit the following commits during testing:0a7d8e
fails in SeaMonkey Mozilla/5.0 (X11; Linux x86_64; rv:29.0) Gecko/20100101 Firefox/29.0 SeaMonkey/2.265dc3eb
is a reverse dependency of 0a7d8eAffected issue ticket is greasemonkey/greasemonkey#1937
Author reported Step to Reproduce (STR):
What this may mean:
What this ultimately means since I am the remaining maintainer of GM Port, since Philip seems to have gone off the GM map, is that rather than pollute the slavestep branch with a strong veer of a major GM API method... I am going to wait and see what happens. It is possible to cherry pick all the other commits for 2.1beta1 and they seem to check out okay in SeaMonkey.
Please remember to try things out in Firefox + Greasemonkey (optionally on SourceForge) and if they don't work report on GitHub GM. I am always paying attention for GM Port and will try, as much as possible, any clear STRs for SM.
Please don't obfuscate your code. This is currently prohibited.
You and/or your script has become eligible for removal.